leaving smssl.bat in logon script after client installation

[Zach Harings]

Do I gain any think from leaving smsls.bat in the clients logon script after
client installation, should this be done.

[Richard Davies]

Zach,

Yes you do. When you install a new workstation, you don't have to remember
to install the SMS software because the first person who runs smsls.bat at
logon does it for you. The overhead that occurs when the smsls.bat runs on a
client which already has the SMS software installed is very minimal.

Regards

Richard Davies
"Zach Harings" <zhar...@tds.net> wrote in message
news:Ov6OrKYV$GA.221@cppssbbsa04...

[Chris Reynolds]

I agree with Richard.
The batch process is minimal overhead in a LAN or local validation
environment. It ensures more than just new client installations or CAP
settings. In will help validate and update any client settings which may
have changed during their 23 hour update period. It's an added bonus of
applying new installations and settings rather than waiting for the many
Executive Services to take care of them on a scheduled or manual
configuration.

Chris

[Tony Neuser]

Zach,

Generally speaking . . . No. If your SMS environment is stable and you
don't plan on adding or moving CAPs the SMSLS.bat file offers existing
clients nothing. When new users are added to the domain and you want them
to receive the SMS client, simply insert the script and then remove it when
the client has successfully installed. Other issues may influence your
decision as well. For example, if you currently do not run any other
scripts, and you can keep your logons script free by removing SMSLS.bat, I
would remove it.

While resources required on a machine that already has the client is
"minimal," this is still relative to current network performance. I've been
in more than one environment where network performance was so shotty that
users had enough time to berate SMS at each logon due to the delay that was
caused. There's also the non-technical reasoning of just making SMS as
trasparent to the user as possible. If you have NT workstations it's not
much of an issue, but if you have Win9.x's, users are reminded that SMS is
there every time that darn DOS box pops up on their screen at logon.

Hope this helps to inform your decision,
Regards,
Tony

[Tony Neuser]

In addition to my standing points, be aware that after the client has been
installed the script has nothing to do with clients being able to receive
site configuration "updates." The CCIM32 process, which initiates every 23
hr. is independent of subsequent logons and is responsible for updating the
client. Once your environment is stable, Microsoft Premier Support
recommends removing the scripts under "normal" circumstances.

Chris Reynolds <crey...@poboxes.com> wrote in message
news:uXSgLE0V$GA.259@cppssbbsa04...