How does SCCM handle PC name changes on a client?

[HIMA]

Hi.

 

How does SCCM handle PC name changes on a client?

 

when changed the name of a test machine. I found both name old and new one. However, the old name said it had the client installed, but the new name did not have the client installed.

 

Is there a way configure or repair the client to be enabled and installed on the PC/?

[anyweb]

check the Obsolete status on those pcs, how are they reporting that value ?

[HIMA]

This case not in my environment but it usually happen to me in SMS 2003

 

My question is how the SCCM handle this

[Jimm]

In my case, I see both objects and was able to delete the obsolete objects. Is there a way that this can be done through some sort of scheduled purge within the container? I am also having a similar issue with discovery. My AD discovery gets the device names from a ghost image that is still is use. The PCs join the domain as computer1234. After we place the PC, we rename to the userlast and a dept code. The objects in AD get renamed but the discovery shows errors as it can no longer conenct to device...

 

Jimm