We encounter the same issue in our organisation.
Is there any way to force a 'heartbeat' check on demand (from the SCCM Console or the target machine)?
I have found sometimes running Client Notification > Collect Discovery Data from the SCCM console from right click menu on a device host entry or the ConfiMgr Actions on the target host forces SCCM to recognise the new name, but not always (I understand the Device Discovery Action does the trick, but on endpoints when I do this I tend to run them all as well as the compliance checks in the 'Configuration' tab of the ConfMgr client applet in the Control Panel).
Why this does not work 100% of the time interests me. The devices I am doing this on appear connected (green tick) on the SCCM console, so I assume the endpoint clients are active/seen.
Why we rename
We lease computers and they need to be changed when the leases expire.
On-prem machines have names that suit their location. These do not change (but the hardware does).
In high profile spaces (used often/hard to book out) where the machine uptime needs to be near 100% we rename the old ones adding a letter to indicate it is being swapped imminently.
Once the old ones are renamed, new machines can be imported to SCCM with the correct names, then imaged and software deployed in our IT office/work area and then replaced when the target location has an opportunity window.
Renames are done manually on the old/outgoing target machines (AD and Intel EMA Server entries update immediately).
Andreas
