Hello Forum

We have two Exchange servers coexisting together. A new 2013 and a old 2010.

Everything was setup with the help of the Exchange Deployment Assistant.

I have had alot of trouble with Outlook 2013 Prompting for credentials on Exchange 2013 Mailboxes. None of the 2010 Mailboxes expericence this popup.

I solved most of the popup issues with this by changing the ExternalClientAuthenticationMethod to ntlm.(from negotiate)
http://blog.gothamtg.com/2013/10/15/users-constantly-prompted-for-credentials-after-being-migrated-to-exchange-2013/

and installing this update for Outlook:
http://support2.microsoft.com/kb/2899504/en-us

Now 2013 Mailboxes Work without any anoying popups. Except when they try to open another users mailbox that is located on the old 2010 server or a shared 2010 calander.

The connection to Exchange 2010 is working if I input the users password, but should it not work without this popup too?

This connections name acording to Outlook is called: Exchange-Mail RPC/HTTP (remote [NTLM])

We use the same domain for external and internal autodiscover connections.
Test Exchange Connectivity Analyzer shows everything ok.

If i run

get-outlookanywhere | fl *external*

(2013 server)

ExternalHostname                   : webmail.domain.com
ExternalClientAuthenticationMethod : Ntlm
ExternalClientsRequireSsl          : True

(2010 server)
ExternalHostname                   : webmail.domain.com
ExternalClientAuthenticationMethod : Basic
ExternalClientsRequireSsl          : True  

Only one thing I am wondering here is. If I change my old 2010 Auth Method to NTLM if that will break anything i OWA and so on.

What do you Guys have setup in your environments and can you point me towards any troubleshooting?

Thanks!

Greetings!  We currently have an Exchange 2010 on prem environment and I have been tasked with getting us into a hybrid state with O365.  We already have the tenet portions set up, AD Sync working, etc.  My initial thought was to just use our existing Exchange 2010 servers for the hybrid role, however, upon research it appears that standing up new Exchange 2013 servers specifically as hybrid servers is the suggested route.

My main goal is to do this hybrid deployment with as little impact and change to our environment (and thus user impact) as possible.  From what I have read, I will have to change the autodiscover and ews records to point to the new Exchange 2013 servers.  Is it also the case that I will have to redirect OWA to the Exchange 2013 servers?  Is there any way to deploy Exchange 2013 hybrid servers in a way that I do not have to change owa, autodiscover, etc? 

Thanks in advance!

Followed https://technet.microsoft.com/en-us/library/ee861103(v=exchg.150).aspx to move mailboxes cross-forest between 2 EX2013 servers. Pull migration.

The moves pause for several hours at 99%, and ultimately complete with CompleteWithWarning status. So far, it happens every time. Occurs even with mailboxes created and immediately moved, so it is not a problem with specific, perhaps corrupt mailboxes.

Get-MailboxStatistics -IncludeMoveReport tells me this:

Warning: Unable to update Active Directory information for the source mailbox at the end of the move. Error details: Not connected.

There's a bi-directional forest & domain trust that appears to be working, cross-forest DNS works, and it's able to "connect" to AD in the remote forest for purposes of moving the mailbox, so I'm not sure why it's finding it's "Not connected" when it cleans up at the end.

After the move request goes from 99% to 100% (after a lengthy timeout), the source mailbox still exists, and both source and destination mailboxes can be logged on to. My understanding is that the user account in the source forest should be converted to a mail-enabled user.

I'm OK with troubleshooting and solving this if it's fast. But I'm also OK with writing a PowerShell script to post-process the user account in the source forest to get over the hurdle, since this is a one-time process...the source forest will ultimately go away.

So I'm guessing the script will be as simple as--

Disable-Mailbox someuser@domain.local

Enable-MailUser someuser@domain.local

Also, I'm not clear on whether this is relevant to the MEU, but inbound SMTP will continue to go to the source mail server until migration is complete, so the source server needs to redirect mail for moved mailboxes to the destination server. Both servers have the same external domain. I'm thinking this ends up being handled by a Transport Rule I can create in the same script, so the internal, secondary SMTP address stamped on the mailbox by Email Address Policies should do the job. But if there's something I need to include in Enable-MailUser, please advise.

