Fatal Error Occurred while trying to sysprep the machine

[nice_guy75]

Hi guys,

I am trying to create a customized windows 7 Ultimate installation DVD, after customizing and installing softwares when I tried to sysprep my OS I am getting an error

"A Fatal Error Occurred while trying to sysprep the machine."

Here is log:

2010-02-02 19:07:53, Error [0x0f0085] SYSPRP LaunchDll:Could not load DLL C:\Program Files\Common Files\Microsoft Shared\Ink\IpsMigrationPlugin.dll[gle=0x0000007e]

2010-02-02 19:07:53, Error [0x0f0070] SYSPRP RunExternalDlls:An error occurred while running registry sysprep DLLs, halting sysprep execution. dwRet = 126[gle=0x0000007e]

2010-02-02 19:07:53, Error [0x0f00a8] SYSPRP WinMain:Hit failure while processing sysprep cleanup providers; hr = 0x8007007e[gle=0x0000007e]

Please help me guys.

[Tripredacus]

What is in your setupact.log file? There may be more information there.

Also, did you remove that DLL either physically or in the registry at all? Also, what programs are you installing before running sysprep? Would one happen to be anti-virus?

[MrJinje]

"Custom DVD", ok I see, don't think we ever found out if you removed stuff with vLite or via any other "Custom" method, if yes, what components did you remove.

Here is his other thread, he was working on sysprep'ing his laptop but sysprep has been throwing this error, I asked him to try installing the same ISO in a VM and report back if sysprep worked or failed. If it doesn't work in the VM then obviously he will need to re-create his DVD before sysprep can work.

http://www.msfn.org/board/index.php?showtopic=140840

It should be important to note that he does not need to do all his customizations inside the VM, we are simply testing whether or not Sysprep is functional on the DVD or if the problem is only in your laptop.

[nice_guy75]

Thanks guys, I have managed to solve this problem by myself. I only kept the IpsMigrationPlugin.dll in this folder: C:\Program Files\Common Files\Microsoft Shared\Ink\ and my problem is solved.

Thanks to all of you.

[nice_guy75]

I have a new problem with sysprep.

I have created a install.wim of my customized OS, I have customized my OS then I syspreped my OS then capture install.wim (ofcourse booting from winPE)

During customization, I have set all the icons on the desktop (incuding my computer, network, control panel and all and icons of some installed applications as well) but when I capture image after sysprep all the icons from desktop are gone. Theme is also set to the default.

How can I capture image with all the icons on the desktop??????????

Edited February 10, 2010 by nice_guy75

[cluberti]

It's called reading the documentation. Specifically, the <CopyProfile> parameter of your unattended file. If you ran sysprep /generalize (and if you're at least following the sysprep documentation to create a proper image, you did) then it's doing what you told it to do .

Also, you've still not answered MrJinje's question...

[nice_guy75]

I have removed these components:

[Components Removed]

[Accessories]

Accessibility

Character Map

Mobility Center

Speech Support

Welcome Center

[Languages]

Arabic

Brazillian

Bulgarian

Croatian

Czech

Danish

Dutch

Estonian

Finnish

French

German

Greek

Hebrew

Hungarian

Italian

Japanese

Korean

Latvian

Lithuanian

Norwegian

Polish

Portuguese

Romanian

Russian

Serbian

Simplified Chinese

Slovak

Slovenian

Spanish

Swedish

Table Driven Text Input Processor

Thai

Traditional Chinese

Turkish

Ukrainian

Welcome Center

[Multimedia]

Media Center

[services]

Error Reporting

Quality Windows Audio Video Experience

[system]

Natural Language

Reliability and Performance Monitor

Tablet PC

And regarding VM yes on VM as well the sysprep was failing, but now sysprep is not the problem. I have successfully syspreped my OS the only issue left is of icons and some customization (like applying iconpackager theme and OS theme) which I do before sysprep.

Edited February 10, 2010 by nice_guy75

[cluberti]

