Troubleshooting Tips

If a Windows client is discovered but not installed:

• Verify that the Windows Networking Logon Client Installation method is initiated for the site in the SMS Administrator console.
• Verify that SMSls.bat is in the user’s logon script.
• Verify that the prospective client’s IP address or IPX network number is within the IP subnet or IPX network number range specified in Site Boundaries in the SMS Administrator console.

  At the client, examine the Wn_logon.log file to determine which IP subnets the client found from its network configuration. Verify that the site boundary assignments have been copied from the site control file to the information stored for the site in the Netconf.ncf file in the \\<LogonPoint>\SMSLogon\Sites\<SiteCode>\ directory. You can open the Netconf.ncf file in Microsoft Notepad, but do not attempt to change this file directly.

• Check the SMS\Logs\NTlginst.log file on the site server to see if the discovery data record (DDR) was received and processed. Installation will not occur if the DDR for the discovered computer has been rejected.
• Determine whether the user who is logged on to the prospective client has administrative rights to the local computer. If not, examine the Ccm.log file at the site server to verify that Client Configuration Manager is running and has administrative rights to the prospective client.

  If the user who is logged on to the prospective client does not have rights to the workstation, check for a Bootstrap service on the client. Client Configuration Manager installs and starts the Bootstrap service on the client in order to install the client components. When Client Configuration Manager accesses the client successfully, it creates a Wnremote.log file on the client.

• Verify that the SMSCliSvc account is a member of the Local Administrators group on the client.
• Confirm that the user on the prospective client has sufficient privileges to edit the registry.
• Verify that permissions on the Netlgon Share have been set to Everyone: Read. Verify that permissions on the CAP_<Site_Code> Share have been set to Administrators: Full, Guests: Change, and Users: Change.
• Verify that Copy Queue copied SMS 2.0 client components from the client access point (CAP) to the client by checking the client’s Cqmgr32.log.