The best way I know to troubleshoot client installs is to grab the client logs during the installs. Often, when the client fails to install, it begins, writes an install log (wn_logon.log or other) and at some point a ccim32.log. I have found these the best 2 logs for troubleshooting installs...
I have a Compaq 15/30 External Tape drive and need the Windows 2000 Server drivers. They've been removed from the Compaq web site and that model is now unsupported. Has anyone seen these or know where I can get them?
TIA,
G
Is everything in the same domain? Do you have a valid site system connection account with appropriate permissions? This article explains some of the accounts created by SMS:
http://support.microsoft.com/default.aspx?scid=kb;en-us;199234&Product=SMS200.
Any errors in nt_logon.log on the site server?
When you check the %windir%\ms\sms\core\data\SMSAsign.ini are the clients assigned? Are all options correct in the SMS applet (e.g. Site assignment, components installed)? If you choose repair for SMS Client Base Components e.g., does the component return to "Installed" status? How...
I have one client in one site that will not run advertisements. Clicking on the Advertised Programs icon in CP gives "Failed to connect to the Advertised Program server". Have remove and reinstalled the SMS client Mult times. The SMSAPM32.LOG has the following:
SERVICE ...
Logon installation (Windows Networking Logon Client Installation) will modify logon scripts automatically. Turn on Modify logon scripts on the logon script page for that method...if I understand your question.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.