We are converting 200+ users from a Samba 3.5.6 domain to AD running on Windows 2012. So far, it has been a spotty process, with issues pulling group machine and user policies, multiple re-boots, corrupted roaming profiles, etc.
The steps we are currently taking are:
* Copy user's favorites and local files to a network directory
* Log into PC (Win 7) as local Admin, and create new DNS entries for AD
* Set the domain to WORKGROUP, restart, and join PC to the AD domain (FOG.Local)
* On the AD server, move the newly joined machine to the OU that gets policy, run gpupdate and restart the PC
* Log into the PC as Domain Admin (this is another spot where there are often problems - sometimes it take 3 or 4 restarts/gpupdate before the Domain Admin password is pushed from policy)
* Log in as user (can take up to 15 minutes to build a profile, which is a roaming profile stored on a share created via GP)
* Restore favorites and local files from network, and user is good to go
Once the conversion is done, the user doesn't have any trouble logging into FOG.Local, but we have a ton of users, and it can take an hour or more to convert one user machine, so to convert everyone to AD will take months. It seems like there should be a much more streamlined process (or even a utility?) to make this go faster. Are we doing something wrong or missing a step?