How can I deploy service pack to worksta

One way without any enterprise management software is by packaging the keystrokes with ScriptIt and running from the login scripts.

ScriptIt is available from the Microsoft Website and simulates key presses. So you can automate all the "Next" and"Ok" commands for the patch/Service pack install.
This can be kicked off from the login script so when anyone logs in it checks the patch and then installs if its required.
I've distributes service packs and patches in this manner. Any problems - feel free to mail me.

Unless your users have local administrative rights to their workstations, they won't be able to install MS service packs and/or patches from a login script. Also, most service packs and many patches require a reboot after installation, so this method is tricky at best. There are some third party applications that can do this, although they're not without cost. I can't remember any specific ones at the moment, but there was a review of this type of software in Windows 2000 Mag a few months ago - I'll try to remember to look it up later and post an additional comment on this answer to give you some ideas on this. Hope this helps!

You don't need any tools for this. What you will need is a batch file, and some time (If you don't have batch file scripting experience then nows the time to get some, any admin who can't script frankly isn't an admin - esp with VBscript and wmi scripting becoming more prevalent)). I pushed out NT4 sp5 to 5000 odd workstations situated in some 800 shops in the uk using my desktop and a couple of servers at the customers head office. The first thing you must do is TEST, 'cos if you push the SP out and it breaks anything then you're the one they'll target when finger pointing time comes. Depending on your network layout, make an initial decision as to whether you need to send a copy the service pack to every machine, or whether the clients can run it by connecting to a network share on a server or servers. Your script will copy the file out (if appropriate - mine sent it to one machine in each shop and then had the others run it from there) suggested utility for this is robocopy (reskit). Bear in mind that if you have remote locations, the copies made need to be run overnight, x number of sessions at a time, x days before you upgrade. Remember to do some checking as to whether the file copied successfuly. SP5 (as I recall, it was a while ago now !) required an admin login, so two files were run on the workstation. The first, scheduled via an AT job from a central script, set the autoadmin logon keys in winlogon (this is covered in technet) using reg.exe (reskit), and added the second script to the runonce key in the registry (reg changes made using reg.exe - reskit). then it rebooted the machine (shutdown.exe - reskit).

This question was closed by the author