We are having issues with renaming client machines managed by SCCM 2007. When we rename them they show up in the collections but they do not show as having the client installed (in the configuration manager console), there is no information in the database showing the history of the machine (like the patch history or hardware inventory information). We are not deleting the machines in AD simply renaming them. We have our AD discovery occuring twice a day and we have the heartbeat discovery occuring once a day. The client is instaled on the computers and we manually initiated all of the available actions available in the configuration manager client. There is no firewall preventing communication between the computer and the SCCM server.

You should check the timing of the AD discovery vs. the Heart Discovery. The only scenario where I can think of something like that happening is if you rename a computer (whcih in turn renames its account in AD) and then AD discovery sees the renamed computer account and creates a DDR for it which cause ConfigMgr to create a new resource for them. Have you verified that you simply don't have multiple objects for the same system with one being marked obsolete? Try renaming a system and immediately running a heartbeat discovery on that system after it reboots. Jason | http://blog.configmgrftw.com

Thanks for the reply. The devices are being renamed to unique names that have never existed so they are not duplicate entries or another entry that is marked as obsolete. I am not sure how manually kickoff a heartbeat discovery. There is not a "Run Discovery As Soon As Possible" option displayed on the heartbeat properties.

Heartbeats are client intiated on the Actions tab -- it's called Data Discovery cycle there.Jason | http://blog.configmgrftw.com

Heartbeats are client intiated on the Actions tab -- it's called Data Discovery cycle there.Jason | http://blog.configmgrftw.com

Heartbeats are client intiated on the Actions tab -- it's called Data Discovery cycle there.Jason | http://blog.configmgrftw.com

Any errors in PolicyAgent.log?

Any errors in PolicyAgent.log?

Hi, Please see About Heartbeat Discovery Heartbeat Discovery differs from other Configuration Manager 2007 discovery methods because, by default, it is enabled, and it does not discover new resources. When Heartbeat Discovery runs according to the Heartbeat Discovery schedule or when it is initiated from the client, the client sends information to its assigned management point. This action refreshes the client record in the database and enables the client to maintain an active status in the Configuration Manager 2007 database. Without this action, the client record might be aged out or deleted from the database by a site maintenance task. You may go to the following article to configure it: How to Configure Heartbeat Discovery Regards, Sabrina

Hi, Please see About Heartbeat Discovery Heartbeat Discovery differs from other Configuration Manager 2007 discovery methods because, by default, it is enabled, and it does not discover new resources. When Heartbeat Discovery runs according to the Heartbeat Discovery schedule or when it is initiated from the client, the client sends information to its assigned management point. This action refreshes the client record in the database and enables the client to maintain an active status in the Configuration Manager 2007 database. Without this action, the client record might be aged out or deleted from the database by a site maintenance task. You may go to the following article to configure it: How to Configure Heartbeat Discovery Regards, Sabrina

Hi, Please see About Heartbeat Discovery Heartbeat Discovery differs from other Configuration Manager 2007 discovery methods because, by default, it is enabled, and it does not discover new resources. When Heartbeat Discovery runs according to the Heartbeat Discovery schedule or when it is initiated from the client, the client sends information to its assigned management point. This action refreshes the client record in the database and enables the client to maintain an active status in the Configuration Manager 2007 database. Without this action, the client record might be aged out or deleted from the database by a site maintenance task. You may go to the following article to configure it: How to Configure Heartbeat Discovery Regards, Sabrina