SMS Installation
SMS Installation
(OP)
I'm curious if anyone else has this issue:
I have implemented/installed SMS 2.0 into several companies over the past year. In every case I get about a 92%-96% penetration, meaning that the SMS clients fully configure as a SMS client, all the components work on the client, and they show up correctly in the collection (domain, etc..)
I have never achieved this at 100% and always have to re-install those clients, or send ddr files using the addsysgui tool on BOK4.5.
I have SMS set up thus:
Windows Networking Logon Client Installation and Windows Networking Logon Discovery are enabled, updating logon points every 2 hours, not modifing logon scripts.
I install the clients using custom .bat or .kix files that search the client for %systemroot%\smscfg.ini and call the smsboot1.exe file for installation.
Lately I have modified the scripts to search for the clicomp directory .exe files (hiv32.exe,sinv32.exe, Wuser.exe,etc..) and recalling the smsboot1.exe if any of these are missing.
So, what are all of you doing? Is this pretty much normal? I (unfortunately) have always been on my own with SMS and would really like some feedback on this.
Thanks all!
I have implemented/installed SMS 2.0 into several companies over the past year. In every case I get about a 92%-96% penetration, meaning that the SMS clients fully configure as a SMS client, all the components work on the client, and they show up correctly in the collection (domain, etc..)
I have never achieved this at 100% and always have to re-install those clients, or send ddr files using the addsysgui tool on BOK4.5.
I have SMS set up thus:
Windows Networking Logon Client Installation and Windows Networking Logon Discovery are enabled, updating logon points every 2 hours, not modifing logon scripts.
I install the clients using custom .bat or .kix files that search the client for %systemroot%\smscfg.ini and call the smsboot1.exe file for installation.
Lately I have modified the scripts to search for the clicomp directory .exe files (hiv32.exe,sinv32.exe, Wuser.exe,etc..) and recalling the smsboot1.exe if any of these are missing.
So, what are all of you doing? Is this pretty much normal? I (unfortunately) have always been on my own with SMS and would really like some feedback on this.
Thanks all!
Talk To Other Members
RE: SMS Installation
I am currently running sms 1.2 and planning to upgrade to 2.0.
1.IS there a controlled way of installing the clients rather than upgrading the entire company at the same time ?
2.Can this be controlled at machine or machine groups level ?
3.Can i disable the smsls.bat from the existing login script and then use remote install ?
4. Would the upgrade upgrade the Logion servers also ?
5.we have control panel disabled thro policy,how do i give the users access to the sms icons ?
I'd like some inputs from you . Thanks again.
Cheers,Padhu