System Center Configuration Manager TechCenter >
System Center Configuration Manager Forums
>
Configuration Manager Operating System Deployment
>
Known and Unknown Computer Name
Known and Unknown Computer Name
- Hi,
I am interested to know how SCCM deals with OSD when it comes to imaging a KNOWN computer object and changing of its computer name.
Example:
Computer Name = PC1
Mac Address = 00:11:22:33:44:55
PC1 is in the SCCM database as an approved active client computer / agent. I want to re-image PC1 so I advertise a task sequence to it with the OSDComputerName variable set to NULL. The install will prompt me for a computer name (I enter PC2). When the OSD process is finished, PC2 is now reporting back to SCCM with the same
MAC address 00:11:22:33:44:55 but with a different computer name PC2. Will SCCM discard the old PC1 entry and replace it or will there be orphaned objects somewhere.
FYI, i have a custom variable setup for the Unknown Computers Collection with OSDComputerName set to NULL so that any unknown computer will be assigned a valid computer name prior to setup completing. This is working great and I want to apply a similar process for KNOWN computers.
Thanks!
Answers
- Manual intervention in the form of going to the conflicting records node and right-clicking on entries to choose an action. Here are a couple of links with better info:
http://technet.microsoft.com/en-us/library/bb693963.aspx
http://www.myitforum.com/articles/42/view.asp?id=10988
Jason | http://myitforum.com/cs2/blogs/jsandys | http://blogs.catapultsystems.com/jsandys/default.aspx | Twitter @JasonSandys- Marked As Answer byMikeFi Friday, November 06, 2009 4:48 PM
All Replies
- In the scenario described above, the result is based upon your duplicate GUID setting: either it will create a new resource and mark the old obsolete or it will create an entry in the conflicting GUID node awaiting admin intervention.
System names are not unique identifiers in ConfigMgr, resource GUIDs are. ConfigMgr will match the old resource and the new based on the hardware ID which is a unique hash value created from identifying hardware characteristics of the system involved. Since it's the same system, the same hash will be created before and after the imaging process. However, the SMS UUID/GUID will be recreated thus resulting in either the new record or the requirment of manual inetervention based upon your policy.
Jason | http://myitforum.com/cs2/blogs/jsandys | http://blogs.catapultsystems.com/jsandys/default.aspx | Twitter @JasonSandys "However, the SMS UUID/GUID will be recreated thus resulting in either the new record or the requirment of manual inetervention based upon your policy ."
The hash will remain the same correct.
?, when you say manual intervention are you referring to manually removing any marked obsolete data if the old ones persist? What should i look out for so i don't generate duplicate records?- Manual intervention in the form of going to the conflicting records node and right-clicking on entries to choose an action. Here are a couple of links with better info:
http://technet.microsoft.com/en-us/library/bb693963.aspx
http://www.myitforum.com/articles/42/view.asp?id=10988
Jason | http://myitforum.com/cs2/blogs/jsandys | http://blogs.catapultsystems.com/jsandys/default.aspx | Twitter @JasonSandys- Marked As Answer byMikeFi Friday, November 06, 2009 4:48 PM
http://technet.microsoft.com/en-us/library/bb693963.aspx
Exactly what i was looking for! Thanks for getting me in the right direction!
