I'm having autodiscover issues with the new Exchange 2013 server. I rechecked the authentication and its fine. I rechecked my certificate with SAL and it has autodiscover.mydomain.com in it. Services are assigned to the certificate.

However, when I run the remote test for outlook connectivity it states its having trouble with autodiscover.

My main domain used for all services is m1.mydomain.com and I have an A record out there on DNS servers on the internet. Do I need one also for the the autodiscover.domain.com?  The test states it cannot The Microsoft Connectivity Analyzer is attempting to test Autodiscover for mymailbox@domain.com  testing autodiscover failed.   The Autodiscover service couldn't be contacted successfully by any method.  Also all other tests failed. What am I missing? Do I need to configure the autodiscover area in virtual directories? Currently when I click on the wrench there is no information in there. None in the external address. is something suppose to be there?

Hey all,

I'm running Server 2012 R2 with all available updates installed and all Exchange prerequisites completed but when I go to install Exchange Server 2013 SP1 I get the error that my OS isn't supported even though it is. Any ideas?

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

https://arcserve.zendesk.com/hc/en-us/articles/201992659-Exchange-2013-Document-Level-Backup-fails-to-backup-n-mailboxes-Error-AE9609-A-necessary-Exchange-service-is-not-running-Please-start-the-related-service-on-the-Exchange-server-manually-

http://www.arcserve-knowledgebase.com/index.php?View=entry&EntryID=5481

https://arcserve.zendesk.com/hc/en-us/articles/202153889-AE9609-AE9603-AW9627-ErrErr-800000008004011d

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!!!

Dear Sir, 

         We recently finished installing Exchange 2013 and it has been working fine. However, we noticed that we cannot keep messages to both forwarding address and mailbox. We do not have the check box option in Delivery Options.

How do we fix or enable that the check box for Deliver message to both forwarding address and mailbox?

Thanks

Hi Everyone, 

   I've been having issues with clients connecting to an existing Exchange server (Getting login prompt- but not usual reason).  

We currently run Exchange 2010 with approx 200 mailboxes on the server.  Last night I renewed the certificate on the 2010 server (go daddy SAN cert, all ok) and added the cert to my new Exchange 2013 server.  I tested it with my account, and a test account approx 12 times, and had not login prompt when launching Outlook. All seemed ok, until this morning.....

This morning, most (not all) users are getting the login prompt.  We are able to get by this by inputting domain\username and Outlook opens fine and is able to connect.  No users are on the Exchange 2013 server yet (only 1 test account) 

I've been googling all morning and I'm not seeing anything directly relating to my issue.  I've read about the Anon vs Negotiate issues (KB2834139) - But - the strange thing is all clients are set to negotiate network security (And encrypt data) This is opposite of what the MS article says.  CLients are all Outlook 2010 

Here are my outlook anywhere settings: 

If I change the Exchange 2010 server to NTLM, will this resolve what I'm seeing? And do I need to restart RPC Client Access and Transport Service to make changes take effect? Or reboot the whole server? 

If you need more info or logs please let me know

Thank you for any help! 

-Jeff

Exchange 2013 SP1.  

Ran into this issue with my Exchange 2013 test environment.  Basically I have an "orphaned" mailbox that I am unable to delete because there is no AD object for the mailbox.  This is probably easy i just cant figure out how to remove it.  When I try "remove-storemailbox" it thows back the "operation couldnt be performed because the object "username" couldnt be found. 

Any ideas how I can remove this orphaned box?

thanks

*****************************************

Info on how I got here in case this is not an easy fix:

Deleted a particular user mailbox from EAC to free some room up.  I then wanted to purge the mailbox from the back end as it was still in database do to mailbox retention.

I then did the following to make sure it was disconnected and to get the GUID for removal:

Get-MailboxDatabase | Ge-MailboxStatistics | where { $_.Displayname "the user" } | fl DisplayName,Database,DisconnectReason,MailboxGuid

To my suprise It listed the mailbox as being in two databases.  The mailbox GUID was the same for both.  One of the databases (the users active database at time of deletion) was listed with disconnect reason as disabled as expected.  The other database has the disconnectedreason property as blank.

