UNSOLVED
wireless stops working after sysprep?!
Deploying a Windows 7 image that I would like to use on all our hardware (latitude & optiplex). Using deployment workbench & windows deployment services. Everything works flawlessly until after I sysprepped the image.
When I boot an image I created after sysprep (/generalize /oobe) has run on it the wireless stops working.
The correct driver is installed, according to device manager (exactly the same driver Dell is using in their standard installs, the driver from the CABs) but you're just not able to see any wireless networks. When I ran the Intel wifi diagnostics as a test it says that the hardware is disabled. Uninstalling the driver and installing an other driver doesn't help at all.
I should be able to get around the issue by using PersistAllDeviceInstalls and DoNotCleanUpNonPresentDevices but I recon that will give me some issues when putting the image on different hardware.
I'm out of ideas, the only thing I can think of is a bug in the sysprep version I use or an incompatibility between the source of my image, Windows 7 ENT SP0, (I added updates manually) and the deployment solution. I already tried to uninstall the driver before the sysprep process. Sysprep then installs the driver while booting the image and the problem persists.
When I boot an image I created after sysprep (/generalize /oobe) has run on it the wireless stops working.
The correct driver is installed, according to device manager (exactly the same driver Dell is using in their standard installs, the driver from the CABs) but you're just not able to see any wireless networks. When I ran the Intel wifi diagnostics as a test it says that the hardware is disabled. Uninstalling the driver and installing an other driver doesn't help at all.
I should be able to get around the issue by using PersistAllDeviceInstalls and DoNotCleanUpNonPresentDevices but I recon that will give me some issues when putting the image on different hardware.
I'm out of ideas, the only thing I can think of is a bug in the sysprep version I use or an incompatibility between the source of my image, Windows 7 ENT SP0, (I added updates manually) and the deployment solution. I already tried to uninstall the driver before the sysprep process. Sysprep then installs the driver while booting the image and the problem persists.
- Unfortunately, no. I haven't had the time to look into it further. At the moment I do not sysprep the machines and I use one image per type. I know I should do it but it simply does not work.
I am going to start from scratch whenever I find the time (with new sources including SP1). DELL-Warren B
1 Rookie
•
1124 Posts
850
0
Posted June 20th, 2011 08:00
Multi-model deployment is definitely doable. The keys to getting this correct are the following
1. capture a base image on a virtual machine so that no drivers are included.
2. Deploy the captured (and sysprepped) image with drivers being applied to the base image on a model specific basis.
Both MDT and ConfigMgr have this capability which allows for multi-model support with a single deployment process.- yeah I'm using MDT as we don't have the ConfigMgr environment set up atm (and it's a lot of work for which I simply don't have the time).
It works for all my desktop machines (I basically just added the drivers I needed with DISM after I sysprepped & captured the image; which to my surprise, worked perfectly).
I did use a real machine though, no vm. I tried capturing without the wireless driver too, which SHOULD work if logic would apply. My next image will surely be created on a VM and I suspect smooth sailing. - Restarted from scratch. Made custom installation as virtual machine in hyper-v so didn't have to add any drivers.
My first approach was to add all drivers from the combined notebook cab files to the sysprepped wim image with dism (offline). This gave me the exact same problem but this was expected as I thought this wasn't the best way to add drivers.
Now I'm using a drivergroup variable in MDT (added task variable "Drivergroup" with value Windows 7 x64\%Make%\%Model%) which installs only the drivers from that respective model from the Out-of-box drivers tree. It works fine and installs all drivers but I still have the wireless issue. Test machine atm is Latitude E6220 but I'm sure it'll be the same on our other hardware. Now I will try to remove the wireless driver and install it manually at the end. - Update: When I do all updates of a basic W7 install except for the 982670, it works.
When I then install office, it fails (our office installation automatically updates so I think it might contain this update).
If I install our standard applications on top of the basic W7 install, it also fails (I'm sure that Design Review installs .NET 4 so I'm still suspecting that one).
Hell, I'm going the thin image road now. Wasted too much time. DELL-Warren B
1 Rookie
•
1124 Posts
850
0
Posted July 25th, 2011 13:00
thanks for keeping us updated on your testing progress.
joewo1
1 Message
850
0
Posted June 15th, 2011 08:00