I'm trying to find out if there is a way to test Outlook (2010) connectivity to Exchange 2013 prior to moving to a co-existence state.  OWA tests out great, all certs are in and VD's/Outlook anywhere is configured on the 2013 system (NTLM authentication). I have configured the local machines hosts file to point to the autodiscover address of my 2013 CAS server.  I can communicate to the autodiscover service properly through IE receiving ErrorCode 600.  

I changed the SCP of my 2013 CAS Server to https://autodiscover.domain.com/autodiscover/autodiscover.xml - doing so did not allow outlook to connect - I received a prompt for credentials as well as error: outlook is unable to connect to the proxy server. (error code 0).  Entering credentials didn't work.

I've since changed the SCP to point to that of the 2007 Exchange server as users we're complaining they couldn't connect.

I've tried multiple avenues of manually setting up outlook with no success.  Outlook seems to be getting some settings properly as after I cancel the authentication prompt it shows me the GUID@domain.org as the exchange server its attempting to connect to.  

Further information:

Single 2007 SP3 Rollup 11 Exchange server, Server 2003 R2

Single 2013 SP1 CAS, Server 2012 R2 (fully updated 2 weeks ago)

Single 2013 SP1 MBX, Server 2012 R2 (fully updated 2 weeks ago)

Outlook 2010 SP2

Thank you.

Hi!

We are installing a new Exchange 2010 on a Windows 2008 R2 Server to migrate from Exchange 2003 to 2010. Is there any specific procedure we have to follow to install Exchange 2010 SP3 after installing Exchange 2010 or we can directly run SP3 setup?

Thanks.

Hi Everyone, I have 2 send connectors and 4 receive connectors configured on exchange server 2007.How do i know which send or receive connector i am using for my exchange 2007.I am doing the transition to exchange server 2013. If i  create a new send and receive connector in exchange 2013 without looking back to exchange 2007 will i face any issue.Do guide me how to create it in exchange 2013.

Hi!

Is there a limit to move Exchange 2003 to 2010 mailboxes for move request? What are the recommendations? How many mailboxes we can select for one move request?

Thanks.

I try to migrate mailboxes between two Exchange organizations. 

Source have Exchange 2007 Sp3 and AD on Windows 2008 R2.

Destination has Exchange 2013 Cu3 on Windows Server 2013. Ad on this forest is 2012.

Source AD is: contoso.com

Destination is: fabrikam.com

Trust: $false

.\Prepare-Movereguest runs without any problems.

Its no trus between the forests

No traffic is blocked by FW

I have used this article http://blogs.technet.com/b/exchange/archive/2010/08/10/3410619.aspx

