I am migrating from Exchange 2007 to O365 via Exchange 2013 Hybrid.  The Exchange 2013 install was successful, the Hybrid Configuration was successful.

Most mailboxes still exist on Exchange 2007.  Some test ones are located on Exchange 2013, and we have migrated several over to O365.  All of these have worked with no issues.

OWA and OWA redirect to legacy works, A/S works.

During the build of Exchange 2013, the virtual directories were set to the well-know URL (mail.xxx.com)  The Exchange 2007 server virtual directories were set to legacy.xxx.com.

Free/Busy from O365 to Exchange 2013 mailboxes (and Exchange 2013 to O365) work perfectly.

Free/Busy from Exchange 2013 to Exchange 2007 mailboxes get the "hash marks" for free/busy

Free/Busy from O365 to Exchange 2007 mailboxes get the "hash marks" for free/busy

Free/Busy from Exchange 2007 to both Exchange 2013 and O365 work correctly.

I ran the Free/Busy tool from Test Exchange Connectivity and got this error from ANY mailbox querying against Exchange 2007.

Thanks in advance...

Hello All,

I need a bit of help.  I took over a network that was running Small Business Server 2008 with Exchange installed.  I bought a new Dell and virtualized three servers.  One of my virtual servers has Windows Server 2012 and Exchange 2013. After I installed Exchange 2013, I went to migrate some mailboxes from the Exchange 2007 machine (SBS).  When I did, the test mailboxes moved but would not open in outlook. The mailboxes that I need to move are huge and the test box wasn't.

I contacted Microsoft and we could not figure it out.  So I just left all the mailboxes on the SBS Exchange 2007 system. I would like to remove the .VHD that has Exchange 2013 on it.  I am going to virtualize the SBS and then reformat the server that the SBS resides on.  I would then like to install 2012 R2 and Exchange 2007 on that server to migrate the mailboxes and kill the SBS virtual server.

First - Is this even possible?

Second - Can I kill the Exchange 2013 .vhd without any issues?

I don't know if Exchange 2013 has been improved and I should try it again but I am a bit gun shy now.  Any advice or help would be greatly appreciated.

Thanks

Will

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

I was just wondering if anyone has stumbled upon any good "how-to" sites for those of us that (up to now) have been used to using SBS servers but now find ourselves needing to go the manual route with separate new servers (domain controller and Exchange 2013 server)?

I'm trudging along with my first Server 2012 R2 and Exchange 2013 SP1 installation and configuration, but since I'm used to things configuring themselves in SBS, the piecemeal approach to 2013 is presenting challenges for me.  

Considering the market for SBS is small business (and for me, typical 20 users), I'm looking for some direction and help in configuring these new servers to act like SBS 2011 replacement servers, with similar capabilites, etc...from the viewpoint of an SBS administrator, per se.

Maybe nothing exists and we have to start from scratch, but I was hoping with as big as the SBS market was, there would be some useful info out there with the realization that we're coming from SBS.

Thanks.

I'm following the procedure as per this Microsoft article:

http://technet.microsoft.com/en-us/library/jj150486(v=exchg.150).aspx

However at the New-PublicFolderMigrationRequest step (step 5 - migrate Exchange 2010 folders)  I'm getting the error at bottom.  Anybody know what could be causing this?  It certainly seems to be able to access ATLAS.  I've tried using atlas.es.tv, tried using just the name of the PF DB, nothing works.

