Offline 800xA upgrade and preserving Domain users to sync properly in SV6
Typically we don’t make an image of the existing domain controllers and use that as a synchronizing controller for the new domain. Was hoping that there might be a more easier way to handle this. We will be implementing separate GPOs than what is in the existing system.
Voted best answer
CONTOSO\USER1 = contoso\user1, regardless if ”Contoso” is a domain or workgroup.
Surely it must be possible to extract and inject lists of user group names and user names out of and into a domain or workgroup using NETSH, Powershell or other Command Line tools of Microsoft.
As long as the name matches (not case sensitive!) System 800xA will not see any difference.
There are several "gotcha's" that can cause trouble when you upgrade on one domain and move back to another domain. For example, although you use the same Service Account Name, if it isn't the same domain, then it isn't the same Service Account. 800xA might not care, but some DCOM and system services will. For this reason, you need to be careful if you are cloning servers and domain controllers.
In Version 5.1 it was relatively simple to upgrade everything on any domain you want, then just move the upgraded servers into the new domain by "joining" them and then just Restore the system. Unfortunately, the new System Console in Version 6 breaks all this because it requires you to configure everything from scratch in the correct domain. (Which is yet another reason why the new System Configuration Console needs to be taken out back and shot)
If you want to completely configure a new system on the same domain then one way to do it is to transfer all the PDC roles to one server, and take THAT primary domain controller back to the office and do your upgrade there. Leave the old system running on the backup domain controller only. Add a new backup domain controller in the office and then take the whole system back to site. Ditch the old backup domain controller when you commission the Version 6 system.