SCCM OSD VISTA ERROR
- April 23rd, 2010
- Posted in Microsoft . sccm . windows
- Write comment
I was getting a nice 4005 error while trying to Build/Capture of Vista Sp2, the error was occuring just before windows installtion had started (after applying drivers)
It seems there was an incompatibility on one of the divers as I use mainly XP Drivers, To workaround this I created a new driver category for Vista to use (instead of all the drivers avaliable)
I got it working by
- Create a “Vista_Network” driver catergory and added the basic Network/required drivers

- Edit The Build-Capture tasksequence
- Goto the “Apply Driver” task
- Select “Limit Drivers To “Vista_Network” Category”
- Save
It will now work and you dont need to disable drivers etc.
Good Luck

@Carlos Morales
Hi Carlos,
I have updated the blog with some images, This is what I mean. In the end its better to go back and remove old/duplicate drivers that might be causing issues.
If i remember right, when there are two drivers that are the same (different versions) it can cause OSD to fail as it wont choose the right one. (bad remembering ;/ )
Good luck!
Hi.
I understand, download NIC drivers and create Package, after edit Task Sequence and Add – Drivers – Apply Driver Package. Is correct?
Questions.
Step Apply Device Drivers – delete?
Where you put step Apply Driver Package, between what steps.
Thanks,
Hi. I did what you mentioned but still not working.
I Deploy Windows 7.
The Steps in Task Sequence are:
1. Restart in Windows PE
2. Partition Disk
3. Apply Operating System
4. Apply Data Image 1
5. Apply Data Image 3
…
…
The Task Sequence stop in step four – Apply Data Image 1.
Review smsts.log and show only one error:
Failed to connect to “\\ruv0800.svcs.itesm.mx\SMSPXEIMAGES$\SMSPKG\UV100011″ (5)
Other idea? Thanks,
@Carlos Morales
Have you enabled “Command Support” on the boot image?
if so, press f8 when you get a failure and then ping the server also check network is working etc.
If you want you can pastebin.com the log and I can take a look?
good luck