Deploying Office 2003 Pro Troubleshooting

I'm trying to deploy Office 2003 within our GPO Software.

1. I copied the Office 2003 Pro to a network shared, gave it authenticated user read, and domain users read, prep it with "setup /a"

2. Created a GP on a particular test OU. I will be choosing per computer assignment, not per user.

3. Next I created a MST file to uninstall the old Office XP.

4. Then I create a New Package within the Per Compute (Computer Configuration\Software Setting\Software Installation node). I then enter my path to the shared office installer by UNC

5. Then since I'm using MST, i choose Advance. Then I click the Modification tab and add my .MST file i created with Ork.

I click OK OK OK OK, exit out.

I goto the DC and type "gpupdate", then to the testing client "gpupdate". Reboot the testing workstation and nothing.

Nothing, Nothing, Nothing, Nothing, Nothing!!!!!

What am I doing wrong??

0 Comments   [ + ] Show comments

Answers (7)

Posted by: AngelD 12 years ago
Red Belt
Sounds like you did the right way.
Verify the NTFS permissions on the folder/files and there share.

Check the eventview for any clues.
Run rsop.msc to find out if the group policy is applied for the user/machine
Posted by: techsmith 12 years ago
Senior Yellow Belt
I checked the Event Viewer and it shows a warning EVENT ID 119. Also sometimes there are nothing in the Event Viewer so I assume everything is working? but once I get to the desktop, nothing again and no error or warning in the Event Viewer.

"Software Installation Encounter an Unexpected Error While Reading From the MSI file \\server1\package\pro11.msi. The error was not serious enough to justify halting the operation. The following error was encountered. The operation completed successfully.

But it didn't uninstall my office XP suite and Office 2003 pro was never installed.

RSOP.msc is fine. I checked it on the testing domain workstation.
Posted by: techsmith 12 years ago
Senior Yellow Belt
I just now deleted the Per Computer GP. I created a new GP under Per User with Assign, I even stuck the MST in there.

Results: Office 2003 did get pushed up to the workstation but MST didn't work (didn't uninstall the Office XP suite so I can still open and use Word XP). and Office 2003 didn't get installed automatically but as soon as I clicked a .DOC it then installed.

So why didn't Per Computer work but Per User did? and Also why didn't Per User uninstall Office XP suite since my MST file is correct?

I can rule out the NTFS and Shared permission as the problem on the Per Computer scenario.
Posted by: AngelD 12 years ago
Red Belt
I have no direct answer for you but maybe any of the links below can shed som light

Using Group Policy to Deploy Office

Office 2003 Deployment

Deploying Microsoft Office Using Group Policy

Deploying Office 2003 with Group Policy
Posted by: techsmith 12 years ago
Senior Yellow Belt
I have done tons of reading regarding my situation and for the most part I'm not doing anything wrong.

Currently my deployment of Office 2003 Pro through the GPO is from an exisiting OU.

I read somewhere else I had to create a New OU, create a new policy within this new OU, then proceed to configure the software package under Per Computer.

Then go to the Computer folder under the Doman Root. The Computer folder under the root has all the computer names of all domain workstations. I'm supposed to move which ever computer name I want to deploy into the newly created OU.

How would this step different then what I did above, which I configure the Per Computer under the particular OU I want Office 2003 to deploy?
Posted by: AngelD 12 years ago
Red Belt
You don't have to create a new OU/GPO, use you current OU design.
Posted by: techsmith 12 years ago
Senior Yellow Belt
I do agree with you saying there should be no difference but one works and the other doesn't .

So by creating a new OU with the software installation policy, I then goto the Computer folder and move the computer name icon I want to deploy Office 2003 Pro to, and it works after a "gpupdate", or wait 5 minutes, or reboot twice.

Why this scenario works and the initial scnenario didn't beats me. But i'm happy at least this works, otherwise I had to uninstall Office XP then reinstall Office 2003 for 100 plus machines, forget that!

Since I created the administrative install I'm allow to roll out updates or service packs through the same 2nd scenario (saves me time for managing updates).

But thanks for your help though.
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