|
|
|||||||
We are planning to upgrade all our workstations to sp4 for Win2k. Below a little script for anyone who is interested. Servicepack should be unpacked first. Options for silent, unattended, etc... -u = unattended mode -f = force other applications to close when system shuts down after install -n = do not backup file for un-installation -o = overwrite OEM file without prompting -z = do not restart when install is complete -q = quit mode (no user interaction) -l = list installed hot fixes -s:dir = integrate service pack files into dir -d:dir = backup files onto dir Options can be ussed with this part of the script. code:Full script.Shell '\\servername\sharename\i386\update\update.exe' code:;=============================================================================================== [ 11. July 2003, 10:49: Message edited by: R2D2 ] |
||||||||
|
|
|||||||
not doing a quiet install? |
||||||||
|
|
|||||||
I'm doing a silent install with the -f, -n, -o and -q options. Never underestimate the stupidity of a user, so our workstations are updated without any user input. Same goes for the Acrobat 6 update we are doing. Script available here. This is just the basic script with no options set so anyone can choose it’s own settings. |
||||||||
|
|
|||||||
you are? so why this script is full of output? and it even asks the user if he is willing to do it |
||||||||
|
|
|||||||
you may want to extract the files to the client machine (c:\winnt\sp4) and have it run the update.exe from their PC. win2ksp4_en.exe -u -x:%windir\sp4 %windir\sp4\i386\update\update.exe -f -n -o -q If there is a case of installing a new device or software option, and the system wants the sp4 files you will be SOL without it. |
||||||||
|
|
|||||||
Ok, ok Lonkero your right. But this is just for testing if it works. All message boxes and stuff can be removed for an actual silent install. Leaving the code:in might be handy so users know what is happening before calling the helpdesk with the "Some stupid window is open on my computer please get your f@#&^%% hands out of my computer" question.?'Installing Windows 2000 Servicepack 4, please wait.....' Like I said this is the basic script, feel free to customize it to your needs. [ 11. July 2003, 12:13: Message edited by: R2D2 ] |
||||||||
|
|
|||||||
what window? if you run silent install, what is the window you then have? |
||||||||
|
|
|||||||
beyond that... you should replace all those if statements with a select/case structure instead. then replace the select/case with: if $csd and right($csd,1)<'4' do install endif |
||||||||
|
|
|||||||
As far as I know a command prompt is always open when you run a kix script. Maybe with MS SMS or something it can be forced to run in the background so there will be no screen output at all. |
||||||||
|
|
|||||||
oh, you are one of those that do not know! wkix32.exe (renamed after some beta state of 4.00) is fully windowless. the name was changed to wkix32 to keep the kix32 same as the old 3.xx style. anyway, it creates window only if you output something to the console-screen. and that is why I have been using it for my logonscripts for about 1,5 years |
||||||||
|
|
|||||||
I would also not run it while users are logged into the computer. Rather schedule a silent install from an administrative computer via Task Scheduler at night and have the computer reboot automatically. Additionally, the service pack install has to run under amdin privileges anyway, and when using the Task Scheduler as potentially logged-in user would not see the install anyway as a different account is being used. |
||||||||
|
|
|||||||
Well we don't have our machines running like Jens and we do perform rollouts during LOGON. Our users typically are Administrators on their local system. R2D2 Take a look at this script and see if there is anything you might want to use in yours or see what you might have forgotten to check. http://www.kixtart.org/cgi-bin/ultimatebb.cgi?ubb=get_topic&f=2&t=004424 |