Jump to content


  • 0
rhumphreys

SCCM Client Active=No

Question

Hi All,

 

I'm having an issue with the SCCM client. Our environment is SCCM 2007 r3, Clients are Windows 7 Enterprise 32-bit.

 

I run a task sequence which installs an existing image package. The task restarts the client in PE, partitions the drive, installs the WIM, applies drivers, adds to the Domain, installs the SCCM Client and configures the client machine.

 

Once the Task has completed for some reason the Client and SCCM server don't communicate. After a little time, I update the update Collection Membership and the client show's Active=NO. At which point I can't apply advertisements.

 

Any help would be greatly appreciated.

Share this post


Link to post
Share on other sites

4 answers to this question

Recommended Posts

  • 0

Hi All,

 

I'm having an issue with the SCCM client. Our environment is SCCM 2007 r3, Clients are Windows 7 Enterprise 32-bit.

 

I run a task sequence which installs an existing image package. The task restarts the client in PE, partitions the drive, installs the WIM, applies drivers, adds to the Domain, installs the SCCM Client and configures the client machine.

 

Once the Task has completed for some reason the Client and SCCM server don't communicate. After a little time, I update the update Collection Membership and the client show's Active=NO. At which point I can't apply advertisements.

 

Any help would be greatly appreciated.

 

 

What have you been done on this (basic Troubleshootings steps) ? You will have to check ccmsetup.log for scucessful installation of Client if it is okay .Check clientlocation.log and locationservices.log as well for other info .

 

Check this link for basic steps to check. http://eskonr.com/2010/11/smssccm-clients-installation-troubleshooting-check-list/

Share this post


Link to post
Share on other sites

  • 0

What have you been done on this (basic Troubleshootings steps) ? You will have to check ccmsetup.log for scucessful installation of Client if it is okay .Check clientlocation.log and locationservices.log as well for other info .

 

Check this link for basic steps to check. http://eskonr.com/2010/11/smssccm-clients-installation-troubleshooting-check-list/

 

Hi Eswar,

 

Thanks for the reply.

 

Ok I have checked the logs.

 

CCMsetup.log - Installation Succeeded.

clientlocation.log - No failures or Errors

locationservices.log - Had warnings and failuers. See bellow........

 

Failed to resolve 'SMS_SLP' to IP address from WINS LocationServices 18/12/2010 2:28:46 PM 3172 (0x0C64)

LSGetSLP : Failed to resolve SLP from WINS, is it published LocationServices 18/12/2010 2:28:46 PM 3172 (0x0C64)

LSGetManagementPointForSiteFromSLP : Unable to get the list of SLPs LocationServices 18/12/2010 2:28:46 PM 3172 (0x0C64)

Failed to retrieve Default Management Point from SLP LocationServices 18/12/2010 2:28:46 PM 3172 (0x0C64)

Failed to resolve 'NLB_TSS' to IP address from WINS LocationServices 18/12/2010 2:29:23 PM 3172 (0x0C64)

Failed to resolve 'MP_TSS' to IP address from WINS LocationServices 18/12/2010 2:29:56 PM 3172 (0x0C64)

Failed to retrieve default MP through WINS. LocationServices 18/12/2010 2:29:56 PM 3172 (0x0C64)

Failed to resolve 'SMS_SLP' to IP address from WINS LocationServices 18/12/2010 2:31:33 PM 1412 (0x0584)

LSGetSLP : Failed to resolve SLP from WINS, is it published LocationServices 18/12/2010 2:31:33 PM 1412 (0x0584)

LSGetManagementPointForSiteFromSLP : Unable to get the list of SLPs LocationServices 18/12/2010 2:31:33 PM 1412 (0x0584)

Failed to retrieve Default Management Point from SLP LocationServices 18/12/2010 2:31:33 PM 1412 (0x0584)

Failed to resolve 'NLB_TSS' to IP address from WINS LocationServices 18/12/2010 2:32:06 PM 1412 (0x0584)

Failed to resolve 'MP_TSS' to IP address from WINS LocationServices 18/12/2010 2:32:45 PM 1412 (0x0584)

Failed to retrieve default MP through WINS. LocationServices 18/12/2010 2:32:45 PM 1412 (0x0584)

Unknown task LSProxyMPModificationTask in non-quarantine - ignoring. LocationServices 18/12/2010 2:32:45 PM 2412 (0x096C)

Failed to open to WMI namespace '\\.\root\ccm' (8007045b) LocationServices 18/12/2010 2:33:34 PM 1412 (0x0584)

Failed to open to WMI namespace '\\.\root\ccm\LocationServices' (8007045b) LocationServices 18/12/2010 2:33:34 PM 1412 (0x0584)

Failed to open to WMI namespace '\\.\root\ccm\policy\machine' (8007045b) LocationServices 18/12/2010 2:33:34 PM 808 (0x0328)

 

Might be also worth noting that the clients end up with a 169 APIPA address. Then once I reboot the clients they obtian a DHCP lease and I then update the ALL SYSTEMS collection and the same client appears twice. One which is active and one which is not.

 

Thanks for you help with this.

Share this post


Link to post
Share on other sites

  • 0

On the Clients - Control Panel , CM (32) , Actions TAB, Discovery Data Collection Cycle , highlight by clicking, Initiate Action

 

Then depending on the Heartbeat Discovery Period , it should appear.

 

I only noticed this today also that all except for the SCCM server are showing as NO, doing the above steps should that work is not a solution when you cant be going around each client workstation do to it.

 

Note: I have previously disabled Windows Fireall via GPO on workstations, so it cant be firewall, even the Kaspersky Client on the workstations shouldnt be able to interfer IMO.

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
Answer this question...

×   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...


×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.