Issue with computer renaming - becomes unregistered on console

[JeffIT]

Hi,

I have just realised that when I rename a computer the Management Console is showing the computer as unregistered. The computer is up to date and seems fine but the console is not able to see it. What do I need to do to rectify this?

[djacobson]

Hi @JeffIT, remove and re-add your AD Group.

[JeffIT]

Hi,

I am on GMT so sorry for delayed response.

I have readded the AD OU and I am still having many laptops show as unregistered even though they are online now and up to date. What can I try next?

[JeffIT]

Hi,

Here is one example where I have a computer that is installed and up to date yet it shows as unregistered on the client tab from the management console.

[JeffIT]

I just got it to show back up. The issue was the MEEClientService was not running. After restarting it it has once again showed up on on management console. I will now check this with all the problem computers and let you know if any issues still occur.

[djacobson]

Good find, that's our comm service, though when it is off, they usually just show as offline, not unregistered. Another thing you may see is laptops may have double entries, one for the ethernet and one for the wifi. Which ever NIC was in use during deployment will have that MAC saved to the machine, when it is on the other NIC, it may show an unregistered entry along with its checked-in entry.

[JeffIT]

Thanks djaconson that is good to know in regards to the double entries.

Can I ask you if setting this service to delayed startup is a workable solution?

The reason I ask is we have quite a few things running at startup which is possibly after creating the issue. Currently we have quite a few computers showing up as unregistered and I am manually logging onto them and starting or restarting this service, as needed, with elevated permissions. I am also looking at a gpo to ensure this service runs so that I can avoid this scenario going forwards.

[djacobson]

If you are on MBMC 1.9, definitely utilize the new service startup type and failure restart options on the general page in policy, this is exactly what those are meant to fix, especially with Win 10.

The startup delay option under the Protection tab is for conflict/performance issues against Anti-Malware's web blocker and malicious file blocker with other security program during logon.

[JeffIT]

I had best update to that version now to fully fix this issue. Thanks once again djacobson.