- Make sure the rush network is idle.
To install the new release, you must first stop the old release
network wide. The new version is not backwards compatible.
Weekends are generally a good time to do upgrades.
In the text below, change the red text as needed.
- Verify no jobs are running.
Check the network to make sure no jobs are running with either:
OR
Dump any jobs that are running.
- Install first on the license server.
- Stop the daemon on the license server:
net stop rushd
- Rename out the old release:
cd c:\
move \rush \rush.old
If you get errors during the 'move' about 'file in use'
or 'sharing violation', use the task manager to kill processes
called 'rush', 'rushd', or any rush invoked renders or scripts.
- Extract the new version to C:\rush
- Preserve your previous hosts and license.dat files:
copy \rush.old\etc\hosts \rush\etc
copy \rush.old\etc\license.dat \rush\etc
Manually merge in any custom changes to your rush.conf file, e.g. check
for local customizations to ntrushuid/ntrushgid, and smtpserver/smtpfrom.
Do *NOT* just copy your old rush.conf file into the new release directory.
- Start the new daemon:
net start rushd
- Verify the local daemon is running:
rush -ping
- Upgrade the rest of the net.
To upgrade the other machines is easier, usually just by
having each machine run this batch script:
Network Install Commands
|
net stop rushd
rush -sleep 5
xcopy /s \\masterhost\C$\rush \rush    
net start rushd
|
- Verify the network install is up.
rush -ping +any
..all machines should reply with the same version number.
Any that don't, check the c:\rush\var\rushd.log for errors.
If a machine complains about 'bind(): address in use' for more
than 2 minutes, you may need to reboot that machine.