Hostname while joining to the domain
-
Hi I am a newbie here and trying to take baby steps using FOG.
I have a project at hand, where I would like to image say 50 workstations from single image. So the catch is I would like the hostnames of each machine to be retained, while the image is getting deployed.I really wish to use multicast option and have the FOG client service running in the parent image. So how can I achieve this?
-
@whity said in Hostname while joining to the domain:
I am planning to have FOG client installed in the golden image. Is it mandatory to have the Sysprep done before capturing the image?
Sysprep is a standard/typical step needed to make the reference image ready to install on multiple hardware. There are too schools of thought there. If you are using the idea that you will create one golden image per hardware model then you technically don’t “need” to run sysprep. But if you want to have one golden image for all hardware platform then you need to use sysprep to neutralize the golden image so that it can install on multiple hardware configurations. I can say I always run sysprep with my golden images. The decision to run sysprep or not is not related to FOG. FOG doesn’t care if the image has been syspreped or not.
Also, my understanding is that the FOG client is needed in the golden image to aid the domain joining while deploying the image? Is that right?
The fog client is needed if you want FOG to connect the target computer to AD, name the computer as defined in FOG, as well as if you want to run snapins or other fog managed services. In my case I don’t use FOG to connect the target computer to AD because I have a complex domain structure. I do use FOG’s post install scripts to calculate the proper AD location for the computer at deployment time and then update the unattend.xml file with the proper AD location and calculated computer name, then when Windows OOBE runs it looks at the unattend.xml file and connects the target computer to AD in the proper OU location. This is having windows setup connect the computer to AD and not FOG.
-
@whity said in Hostname while joining to the domain:
So the catch is I would like the hostnames of each machine to be retained, while the image is getting deployed.
The host name set on the target system typically comes from the host name you define when you register the host on the FOG server. So if you set the desired host name during registration it will be set during imaging.
I really wish to use multicast option and have the FOG client service running in the parent image. So how can I achieve this?
One point to bring up here, if you are sysprepping your golden image before image capture, be sure to set the fog service to disable or manual start. Then have the setupcomplete.cmd batch file to reenable the service. If the service is left in autostart mode, it will start any pending tasks before OOBE completes leaving the system in a broken state. ref: https://wiki.fogproject.org/wiki/index.php/FOG_Client#FOG_Client_with_Sysprep
Multicasting requires your networking infrastructure to support multicasting. If your target computers are on the same subnet/vlan as your fog server then you shouldn’t have any major issues. If your target computers are on a different subnet then you need to have a multicast router setup to forward the multicast packets between your networks.
-
Thanks for the reply.
-
Instead of registering the hosts from the PC side, can we import the host name with MAC address of a PC using a .CSV file and assign the needed image and deploy? Would that work?
-
When I am creating a multicast imaging session, the entry shows for a while and then disappears when page is refreshed. Is that behavior normal?
-
-
@whity said:
Instead of registering the hosts from the PC side, can we import the host name with MAC address of a PC using a .CSV file and assign the needed image and deploy? Would that work?
Sure you can import hosts as CSV - see Tom’s post here for some details. Or you can export a CVS from a dummy host created and use that as a template. Find the option to import/export in the Host section of the web UI.
When I am creating a multicast imaging session, the entry shows for a while and then disappears when page is refreshed. Is that behavior normal?
Please check FOG multicast.log (in /var/log/fog/)…
-
@Sebastian-Roth Great then. Will check these out. Thanks.
-
This post is deleted! -
@george1421 said in Hostname while joining to the domain:
@whity said in Hostname while joining to the domain:
So the catch is I would like the hostnames of each machine to be retained, while the image is getting deployed.
The host name set on the target system typically comes from the host name you define when you register the host on the FOG server. So if you set the desired host name during registration it will be set during imaging.
I really wish to use multicast option and have the FOG client service running in the parent image. So how can I achieve this?
One point to bring up here, if you are sysprepping your golden image before image capture, be sure to set the fog service to disable or manual start. Then have the setupcomplete.cmd batch file to reenable the service. If the service is left in autostart mode, it will start any pending tasks before OOBE completes leaving the system in a broken state. ref: https://wiki.fogproject.org/wiki/index.php/FOG_Client#FOG_Client_with_Sysprep
Multicasting requires your networking infrastructure to support multicasting. If your target computers are on the same subnet/vlan as your fog server then you shouldn’t have any major issues. If your target computers are on a different subnet then you need to have a multicast router setup to forward the multicast packets between your networks.
I am planning to have FOG client installed in the golden image. Is it mandatory to have the Sysprep done before capturing the image?
Also, my understanding is that the FOG client is needed in the golden image to aid the domain joining while deploying the image? Is that right? -
@whity said in Hostname while joining to the domain:
I am planning to have FOG client installed in the golden image. Is it mandatory to have the Sysprep done before capturing the image?
Sysprep is a standard/typical step needed to make the reference image ready to install on multiple hardware. There are too schools of thought there. If you are using the idea that you will create one golden image per hardware model then you technically don’t “need” to run sysprep. But if you want to have one golden image for all hardware platform then you need to use sysprep to neutralize the golden image so that it can install on multiple hardware configurations. I can say I always run sysprep with my golden images. The decision to run sysprep or not is not related to FOG. FOG doesn’t care if the image has been syspreped or not.
Also, my understanding is that the FOG client is needed in the golden image to aid the domain joining while deploying the image? Is that right?
The fog client is needed if you want FOG to connect the target computer to AD, name the computer as defined in FOG, as well as if you want to run snapins or other fog managed services. In my case I don’t use FOG to connect the target computer to AD because I have a complex domain structure. I do use FOG’s post install scripts to calculate the proper AD location for the computer at deployment time and then update the unattend.xml file with the proper AD location and calculated computer name, then when Windows OOBE runs it looks at the unattend.xml file and connects the target computer to AD in the proper OU location. This is having windows setup connect the computer to AD and not FOG.
