we had 2 identical workstations. desktop019 and desktop031. last time we had HDD failure on one of workstation (031). becouse we needed it fast we created backup of other (019) workstation and restored on the first one. after this we changed name of this workstation to desktop031 added to domain, asigned IP address. all was good until we noticed that sccm treat both of this mashinas as one. if i install sccm client on desktop019 than we lose connection to desktop031( exacly i will see 2x desktop019. one of them aproved and sccm client instaled, second desktop19 with no instaled sccm client) and thesame if we do oposite. we will lose conection to desktop019 but we will se 2x destkop031. any suggestions?

did you sysprep the computer? http://technet.microsoft.com/en-us/library/cc783215(WS.10).aspx Kent Agerlund | My blogs: http://blog.coretech.dk/author/kea/ and http://scug.dk/ | Twitter @Agerlund | Linkedin: /kentagerlund

we just used windows7 backup and restore tool to make system image. next we restored this image on fixed workstation HDD. than we had to activate windows again. assign diferent IP, AD name. i had checked MAC and it is also diferent. So those are diferent PC now but not for sccm.

That's bad for a lot of reasons and is completely unsupported by Microsoft. You must sysprep a system to remove unique identifiers before deploying a duplicate of that system. There are many unique identifiers, including those used by ConfigMgr, that must be removed or reset. Sysprep does not know about ConfigMgr though so you must take one additional step: http://technet.microsoft.com/en-us/library/bb694095.aspx.Jason | http://myitforum.com/cs2/blogs/jsandys | http://blogs.catapultsystems.com/jsandys/default.aspx | Twitter @JasonSandys

That's bad for a lot of reasons and is completely unsupported by Microsoft. You must sysprep a system to remove unique identifiers before deploying a duplicate of that system. There are many unique identifiers, including those used by ConfigMgr, that must be removed or reset. Sysprep does not know about ConfigMgr though so you must take one additional step: http://technet.microsoft.com/en-us/library/bb694095.aspx.Jason | http://myitforum.com/cs2/blogs/jsandys | http://blogs.catapultsystems.com/jsandys/default.aspx | Twitter @JasonSandys

I am absolutly sure that this is problem with sccm client. we did this procedure many times before (restore backup made from other workstation). we have sccm instaled only month ago. on all desktops (restored previousy or not) sccm client instaled coreclty. there was no problem with duplicate certificates or anything else described in articles you posted above. no problems. no duplicate workstation. ALL WAS OK. this situation diferents only by this that we did mirror WITH sccm client instaled on source PC. we try to uninstall sccm but it as alvays (i asume) lives some trash in registry after uninstall. When we install it again sccm client uses those info again. my question is this : how to pernamently remove sccm client (and all registry keys left by it)?? we used msiexec /x client.msi. but this dont work sa supposed. can you tell what registry keys sccm client create?? how can we clean pc from any sign of sccm client installed?

I am absolutly sure that this is problem with sccm client. we did this procedure many times before (restore backup made from other workstation). we have sccm instaled only month ago. on all desktops (restored previousy or not) sccm client instaled coreclty. there was no problem with duplicate certificates or anything else described in articles you posted above. no problems. no duplicate workstation. ALL WAS OK. this situation diferents only by this that we did mirror WITH sccm client instaled on source PC. we try to uninstall sccm but it as alvays (i asume) lives some trash in registry after uninstall. When we install it again sccm client uses those info again. my question is this : how to pernamently remove sccm client (and all registry keys left by it)?? we used msiexec /x client.msi. but this dont work sa supposed. can you tell what registry keys sccm client create?? how can we clean pc from any sign of sccm client installed?

The proper way to uninstall the client is "ccmsetup /uninstall". But that's moot. What you are doing is unsupported and there are bigger ramifications beyond ConfigMgr. Just because you have done it, doesn't mean you should be doing it. If you don't beleive me, call CSS and ask them.Jason | http://myitforum.com/cs2/blogs/jsandys | http://blogs.catapultsystems.com/jsandys/default.aspx | Twitter @JasonSandys

If you don't beleive me, call CSS and ask them. Jason | http://myitforum.com/cs2/blogs/jsandys | http://blogs.catapultsystems.com/jsandys/default.aspx | Twitter @JasonSandys Now when I have confirmed problems with backup I will try to force a change in the procedure. It is not about beliveing or not. i cant just reinstall PC this is problem and i have to find solution for romoving problem. It is legacy that left me previous admin.