Hello...A small client of about 20 users will be moving off their legacy Windows Server 2003 Small Business model to a full Windows Server 2008 R2 model. They've already moved off Exchange 2003 to Office 365, so SBS 2003 Exchange is not a concern. Only the user accounts, PCs, printers, file shares and network-related service account/applications are affected.
I want my new domain to be completely clean and I'm a little concerned about the legacy SBS 2003 domain - it may have experienced some corruption in the past that could cause a garbage-in, garbage-out situation if I was to migrate the resources from the old to the new domain. I'm considering doing the following:
1. Build a new Windows Server 2008 R2 domain.
2. Create new accounts with exact same username and password.
3. Gradually move PCs, printers, file shares and so on to new domain.
4. Once all resources are migrated, wipe SBS 2003 server and rebuild SBS 2003 server as Server 2008 R2 DC on new domain.
My main concern during the migration is that users - whether on the existing SBS domain or the new domain - can seamlessly access resources on the peer domain. So for example, when I remove a PC from the SBS domain and add to the new domain, the user will need access to file shares on the legacy SBS server. Conversely, if I move printers to the new domain, the users still on the legacy SBS domain will need printing capability from the newly hosted printer on the Server 2008 R2 box.
I'm hopeful that setting up the new domain with the same usernames and passwords will accomplish this.
Am I correct?
Is there a better way to do this?