Hi all,
not sure how I did it previously, but I am able to generate a usable certificate from my local CA server, which is standalone (not enterprise ver.).
I was trying to request for a new certificate for my exchange server currently but its mentioning not valid.
Is CA Standalone version not meant for Exchange servers? Due to parent/child domain we are not able to create enterprise CA in child domain, and we have no access to parent domain, using my AD account.
Thanks and Regards,
Low
Hi All,
I've been working on this issue for a while now, but haven't had any luck. I am missing the Autodiscover Virtual Directory in IIS. I have run the following command in Exchange Powershell...
New-AutodiscoverVirtualDirectory -Websitename "Default Web Site" -BasicAuthentication:$true -WindowsAuthentication:$true
Unfortunately, I am receiving this error...
The virtual directory 'Autodiscover' already exists under 'EXCHANGE.CORP.AD/Default Web Site'.
Parameter name: VirtualDirectoryName
+ CategoryInfo : InvalidArgument: (EXCHANGE\Autodiscover (Default Web Site):ADObjectId) [New-Autodiscover
VirtualDirectory], ArgumentException
+ FullyQualifiedErrorId : 779E2C6B,Microsoft.Exchange.Management.SystemConfigurationTasks.NewAutodiscoverVirtualDi
rectory
IIS does not show the directory. I have found several articles suggesting I should delete Autodiscover from the IIS Metabase, but there's no entry for Autodiscover found via IIS Metabase Explorer. Also, there's no entry regarding Autodiscover in...
C:\Windows\System32\inetsrv\config\applicationHost.config
Any suggestions are more than welcome.
Hello All,<u1:p></u1:p><o:p></o:p>
We have Exchange Server 2013 in my environment, and we have issue with Receive connector a scan to email, the technical support can configure the multi-function print device scan to email successful using Internal SMTP relay without any permission from the Exchange side.<u1:p></u1:p><o:p></o:p>
I Have the custom Received connector created before and also removed the default IP address range remote network settings.<u1:p></u1:p><o:p></o:p>
Any setting needs to check or to apply to prevent this type of scan to email , and only provide the permission to Multi-function print device or any device through the Exchange side.<o:p></o:p>
<u1:p>Thank you .</u1:p><o:p></o:p>
We are in an hybrid environment of Exchange OnPremises and Exchange Online and in the OnPremises environment we have cohexistence of Exchange 2010 and Exchange 2013.
As a backup solution we have CA Arcserve Backup, that allow us to make a backup in document level of the exchange 2013 mailboxes.
We still can´t do the backup document level. In the logs files from the ca agent installed in the server, we found some MAPI errors.
We followed all the articles bellow, but without success.
We had a remote support from CA and they told us that we are facing a problem on the Exchange Server.
We ran the Test-MapiConectivity that returns Success.
Below of the links, follow the logs, if someone could help-me to diagose the MAPI on Exchange 2013, I will be vary glad.
http://www.arcserve-knowledgebase.com/index.php?View=pdf&EntryID=4969
http://www.arcserve-knowledgebase.com/index.php?View=entry&EntryID=5481
https://communities.ca.com/thread/241692506
https://communities.ca.com/thread/241690757
http://arcserve-knowledgebase.com/index.php?View=entry&EntryID=2
http://arcserve-knowledgebase.com/index.php?View=entry&EntryID=1193
http://arcserve-knowledgebase.com/index.php?View=entry&EntryID=2522
http://arcserve-knowledgebase.com/index.php?View=pdf&EntryID=4600
https://arcserve.zendesk.com/hc/pt-br/requests/10740
<01/28/2015-17:36:16:852 TID:20ac>Begin MAPILogonEx() failed MAPICODE: 0
<01/28/2015-17:36:16:992 TID:20ac>End MAPILogonEx() failed MAPICODE: 0
<01/28/2015-17:36:17:08 TID:20ac>After MAPILogonEx() before call my failed MAPICODE: 0
Thanks in advance!
Fabio Martins MCDST/MCSA Brasil!!!
Fabio Martins MCDST/MCSA Brasil!!!
We have the following configuration in our Exchange 2007 environment.
Webmail.company.com, and an existing certificate.
We have purchased a new certificate with the following names;
Autodiscover.company.com
Legacy.company.com
I am stuck on how to configure Exchange 2013 with these two certificates.
I can’t get Outlook clients to authenticate if their mailbox is on the 2013 server, and I need some guidance in getting this to work.
New Certificate assigned to IIS--- with Autodiscover.company.com and a SAN of legacy.company.com, users get a certificate warning and then “The Connection to Microsoft Exchange is unavailable. Outlook must be online or connected to complete this action.” Outlook settings populate with the proper GUID of Exchange Server and Mailbox.
Webmail.company.com certificate assigned to IIS---users do not see a certificate warning but still cannot connect to a mailbox on 2013. “The Connection to Microsoft Exchange is unavailable. Outlook must be online or connected to complete this action.” Outlook settings populate with the proper GUID of Exchange Server and Mailbox.
Is it possible to maintain the webmail.company.com and the original certificate?
Or should we choose a new URL for 2013, say mail.company.com/owa andobtain a new certificate with mail.company.com and two SANs for autodiscover and legacy?
Thank You
I have a edge server 2010 and a mailbox using exchange 2013
On ecp : server> edge server i see status " Unlicensed "
on edge server i using : Set-ExchangeServer <edge_server> -ProductKey AAAA-AAAA-AAAA-AAAA
but result : WARNING: The Exchange server "edge_server" is already licensed
Help me please!
thanks and regards
Hello All,
I have Exchange server 2007. Hub & Cas in one hardware box and Mail box is running on another server. Now hub & Cas stopped working after a microsoft update. I would like to install Hub & Cas in another hardware box with old hostname and IP address.
After the installation, will I lose all mail boxes?
Regards
Tonio
Brannon Vaughan
As the title states, I am in the process of moving to Exchange 2013 from Exchange 2010.
This is a partially live upgrade and I want to ensure little to no downtime.
During the prerequisite check I get this message:
"Warning:
Setup will prepare the organization for Exchange 2013 by using 'Setup /PrepareAD'. No Exchange 2007 server roles have been detected in this topology. After this operation, you will not be able to install any Exchange 2007 servers."
As I stated, we do not have any 2007 Exchange servers, only a single 2010 server. This being my first 2013 Exchange install, I am not sure if this is a "point of no return" where it makes AD changes that will effect our current production network.
Any assistance would be greatly appreciated.
Thanks!
Hello All,
I have Exchange 2007 --- One Hub & CAS and another mail box server. Plast 7 years it never given me any trouble. Past two weeks mails are not going to outside domain and it is in the queue. I am able to receive and even able to send/receive within the domain.
I checked SMTP send connector, space, re-installed Hub & Cas, Disable firewall, AV etc...
After doing all these also, it is in the same situation.
Can someone help me?
Tonio
Hello,
I am trying to migrate cross-forest from SBS2008 to Exchange 2013.
I'm stuck on running the move-request as it throws up a MRSProxy error, saying "failed because no service was listening on the specified endpoint" then 404 error.
I'm running the move request from the 2013 server and it appears it's trying to use the MRSProxy service to connect to the 2007 mailbox, which doesn't appear available.
Does anyone know if this is possible and able to point me in the right direction?
I've done this before but from 2010 to 2013 and it worked fine, but this time since it's 2007, it seems I can't because MRSProxy was only introduced in 2010. I was hoping to use this guide here.. at step 8 (can't do forest trust since it's SBS)
http://careexchange.in/cross-forest-migration-guide-exchange-2010-to-exchange-2010/
Thanks
Miles
Hi ,
I am currently testing a cross forest migration from exchange 2007 to exchange 2013. i do not have trust between my forest but i did set up conditional forwarding in both the source and target environment.
The Mailbox replication service does not behave as expected when i submit a new move request.
the move request : New-MoveRequest -Identity "f2867850-5e88-4f97-9efb-0b867a1fdb4b" -BadItemLimit "10" -TargetDeliveryDomain "TargetDomain" -TargetDatabase "{cbc90e5e-6124-458c-8105-464bc27d26c1}" -RemoteCredential (Get-Credential "sourcecredential") -RemoteGlobalCatalog "FQDN of source GC" -RemoteLegacy:$true
the error : "The call to 'net.tcp://SERVERNAME/Microsoft.Exchange.MailboxReplicationService SERVERNAME (15.0.775.35 caps:3F)' timed out. Error details: This request operation sent to net.tcp://SERVERNAME/Microsoft.Exchange.MailboxReplicationService
did not receive a reply within the configured timeout (00:01:00). The time allotted to this operation may have been a portion of a longer timeout. This may be because the service is still processing the operation or because the service was unable to send a
reply message. Please consider increasing the operation timeout (by casting the channel/proxy to IContextChannel and setting the OperationTimeout property) and ensure that the service is able to connect to the client."
I can ping both global catalog in the source environment and in the target from both side. nslookup and autodiscover is working as well.
MRS Proxy is enable on the exchange 2013 side and i have enable remote Powershell on both side.
i do not have any load balancer configure.
If anyone can point me in the right direction where to look it would be greatly appreciated.
thanks you
Frédéric Bédard
Regards, Noval
I seek opportunity
Hello Guy's,
I have a question about 1 of my costumers. It has a DC/Forest and 1 I'm gonna create. So in total it will be 2.
I want to make a trust between the domains but is it possible to use 2 domains on 1 exchange server. Its for a company and its sister firm, but it needs to be connected to each other and 1 exchange server.
With kind regards,
Vincent
Hi all,
I am process of migrating Exchange 2010 to Exchange 2013. Co-existence is setup and mailbox movement is in progress.
Currently there are multiple dynamic distribution group exists on Exchange 2010. what is the appropriate way to migrate them to Exchange 2013 ? . When I see the information of these DDG's using exchange shell I see that ExchangeVersion value is "0.1 (8.0.535.0)" that means Exchange 2007. Also "AddressListMembership" value of these dynamic distribution groups is showing "{\Default Global Address List}" which is Exchange 2007/exchange 2010 GAL which will be removed once we uninstall source Exchange 2010 server from the environment.
I am handling only the migration part of this client and not aware of the history of this environment. Can anyone tell me if I can migrate these dynamic distribution groups to Exchange 2013 server or do I need to create new DDG on Exchange 2013 same as the old ones ?
As we plan to upgrade our Exchange 2013 SP1 (CU4) to CU9, we also planned to update the .NET Framework to 4.5.2 (so we could use MAPI/HTTP, etc.).
Exchange 2013 is running on Windows 2012 Standard (not R2).
Now we see that .NET Framework 4.6 is available.
Has Microsoft verified that 4.6 will work well with CU9 ?
On the Exchange 2013 CU9 servers, should we use .NET Framework 4.6 ?
Thanks
==
Hi Just looking over Hybrid Deployment for one of our customers Just a have a quick questions
1) My customer currently has 1 x CAS and 2 x MBX servers for hybrid deployment i was reading and i need the cas to have the mailbox role on it correct? If that is the case i can create a new CAS server and add the mailbox role would be the easiest method. Please correct me if i am wrong
Thanks in advance for the answers and comments
Hi,
I have Exchange 2010 DAG and CASHUB severs in site A. I need to them to site B, where most of users reside. I plan to install in site B new multirole servers and switch existing databases to them using database portability fuctionality. I changed URL's in every Exchange services (EWS, Outlook Anywhere) to redirect connections to new servers in site B. Unfortunately I came to a stop at changing a site in exitisting CAS Array. In Outlook connection status I see connections to old CAS servers in site A, but netstat command shows connections to new servers in site B. I didn't change FQDN od CAS Array, just site.
As article http://blogs.technet.com/b/exchange/archive/2012/03/28/demystifying-the-cas-array-object-part-2.aspx says in point 5 changing FQDN od CAS Arrays makes trouble for Outlook, so apparently similiar problem is even if you don't change FQDN of CAS Array, but just site parameter.
The question is how to obey this obstacle in enterprise scale? (the right way)
If I plan to move existing databases to new servers in site B via database portability - should I do it before or after changing CAS Array?
I just performed a fresh install of Exchange 2013 w/ SP1 on Windows 2012 Standard R2 which is also a domain controller in an organization that already has an Exchange 2010 server (on a separate server). When I launch the Exchange Management Shell and attempt to run "Get-ExchangeServer" I get the error "The term 'Get-ExchangeServer' is not recognized as the name of a cmdlet, function, script file, or operable program..." I see that \\HKLM\SOFTWARE\Microsoft\PowerShell\1\PowerShellSnapIns\Microsoft.Exchange.Management.PowerShell.SnapIn is loading the module name "D:\Program Files\Microsoft\Exchange\bin\Microsoft.Exchange.PowerShell.Configuration.dll" (which is the correct path to that file).
I've restarted the server twice and have the same issue. Also tried doing an unattended install of just the Managment Tools since using the setup GUI didn't give me the option of uninstalling and reinstalling the Management Tools since the checkbox is greyed out. I searched the ExchangeSetup log for errors and didn't find any.
How do I get the Exchange Management Shell to register the Exchange Powershell commands? Do I need to uninstall Exchange and Re-Install?