bookie32 Posted February 20, 2012 Posted February 20, 2012 Hi again I don't create images that often and it is a headache from start to finish every time when I use MDT 2010?!I have created a task sequence on mdt 2010 to sysprep and capture the image from my computer and it throws up lots of errors?!I can't even run a standard sysprep without getting the errors in following:?!2012-02-20 08:22:15, Error [0x0f0082] SYSPRP LaunchDll:Failure occurred while executing 'drmv2clt.dll,Sysprep', returned error code -2147024864[gle=0x00000020]2012-02-20 08:22:15, Error [0x0f0070] SYSPRP RunExternalDlls:An error occurred while running registry sysprep DLLs, halting sysprep execution. dwRet = -2147024864[gle=0x00000020]2012-02-20 08:22:15, Error [0x0f00a8] SYSPRP WinMain:Hit failure while processing sysprep cleanup providers; hr = 0x80070020[gle=0x00000020]2012-02-20 08:43:40, Error [0x0f0082] SYSPRP LaunchDll:Failure occurred while executing 'drmv2clt.dll,Sysprep', returned error code -2147024864[gle=0x00000020]2012-02-20 08:43:40, Error [0x0f0070] SYSPRP RunExternalDlls:An error occurred while running registry sysprep DLLs, halting sysprep execution. dwRet = -2147024864[gle=0x00000020]2012-02-20 08:43:40, Error [0x0f00a8] SYSPRP WinMain:Hit failure while processing sysprep cleanup providers; hr = 0x80070020[gle=0x00000020]2012-02-20 09:22:23, Error [0x0f0082] SYSPRP LaunchDll:Failure occurred while executing 'drmv2clt.dll,Sysprep', returned error code -2147024864[gle=0x00000020]2012-02-20 09:22:23, Error [0x0f0070] SYSPRP RunExternalDlls:An error occurred while running registry sysprep DLLs, halting sysprep execution. dwRet = -2147024864[gle=0x00000020]2012-02-20 09:22:23, Error [0x0f00a8] SYSPRP WinMain:Hit failure while processing sysprep cleanup providers; hr = 0x80070020[gle=0x00000020]2012-02-20 09:48:50, Error [0x0f0082] SYSPRP LaunchDll:Failure occurred while executing 'drmv2clt.dll,Sysprep', returned error code -2147024864[gle=0x00000020]2012-02-20 09:48:50, Error [0x0f0070] SYSPRP RunExternalDlls:An error occurred while running registry sysprep DLLs, halting sysprep execution. dwRet = -2147024864[gle=0x00000020]2012-02-20 09:48:50, Error [0x0f00a8] SYSPRP WinMain:Hit failure while processing sysprep cleanup providers; hr = 0x80070020[gle=0x00000020]All I have done is install all applications, update windows etc and then try to run my task sequence from my server...I connect to the server by using ip address + Build$ and then run the lite vbs script...Everything goes OK and then I get the error window with 8 errors etc.Please, tell me why this should be such a pain to do every time?bookie32PS sorry the image is in Swedish..
bookie32 Posted February 20, 2012 Author Posted February 20, 2012 (edited) Hi again!Well, I am getting more and more fedup with Microsoft and their crap....I found a part solution to my problem and the info was here Windows Media Player Network Sharing Service I can't believe that sysprep would fail because of Windows Media Player Network Sharing Service...but he is right.I followed the instructions and tested a standard sysprep and not MDT 2010 and it worked OK?I tried MDT 2010 and everything started OK and even gave me about 500mb av wim file before it threw up errors of which I haven't documented at the moment.Does anyone have any input?bookie32BTW This problem was supposed to have been fixed before windows 7 was released....then why is it rearing its ugly head again and I have a retail version? Edited February 20, 2012 by bookie32
bookie32 Posted February 20, 2012 Author Posted February 20, 2012 Hi again!When MDT 2010 gave errors while creating wim file...I took the opportunity of booting from a PE Boot disk and capturing the drive.This has gone without errors....So, I presume I have some setting in the task sequence that isn't playing ball, but I only have standard settings....?So, I would like some feed back about the whole process to see if I am doing something wrong....This seems repetative now because I have posted about all of this before...bookie32
Tripredacus Posted February 20, 2012 Posted February 20, 2012 In your TS, make sure to set your Network Location to Public.
bookie32 Posted February 20, 2012 Author Posted February 20, 2012 Hi mate Nice one...I will have a look at that as soon as I can.Not wanting to risk the restrictions with sysprep...I booted a peboot cd and used mapping to network drive to transfer the image directly to my server...which worked.Never done mapping to a network drive before, so that saved me some time...Will get back to you on this!Thanks!bookie32
Tripredacus Posted February 20, 2012 Posted February 20, 2012 Here is a reference. It might be related. Sadly we all wished it would be fixed in SP1 but it wasn't. Maybe SP2 or Windows 8 will have it fixed.
bookie32 Posted February 20, 2012 Author Posted February 20, 2012 Hi again!Can't see how to set network location to public in the TS?In your TS, make sure to set your Network Location to Public.bookie32
Tripredacus Posted February 21, 2012 Posted February 21, 2012 I'll have to look when I get back to work. Did you use any guides or templates when you created your TS?
bookie32 Posted February 21, 2012 Author Posted February 21, 2012 Hi Tripredacus If I understand you question - then I just chose new task sequence and set as follows:New Task Sequence:Task sequence id = bla, blaTask sequence name: Sysprep and CaptureSelect Template:Sysprep and CaptureSelect OS:OS= Windows 7 Ultimate 64bitSpecify product key:Do not specify product key at this timeOS Settings:Full name= Windows UserOrganization=datornissen Admin Password:Do not specify an Administrator password at this timeMy deployment settings are standardMy bootstrap is standard and points to my Server computer \\DN1\Build$I do like most and use the ipaddress when connecting to server \\192.168.1.2\Build$Using \\DN1\Build$seems to throw up problems?I tested the reference you gave and it came up OK, but wouldn't run a stadard sysprep with out deactivating the Windows Media Player Network Sharing Service...Thanks Mate!bookie32
Tripredacus Posted February 21, 2012 Posted February 21, 2012 On my TS Properties, on the OS Info tab. I press "Edit Unattend.xml" which will open the XML in WSIM. I see that in the OOBE object, the NetworkLocation default value is "Work." Try changing this to Public and try again.
bookie32 Posted February 21, 2012 Author Posted February 21, 2012 Hi mate!OK as soon as I get a mo I will try that....and get back to you.Thanks!bookie32
bookie32 Posted February 21, 2012 Author Posted February 21, 2012 Hi again!OK the only settings under that are Home, Work, and other, so I have set it to other to try that....bookie32
Tripredacus Posted February 21, 2012 Posted February 21, 2012 Hi again!OK the only settings under that are Home, Work, and other, so I have set it to other to try that....bookie32Yes, sorry. I don't know why the Unattend setting uses different words than what actually shows up on that screen.
bookie32 Posted February 21, 2012 Author Posted February 21, 2012 Hi mate!No worries...I diactivated the media service as stated in a previous post and then changed the Unattend settings to "other" and that did the trick OK! now I need to test the wim on a different computer and we are starting to get somewhere.....YES!Nice find mate!Thanks a bunch I have logged back into the computer after syspreping it and all my programs are working fine....Now to deploy the wim to my main computer and get back to some real work....lolbookie32
bookie32 Posted February 22, 2012 Author Posted February 22, 2012 Hi again Little update...I deployed my wim with one error and that image I am adding here for someone to comment on? I need to add some info to my Deployment TS because after deployment I was logged in as Administrator and then after reboot my account showed up I also have checked my drive and found that I have a BDEDrive of 300mb's which is after my "C" drive? I did not think about the system drive when capturing C: so perhaps someone could explain that to me...I do understand that I need to add some info to setup partitioning etc in the unattend file...if someone can help me with that?So, the deployment was successful, but a little work needs to be done to clean up the deployment a little...bookie32
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