[wds] New image needs network card disable/enable to join domain....

[kennysarmy]

Our windows 7 64 bit image was getting on for a year old and it was taking ages to do the MS updates so I created a new image.

 

We have three motherboard types on site, Intel DH55 & DH61 and latest PC's on MSI H81M-P33

 

I created the new build on a DH61 and then added to the WIM file the latest drivers for the DH55 and P33 boards.

 

Whenever we image a PC now it won't join the domain unless we disable and then enable the network card.

 

In device manager everything looks as it should....

 

Does anyone have any ideas?

[kennysarmy]

Yes - does n't make any sense does it

[hallb15]

Sounds like a resource conflict - IP addr maybe?

[kennysarmy]

Sounds like a resource conflict - IP addr maybe?

@hallb15 - how could we ascertain this was the reason?

[hallb15]

After imaging, does the PC get an IP assigned from the DHCP server or does it have a static IP set?

Check your DHCP server to see what IP addrs have been leased.

[CraigM]

Did you generalise your Windows image with Sysprep before you imaged? Unfortunately I don't use WDS, MDT was just a much better solution all round. Needing to disable and then enable sounds like a driver issue to me, not IP conflict.

[kennysarmy]

Did you generalise your Windows image with Sysprep before you imaged? Unfortunately I don't use WDS, MDT was just a much better solution all round. Needing to disable and then enable sounds like a driver issue to me, not IP conflict.

 

Yes I did.....

 

We've discovered it was something to do with the Bonjour service....disabling that service and then restarting sorts out the issue

[CraigM]

Yes I did.....

 

We've discovered it was something to do with the Bonjour service....disabling that service and then restarting sorts out the issue

 

Ah ok I see. I no longer image a reference PC up, I start from a clean Windows 7 image and install as much as possible via the MDT task sequence. It takes a bit longer than using a "fat" image but I found it made things more flexible when deploying machines with different needs to different locations. Six of one, half a dozen of the other I guess.

[haleema]

Having made a second FOG server recently, it has probably got easier with the newest version. Build your server (I used Debian x64). Install ssh so you can remotely manage it. Give it a static IP. Then download the FOG installer (you can do this via the terminal or drag and drop it from a Windows PC using an SCP client). Enter the FOG install directory and run the installfog.sh script. Follow through the steps. You should then set your DHCP settings so that your clients PXE boot from the new FOG server.