Problem with SCCM 2007 Client checking in
I posted this yesterday on the wrong forum, but here is the scenario(BTW I'm new to the SMS/SCCM world). I've been installing the client as a admin directly on the client computer. We have a working SCCM 2007 Mixed Site and have a number of clients that have not checked in or the client isn't installed correctly. 1. Is there a way to force the client to register/check in with the server? 2. Which log can I check or how can I verify the client is insatlled correctly? Currently it's taking over 6 and upto 24 hours to get the clients registered. Also these are Vista SP2 Enterprise clients and W2K8 Server Tom Gaul
May 18th, 2011 10:05am

Hi Tom 1.Configure Boundary properly,Install Client with Site Code in command,Extend ADSchema. 2.CCMsetup.log,ccmexec.log,clientlocation.log. Regards Karthick V
Free Windows Admin Tool Kit Click here and download it now
May 18th, 2011 10:22am

Which client install method are you using? The clients should check-in just after installation. Make sure they are getting a site code when you install them. On the client you can check C:\Windows\System32\ccmsetup\ccmsetup.exe to make sure they installed. Or simply open the control panel and check for the configuration manager icon. Open that up and force a machine policy retrieval action. John Marcum | http://myitforum.com/cs2/blogs/jmarcum/|
May 18th, 2011 10:24am

I'm doing a manual install from the "ccmsetup.exe on the SCCM server. I can check tbe SMSCFG.INI file and see that it's installed and go to the applet in control panel and see that all the properties (site name, client version, UID etc). I ran the Discover Data Collection Cycle from the action menu. I have the Configuartion Manager Console open and refereshed the "All Systems" collection and this lient is not there. I guess one of my questions is - is there a better way to tell that the client and server are communicating? We have many systems that aren't in a the All Systems collection and I'm running through a re-install of the client and end up waiting over night to verify that they're in the collection before getting it back to the user.Tom Gaul
Free Windows Admin Tool Kit Click here and download it now
May 18th, 2011 4:32pm

look at clientlocation.log(site assignment tasks.) and locationservices.log(Records attempts to find management points and distribution points.). also check inventoryagent.log on the client side .//Eswar Koneti @ www.eskonr.com
May 19th, 2011 5:37am

I assume you are updating the collection and refreshing it? John Marcum | http://myitforum.com/cs2/blogs/jmarcum/|
Free Windows Admin Tool Kit Click here and download it now
May 19th, 2011 9:12am

Yes, I've refreshed the collection a number of times. I installed the client yesterday morning and I didn't see it till this morning. But when I check the resource explorer for the last software scan it was done with in an hour or so of the installation. What we are trying to accomplish is, when we image a new machine (or re-image and older one) is get it into the SCCM/WSUS and ePO databases and verified prior to releasing them to the customer. This is a US .mil enviroment and we have to comply with IAVA policy within a 15-20 day period. So verifying the client is talking to get patched on time is very important.Tom Gaul
May 19th, 2011 12:43pm

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

Other recent topics Other recent topics