Member "TheVyrys" writes:I have Win2003 servers and Active Directory.....single domain....approx. 100 client computers.....one location. Am upgrading all computers from Office XP to Office 2003.
By submitting your email address, you agree to receive emails regarding relevant topic offers from TechTarget and its partners. You can withdraw your consent at any time. Contact TechTarget at 275 Grove Street, Newton, MA.
The other method I tried was to use group policy and assign the installation. This worked well, but does not support chaining....so I cannot run the updates.....and once again, I can't just supply a path for users to run the updates, because they aren't local admins.
Now for the questions:
Member "joshua2" writes: I give WSUS the thumbs-up. It's easy and effective. WSUS handles Office updates. We run it on a PC class machine and it goes just fine. There are several options for the client that are a snap to set up (such as asking them to restart after a patch, or forcing it). You'll incur the cost of a server license, but as critical as Windows/Office patching is, this expense should readily justifiable.
I think you can run the Office upgrade and then follow up with WSUS patching - especially since you don't have any WAN links to worry about.
Member sagreed writes: Here's some links to MS pages on installs and updates. They cover both install and updating via policy and the various 'sources' I recommend the "administrative image" and "Caching installation files locally" methods if your network can handel the bandwidth requirements.
Using Group Policy to Deploy Office
Strategies for Updating Office 2003 Installations