My guess is that this "dual database" happened during mailbox migration from Exchange 2007.  For this user, I do believe the migration failed initially to the first database (the one that is showing with no disconnectedreason) and I then had to fix the issue and restart the migration and it finished successfully to the second database.

I wrote this off and proceeded to purge the mailbox using the "remove-StoreMailbox -Identity "username" -MailboxState Disabled" command.

This removed the disconnected mailbox, however the other orphaned mailbox is still there!  Now I cant figure out how to remove this orphaned mailbox, because there is no longer an AD account associated with the mailbox and I run into the object couldnt be found error.

How can I get this mailbox removed?

I did a complete barebones install with all the prereq's on a Server 2012 and everything went fine until I actually tried to log into the Exchange Admin Website OR the PowerShell to manage Exchange.    Here is the error I get with Exchange Powershell:

VERBOSE: Connecting to exssrv.cas.local.
New-PSSession : [exssrv.cas.local] Processing data from remote server exssrv.cas.local failed with the following error
message: The WinRM Shell client cannot process the request. The shell handle passed to the WSMan Shell function is not
valid. The shell handle is valid only when WSManCreateShell function completes successfully. Change the request
including a valid shell handle and try again. For more information, see the about_Remote_Troubleshooting Help topic.
At line:1 char:1
+ New-PSSession -ConnectionURI "$connectionUri" -ConfigurationName Microsoft.Excha ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : OpenError: (System.Manageme....RemoteRunspace:RemoteRunspace) [New-PSSession], PSRemotin
   gTransportException
    + FullyQualifiedErrorId : -2144108212,PSSessionOpenFailed 

All the services come up fine and I AM able to get into OWA.    However ADMIN functions are beyond my reach.  When I try to log into the ECP as Administrator It takes me to OWA!   Event viewer has something weird in MS Exchange Management Log too: 

Now I have tried everything I think i could find.. I doublechecked the Administrator permissions in the Group policy and redirect stuff in IIS and even created a self signed Cert.   It gives me a login prompt when I try to go to the local ecp:  http://exssrv.cas.local:81/ecp/ HOWEVER it then just takes me to OWA.    Has anyone ever seen this?   I am willing to try anything and would really appreciate any suggestions from the Exchange Gurus. 

Thanks a million!

Recently, we moved Active Directory Certificate Services off of our exchange server and onto a dedicated ADCS box. We kept the same CA name, however the server name changed. After migrating the database and configuration from the old server to the new one, we are now getting the status 'Revocation check failed' with our exchange certificates. We are on Server 2012 R2 with Exchange 2013.

PKIView.msc:
CA Certificate = OK
AIA Location #1 = OK
CDP Location #1 = OK
DeltaCRL Location #1 = OK

Trying to update a new CU6 installation to CU7 and I can't get past this error.  Please help.

Exchange Server component Mailbox role: Transport service failed.

Error: Error:

The following error was generated when "$error.Clear();

          $feVdirName = "PowerShell (Default Web Site)";

          $beVdirName = "PowerShell (Exchange Back End)";

          $vdirName = "PowerShell";

          $InternalPowerShellUrl="http://" + $RoleFqdnOrName + "/powershell";

          get-PowerShellVirtualDirectory -ShowMailboxVirtualDirectories -server $RoleFqdnOrName -DomainController $RoleDomainController | where { $_.Name -eq $beVdirName -or $_.Name -eq $feVdirName } | remove-PowerShellVirtualDirectory -DomainController $RoleDomainController;

          new-PowerShellVirtualDirectory $vdirName -Role Mailbox -DomainController $RoleDomainController -BasicAuthentication:$false -WindowsAuthentication:$true -RequireSSL:$true -WebSiteName "Exchange Back End" -Path ($RoleInstallPath + "ClientAccess\PowerShell-Proxy");

          new-PowerShellVirtualDirectory $vdirName -Role Mailbox -InternalUrl $InternalPowerShellUrl -DomainController $RoleDomainController -BasicAuthentication:$false -WindowsAuthentication:$false -RequireSSL:$false -WebSiteName "Default Web Site" -AppPoolId "MSExchangePowerShellFrontEndAppPool";

        " was run: "System.ArgumentException: The virtual directory 'PowerShell' already exists under 'NSCCEx13.administration.nashvilletech.int/Exchange Back End'.