[PS] C:\Windows\system32>New-PublicFolderMigrationRequest -SourceDatabase (Get-PublicFolderDatabase -Server ATLAS) -CSVD
ata (Get-Content "C:\PFscripts\foldermailbox.csv" -Encoding Byte)
MapiExceptionLogonFailed: Unable to make connection to the server. (hr=0x80040111, ec=-2147221231)
Diagnostic context:
    Lid: 49064   dwParam: 0x1
    Lid: 37288   StoreEc: 0x6AB
    Lid: 49064   dwParam: 0x2
    Lid: 49191   EMSMDBMT.EcDoConnectEx called [length=191]
    Lid: 48679   EMSMDBMT.EcDoConnectEx returned [ec=0x80040111][length=56][latency=0]
    Lid: 45169   StoreEc: 0x80040111
    Lid: 50544   ClientVersion: 15.0.913.22
    Lid: 52080   StoreEc: 0x80040111
    Lid: 1494    ---- Remote Context Beg ----
    Lid: 22086
    Lid: 27206
    Lid: 39869
    Lid: 56893   StoreEc: 0x8004010F
    Lid: 44989
    Lid: 24684
    Lid: 20076   StoreEc: 0x80040111
    Lid: 29100
    Lid: 20396   StoreEc: 0x80040111
    Lid: 9486    StoreEc: 0x80040111
    Lid: 24492
    Lid: 18348   StoreEc: 0x80040111
    Lid: 26540   dwParam: 0xE0003
    Lid: 22444   dwParam: 0xC30001
    Lid: 1750    ---- Remote Context End ----
    Lid: 51152
    Lid: 52465   StoreEc: 0x80040111
    Lid: 60065
    Lid: 33777   StoreEc: 0x80040111
    Lid: 59805
    Lid: 52487   StoreEc: 0x80040111
    Lid: 19778
    Lid: 27970   StoreEc: 0x80040111
    Lid: 17730
    Lid: 25922   StoreEc: 0x80040111
    + CategoryInfo          : NotSpecified: (:) [New-PublicFolderMigrationRequest], RemoteTransientException
    + FullyQualifiedErrorId : [Server=MB2-2013,RequestId=2dcefa76-98ad-4a2e-bb33-237d7fd795fd,TimeStamp=10/23/2014 7:1
   7:17 PM] [FailureCategory=Cmdlet-RemoteTransientException] 4A6EEF8C,Microsoft.Exchange.Management.RecipientTasks.N
  ewPublicFolderMigrationRequest
    + PSComputerName        : mb2-2013.es.tv

----------- Ron E Biggs Chief Tech Officer Entertainment Studios

Hello,

I installed a trial version of MS Exchange 2013 SP1 from a DELL Server.  Tried to de-install it and get message that "mailbox database" can't be deleted.  How do I get around this?  I want to completely remove the product and start over.  I have tried 3 times to remove it with no success.  Any help is appreciated.

Thx

John G.

John Grace

I'm using Exchange 2010 Edge Transport in our organization that I've recently upgraded to Exchange 2013. I like Edge Transport - along with our spam filter it is an effective and simple way to send and receive external e-mail - and I don't want to get rid of it.  But it seems like it needs a 2010 Hub Transport server to interact with. 

Right now the only other Exchange 2010 Server I have left running in the organization is the one Hub Transport server that interacts with the Edge Server.  Is there a way to undeploy this server too and connect the Edge Server directly to one of the 2013 Mailbox Servers?  Or will this need to stay as part of the organization as a pair with Edge Transport?

I noticed mail flow was running just fine while the Hub Transport server was turned off.  So it seems like it's possible.  But I want to be able to undeploy it safely without hurting mail flow.  Are there any links or white papers that show how best do do this?

----------- Ron E Biggs Chief Tech Officer Entertainment Studios

Hello All

I would like to get more hands on experience using Exchange 2010 beyond the basics of creating mailboxes. I would like to do this at home in my lab environment that consist of one AD domain server with a forest functional level of Server 2012 R2. I found some pretty good install guides. So to get to my question:

I don't have a domain name ex name@domain.com is there a way around this? if the email is going to be internal to my lab can I just make something up and use my domain exname@mydomain.local or .com

Thanks!!

Phil Balderos

I have used two mail server (Exchange 2013 and Linux sendmail) for mailing in the same domain like abc.com.

I have converted authoritative domain in to internal relay for sending mail in Linux mail user, and create a send connector point to Linux mail system as a smart host. in that case my exchange user send mail to Linux user and internet via Linux smart host,

then I create a receive connector in exchange server for receiving mail from Linux mail system as edge transport custom connector & permission set to anonymous, when Linux user send mail to my exchange user it queued in my exchange message queue and the error is:

Last Error:A local loop was detected.

What's the problem?

We are providing Exchange 2010 today - in the past it was migrated from Exchange 2003. Now I am prepearing migration to Exchange 2013 - migration proces stopped with error message there is still Exchange 2003 server in configuration. I checked it through Exchange management console and there are realy 2 servers in server summary screen. I did not find legacy Exchange2003 anywhere else in configuration. So I search through internet and found some artical with manual removing old records through ADSIedit tool.
A removed the record from
Configuration\CN=Microsoft Exchange\CN=<Exchange Domain>\CN=Administratice Groups\CN=First Administratice Group\CN=Servers

there was one record with Exchange 2003 specification - so this has been deleted - but in the Exchange console I can still see the legacy Exchange2003 in the Server Summary.

Can somebody point me, what else I should check?

Note: There is still one record in:
Configuration\CN=Microsoft Exchange\CN=<Exchange Domain>\CN=Administratice Groups\CN=First Administratice Group\CN=Routing Groups\CN=First Routing Group\CN=Connection

which it seems define some connection between non existing Exchange2003 and current Exchange2010.

Should I remove this too? Is it safe?

