[VINCIE007]

Hello,

I wanted to ghost an XP pro pc to be used my base build for other XP pro pcs. I use sysprep and ghostpe 2004. Once ghosted the pc gets DCOM errors.
Event id: 10020

Does anyone know how to fix this error or suggest a better way to clone XP pro so I an regenerate the SIDs?

Thanks in advance

[Advertisements]

1: Please note that you have to buy a license for each of the other computers.

2: There is a very good chance that it will not work on other computers because the hardware is different. This can be overcome by performing a repair installation on the other computers and installation of their motherboard and other hardware drivers.

[The Skeptic]

1: Please note that you have to buy a license for each of the other computers.

2: There is a very good chance that it will not work on other computers because the hardware is different. This can be overcome by performing a repair installation on the other computers and installation of their motherboard and other hardware drivers.

[VINCIE007]

Hello,

Exact same MB and hardware in each pc, I use a different key that is on the side of each case during the XP mini-setup and the pc activates successfully each time. The only error after the cloned\ghosted install is a DCOM 10010 error.

Thanks

[The Skeptic]

Do you have all windows updates installed?

[happyrock]

if you are seeing those errors in the event viewer log only and not having any issues you can ignore them...
if you are having issues try this..

Click on Start ... Click on Run...

Type in following command in the text box provided in the Run window.

regsvr32 C:\WINDOWS\system32\wbem\wmidcprv.dll

press Enter ...

Once you receive the confirmation message, follow same steps above to register the second file.

regsvr32 C:\WINDOWS\system32\wbem\wmiprvsd.dll

[VINCIE007]

Hello,

All the windows updates were installed before it was cloned\ghosted.

I'll try registering the wmidcprv.dll driver.

Also, the pc is on a network and is sent user and group policies.

Thanks

[VINCIE007]

Hello,

Error is fixed, adjusted permissions using dcomcnfg.

Thanks

[Ztruker]

Can you explain exactly what and how you did this please? I'd like to learn and it could be of use to others.

Thanks,