Parameter name: VirtualDirectoryName

   at Microsoft.Exchange.Configuration.Tasks.Task.WriteError(Exception exception, ErrorCategory category, Object target, Boolean reThrow, String helpUrl)

   at Microsoft.Exchange.Configuration.Tasks.Task.WriteError(Exception exception, ErrorCategory category, Object target)

   at Microsoft.Exchange.Management.SystemConfigurationTasks.NewExchangeVirtualDirectory`1.InternalValidate()

   at Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__b()

   at Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean terminatePipelineIfFailed)".

Error:

The following error was generated when "$error.Clear();

          $feVdirName = "PowerShell (Default Web Site)";

          $beVdirName = "PowerShell (Exchange Back End)";

          $vdirName = "PowerShell";

          $InternalPowerShellUrl="http://" + $RoleFqdnOrName + "/powershell";

          get-PowerShellVirtualDirectory -ShowMailboxVirtualDirectories -server $RoleFqdnOrName -DomainController $RoleDomainController | where { $_.Name -eq $beVdirName -or $_.Name -eq $feVdirName } | remove-PowerShellVirtualDirectory -DomainController $RoleDomainController;

          new-PowerShellVirtualDirectory $vdirName -Role Mailbox -DomainController $RoleDomainController -BasicAuthentication:$false -WindowsAuthentication:$true -RequireSSL:$true -WebSiteName "Exchange Back End" -Path ($RoleInstallPath + "ClientAccess\PowerShell-Proxy");

          new-PowerShellVirtualDirectory $vdirName -Role Mailbox -InternalUrl $InternalPowerShellUrl -DomainController $RoleDomainController -BasicAuthentication:$false -WindowsAuthentication:$false -RequireSSL:$false -WebSiteName "Default Web Site" -AppPoolId "MSExchangePowerShellFrontEndAppPool";

        " was run: "System.ArgumentException: The virtual directory 'PowerShell' already exists under 'NSCCEx13.administration.nashvilletech.int/Default Web Site'.

Parameter name: VirtualDirectoryName

   at Microsoft.Exchange.Configuration.Tasks.Task.WriteError(Exception exception, ErrorCategory category, Object target, Boolean reThrow, String helpUrl)

   at Microsoft.Exchange.Configuration.Tasks.Task.WriteError(Exception exception, ErrorCategory category, Object target)

   at Microsoft.Exchange.Management.SystemConfigurationTasks.NewExchangeVirtualDirectory`1.InternalValidate()

   at Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__b()

David

I am attempting to put in a 2013 server in an environment that has 2007. The pre-req check fails saying one of the edge servers is not on SP3, but it is.

When doing a get-exchangeserver |fl name,admindisplayversion, The internal servers all show 8.3.6

When I do the same thing on the edge server, it shows 8.2 (build 176.2) for itself. That is the only place it shows it is 8.2. Everywhere else, including exsetup, it shows the correct 8.3 version number. I can also see that SP3 RU14 is installed on the edge server.

I have a maintenance window to redo the edge subscription this weekend, however I'm not sure if that will fix anything, since it's the edge server that is not able to identify it's own installed version.

How can I get the AdminDisplayVersion on the Edge server to show the correct SP that is installed?

http://jaworskiblog.com

We've currently installed a new Exchange Server 2013 (NOC 1 internal corp mail behind firewall) however currently use an external  mail Server (NOC2) IMAP POP3/SMTP for clients to authenticate and download and relay (SMTP) their e-mail. I'm looking for advise on how to effectively maintain the current Server performing primary scanning/anti virus & RBl filtering and relay, post scanned e-mail to our internal corporate Exchange 2013 server.  Also, would like, if at all possible, best practices for over-all security hardening of IIS & Exchange.

Thank you in advance,

William

Dear All,

I migrated Exchange 2010 to Exchange 2013 but was facing lot of issues on Windows XP clients with Office 2007 SP3 with November update. XP clients machine were continuously prompted user name and password and some times windows 7 with Office 2007 SP3 with November update were also behaved like this. I googled alot but couldn't find any solutions.