- EventData

   New-MoveRequest
   {RemoteLegacy=True, Identity=User01, RemoteCredential=System.Management.Automation.PSCredential, SuspendWhenReadyToComplete=True, TargetDatabase=Users01, TargetDeliveryDomain=fabrikam.com, BadItemLimit=100, RemoteGlobalCatalog=azrad01.contoso.com, AcceptLargeDataLoss=True}
   fabrikam.com/Users/ivarasen
   S-1-5-21-4127437306-2113419879-3149575443-500
   S-1-5-21-4127437306-2113419879-3149575443-500
   Remote-ManagementShell-Unknown
   9176 w3wp#MSExchangePowerShellAppPool
   
   25
   00:00:00
   View Entire Forest: 'False', Default Scope: 'fabrikam.com', Configuration Domain Controller: 'Azrad02.fabrikam.com', Preferred Global Catalog: 'Azrad02.fabrikam.com', Preferred Domain Controllers: '{ Azrad02.fabrikam.com }'
   Microsoft.Exchange.MailboxReplicationService.TimeoutErrorTransientException: The call to 'net.tcp://azrex01.fabrikam.com/Microsoft.Exchange.MailboxReplicationService AzrEx01.fabrikam.com (15.0.775.35 caps:3F)' timed out. Error details: This request operation sent to net.tcp://azrex01.fabrikam.com/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. ---> System.TimeoutException: This request operation sent to net.tcp://azrex01.fabrikam.com/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. Server stack trace: at System.ServiceModel.Dispatcher.DuplexChannelBinder.Request(Message message, TimeSpan timeout) at System.ServiceModel.Channels.ServiceChannel.Call(String action, Boolean oneway, ProxyOperationRuntime operation, Object[] ins, Object[] outs, TimeSpan timeout) at System.ServiceModel.Channels.ServiceChannelProxy.InvokeService(IMethodCallMessage methodCall, ProxyOperationRuntime operation) at System.ServiceModel.Channels.ServiceChannelProxy.Invoke(IMessage message) Exception rethrown at [0]: at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg) at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type) at Microsoft.Exchange.MailboxReplicationService.IMailboxReplicationService.GetMailboxInformation3(Guid primaryMailboxGuid, Guid physicalMailboxGuid, Byte[] partitionHint, Guid targetMdbGuid, String targetMdbName, String remoteHostName, String remoteOrgName, String remoteDCName, String username, String password, String domain) at Microsoft.Exchange.MailboxReplicationService.MailboxReplicationServiceClient.<>c__DisplayClassa.<GetMailboxInformation>b__9() at Microsoft.Exchange.MailboxReplicationService.CommonUtils.CallWCFService[ExceptionT](Action serviceCall, String epAddress, Action`1 faultHandler, VersionInformation serverVersion) --- End of inner exception stack trace --- at Microsoft.Exchange.MailboxReplicationService.CommonUtils.CallWCFService[ExceptionT](Action serviceCall, String epAddress, Action`1 faultHandler, VersionInformation serverVersion) at Microsoft.Exchange.MailboxReplicationService.CommonUtils.CallService(Action serviceCall, String epAddress, VersionInformation serverVersion) at Microsoft.Exchange.MailboxReplicationService.MailboxReplicationServiceClient.GetMailboxInformation(Guid primaryMailboxGuid, Guid physicalMailboxGuid, TenantPartitionHint partitionHint, Guid targetMdbGuid, String targetMdbName, String remoteHostName, String remoteOrgName, String remoteDCName, NetworkCredential cred) at Microsoft.Exchange.Management.RecipientTasks.NewMoveRequest.RetrieveSourceMailboxesInfo() at Microsoft.Exchange.Management.RecipientTasks.NewMoveRequest.InternalValidate() at Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__8() at Microsoft.Exchange.Configuration.Core.LatencyTrackerExtension.StartAndEndInternalTracking(LatencyTracker latencyTracker, String groupName, String funcName, Boolean logDetailsAlways, Action action) at Microsoft.Exchange.Configuration.Core.CmdletLatencyTracker.StartAndEndInternalTracking(Guid cmdletUniqueId, String groupName, String funcName, Boolean logDetailsAlways, Action action) at Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__7()
   ServerTransient
   System.TimeoutException: This request operation sent to net.tcp://azrex01.fabrikam.com/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. Server stack trace: at System.ServiceModel.Dispatcher.DuplexChannelBinder.Request(Message message, TimeSpan timeout) at System.ServiceModel.Channels.ServiceChannel.Call(String action, Boolean oneway, ProxyOperationRuntime operation, Object[] ins, Object[] outs, TimeSpan timeout) at System.ServiceModel.Channels.ServiceChannelProxy.InvokeService(IMethodCallMessage methodCall, ProxyOperationRuntime operation) at System.ServiceModel.Channels.ServiceChannelProxy.Invoke(IMessage message) Exception rethrown at [0]: at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg) at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type) at Microsoft.Exchange.MailboxReplicationService.IMailboxReplicationService.GetMailboxInformation3(Guid primaryMailboxGuid, Guid physicalMailboxGuid, Byte[] partitionHint, Guid targetMdbGuid, String targetMdbName, String remoteHostName, String remoteOrgName, String remoteDCName, String username, String password, String domain) at Microsoft.Exchange.MailboxReplicationService.MailboxReplicationServiceClient.<>c__DisplayClassa.<GetMailboxInformation>b__9() at Microsoft.Exchange.MailboxReplicationService.CommonUtils.CallWCFService[ExceptionT](Action serviceCall, String epAddress, Action`1 faultHandler, VersionInformation serverVersion)
   ExAA9BE9

Best Regards

Rinken

Rinken

We are in the middle of a migration and am noticing that if a user has an Exchange 2013 mail account, if they open outlook for the first time it will not work.  We have it set so the default outlook profile pulls the user ID and tries to resolve the mailbox by that user ID.  That works fine if user is on Exchange 2k7 but if they are on 2k13 we cannot resolve the mailbox by user ID we have to type in their display name.  Is that by design?

 I know its easy enough to just create a new profile  but it was nice when the user got a  newly image machine they could just open outlook and because we had the default profile settings set everything just loaded up with no input from the user at all.  But if Exchange 2013 wont allow you to resolve the mailbox by user ID, then this isnt going to work.  

