Jump to content


Sign in to follow this  
Tjindarr

Client problems with new SCCM installation

Recommended Posts

Ive just set up a new SCCM server and uninstalled the old one, the reason for this is that the old one was a test from the begining and we implemeted it into our production enviroment becouse lack of time.

 

Now ive setup a new one with server 2008 R2 and the SQL database is on a seperate SQL server 2008R2.

 

The problem im having is that about 70% of the CCM clients are not reporting back to the server that the client is installed.

I´ve checked about 10 computers in our domain and the client is installed the the sitecode is correct.

 

If i go to control panel > Configuration Manager and check under actions i have machine and user policy retrieval.....

When i run these 2 the client shows up as installed on the SCCM console.

Is there a way to trigger these 2 with a login script or a GPO?

 

I really really dont wanna go around starting those actions on 400 computers.

Share this post


Link to post
Share on other sites

Is there a way to trigger these 2 with a login script or a GPO?

 

I really really dont wanna go around starting those actions on 400 computers.

 

 

You can use Right click Tools or simple batch script to restart the SMS agent Host service to look up for changes and assign to New SCCM site server.

Share this post


Link to post
Share on other sites

You can use Right click Tools or simple batch script to restart the SMS agent Host service to look up for changes and assign to New SCCM site server.

 

 

Shouldent that restart when the computer restarts?

Share this post


Link to post
Share on other sites

If i go to control panel > Configuration Manager and check under actions i have machine and user policy retrieval.....

 

This tells me that client is communicating with the server yet. Did you check the logs?

Share this post


Link to post
Share on other sites

I would start with the ClientIDManagerStartup.log, the LocationServices.log and the ClientLocation.log

 

Solved it by adding a login script that initiates the user and machine policy action.

Tried it on a couple of computers and there status quickly changed from "no" to "yes" under client

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
Sign in to follow this  

×
×
  • Create New...