@Quazz Thank you good sir, this will help me in my future endeavors. I have already re-mastered my image using these steps, but it will help with my next rebuild.

We do that with a GPO. Even with groups from a trusted domain.

@Jbob ah ok. I’m slowly figuring out how this works.
Solved and Thanks !

@Rusty said:

Do I just add an entry like in the pic ? Is the change on the network pretty quick or do the changes need to be propagated somehow ?

It’s hard to tell from the picture, but I can see that the .local Top Level Domain is selected. Generally it’s not good in the long run to use the generic top level domains like .local See this for more details on best practices: http://serverfault.com/questions/402580/what-is-active-directory-domain-services-and-how-does-it-work

The entry looks right, but is you’re fog server actually named “fog-server” ? Maybe create an A record for it’s real name too?

Also - is DHCP configured to hand out this particular DNS server? Also - are the hosts in the environment set to automatically configure DNS or is DNS statically set?

On windows, you can use the nslookup utility to resolve IPs and names, you can also specify which DNS server to use.

Ok, thanks to everyone answering my noob questions 😉

@Wayne-Workman its not just inside VMWare. I have had multiple physical servers with just CentOS 7 installed fail with this update.

also if you are creating a “universal” image and can spare an extra 10gb or so then look at “snappy driver” for deploying drivers. That is what I use for my “universal image”.

for our Windows 7 image I did the following:

*set up our “unattend.xml” using a workstation.
*from within a hyper-v guest, install fresh W7 and boot into audit mode.
*install base software (office, serif, any other site licenced products).
*install FOG client
*copy snappy drivers and download the packs.
*configure setupcomplete.cmd to run my snappy driver .bat. This BAT autoruns snappy driver to install MISSING drivers, then deletes the folder of drivers when completed.
*windows update
*copy the unattend.xml created earlier.
(I then “backup” my VM at this point so I can come back to it later)
*sysprep shutdown and generalise
*capture the image into FOG then restore VM from backup ready for the updates next time.

To get snappy drivers to install, simply open it, update the packs, then in your setupcomplete.cmd call

SDI_x64_Rxxx.exe -autoinstall -autoclose -license

The batchfile also cascades into an RD and shutdown reboot at the end of it so it is self cleaning. NOTE I also shutdown the FOGClient service in my setupcomplete.cmd as I DONT want it to join the domain as soon as it sniffs the network! It will join the domain (and rename etc) AFTER the drivers have been installed and rebooted. The batch file also ensures our KMS key is added and I run slmgr /ato. I also add the office KMS key and activate that at the end too, whilst there are default KMS keys when products are installed, I have other images with MAK keys as some of our machines are destined to be unplugged from the network (exam machines etc).

My image is a monster, weighing in at 40gb but works on every single machine I have thrown it on and they are pretty much ready to go (WSUS always has more updates on first boot)

After capturing images from multiple machines, it looks like this issue is due to an incompatible BIOS in these old Dell machines.
I guess this issue can be marked solved…
Thanks for your help everyone

@Rusty Great to hear that you got things sorted. I am marking this solved for now. You are more than welcome to post a more detailed article about this here. Or get in contact with us so we can add this to the wiki! Thanks.