I've mostly completed a successful coexistence/migration from EX2010 to EX2013 for a small test-environment.

One of the issues that I'm quite puzzled with is when configuring an Outlook client using AutoDiscover.  Instead of the expected local FQDN of the CAS, the 'Server-name' gets populated with what looks like a GUID(f8a4ed0f-24c1-487f-7709-1031ed808516@[mail.EXT-FQDN.com]) and the proxy-addresses get populated with *internal* DNS-names([svr-FQDN.local]/msstd:[svr-FQDN.local]).

I have to manually change the proxy addresses, and then the Outlook client works just fine...even with the existing strange GUID-looking server-name in place.

I've verified that the OutlookAnywhere settings in ECP contain the correct FQDN's for both external & internal host-names...I even changed them both to be external FQDN's since I have split-brain DNS in-place thinking that might help the cause.

thanks in advance for any/all insight to this odd little problem,

~~Rob

thx, ~~Robb

Hi,

We have a client who were running the following setup:

2 x Exchange 2013 CU2 CAS servers / Win Srv 2012

2 x Exchange 2013 CU2 MBX servers / Win Srv 2012

Active Directory etc, basically everything else, runs on Win Server 2012.

Due to upgrading etc, one of the mailbox servers has been removed. It is to be installed with Ex2013 SP1 with 2012 R2 from scratch, and eventually also upgrade the remaining CAS and MBX srvers with SP1 and 2012 R2.

So my question is..will this present a problem? Is it possible to have one MBX running 2013 CU2 on Server 2012 and one MBX running 2013 SP1 on Server 2012 R2?

I've read that failover clustering service is not possible between 2012 and 2012 R2, but i'm not sure how this effects Exchange.

Thanks for your time.

hey 

i have a problem to complete the pending request. when i tip in the destination and press on ok i get the following error: 

error 
A special Rpc error occurs on server Servername: The source data cannot be imported or the wrong password was specified. 

and i cant finde any error 

Hi all. 

I'm a bit lost, it's my first exchange 2013 install and my first coexistence scenario. So I need help. 

I've got an existing Exchange 2007 SP3 CU 12 organization, with 3 servers : 

- Server38 and Server39 as Mailbox Server, CCR Cluster, virtual node isServer40

- Server41 as CAS Server. 

I want to migrate everything to Exchagne 2013 SP1 on Windows 2012 R2. I have 2 servers : 

- Server12 and Server13 are Multirole servers, CAS ans MBX. I have configured a DAG. It's working. 

To provide HA on CAS service, I put this in order : http://exchangeserverpro.com/exchange-2013-client-access-server-high-availability/

Clearly, I want my CAS Server to be accessed with mail.domain.com instead of Server12.domain.com or Server13.domain.com

So I configure Outlook Anywhere like this : "Set-OutlookAnywhere -InternalHostname mail.domain.com -InternalClientsRequireSsl $false"

Now, I don't really imagine how I can use this platform during coexistence. 

I want to set users on my new servers, but autodiscover is configured in DNS to point Server41. 

Users can access to their mails via OWA and Outlook. 

How can I configure autodiscover? Must I change autodiscover record in DNS to point to new servers or should I let it on Server41? 
How will Outlook work when I migrate one user to the new servers? Will I have to change config? 

Thanks

Hi Guys,

Most probably I am going to deliver one project in nearest future, which included to move Mailboxes and mail data from Novel Group-wise to Exchange 2013. i want to know what should be the approach and what are the per-requisites that need to be consider to perform Migration steps in above scenario? please let me know how the mail-flow work to/from Group-wise to exchange 2013 and vice-verse. please suggest me some initial steps and URLs for this requirement. i want to be clarified logically before i suggest any solution on this to my customer.

step by step docs will be more helpful to achieve this goal..

Regards,

Aanand Singh

Hi folks. I've been reading quite a bit about cross-forest migrations, as I am about to perform one, and want to do a sanity check on my process and ask a few questions.

First some info:

