|11 Nov 2011||#1|
| || |
Event 10009 after cloning a windows 7 laptop
I created an image from an existing windows 7 enterprise laptop and used sysprep. However when I restored that image to new laptops I am getting a DCOM error 10009 that "DCOM is unable to communicate with the computer (old name) using any of the configured protocols". There is an end user who has the original computer however I don't want several dozen systems trying to connect to him when he's online. I can do a netstat and see an epmap trying to connect to that computer name. Also I'm worried that I'll have this error if I make another image. I thought sysprep would have scrubbed that out when generalizing. One hint I have is the bluetooth software has the old computer name in the registry, however I removed that info and still get the error. Does anyone know how to fix this and how I can avoid this error if I build another image? Any help is appreciated.
|My System Specs|
|Similar help and support threads for2: Event 10009 after cloning a windows 7 laptop|
|Cloning Outlook 2013 from PC to laptop||Microsoft Office|
|Is this possible? Cloning PC to laptop||Backup and Restore|
|Cloning laptop HDD breaks Win Update and Win Live Mesh||Backup and Restore|
|Cloning program drive and data drives from XP to Windows 7 laptop||Backup and Restore|
|Cloning Laptop HDD||Hardware & Devices|
|[New Windows 7 Laptop] BSOD Kernel-Power Event ID 41 Task Category 63||BSOD Help and Support|
|Cloning a Laptop HDD||Hardware & Devices|
|Our Sites ||Site Links ||About Us ||Find Us |
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.
© Designer Media Ltd
All times are GMT -5. The time now is 10:38 PM.