andre9540: If you are interested in automating the process of installing SP3 then I can help you with that. It's really easy and does not require much administration from you at all.
The following assumes that all the PCs are on the same network and that they are reachable by your PC. It also assumes that the administrator password is the same on all PCs.
1. Create a file (lets call it c:\pcs.txt) and dump all of the computer names to it, one per line.
2. Drop to a command prompt.
3. Enter the following "for /f %i IN (c:\pcs.txt) DO copy c:\w2ksp3.exe \\%i\c$\temp\w2ksp3.exe>>cop
ysp3.bat" (without quotations) This will create a batch file with each line reading as follows:
copy c:\w2ksp3.exe \\computer1\c$\temp\w2ksp3.exe
copy c:\w2ksp3.exe \\computer2\c$\temp\w2ksp3.exe
...and so on
This file will copy the service pack locally on the PC. Make sure that you have the original SP3 on your C drive. (c:\w2ksp3.exe)
4. Now do a runas on a command prompt using the administrator account (in case you do not know how... Hold down your SHIFT key and right click on the command prompt icon, or from a command prompt enter "runas /user:localcompname\administrator cmd.exe")
5. In the administrator command prompt enter "for /f %i IN (c:\pcs.txt) DO at \\%i XX:XXpm w2ksp3.exe -u -z -q>>runsp3.bat" (without quotations of course...) This will create a batch file that will create a task scheduler event on each of the PCs. Where XX:XX equals the time such as 10:32am. I would suggest that you have it run sometime in the middle of the night. the -z switch keeps the PC from rebooting so this gives you the ability to do it during work hours. If you choose to do it after hours then you can omit the -z switch and the PCs will reboot after they are done.
at \\computer1 XX:XXpm w2ksp3.exe -u -z -q
at \\computer2 XX:XXpm w2ksp3.exe -u -z -q
...and so on
--------
Now, you have two batch files. copysp3.bat and runsp3.bat
I suggest that you complete copysp3.bat BEFORE you compile runsp3.bat. Remember that SP3 is 100+MB so make sure that your pipe can handle it. If they are all local PCs then you should be OK. If you have remote sites then you may want to look into other means. I have and do use this method quite a bit. I know it to work very well if used right. You may also want to split it into 2 days... running the copy script overnight on one day and then the scheduler script the next. Please let me know if you have any questions. Good luck! Hope you read this before you get too involved doing it the hard way.