Thanks for any help

Pavel

Dears,

I'm facing a issue with Exchange 2013 SP1 CU5 "15.00.0913.022" suddenly after 2 month of the migration from Exchange 2010 i get the "Unknown" status for Content Index status on any database hosted on two servers only

my new Exchange 2013 topology is : 3 CAS servers & DAG contains 6 Mailboxes servers and 4 lagged Mailboxes servers

The following is the errors and warnings logs on my effected mailboxes servers:

The indexing of mailbox database DB53 encountered an unexpected exception. Error details: Microsoft.Exchange.Search.Core.Abstraction.OperationFailedException: The component operation has failed. ---> Microsoft.Exchange.Search.Engine.FeedingSkippedException: "Feeding was skipped for '3a5ec474-ea70-42b5-a123-d7ff7e5aadc3 (DB53)' due to the state 'Unknown', error code: 'Unknown'."

   at Microsoft.Exchange.Search.Engine.SearchFeedingController.InternalExecutionStart()

   at Microsoft.Exchange.Search.Core.Common.Executable.InternalExecutionStart(Object state)

   --- End of inner exception stack trace ---

   at Microsoft.Exchange.Search.Core.Common.Executable.EndExecute(IAsyncResult asyncResult)

   at Microsoft.Exchange.Search.Engine.SearchRootController.ExecuteComplete(IAsyncResult asyncResult)

The FastFeeder component received a connection exception from FAST. Error details: System.ServiceModel.FaultException`1[System.ServiceModel.ExceptionDetail]: Internal error while processing request (Fault Detail is equal to An ExceptionDetail, likely created by IncludeExceptionDetailInFaults=true, whose value is:

Microsoft.Ceres.InteractionEngine.Component.ProcessingEngineException: Internal error while processing request

   at Microsoft.Ceres.InteractionEngine.Component.CieProcessingEngine.LogAndRethrowException(Exception e)

   at Microsoft.Ceres.InteractionEngine.Component.CieProcessingEngine.GetItems(Guid flowIdentifier, String outputName)

   at SyncInvokeGetItems(Object , Object[] , Object[] )

   at System.ServiceModel.Dispatcher.SyncMethodInvoker.Invoke(Object instance, Object[] inputs, Object[]& outputs)

   at System.ServiceModel.Dispatcher.DispatchOperationRuntime.InvokeBegin(MessageRpc& rpc)

   at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage5(MessageRpc& rpc)

   at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage31(MessageRpc& rpc)

   at System.ServiceModel.Dispatcher.MessageRpc.Process(Boolean isOperationContextSet)).

----------------------------------------------------------------------------------------------------------------------------------------------------------------------

Event 169 (Search) of severity 'Error' occurred 14 more time(s) and was suppressed in the event log

-------------------------------------------------------------------------------------------------------------------------------------

An operation attempted against a FAST endpoint exprienced an exception. This operation may be retried. Error details: Microsoft.Exchange.Search.Fast.PerformingFastOperationException: An Exception was received during a FAST operation. ---> System.ServiceModel.CommunicationObjectAbortedException: The communication object, System.ServiceModel.Channels.ServiceChannel, cannot be used for communication because it has been Aborted.

Server stack trace:

   at System.ServiceModel.Channels.CommunicationObject.ThrowIfDisposedOrNotOpen()

   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.Ceres.CoreServices.Admin.IAdminServiceManagementAgent.SystemInfo()

   at Microsoft.Exchange.Search.Fast.NodeManagementClient.CheckForAllNodesHealthy(Boolean retry)

   at Microsoft.Exchange.Search.Fast.IndexManager.<UpdateConfiguration>b__8()

   at Microsoft.Exchange.Search.Fast.FastManagementClient.<>c__DisplayClass1.<PerformFastOperation>b__0()

   at Microsoft.Exchange.Search.Fast.FastManagementClient.PerformFastOperation[T](Func`1 function, String eventLogKey)

   --- End of inner exception stack trace ---

------------------------------------------------------------------------------------------------------------------------------------

