Move to another Active Directory domain
-
Hi,
We are planning to change our AD domain soon. All hosts are already in an AD domain.
When we change the values in the Active Directory properties, if the client is already member of a domain, it seems it’s not removed from it and it’s not joined to the new AD domain.
No problem if the client is in a workgroup or manually removed from our old domain, it is put in the new domain through the properties in FOG and in the desired UO.
Is it a normal behavior of FOG?
thanks.
-
@hernani In domain moves you are better to stick to the Windows world for this action. You can use FOG to deploy vbs/ps/cmd file that changes the target computer’s affiliation. You will have less issues if you do this in the windows realm.
For one deployment I setup the computers where initially put in one Imaging OU that had no GPO policies that would break imaging. Then in the first run part of the unattend.xml file I ran a VBS script called move to OU to relocate the target computer to the proper OU. Now this was not moving to a different AD domain, just to a different OU.
I think there was a netdom command that we used at one time to join computers to domain (not by using fog). That utility had the ability to connect and disconnect a device from domains.
One other thing you need to keep in mind is make sure you have a local admin account on the target computer you can use if the domain move fails, otherwise your target system will be lost if the reconnect to the new domain fails.
