Office 2007 Pro Plus deployment
I have a very interesting issue regarding Office 2007 Pro Plus deployment and I'm hoping someone here can help me out.
The issue pertains specifically to users who have Office 2003 already installed and I've tested it with two methods of deployment.
Method 1
Remove Office 2003 from the GPO and set it to uninstall immediately from all users
Place Office 2007 in the GPO
Result for Method 1
Office 2003 uninstalls, but during the Office 2007 install I receive an error stating something to the effects of, "the memory could not be written".
I'm asked to either click OK to cancel the installation or DEBUG.
Clicking OK will bring me to the login prompt, but once logged in, the user has no Office applications. However, if the user restarts again, Office 2007 will install without error. Obviously, this is a pain to convey to users and we would most likely receive a ton of phone calls from users telling us they don't have any Office apps.
If I hit DEBUG, the application just hangs and I never get to the login prompt.
Method 2
Place Office 2007 in the GPO and the GPO recognizes it as an upgrade to Office 2003
Result for Method 2
All Office 2003 applications are successfully upgraded to 2007, except for Outlook. Any idea why that would happen?
If anyone could lend me some insight on how to resolve this issue, it would be greatly appreciated.
The issue pertains specifically to users who have Office 2003 already installed and I've tested it with two methods of deployment.
Method 1
Remove Office 2003 from the GPO and set it to uninstall immediately from all users
Place Office 2007 in the GPO
Result for Method 1
Office 2003 uninstalls, but during the Office 2007 install I receive an error stating something to the effects of, "the memory could not be written".
I'm asked to either click OK to cancel the installation or DEBUG.
Clicking OK will bring me to the login prompt, but once logged in, the user has no Office applications. However, if the user restarts again, Office 2007 will install without error. Obviously, this is a pain to convey to users and we would most likely receive a ton of phone calls from users telling us they don't have any Office apps.
If I hit DEBUG, the application just hangs and I never get to the login prompt.
Method 2
Place Office 2007 in the GPO and the GPO recognizes it as an upgrade to Office 2003
Result for Method 2
All Office 2003 applications are successfully upgraded to 2007, except for Outlook. Any idea why that would happen?
If anyone could lend me some insight on how to resolve this issue, it would be greatly appreciated.
0 Comments
[ + ] Show comments
Answers (3)
Please log in to answer
Posted by:
FunWithApps
16 years ago
In my setup customization, I have the install automatically remove any office 2003 products. That way everyone gets a clean install of 2007, and the install is smart enough to migrate the outlook 2003 settings.
If you do a setup.exe /admin from the command line, it will bring up the customization tool. The resulting MSP file goes in the Updates folder.
Then when you run setup, it will automatically apply any changes found in the Updates folder.
Can you just run the app install of 2007 from the GPO, and not worry about the 2003 uninstall from GPO?
Hope this helps!
Diane
If you do a setup.exe /admin from the command line, it will bring up the customization tool. The resulting MSP file goes in the Updates folder.
Then when you run setup, it will automatically apply any changes found in the Updates folder.
Can you just run the app install of 2007 from the GPO, and not worry about the 2003 uninstall from GPO?
Hope this helps!
Diane
Posted by:
alanho
16 years ago
I tried using the Office Customization Tool, but I get the same results as in Method 2. All Office 2003 applications are successfully upgrade to 2007, except Outlook, which remains Outlook 2003.
Posted by:
FunWithApps
16 years ago
If you customize a second app, where you only remove outlook 2003, and then install 2007, does it fail? Instead of running it from GPO, set the app to show an interface, and run it manually from the workstation (you would need to take your original customization out of the updates folder though)
If there is something running that is a component of outlook 2007 (but I can't think of what that would be) that is hosing the install, but rebooting after it removes everything (in method 1) clears whatever it is.
Good luck with it, let us know what it turns out to be.
Diane
If there is something running that is a component of outlook 2007 (but I can't think of what that would be) that is hosing the install, but rebooting after it removes everything (in method 1) clears whatever it is.
Good luck with it, let us know what it turns out to be.
Diane
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.