Exchange Server Information Store has encountered an error while executing a full-text index query ("string("ItemWarmUpSearch31febf7b418e44878df6e5623e37c828*", mode="and")"). Error information: System.ServiceModel.FaultException`1[System.ServiceModel.ExceptionDetail]: Internal error while processing request (Fault Detail is equal to An ExceptionDetail, likely created by IncludeExceptionDetailInFaults=true, whose value is:

Microsoft.Ceres.InteractionEngine.Component.ProcessingEngineException: Internal error while processing request

   at Microsoft.Ceres.InteractionEngine.Component.CieProcessingEngine.LogAndRethrowException(Exception e)

   at Microsoft.Ceres.InteractionEngine.Component.CieProcessingEngine.ExecuteSearchFlow(String flowName, IEnumerable`1 inputData)

   at SyncInvokeExecuteSearchFlow(Object , Object[] , Object[] )

   at System.ServiceModel.Dispatcher.SyncMethodInvoker.Invoke(Object instance, Object[] inputs, Object[]& outputs)

   at System.ServiceModel.Dispatcher.DispatchOperationRuntime.InvokeBegin(MessageRpc& rpc)

   at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage5(MessageRpc& rpc)

   at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage31(MessageRpc& rpc)

   at System.ServiceModel.Dispatcher.MessageRpc.Process(Boolean isOperationContextSet)).

What i have tried to solve the issue with no luck is: 

1- Reseed the effected Databases

2- Reset the index manually by stop the Search and Search Host Controller services and delete the index folder and start the services again in order to force it to rebuild the index

3- Restart the mailbox server that has the index issue

4- Create the AD group "ContentSubmitters" and then grant Admistrators and NetworkService full access to the group as the following technet article http://support.microsoft.com/kb/2807668

Any Idea will be much appreciated.

Thanks,

Ayman Saleh

Ayman Saleh

I've been researching this and I think I found a solution, but need a sanity check.

I'm upgrading from Exchange 2007 to 2013 (co-existence migration), and when I try to migrate a couple test mailboxes I get an Error: “This user does not have an Exchange mailbox.”

https://social.technet.microsoft.com/Forums/exchange/en-US/d0c96836-3ad5-49c8-bd85-2df52f481b0c/exchange-2013-migration-says-the-user-does-not-have-an-exchange-mailbox?forum=exchangesvrdeploy

http://support.microsoft.com/kb/2812509/en-us

The “get-mailbox –arbitration” and “get-mailbox –arbitration |fl name,alias” commands show corrupted several corrupted mailboxes on the 2013 server:

SystemMailbox{1f05a927-ac1a-45fa-9abc-338f309be380}

SystemMailbox{bb558c35-97f1-4cb9-8ff7-d53741dc928c}

Migration.8f3e7716-2011-43e4-96b1-aba62d229136

FederatedEmail.4c1f4d8b-8179-4148-93bf-00a95fa1e042

The remaining mailbox (SystemMailbox{e0dc1c29-89c3-4034-b678-e6c29d823ed9}) is not corrupted.

Running the command to enable the migration mailbox fails.  Error: “This task does not support recipients of this type.  The specified recipient “Migration.{GUID}” is of type UserMailbox.

This thread suggests deleting them from ADUC and then running ADprep again to recreate them.  

https://social.technet.microsoft.com/Forums/en-US/bba16b29-0d1f-4f2b-943c-e2110ae0d8b6/fixing-corrupted-mailboxes-after-migration

Is it safe to delete all of the arbitration mailboxes (including the non-corrupted system mailbox) and then recreate them?

Hello every one,

I have a problem to migrate mailbox from exchange 2013 to exchange 2007 back.

Recently We have installed a pilot exchange 2013 and already migrate about 100 mailboxes.

But we still have some problems, and need transfer/migrate some mailboxes back to exchange 2007

i'm facing with this problem couple of days from now, can't move some mailboxes i'm geting this message:

Relinquishing job because the mailbox is locked. The job will attempt to continue again after 5/27/2013 10:27:43 AM.

I have just clicked on sign out button in 2013 ECP and can no longer log in again, I can log in to OWA

This is a new installation and yes I made a full backup before I started to configure it, so I can go back to that if need be but unless I know why it will probably happen again.

I am using Exchange 2013 CU6 installed on 2012 standard.

Hi All ,

Planning to have a coexistence scenario in my environment which is mentioned below

Exchange 2010 - ambiguous url in place - OA enabled 

For mapi/rpc traffic - mail.domain.in -  exchange 2010

For https traffic - mail.domain.in - exchange 2010

mail.domain.in will get resolved in to cas array in exchange 2010 .

After coexistence On our side we are not going to move the mail.domain.in namespace to exchange 2013 , Instead of that we are going to use a new namespace in exchange 2013 for internal outlook anywhere and it will be outlookmail.domain.in and for the remaining exchange 2013 services like pop,imap,owa,active sync url's,external OA will be having mail.domain.in as same as exchange 2010 namespace.

just consider outlookmail.domain.in is available on the san certificate installed in exchange 2013.

Note : 

On my ide I would assume Internal outlook 2010 mapi users will connect directly to exchange 2010 servers on the namespace mail.domain.in

