Exchange 2010 Cross Forest Migration: The case of the missing User Account Attributes
Recently I encountered a situation where the client created a new active directory forest was created and all user objects were “migrated” to the new forest. The legacy forest was left intact as Exchange 2003 was not migrated. All applications and other services were migrated to the new forest while Exchange was the only service remaining in the legacy forest. The users accessed their mailboxes via an account in the legacy forest.
I was engaged by the client to design, deploy and migrate to Exchange 2010 SP1 in the new forest. Once this was all setup and configured, migrating the mailbox should be a walk in the park with the power of the Exchange Management Shell. However, in my initial review of the new and old forests, I should have checked the following with the client:
- How were the user accounts migrated? i.e. was a tool used to migrate the accounts? If so, which tool?
- If a tool was indeed employed, which user account attributes were migrated in the migration process?
These questions are very important especially if SIDHistory was not migrated as an attribute on the user account. Read more »
Exchange 2010 Cross-Forest (Cross-org) Client Migration Planning
After some absence, I’ve decided to get my blog running. I have a couple of ideas of what I would like to publish but that will have to wait for now. This week I’m performing a cross-forest migration for a client. After reviewing the assistance available for CLIENT – SIDE CONSIDERATIONS on the Internet, I thought I’d start publishing a list of issues I have encountered so far. It would be great if you could leave your comments so that I can update the list so that it captures a well-rounded list of scenarios and possible issues.
This is a WORK IN PROGRESS – Feel free to send me your comments.
This client has two active directory forests. Both forests have a mix of Windows 2003 and Windows 2008 R2 servers as DCs. The legacy Exchange organization has Exchange 2003 deployed, while the target organization has Exchange 2010 SP1 deployed. The client active directory accounts have already been migrated but are still accessing their mailboxes in the legacy forest / organization. The user accounts used to access the existing Exchange 2003 organization are still the old accounts in the legacy forest.
The Outlook clients deployed in this scenario are:
- Outlook 2003
- Outlook 2007
Here are the items I need to review: Read more »
Exchange 2010 SP1 (Beta)
Exchange 2010 SP1 has gone to beta. Review the contents of Exchange SP1 at the Exchange Team’s Blog: http://msexchangeteam.com/archive/2010/04/05/454533.aspx or check the highlights at Chris and Robin’s blog: http://blog.chrislehr.com/2010/04/exchange-2010-sp1-announced.htm.
-
Recent
- Exchange 2010 Cross Forest Migration: The case of the missing User Account Attributes
- Exchange 2010 Cross-Forest (Cross-org) Client Migration Planning
- Vonage – Firewall
- Exchange 2010 SP1 (Beta)
- Exchange 2010 RTM: ActiveSync and the Personal Archive
- Exchange 2010 DAG Implementation
- Upgrade Exchange 2003 Default Address Policy & Address Lists to Exchange 2010
- External HA failover in multiple Internet facing Exchange 2010 sites
- Configuring IE Enhanced Security Configuration on Windows 2008 R2
- Building NLB Exchange 2010 RTM CAS / HT Servers (Hyper-V) – Part 3
- Building NLB Exchange 2010 RTM CAS / HT Servers (Hyper-V) – Part 2
- Building NLB Exchange 2010 RTM CAS / HT Servers (Hyper-V) – Part 1
-
Links
- Belgium Exchange Pro's
- D Golman's Blog – Exchange Escalation Engineer
- Joe Richard's AD Site
- Eric Walter's Exchange Blog
- Harold Wong's Blog
- Exchange Server Team (You Had Me At EHLO)
- Steve Thompson – ConfigManager MVP
- My LinkedIn Profile
- Chris and Robin's Technology Blog
- Jeff Guilet's Expta Blog
- Hugh Marlor's AllUnified Blog
- Elan Shudnow's Blog
Visitor Locations
