Windows Forum

Ask something
Discussion Locked

Staggering updates with kix scripts

0 helpful
3 replies

by mteal

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

On a network of about 40 people, I wanted to rollout some Office 2000 upgrades. Rather than implement Service Pack 2, which includes the attachment upgrade we don't want to implement, I want to roll-out seven separate upgrades.

We have an existing logon script written using kixtart.

The proposed script for the roll-out is:
if $ras=NO
if exist("c:\flags\office2000.0004")=0
run ?@lserver\netlogon\Files\Office2000\of9data.exe /q?
run ?@lserver\netlogon\Files\Office2000\out2ksec.exe /q"run ?@lserver\netlogon\Files\Office2000\Uactlsec.exe /q"
copy "@lserver\netlogon\Files\Office2000\office2000.004" "c:\flags"
endif
endif

My question is regarding 'staggering' the rollout.

Is there an easy way to limit how many users are rolled-out per day?

Also, a couple of these upgrades reboot after installing. Is there a way to implement all of the upgrades at once and have a single reboot at the end?

3 replies

by ewing bettles

You might want to create a Domain Group (i.e. ROLLOUT) for your rollout and then place all the users that you wish to rollout to that day in that group. In the Kixtart script you can check for that group membership using the INGROUP function.

Adding to your code:

if INGROUP(ROLLOUT)
if $ras=NO
if exist("c:\flags\office2000.0004")=0
run ?@lserver\netlogon\Files\Office2000\of9data.exe /q?
run ?@lserver\netlogon\Files\Office2000\out2ksec.exe /q"
run ?@lserver\netlogon\Files\Office2000\Uactlsec.exe /q"
copy "@lserver\netlogon\Files\Office2000\office2000.004" "c:\flags"
endif
endif
endif

You could also add a bit of code to add the userid to a commonly located network log file when they have run all or part of the script. This would give you some centralized tracking of the install progress.

As for reboots, unless there's a NOREBOOT flag of some sort for each of the Office executables you've listed, like the QUIET flag (/q) that you've used, I don't think you will be able to get past it using just the scripted install via Kixtart. You would need to build some sort of custom install package, like a .msi install, and then ship it via the script.

Hope this helps, -Ewing

by mteal

Thanks very much for your help.

It's a pity that service pack 2 doesn't give the option to ignore the email attachment update. That way I could only install one file and it should only require one reboot.

This discussion is closed to new replies.