Using Exchange 2013 (e2013), SP1.
Three locations.  (Let's say  Location-A, -B, and C.)
Each Location is an AD site, and physically "remote" from the others.
Each location will have one e2013 server,  each server running both CAS and Mailbox function.

The main location ( LOC-A) is where all external OWA and EAS will "enter" from the Internet, via a firewall.
The E2013 server there will "connect" (?) to the e2013 server for "this mailbox",...at any of the 3 locations.

What "special" configuration do we need on the 2 remote/other e2013 servers for OWA virtual directory (or similar).

It looked like it was working "out of the box".

Some users work OK, with no special changes to anything.

But some users have OWA in a "never ending wait" (browser appears to spin forever), 

and that might be due to a different Language at the other locations.

I guess Exchange knows how to "internally route" the OWA traffic from the LOC-A CAS to the LOC-B CAS.

(In Exchange 2007 we called this "Exchange CAS proxy" as I recall, but not sure that term is correct in e2013.)

Thanks.

==

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?

Hi everyone,

I have a single Exchange 2007 VM as well as 4 x Exchange 2013 SP1  servers in a single organisation. Exchange 2013 SP1 servers are also VM's, with 2 x CAS and 2 x MBX and a single DAG. All of these existing servers use a single namespace for CAS services of mail.domain.com. In public and internal DNS that name resolves to the IP address of the Exchange 2013 DAG IP.

I'm replacing the above 5 VM's with 4 physical servers running 2013 CU7. In the architecture I'm using IIS Application Request Routing (ARR) as a clustered load balancer and reverse proxy. This will be used for all HTTP(S) traffic. (OWA, RPC/HTTPS, OAB, Autodiscover etc.).

e.g. oa.domain.com (Outlook Anywhere), outlook.domain.com (OWA), oab.domain.com etc. A key point in this design is that Outlook Anywhere will go via the reverse proxy / load balancer,including internal traffic.

The new Exchange 2013 servers are in place, as is the load balancer / RP, databases created etc. At the minute the virtual directories for the new servers have their URL's / Hostnames set to the Exchange 2007 / existing Exchange 2013 single namespace. So Outlook Anywhere, OWA, ECP, OAB etc. all have their URL's / Hostnames pointing to mail.domain.com (which resolves to the DAG IP of the current / legacy Exchange 2013 environment).

The next steps are to get the CAS traffic flowing over the new Exchange servers - which is a case of setting the virtual directories for the relevant services to point to the new per-protocol namespaces. So I'll set OWA to usehttps://outlook.domain.com/OWA.

My question is.... Do I do this ONLY for the new Exchange servers, or should I also update the URL's that the existing Exchange 2013 / 2007 servers use? For example:

Current Settings

Old Exchange 2013 Server 1
External OWA Virtual Directory: https://mail.domain.com/OWA

Old Exchange 2007 Server:
External OWA Virtual Directory: https://mail.domain.com/OWA

New Exchange 2013 Server 1:
External OWA Virtual Directory: https://mail.domain.com/OWA

New Setting

External OWA Virtual Directory: https://outlook.domain.com/OWA

Question

I need to set the NEW Exchange 2013 servers External URL for the OWA Virtual Directory to behttps://outlook.domain.com/OWA. But do I need to set this on the existing / legacy Exchange 2007 and Exchange 2013 Servers also? Or do I leave them, migrate the databases and then decommission the servers in due course without worrying about updating the URL's and hostnames on them?

In particular, what do I do about Outlook Anywhere? Again, I need to update the Internal and External Hostnames for the RPC Virtual Directory to point to the new name - oa.domain.com - but do I set this only on the NEW servers, or on all servers?

Any help greatly appreciated.

Big thanks in advance!

Steve

Hi Everyone,

I'm hoping others on this forum have some thoughts on whether it is worthwhile deploying only the Exchange 2013 CAS role for the purposes of SMTP relay.

When using Exchange Online, most guides suggest installing the IIS virtual SMTP component in an environment if SMTP relay is required. This is simple enough, however Microsofts future plans for IIS vSMTP look uncertain.

So my question is, has anyone deployed only the Exchange 2013 CAS role in an environment solely for the purposes of SMTP relay?
One pitfall I'm thinking about is the autodiscover service. Once the CAS role is installed an AD SCP is created, so this could cause potential problems.

I'm not concerned about having to extend the AD schema, or the cost. It's the other technical bits :)

cheers!

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?

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

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!

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?

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,

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