Delete clients from SCCM console
Hi all,I deleted some clients from SCCM console accidently and did not uninstall SCCM clients Now, these clients re-discovery via SCCM. but SCCM clients status still show "NO". I have wait for 25 hours. What cause that and how can I force a update?Thanks.
September 16th, 2009 5:21am

The client will re-register automatically depending on the site configuration. The easiest way to force a re-register to un-install and re-install the client. That will force the client to re-register with the site server.Gabe Brown, Configuration Manager 2007
Free Windows Admin Tool Kit Click here and download it now
September 16th, 2009 6:19am

DDR's don't work the same way in ConfigMgr 2007 as they did in SMS 2003. These were deprecated in favor of registration messages. See ClientIdManagerStartup.log for more details.Gabe Brown, Configuration Manager 2007
September 16th, 2009 6:20am

Heartbeat discovery would just find the client via discovery again which he has already done, it would not cause it to re-register.Gabe Brown, Configuration Manager 2007
Free Windows Admin Tool Kit Click here and download it now
September 16th, 2009 7:30pm

I agree that's a good article, but it is very short on details of the registration process. We're not disagreeing, we just want more information. My searches have turned up very little about things like when registration occurs? Does it recur? Is there a way to manually initiate it? What information does a registration provide to the server? The SDK has some details, but most are implementation specific and not operationally relevant.Jason | http://myitforum.com/cs2/blogs/jsandys | http://blogs.catapultsystems.com/jsandys/default.aspx | Twitter @JasonSandys
September 16th, 2009 8:18pm

I notice this post is a little outdated and was hopeful to see an update from Carol. I searched the SCCM team blog and did not find any updated documentation regarding client registration. I am new to SCCM and recently inherited an existing 2007 R2 installation. I have a similar scenario as Roger started this thread with. I have about 1% of my clients that have a status of Client=No (value=0) in the console (and I have no historical knowledge as to why). I can resolve most of these with an uninstall/reinstall of the client as mentioned in this thread. That is a little time consuming and through monitoring of the client logs I have noticed that many of the clients think they are registered: "ClientIDManagerStartup.log " RegTask - Executing registration task synchronously. Reg Task: Client is registered, exiting. After performing the client uninstall and then a fresh install I see the following entries: RegEndPoint: Received notification for site assignment change from '<none>' to 'MED'. RegTask: Client is not registered. Sending registration request... RegTask: Client is registered. It would be nice to have a more efficient mechanism to force the registration or in this case the "re-registration" of the client. That being said here is my question. If the client "thinks" it is registered and the console thinks it is not, who wins? Is the client really in an unmanageable state? Thanks, Todd
Free Windows Admin Tool Kit Click here and download it now
July 1st, 2010 6:34pm

Todd, to address your first point - unfortunately Gabe is no longer with this product group (why no blog post to date) but this request is not forgotten and we're looking into finding an alternative source to provide more information about registration.
July 12th, 2010 10:56pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics