Hello SBS forums,
I recently did two test migration twice in a lab environment, the first time I learned what not to do because it failed and the second time it went pretty smooth and was able to transfer FSMO roles completing the last bit of demazters guide.
My question is: I took and used a workstation that was on the actual network before I did the lab test migration to see how the workstations would connect and work in an actual real time migration. I didn't backup the workstation thinking I would not have
any issues. The issue I am having is the since I put the workstation back onto the actual network with the original domain controller it seems to still try to connect to the new domain controller that was in the lab test migration environment. But it not in
that lab test migration environment anymore it is now connected backup to the network it was connected to before the migration. How do I make it logon to the original DC also since at logon the new DC had the same credentials as the old DC in terms of "SERVERHERE\usernamehere"
at logon?
I did a echo %LOGONSERVER% and it is pointing to the new DC name that I used in the lab test migration.
I did a set LOGONSERVER=\\actualdc and every time I reboot the machine it goes back to the new DC name that I used in the lab test migration.
So this brought up another question. What if after I do the migration in the mission critical environment and transferred all the FSMO roles. Then for some reason something didn't work right with the new server and need to put the old server back to use by recovering through an image to a pre-migration state. How would all the workstation connect back up to the original DC if they are all now looking for the new DC that they were migrated to?
Thanks,
smg.tech