Lastly decided to revert back to Exchange 2010, every thing went fine but again hurdles started on IMAP/POP3 clients that are not able to send email external domain but able to receive emails from external domains.

The other issue is in Exchange 2013 made some contacts which was deleted in Exchange 2013 but those contacts are now in GAL but couldn't find where these contacts are sit in and how to remove.

Kindly someone guide on those issues and specially on XP machine prompted username and password as I have to again migrate the users from Exchange 2010 to Exchange 2013.

Thanks,

Dear Sir,

Please help me to allocate space for exchange server 2010, or increase it.

Regards, Ravi Kumar

Hi,

I have the client tools (CU6) installed on one of my servers. I am trying to run the CU7 installation in order to update the server. As soon as setup finishes the Copying Files step I receive the following error message:

The Type Initializer for Microsoft.Exchange.Management.Powershell.CmdletConfigurationEntr (line is cut off)

threw an exception. Could not load file or assembly 'Microsoft.Exchange.MailboxLoadBalanceClient Version=15.0.0.0 (message is cut off).

Any ideas how to troubleshoot this?

Thanks,

I. Kinal

Hi,

We are in process of migrating from Exchange 2007 to Exchange 2013 Servers.

To meet the migration requirements we have changed the standard single name SSL certificate with UCC Certificate having multiple SAN values using the exchange 2013 EAC wizard. Later on we applied the same certificate to both Exchange 2013 and 2007 CAS servers.

Outlook Anywhere was enabled since long on exchange 2007 servers and was working fine till we made the certificate change. After we make the change of certificate given were the error message we started encountering:

Another change which we noticed were of Domain Controllers names in the same AD site as exchange getting added to VALID PORTS key under given HASH:

HKLM\Software\Microsoft\RPC\RPCProxy

As per my understanding Valid ports entry is populated with all the mailbox servers in organization only until unless we define DC there, which we never did until now. I can also see values for Exchange 2013 mailbox server there.

And now since Valid ports entry contains reference for domain controller i have to made following registry entry on my domain controllers to make it work :

On the Global Catalog servers: a REG_MULTI_SZ  entry needs to be created on each GC named NSPI interface protocol sequences at HKLM\System\CCS\Services\NTDS\Parameters\ and the value set to ncacn_http:6004

I have tried modifying the Valid Ports entry manually and removing the domain controllers reference from there but then my Outlook Anywhere doesn't work anymore. Yes i know that RPCConfigurator again populate the entry every 15 minutes and i can turn it off,i have tried that but no luck.

Result of the above change now my CAS is directly speaking for my domain controllers which earlier mailbox server was doing through DSPROXY.

Can anyone suggest me what is happening wrong here...given are the environment details:

2 CAS +HUB Exchange 2007 SP3 RU13 server on windows 2003 R2

Exchange 2007 Mailbox Server SP3 RU13 SCC on Windows 2003 R2

Exchange 2013  CU5  CAS + Mailbox Server on Windows 2012 R2

Windows 2003 AD with mix of 2008R2 DC.

Regards,

Vishal Malhan

Hello,

We started to notice that when we move a user from our legacy exchange 2007 to exchange 2013, the contact list appears twice for users.  I heard CU6 was suppose to fix this issue but we went ahead and downloaded the latest version and we are still seeing this.  Can anyone provide guidance on how to stop this for the remaining migrations?

Thanks

Trying to update a new CU6 installation to CU7 and I can't get past this error.  Please help.

Exchange Server component Mailbox role: Transport service failed.

Error: Error:

The following error was generated when "$error.Clear();

          $feVdirName = "PowerShell (Default Web Site)";

          $beVdirName = "PowerShell (Exchange Back End)";

          $vdirName = "PowerShell";

          $InternalPowerShellUrl="http://" + $RoleFqdnOrName + "/powershell";

          get-PowerShellVirtualDirectory -ShowMailboxVirtualDirectories -server $RoleFqdnOrName -DomainController $RoleDomainController | where { $_.Name -eq $beVdirName -or $_.Name -eq $feVdirName } | remove-PowerShellVirtualDirectory -DomainController $RoleDomainController;

          new-PowerShellVirtualDirectory $vdirName -Role Mailbox -DomainController $RoleDomainController -BasicAuthentication:$false -WindowsAuthentication:$true -RequireSSL:$true -WebSiteName "Exchange Back End" -Path ($RoleInstallPath + "ClientAccess\PowerShell-Proxy");

          new-PowerShellVirtualDirectory $vdirName -Role Mailbox -InternalUrl $InternalPowerShellUrl -DomainController $RoleDomainController -BasicAuthentication:$false -WindowsAuthentication:$false -RequireSSL:$false -WebSiteName "Default Web Site" -AppPoolId "MSExchangePowerShellFrontEndAppPool";

        " was run: "System.ArgumentException: The virtual directory 'PowerShell' already exists under 'NSCCEx13.administration.nashvilletech.int/Exchange Back End'.

