Upgraded to SCCM 1906: Client Registration Errors

Dujon Walsham • 8 October 2019

Issue

Once upgraded to SCCM 1906, when building a machine in SCCM for whatever reason you may choose to delete the device from the system or may have machines that contain multiple network adapters which you may want it to register with a different physical/IP address.

Once you delete the machine from SCCM and try to re-register back you may encounter issues.

Investigations within the logs primarily the ClientIDManagerStartup.log located in the C:\Windows\CCM\Logs folder of your SCCM client.

Reason

The client machine normally checks to see if it is already registered within SCCM when it does exist within the console, but in this case after you have deleted the machine and can no longer be seen in the database you may still see messages like this.

The file in question which is normally used to see if the client is already registered is the C:\Windows\SMSCFG.ini file which contains all of the unique SIDs specifically for that client machine.

You can use a query such as select * from vsms_r_system where name 0 = ‘’ to check that your device is gone from the database and you will see it’s not there, but since the upgrade the functionality where the sync between the client and SCCM seems to have broken.

Solution

When upgraded to SCCM 1906, in your SCCM console in the Administration tab under the Updates and servicing you will see a hotfix for Confguration Manager 1906 Hotfix Rollup (KB4517869)

This Hotfix actually details the exact issue described within the support information.

I recommend installing this hotfix as soon as possible to avoid having this issue once you have completed your upgrade to 1906.

Optional Workaround

If you are not in a position to install the hotfix as of right now or experience this issue in other ways there is a workaround for this.

1.Delete the C:\Windows\SMSCFG.ini file

2.Reboot the machine

3.Open the Configuration Manager Applet in the control panel – System and Security

4.Go to the actions tab and run the following policies
Discovery Data Collection Cycle
Hardware Inventory Cycle
Machine Policy Cycle

Approximately after 15 – 30 minutes the C:\Windows\SMSCFG.ini file will regenerate and looking at the C:\Windows\CCM\Logs\ClientIDManagerStartup.log should start to see lines of a new registration.

Microsoft Endpoint Manager: In-Place Upgrade or Side by Side Part 4 - SQL Server Requirement Analysis

by D Walsham • 13 December 2021
Looking through the current SQL Server topology and how it affects our decision

Microsoft Endpoint Manager: In-Place Upgrade or Side by Side Part 3 - Current Branch Upgrade Approaches

by D Walsham • 19 November 2021
Impact of Current Branch Upgrades

Microsoft Endpoint Manager: In-Place Upgrade or Side by Side - Part 2 - Operating System Considerations

by D Walsham • 29 October 2021
Introduction

Microsoft Endpoint Manager: In-Place Upgrade or Side by Side

by D Walsham • 7 October 2021
Introduction

Endpoint Manager: Device Estate Cleanup

by D Walsham • 6 October 2021
Introduction

Modern Workplace Management: Creating Applications Common Practices - LOB vs Win32 Package

by D Walsham • 3 September 2021
Introduction

Modern Workplace Management: Build Endpoints Without SCCM Part 6

by D Walsham • 12 August 2021
All the parts of the series we went into great detail about how we analyse an end to end solution and how we would design a solution in which would allow us to build endpoints without SCCM being a dependency. Whilst we did this, there is another scenario which we have not touched on yet, which is the hybrid scenarios. In a perfect world ideally you would have your Azure Active Directory within the cloud, every machine meets the recommended requirements for Windows 10, everything is imported into Intune/Autopilot and everyone is happy. But we know this isn't realistic in all cases. Many organisations cannot just simply up and go from on-premise into the cloud therefore the checkpoint here is of course getting into hybrid solutions such as; Co-Management Between Intune and SCCM Hybrid AD with Azure AD and On-Premise AD syncing together These things can play a very interesting part in how you would tackle this if you envisage the next step in the blueprint is to be in a position in which you can build and manage endpoints soley within Intune. With this final part of the series we will go in-depth in how the common hybrid setups look like and how we go about moving into the next step of being able to manage and build devices without SCCM.

Modern Workplace Management: Build Endpoints without SCCM Part 5

by D Walsham • 29 July 2021
In continuation from the previous part where we had discussed how we create the "on site" piece of the solution, this was the part which would allow us to get our endpoints into a state in which they would essentially be ready to go through the Autopilot process. Which leaves our next piece of the puzzle, to begin the configuration of the actual backend side that resides within our Endpoint Management console. And you will see how everything ties up together to satisfy the full end to end process of getting an unknown (or known) device to proceed thorough the whole workflow to be finally managed by Intune without the aid of SCCM taking part in any of the prerequisites or preparation at hand.

Modern Workplace Management: Build Endpoints without SCCM Part 4

by D Walsham • 15 July 2021
In this part we are now going to look into the technical step by step points on how we put everything together. In the previous part we spoke about the structure of how we would asses whether a machine was actually ready to be built with Autopilot or not with a build checklist process which would step through all areas which would cover an endpoints eligibility. Now with everything planned out we finally want to step into making things reality by putting everything together.

Endpoint Manager: Find machines not in Autopilot

by D Walsham • 2 July 2021
When it comes to managing your endpoints in endpoint manager, one of the things you may be looking to do is to get all of your Intune registered machines to also be enrolled as Autopilot devices. Now we can of course just have the deployment profile deployed to all machines and then hit the "Convert targeted machines to autopilot" but this might not necessarily be feasible for every client. We may want to perform some due diligence first so we can at least understand what devices in Intune are not in Autopilot.
Show More