- Ex2010 Source Forest and Ex2010 or Ex2013 Target Forest (we'll get back to why this is TBD).

- Two-way trust is configured and functioning. 2008 R2 Server is in Target forest For ADMT.

- Customer wants to keep existing SMTP domain

- Customer has numerous Send/Receive connectors to servers

- Public Folders exist in the Ex2010 Forest (which is why we're TBD on Target forest Exchange version).  We'll get back to the PFs.

- They have Lync in place. I am not involved with migrating the Lync environment. Another partner is doing so after we move Exchange services.

- About 100 mailboxes, so I am planning to move all mailboxes in one night.

Here is what I think I want to do:

- Build Exchange environment (UM server, two with all roles, DAG, certs, etc.)

- Build Internal Relay between each Org for the existing SMTP domain

- Build receive/send connectors to mirror old Org(they have a few). Make sure new Org servers have perms to send to SharePoint, etc. Gradually have senders change to send to new Org servers (since we have an Internal Relay, we can do this part slowly)

- Configure new Exchange Org to accept existing SMTP domain

- Change DNS/firewall to route inbound mail from smarthost to new Org

At this point, I believe mail flow will function and send emails to the old Exchange org. A good checkpoint to test. Let me know if I am missing anything here.

Once mail flow works, it should be time to migrate mailboxes. These are the steps I am considering:

- Verify the MRSProxy is enabled in the old Org

- Grant rights for all Exchange Admins in both Orgs

- Grant rights to the ADMT migration account to move mailboxes in both Orgs

Any rights I am missing?

- Run Prepare-MoveRequest script in the new Org to create MEUs.

- Use ADMT to migrate users.

QUESTION - Migrate the users and make MEUs or just set up Linked Mailboxes until later?

- Move mailboxes to new Exchange Org

QUESTION/THOUGHT At this point, assuming we aren't using Linked Mailboxes, we have MEUs and mail in the new Org. Will the source AD accounts still be enabled? Which credentials should users use when the log in as there are still resources in the old AD Forest they need to access? Essentially, I need some guidance on the user experience at this point.We don't plan to migrate PCs until a later date - likely after the Lync partner migrates/upgrades everything. Let me know if that's asking for trouble.

Now, Public Folders. From what I have read, there is no supported out-of-box method of moving PFs from Ex2010->Ex2013 cross-forest. I read that here: http://social.technet.microsoft.com/Forums/exchange/en-US/663f0dc3-a977-408a-93c7-94584fbefc62/public-folder-issue-cross-forest-migration-exchange-2010-to-2013?forum=exchangesvrdeploy

So, I see a few options.

- We migrate Ex2010->2010 (anyone have a cross-forest Public Folder migration process for this?), then upgrade/migrate accounts to Ex2013.

- We follow the steps on this blog: http://msexchangeguru.com/2013/04/18/exchange2013-public-folders/Will this work cross-forest?

- We buy a 3rd party tool.

- We 'leave behind' the Public Folders in Ex2010 and migrate them later. Is this even an option?

I think that's everything. I know this is a lot to put in one thread, so I appreciate any thoughts you've got.

Thanks!

So, I am having a hard time figuring out why I cant get into ECP. When I login, it throws the invalid password mumbo jumbo stuff. I look into the setup, everything is correct. I even went to the extent of reinstalling windows fresh with nothing on it and still get the same thing. I decided to dig deeper and I found this weird error with OAB in IIS. Can someone tell me exactly what I need to do to fix this? I believe it is causing me other issues such as exchange management shell access denied, etc.

Hi everyone.

I am migrate from Exchange 2010 (2008) to 2013 (2012). I had moved all user mailboxes and i was preparing to decomissioning 2010.

I follow this http://www.petenetlive.com/KB/Article/0000816.htm for last adjustment and migrate Public Folders and Arbitration and Archive mailboxes.

The next day, I try to use the Exchange Management Shell and I receive the following error :

VERBOSE: Connecting to
New-PSSession : [myserver.mydomain] Connecting to remote server failed with the following error message : Access is denied. 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
   New-PSSession : [ ] Connecting to remote server failed with the following error message + FullyQualifiedErrorId : AccessDenied,PSSessionOpenFailed

I follow this steps to fix it, http://www.networksteve.com/exchange/topic.php/Exchange_Management_Shell_fails_to_connect_to_Exchange_Server_20/?TopicId=39825&Posts=2

but problem don't fix and now I get this error:

VERBOSE: Connecting to myserver.mydomain.
New-PSSession : [myserver.mydomain] Connecting to remote server myserver.mydomain failed with the
following error message : The client cannot connect to the destination specified in the request. Verify that the
service on the destination is running and is accepting requests. Consult the logs and documentation for the
WS-Management service running on the destination, most commonly IIS or WinRM. If the destination is the WinRM service,
run the following command on the destination to analyze and configure the WinRM service: "winrm quickconfig". 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 : CannotConnect,PSSessionOpenFailed
VERBOSE: Connecting to myserver.mydomain.
New-PSSession : [myserver.mydomain] Connecting to remote server myserver.mydomain failed with the
following error message : The client cannot connect to the destination specified in the request. Verify that the
service on the destination is running and is accepting requests. Consult the logs and documentation for the
WS-Management service running on the destination, most commonly IIS or WinRM. If the destination is the WinRM service,
run the following command on the destination to analyze and configure the WinRM service: "winrm quickconfig". 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 : CannotConnect,PSSessionOpenFailed
VERBOSE: Connecting to oldmx.mydomain
VERBOSE: Connected to oldserver.mydomain.
[PS] C:\Windows\system32>

Is there any reason for have this problems after migrate Arbitration? And/Or Public folders?

Please help!!!

Thank you!

Error:
The following error was generated when "$error.Clear();
 Install-CannedRbacRoles -InvocationMode $RoleInstallationMode -DomainController $RoleDomainController

" was run: "Active Directory operation failed . This error is not retriable. Additional information: Access is denied.
Active directory response: 00000005: SecErr: DSID-031520B2, problem 4003 (INSUFF_ACCESS_RIGHTS), data 0
".

Hello,

We followed this blog post to migrate from Exchange 2007 to Exchange 2013:

http://blogs.technet.com/b/meamcs/archive/2013/07/25/part-1-step-by-step-exchange-2007-to-2013-migration.aspx

Before decommissioning Exchange 2007, we created a new user on the Exchange 2013 server using ECP and migrated an existing Exchange 2007 user using ECP.

Autodiscovery, Outlook Web Access and Active Sync are working fine.

However, we cannot open these two mailboxes in Outlook 2010 or 2013 on Windows 7.

When I add one of the mailboxes in Outlook, AutoDiscovery is working fine. However, Outlook then complains that "the action cannot be completed. the microsoft exchange address book was unable to log on to exchange."

When I do the same in Outlook with a user that is not yet migrated, the Mailbox is setup just fine.

Any idea?

Best regards,
Florian

So I've decided to start testing SSL offloading with Exchange 2013 SP1 now that it is supported. I have followed this guide: http://technet.microsoft.com/library/dn635115(EXCHG.150).aspx. It is fairly straightforward, remove the "Require SSL" option on the VDIRS and IISRESET.

To test, I load up http://CAS/OWA and it immediately redirects to HTTPS://CAS/OWA. I do not see why it is doing this or how to configure it otherwise. So while my server is accepting connections on port 80, it's just bouncing them over to 443. How do we disable this?

I checked the HTTP Redirect option on the VDIRs, which is not present. Also, I am going straight to the server, so there is not a device in front that is redirecting my requests. Any thoughts?

Thanks,

Brandon

We are attempting our final try at installing Exchange 2013 on a 2012 R2 server. It is a secondary DC on our small LAN. Domain replication and ADDS all running fine on this machine. When trying to install Exchange 2013 we get the following Prerequisite Analysis errors:

Global updates: This user account is not a member of Enterprise Admins. (it is. Enterprise admins, schema admins, domain admins)

Organization Management: Your must be a member of of Organization Management or Enterprise admins (it is a member)

You must use an account that's a member of the Organization Management role group to install or upgrade the first Mailbox Server Role... (it is an enterprise admin account.)

Client Access Role (same thing...user account is not a member of the Enterprise Admins...it is.)

Forest Function Level is not Server 2003 native or later. (both DC's are Server 2012 R2. Function level is Server 2012)

Either Active Directory doesn't exist or it can't be contacted. (Really? It's running on a 2012 DC!)

Can anyone explain what Exchange is not finding so I can fix this? Obviously none of these conditions actually exist so something else is preventing Exchange from installing properly.

We just installed Exchange Server 2013 with sp1 included. Everything is good except IE11 users don't get the premium OWA site. I know that this was fixed in CU3, but you can't install it because SP1 is supposed to contain all the fixes through CU3.

Does anyone have any idea?