@Sted - I have had all sorts of issues with intel's drivers on platforms newer than XP, at one point one of their developers even posted about how intel disliked the new driver model and the problems that it caused them. Other manufacturers have managed and intel are getting much better but as yet intel are the only vendor who have managed to produce drivers that have completely broken any of my syspreped images which is one reason why I do all my images on VMs.
I think this particular issue is as much to do with the drivers as the OS sysprepping.
Well I tried again, new image from the DVD and got it all ready.
Ran sysprep and lo and behold, a fatal error occured. What a crock!
Started a complete fresh install - joined it to the domain,activated it and then tried to sysprep. Same error.
I guess Windows 7 deployment will have to wait until BSF now.
Last edited by GoldenWonder; 17th March 2010 at 11:55 AM.
Another reason I've found for sysprep failing with W7 is SPTD drivers for virtual optical drives. Uninstall them before running sysprep and everything works fine. Just install them again after running sysprep instead.
We had the same error. Take it off the domain and then sysprep it and it should work
I've tried it both joined/disjoined to the domain but get the same error. The logs show the error is related to the sidebar somehow:
Oddly the sidebar seems to work fine (not that I have any gadgets running anyway)Code:2010-03-18 09:14:13, Error SYSPRP WindowsSideShow: Failed to get task folder (0x80070003) 2010-03-18 09:14:13, Error [0x0f0082] SYSPRP LaunchDll:Failure occurred while executing 'C:\Windows\System32\AuxiliaryDisplayClassInstaller.dll,WindowsSideShow_Sysprep_Generalize', returned error code 31 2010-03-18 09:14:13, Error [0x0f0070] SYSPRP RunExternalDlls:An error occurred while running registry sysprep DLLs, halting sysprep execution. dwRet = 31 2010-03-18 09:14:13, Error [0x0f00a8] SYSPRP WinMain:Hit failure while processing sysprep generalize internal providers; hr = 0x8007001f 2010-03-18 09:19:28, Info [0x0f004c] SYSPRP WaitThread:Exiting spawned waiting thread 2010-03-18 09:19:28, Info [0x0f0052] SYSPRP Shutting down SysPrep log
Never had any problems with sysprep on our win7 machines and we have some intel drivers injected into the image. What machine are you sysprepping on and is it fully win7 compatible?
We've not had any issues with Intel drivers messing up sysprep. This is using MDT2010 to capture an image - which it does with the 'Sysprep and Capture' tasg sequence.
If I remember, this is with the Intel 33 chipset (maybe 35)
Funny how it is diffrerent with everyone.
Which version of Windows 7 is this? At the start of the week I sysprepped 7Pro and today sysprepped 7 Enterprise - neither of which had an issue.
Is the sidebar in this editions? It hasn't come up when logging in so I'm going to assume not.
Could you be using the wrong 7?
You know what - forget my message. YOu said SideShow - I read sidebar. Doh...
Yes I'm getting my sideshow and sidebars confused!
Tried a different tack:
Fresh install, but removing the PNY graphics card and replaced with Intel.
Prepped the PC, installed all the required software etc but didn't join to the domain.
Sysprep'd and....it worked! (yay!)
So now I'm not sure whether a) the PCI-e graphics card was causing a wobbly, or b) joining it to the domain was doing it.
This is on a reasonably new PC - works with 7 fine (which is why I've been using it to test)
think ive just worked out my issue x64 win7 with an x86 sysprep file whoops least i can blame myself lol
Don't join the domain, use the answer file to join the domain. I would keep the answer file as simple as possible. Also use the audit mode when prepping the machine for imaging. If someone needs more help I can post my answer but if you mess up, it's best to start over. I have noticed that the answer file is stored in other places other than the sysprep folder.
There are currently 1 users browsing this thread. (0 members and 1 guests)