What is the Automatic Order of Operations of the New Fog Client?
-
Is it?
- rename
- reboot
- join the domain
- reboot
… or is it?
- rename
- join the domain
- reboot
-
https://github.com/FOGProject/fog-client/blob/master/Modules/HostnameChanger/HostnameChanger.cs#L55
- Activate Computer
- Leave Domain (reboot if needed)
- Rename Computer (reboot if needed)
- Join Domain (reboot if needed)
It is possible to do the process in just one reboot on Windows, but that would be for another minor release of the client (v0.x.x)
-
I would strongly vote against renaming and joining the domain in a single reboot. This can lead to Active Directory issues. Namely you end up with two objects on the AD, one with the original name and another with the new name, or it may retain the old name anyways.
My vote is to mandatory restart after renaming, then mandatory restart after joining the domain. This is the MS method as well.
Attempting to do both in a single restart is doubly troublesome for us. We have automated scripts that sort the computers into new OUs and Security Groups depending on the naming structure of the computer. If it isn’t named properly before joining the domain, before the DC scripts automatically fire, then the machine isn’t sorted correctly and never will be until the object is manually removed from the domain and rejoined.
Thank you for the great info!
-
@sudburr said in What is the Automatic Order of Operations of the New Fog Client?:
I would strongly vote against renaming and joining the domain in a single reboot. This can lead to Active Directory issues. Namely you end up with two objects on the AD, one with the original name and another with the new name, or it may retain the old name anyways.
My vote is to mandatory restart after renaming, then mandatory restart after joining the domain. This is the MS method as well.I would agree. I have experience in this area, it’s never gone well.