And regarding VM yes on VM as well the sysprep was failing, but now sysprep is not the problem. I have successfully syspreped my OS the only issue left is of icons and some customization (like applying iconpackager theme and OS theme) which I do before sysprep.

Again:

It's called reading the documentation. Specifically, the <CopyProfile> parameter of your unattended file. If you ran sysprep /generalize (and if you're at least following the sysprep documentation to create a proper image, you did) then it's doing what you told it to do .

Also, you've still not answered MrJinje's question...

[MrJinje]

Another way to capture your user profile before sysprep'ing is to use the Windows Easy Transfer on your DVD, run a capture, then make restoring your profile settings part of your unattend process.

It doesn't even need to be done on the same machine, you can create your profile on a different machine and use your existing install.wim and modify it to install the .mig (windows easy transfer migration file) on first logon via your $OEM$ folder. (or if you have access to USMT that could work too).

Assuming you don't mind having to make an additional reboot after installing, this could be a fix that doesn't require capturing a new sysprep image.

[nice_guy75]

Not at all I don't mind if my system reboot one more time after restoring .mig file. I have already created .mig file when I tried to run that file on the same computer (only for testing purpose) it is opening a window does this mean when I integrate this file in my install.wim the user had to click some buttons in order to get the settings restored or it will be restored silently like silent installers of applications???????????? I don't wish to use OEM folder so is there any alternate method to restore this mig file, like intall folder and cmd file or something like that?????????????

[MrJinje]

Not at all I don't mind if my system reboot one more time after restoring .mig file. I have already created .mig file when I tried to run that file on the same computer (only for testing purpose) it is opening a window does this mean when I integrate this file in my install.wim the user had to click some buttons in order to get the settings restored or it will be restored silently like silent installers of applications???????????? I don't wish to use OEM folder so is there any alternate method to restore this mig file, like intall folder and cmd file or something like that?????????????

I think easy transfer will require some small user interaction (no silent options are known), if you are corporate minded you should be using USMT from the WAIK. It should allow you full automation. Check the WAIK documentation (usmt.chm) for greater details.

$OEM$ folder is just a structure to import files to your image without "mounting/editing" your WIM. If you are more comfortable editing your WIM and placing the files directly inside it, you should be able to script to it's location just the same. (it's all about knowing where the file is when you need to call it from script). Another alternative if you have network access during the install, is to map a drive to your server and run the .MIG from the share.

[just-a-thought]The network option is the best if you have a corporate network, you can point a first login command to a script on your network share, and could update your scripts on the server side without needing to edit your images. Very future proof. [just-a-thought]

[nice_guy75]

Don't we have any alternate method??????????/

I know there is a alternate method but I don't know which. I can't talk about where I have seen other method it is not allowed here.

[MrJinje]

There are 3-4 "alternative" methods listed in this thread. I suggest you pick one and go with it, any one of them should be able to do the trick.

Otherwise, if you can't talk about where you have seen it, why don't you just go there and maybe those people will know what you are talking about. I'm thinking if they invented a method that works, maybe they are the ones to talk with about it. (or at least PM me a link so I can check it out).

[MrJinje]

Just got your PM, here is my reply.

Since you already sysprepped your machine and cannot go back and re-sysprep without some additional effort. The easiest method will be to mount your Install.wim with DISM (or DISM Tool™) and copy/paste your links to Mount\Users\Default\Desktop.

[nice_guy75]

Just got your PM, here is my reply.

Since you already sysprepped your machine and cannot go back and re-sysprep without some additional effort. The easiest method will be to mount your Install.wim with DISM (or DISM Tool™) and copy/paste your links to Mount\Users\Default\Desktop.

I have also replied to your PM.

There is no problem at all I have a copy of pre-syspreped version of my OS, so I can also start my work before sysprep.

And one more thing I have noticed that I am unable to sysprep my OS once again when I tried to install my syspreped version of my OS. Well that is not so improtant as I have a copy of pre syspreped version of my OS as well.

Edit: Please see this link is it worth considering?????????????????

Edited February 13, 2010 by nice_guy75