Likewise i would assume Internal outlook anywhere 2013 users will connect directly to exchange 2013 servers on the namespace outlookmail.domain.in

Services like pop,imap,owa,active sync ,external OA connections for both exchange 2010 and exchange 2013 from the external world will be routed from firewall to exchange 2013 servers .Then https traffic for exchange 2010 mailbox users will be proxied to 2010 exchange server via exchange 2013 server.

question : I would like to know above mentioned scenario is possible or not ?

On my side I know in my environment i am having ambiguous url's in place and at the same time i don't want the exchange 2010 internal outlook users to connect via exchange 2013 rpc over http even though OA is enabled on exchange 2010.

So simply i can say i need my internal exchange 2010 mailbox users has to connect via tcp/ip.

All of you tell me your valuable suggestions.

Regards

S.Nithyanandham

Hello all,

Currently running a single server installation of Exchange 2013 CU1 on Server 2008 R2.

Checked prerequisites for updating to CU5 and all looked good.

Launched the CU5 install via GUI, not command prompt, which from what I remember when I installed CU1 using the GUI didn't work very well.

Anyway, CU5 failed telling me I have to uninstall CU1. Checked a couple forums and found the same answer.

Tried to uninstall CU1 via Programs and Features, but that failed because it couldn't find a file. Also tried Change and that errors out saying the installation failed and to run setup from an installation media location.

So, I enabled the services that where disabled by either the CU5 install or the CU1 uninstall and started chasing and correcting errors. I've got it to the point that where it looks like everything is working, but I can't send or receive. I'm trying to find an error message somewhere, but I'm not having any luck finding any.

I've tried to use the Queue Viewer and suspend the queue, but nothing shows up in the queue. I've looked at send and receive connectors and they look OK.

I've been up all night and I'm at a loss right now and could really use some help getting this train back on the tracks.

Thank you,

Dennis

hi,

I have existing Exchange Server 2010 Hybrid Deployment. Planning to migrate to Exchange 2013. However, while schema update, i am facing some errors/warnings as can be seen in attached screenshot. 

I have already checked and current functional level in DC is Windows Server 2003. What could be the best steps to troubleshoot the problems and proceed further with Exchange 2013 installation?

Thanks

I am trying to install Exchange 2013 on server 2012 r2. AD level is 2012 r2 and I currently have exchange 2010 sp3 with all the rollups running. DCdiag passes with no errors.

The setup fails at the first step which is schema and AD preparation with the following error.

Error:
The following error was generated when "$error.Clear();
	install-ExchangeSchema -LdapFileName ($roleInstallPath + "Setup\Data\"+$RoleSchemaPrefix + "schema85.ldf")" was run: "Microsoft.Exchange.Configuration.Tasks.TaskException: There was an error while running 'ldifde.exe' to import the schema file 'C:\Windows\Temp\ExchangeSetup\Setup\Data\PostExchange2003_schema85.ldf'. The error code is: 8245. More details can be found in the error file: 'C:\Users\hhemmati\AppData\Local\Temp\ldif.err'
   at Microsoft.Exchange.Configuration.Tasks.Task.ThrowError(Exception exception, ErrorCategory errorCategory, Object target, String helpUrl)
   at Microsoft.Exchange.Management.Deployment.InstallExchangeSchema.ImportSchemaFile(String schemaMasterServer, String schemaFilePath, String macroName, String macroValue, WriteVerboseDelegate writeVerbose)
   at Microsoft.Exchange.Management.Deployment.InstallExchangeSchema.InternalProcessRecord()
   at Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__b()
   at Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean terminatePipelineIfFailed)".

The file ldiff.err contains the following

Entry DN: CN=ms-DS-GeoCoordinates-Altitude,CN=Schema,CN=Configuration,DC=palatribe,DC=com
Add error on entry starting on line 134: Unwilling To Perform

The server side error is: 0x20bb Schema update failed: duplicate OID.

The extended server error is:

000020BB: SvcErr: DSID-032603C0, problem 5003 (WILL_NOT_PERFORM), data 8379


An error has occurred in the program

I am migrating an SBS 2011 Exchange server (2010) to Exchange 2013 on a W2012 Server (not a DC). I completed the install and moved one user's mailbox to the 2013 server. All users can process their email via OWA and Outlook. But, if the SBS 2011 server is disconnected, the migrated user cannot log on via OWA and I can't log in to administrator ecp. They just time out. I know the mailbox is migrated because if I disconnect the 2013 server and OWA into the SBS 2011 server it gets an error saying the mailbox server is unavailable. I must have missed a step in the migration. Can someone please point me at some documentation for completing the migration. 

Thank,

Lou

Louyo