Posts Tagged ‘migration’
If you install Exchange 2013 CU1 in an existing Exchange 2010 SP3 environment you might wonder why you will be redirected to Exchange 2010′s OWA/ECP when trying to open Exchange 2013 EAC. In a mixed environment you have to add the Exchange client version as parameter: https://yourEXCHANGE2013-CASServer.yourdomain.com/ecp?ExchClientVer=15 After adding this parameter you should be able […]
Filed under: Exchange 2013 | Leave a Comment
Tags: 2010, 2013, cannot, eac, ecp, environment, exchange, migration, mixed, open
We know a lot of you have been waiting for this, and so it is with great excitement that we announce that Exchange Server 2013 RTM Cumulative Update 1 (CU1) has been released to the web and is available for immediate download! This is the first release using the new servicing model for Exchange Server […]
Filed under: Exchange 2013 | Leave a Comment
Tags: 1, 2010, 2013, coexistence, cu, cu1, migration, release
Cross forrest move mailboxes
Today I’ll post my favourite way to move user and mailbox objects across forrests. Prerequisite: Transitive AD trust, migration server running ADMT Migrate the user object with ADMT Mail enable migrated users with PowerShell Enable-MailUser -Identity user -ExternalEmailAddress user@domain.com Collect both domains’ credentials $LocalCredentials = GetCredential $RemoteCredentials = Get-Credential Prepare move with “prepare-moverequest.ps1″ from Exchange […]
Filed under: Exchange 2010, MBX, Powershell | Leave a Comment
Tags: cross, exchange, forrest, migration, move
ExchangeLegacyDN
Often I’m confronted with problems of mail submissions in freshly migrated Exchange environments. In migrated environments it could happen, that the old ExchangeLegacyDN is missing and users can’t answer on old mails. This might happen, when you migrate users between Exchange organizations. To mitigate this issue, you can add the old ExchangeLegacyDN as X500 proxy […]
Filed under: Exchange 2010, Powershell | 2 Comments
Tags: 2003, 2010, 550 5.1.1 RESOLVER.ADR.ExRecipNotFound; not found, add, coexistence, delivery, DN, error, exchange, ExchangeLegacyDN, failed, IMCEAEX, legacy, legacydn, migration, missing, powershell, RESOLVER.ADR.ExRecipNotFound, x500