JJonas Posted July 28, 2011 Posted July 28, 2011 Do we need to use Sysprep with Fog or will FogPrep do the same job? also with Windows XP we had a Sysprep setup saved on my network that we could use on any XP machine. We dont appear to be able to set up a similar generic Sysprep for Windows 7 each time we have to run through the answerfile setup for each machine prior to taking an image. This is time consuming and leading to inconsistent results.
3s-gtech Posted July 28, 2011 Posted July 28, 2011 You'll need to Sysprep, much more so than with XP (I NewSID on XP still). You'll need to FOGPrep too unless you've just updated to the lastest release of FOG.
JJonas Posted July 28, 2011 Author Posted July 28, 2011 Do I really have to remake the answerfile every time?
3s-gtech Posted July 28, 2011 Posted July 28, 2011 Don't think so - but I'm not sure as I don't use an unattended answer file at present - I'm pretty sure it's possible from reading on here though.
JJonas Posted July 28, 2011 Author Posted July 28, 2011 Right ive been experimenting with sysprep. So far I have been running it without an answerfile and I have discovered that I can only run it so many times before it starts to fail and give errors. Is this where we need an answerfile with the skiprearm setting in it?
SYNACK Posted July 28, 2011 Posted July 28, 2011 You need to sysprep unless you want lasting and strange problems with your deployment. I don't think that skipping the rearm cycle will sort it either which is why most of use use a virtual environment to make a base image and snapshot it before sysprep. You can then just rollback the snapshot to update it. Given the hardware independance of the new sysprep you just need to add the right drivers into the image and you can push the one image to all PCs. 1
glennda Posted July 28, 2011 Posted July 28, 2011 we use sysprep and fog with windows 7 - i'll see if i can digout an answer file for you - although not at work till monday now 1
Jiser Posted July 29, 2011 Posted July 29, 2011 Def sysprep. Answer file can stay in system32 sysprep folder if you want. Just copy and paste. 1
JJonas Posted July 29, 2011 Author Posted July 29, 2011 Thanks for all of the posts and suggestions...will bare them in mind for future images but for this one, i've completely had enough! Made a big image which took best part of yesterday to do, wouldn't sysprep. Even just running sysprep with the generalize setting and no answer file. Fatal error which on lots of google searches showed the most common answer to be it's something wrong with the image and the image needs to be rebuilt. Nothing to do with the re-arm count, it wont even run sysprep. Bit the bullet, wiped the machine today, installed win 7 again from scratch, sp1, all updates, latest drivers, all software (including complete adobe master collection)! never joined it to the domain and guess what....EXACTLY the same problem!. This has happened before on another Win 7 image too. Sysprep sucks!....I have imaged literally hundreds of XP computers at loads of schools without any problems whatsoever. I Read Mark Russinovichs post and despite the title, it seems to me he is saying unique computer sids (which is really all I want sysprep for here) aren't needed. The Machine SID Duplication Myth (and Why Sysprep Matters) - Mark's Blog - Site Home - TechNet Blogs I'm going with just running fog prep as there's no way in hell i'm building an image for a third time, the image is fine. If needed, i'll look for a third party win 7 tool to change the sid as newsid doesn't seem to work. If it really doesn't work, i'll go back to XP for now!
Jiser Posted July 31, 2011 Posted July 31, 2011 Thanks for all of the posts and suggestions...will bare them in mind for future images but for this one, i've completely had enough! Made a big image which took best part of yesterday to do, wouldn't sysprep. Even just running sysprep with the generalize setting and no answer file. Fatal error which on lots of google searches showed the most common answer to be it's something wrong with the image and the image needs to be rebuilt. Nothing to do with the re-arm count, it wont even run sysprep. Bit the bullet, wiped the machine today, installed win 7 again from scratch, sp1, all updates, latest drivers, all software (including complete adobe master collection)! never joined it to the domain and guess what....EXACTLY the same problem!. This has happened before on another Win 7 image too. Sysprep sucks!....I have imaged literally hundreds of XP computers at loads of schools without any problems whatsoever. I Read Mark Russinovichs post and despite the title, it seems to me he is saying unique computer sids (which is really all I want sysprep for here) aren't needed. The Machine SID Duplication Myth (and Why Sysprep Matters) - Mark's Blog - Site Home - TechNet Blogs I'm going with just running fog prep as there's no way in hell i'm building an image for a third time, the image is fine. If needed, i'll look for a third party win 7 tool to change the sid as newsid doesn't seem to work. If it really doesn't work, i'll go back to XP for now! Sysprep works fine and is useful not just for newsid purposes... The issue with your fatal error may be to do with that you have syspreped more than 3 times on that machine. We played around with skip rearm and things started working after KMS started liscencing (count of 25+ first with W7)
JJonas Posted August 1, 2011 Author Posted August 1, 2011 Sysprep works fine and is useful not just for newsid purposes... The issue with your fatal error may be to do with that you have syspreped more than 3 times on that machine. We played around with skip rearm and things started working after KMS started liscencing (count of 25+ first with W7) No, it was the first time Sysprep was run on that machine, freshly built brand new image. here are the error logs if anyone can make sense of them 2011-07-29 13:37:26, Error [0x0f0082] SYSPRP LaunchDll:Failure occurred while executing 'C:\Windows\system32\msdtcprx.dll,SysPrepDtcCleanup', returned error code -2147024891[gle=0x000000b7] 2011-07-29 13:37:26, Error [0x0f0070] SYSPRP RunExternalDlls:An error occurred while running registry sysprep DLLs, halting sysprep execution. dwRet = -2147024891[gle=0x000000b7] 2011-07-29 13:37:26, Error [0x0f00a8] SYSPRP WinMain:Hit failure while processing sysprep cleanup providers; hr = 0x80070005[gle=0x000000b7]
JJonas Posted August 1, 2011 Author Posted August 1, 2011 @glennda would like your copy of the answer file if you can dig that up for me.
JJonas Posted August 1, 2011 Author Posted August 1, 2011 Given the hardware independance of the new sysprep you just need to add the right drivers into the image and you can push the one image to all PCs. Is there a guide on how to do this?
Jiser Posted August 1, 2011 Posted August 1, 2011 (edited) Is there a guide on how to do this? Ive looked everywhere. Apprently there is a sysprep driver scanner but we gave up for the easier solution. We just install as many drivers as we can on one type then go to others and test + resysprep then reupload to FOG. Good to have different image versions anyway. Just out of curiosity what commands are you using to start sysprep? Theres probably something wrong in your answer file if its coming up with a fatal error every time. If you want I will forward you ours. Weve 'rewritten' it a few times and definately works on all our machine types - laptops and desktops (pretty much all dells) and our rubbish Idesks. Edited August 1, 2011 by Jiser
katie.lawe Posted August 1, 2011 Posted August 1, 2011 @glennda would like your copy of the answer file if you can dig that up for me. Is there a guide on how to do this? Hi I would like a copy of both of these if possible please. Thanks
SYNACK Posted August 1, 2011 Posted August 1, 2011 Is there a guide on how to do this? Just inject them into the WIM using DSIM Add and Remove Drivers Offline 1
Modus Posted August 3, 2011 Posted August 3, 2011 Ive looked everywhere. Apprently there is a sysprep driver scanner but we gave up for the easier solution. We just install as many drivers as we can on one type then go to others and test + resysprep then reupload to FOG. Good to have different image versions anyway. Just out of curiosity what commands are you using to start sysprep? Theres probably something wrong in your answer file if its coming up with a fatal error every time. If you want I will forward you ours. Weve 'rewritten' it a few times and definately works on all our machine types - laptops and desktops (pretty much all dells) and our rubbish Idesks. There is a unattended xml file you can use here http://www.edugeek.net/forums/o-s-deployment/67764-fog-windows-7-a.html#post652246 you will need to make some small mods to that file 1
Modus Posted August 3, 2011 Posted August 3, 2011 Is there a guide on how to do this? The tool you guys need is called sysprep driver scanner Vernalex.com - Welcome i have been using this for quite sometime now only with fog, i have 1 image that works only many different hardware (i have several gigs worth drivers) 1
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now