Parameter name: VirtualDirectoryName

   at Microsoft.Exchange.Configuration.Tasks.Task.WriteError(Exception exception, ErrorCategory category, Object target, Boolean reThrow, String helpUrl)

   at Microsoft.Exchange.Configuration.Tasks.Task.WriteError(Exception exception, ErrorCategory category, Object target)

   at Microsoft.Exchange.Management.SystemConfigurationTasks.NewExchangeVirtualDirectory`1.InternalValidate()

   at Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__b()

   at Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean terminatePipelineIfFailed)".

Error:

The following error was generated when "$error.Clear();

          $feVdirName = "PowerShell (Default Web Site)";

          $beVdirName = "PowerShell (Exchange Back End)";

          $vdirName = "PowerShell";

          $InternalPowerShellUrl="http://" + $RoleFqdnOrName + "/powershell";

          get-PowerShellVirtualDirectory -ShowMailboxVirtualDirectories -server $RoleFqdnOrName -DomainController $RoleDomainController | where { $_.Name -eq $beVdirName -or $_.Name -eq $feVdirName } | remove-PowerShellVirtualDirectory -DomainController $RoleDomainController;

          new-PowerShellVirtualDirectory $vdirName -Role Mailbox -DomainController $RoleDomainController -BasicAuthentication:$false -WindowsAuthentication:$true -RequireSSL:$true -WebSiteName "Exchange Back End" -Path ($RoleInstallPath + "ClientAccess\PowerShell-Proxy");

          new-PowerShellVirtualDirectory $vdirName -Role Mailbox -InternalUrl $InternalPowerShellUrl -DomainController $RoleDomainController -BasicAuthentication:$false -WindowsAuthentication:$false -RequireSSL:$false -WebSiteName "Default Web Site" -AppPoolId "MSExchangePowerShellFrontEndAppPool";

        " was run: "System.ArgumentException: The virtual directory 'PowerShell' already exists under 'NSCCEx13.administration.nashvilletech.int/Default Web Site'.

Parameter name: VirtualDirectoryName

   at Microsoft.Exchange.Configuration.Tasks.Task.WriteError(Exception exception, ErrorCategory category, Object target, Boolean reThrow, String helpUrl)

   at Microsoft.Exchange.Configuration.Tasks.Task.WriteError(Exception exception, ErrorCategory category, Object target)

   at Microsoft.Exchange.Management.SystemConfigurationTasks.NewExchangeVirtualDirectory`1.InternalValidate()

   at Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__b()

David

Dear all,

We currently are running Windows Server 2003 DC's in a 2003 domain/forest functional level.

Also are running Exchange 2003 Enterprise SP2 and Exchange Sever 2010 + SP3 (DAG) in coexistance

We are planning on adding 2012 ADC to the domain and Promote windows 2012 ADC to DC and commission Windows 2003 DC.

by doing my environment picture will be ;

Domain Controller = windows 2012 Std

Exchange Server 2003 and Exchange Server 2010.

and in a month or so will be moving all Exchange Server 2003 users to Exchange Server 2010 this is the plan.

So, can any one help me with Standard practice for this.

TheAtulA

Dear All,

Last year, we migrated Exchange 2010 to Zimbra and found it was difficult to handle.

So we want to move back to Exchange 2013. Exchange 2013 and Zimbra may co-exist in our organization.

We will deploy two Exchange Server,CAS+Mailbox.

We are considering if put Exchange as the smarthost.

Anyone has idea?

Besides, is there any wonderful migration tool?

Xiu

Hey, I am back