Troubleshooting Tips

If a 16-bit Windows client is discovered but not installed as a client:

• In the SMS Administrator console, verify that you have initiated the Windows Networking Logon Installation method. Examine the NTlginst.log file to verify that the site boundaries and assignment list at the logon point are up to date.
• 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 Cliex16.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.

• If the client is assigned to the site, examine the Clicore.log file to verify that the Client Core component installation process (Clicore.exe /Full) is called.
• Check the SMS\Logs\NTlginst.log on the site server to see if the DDR was received and processed. If the DDR for the discovered system has been rejected, installation will not occur.