Installing systems across a network

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.

My project:
Install Office 2003 and all updates remotely without going to each machine.

My progress:
I tried the method of creating a network share with a compressed CD image, and chaining the updates with OHotFix.exe, but the installation and updates both fail if the users are not administrators of their local machine.

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:

  1. Can you send out updates for office with group policy?
  2. Are there any other methods out there that you all use/know to get this done fairly easily?
  3. What about WSUS? Would it be a good solution? I have no experience with it.

    Any ideas? How do you all do it?



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

This was first published in August 2006

There are Comments. Add yours.

TIP: Want to include a code block in your comment? Use <pre> or <code> tags around the desired text. Ex: <code>insert code</code>

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy
Sort by: OldestNewest

Forgot Password?

No problem! Submit your e-mail address below. We'll send you an email containing your password.

Your password has been sent to:

Disclaimer: Our Tips Exchange is a forum for you to share technical advice and expertise with your peers and to learn from other enterprise IT professionals. TechTarget provides the infrastructure to facilitate this sharing of information. However, we cannot guarantee the accuracy or validity of the material submitted. You agree that your use of the Ask The Expert services and your reliance on any questions, answers, information or other materials received through this Web site is at your own risk.