Office 2003 deployment issues

Jason Galbreath · Feb 22, 2005

Our organization is currently in the process of testing the Office 2003
deployment. We have created an admin install point and customized the
installation using OCW. The initial install works fine when run quietly.
We run into problems when Office 2003 is completely un-installed. When the
installation is run again none of the features are re-installed, the office
setup shows X's for all features. The only way I've found to get the
applications to re-install is to run the setup with a full UI and re-check
the boxes for Word, Excel, Outlook, and PowerPoint. This is not a valid
solution for us though since we must have the ability to re-run the
installation in quiet mode. I've tried to un-install using the Remove
button in Add/Remove Programs and with the Remove All button in the Office
2003 Setup.

Any assistance would be appreciated.

Jason Galbreath
Arizona Public Service

neo [mvp outlook] · Feb 22, 2005

Did the site check the option to uninstall the managed software when it
falls out of scope? If yes, just remove the computer/user from the software
install gpo. This will cause the policy module to roll the software install
back. Once that is done, reboot the workstation and then re-add the
user/computer back to the GPO.

neo [mvp outlook] · Feb 22, 2005

Did the site check the option to uninstall the managed software when it
falls out of scope? If yes, just remove the computer/user from the software
install gpo. This will cause the policy module to roll the software install
back. Once that is done, reboot the workstation and then re-add the
user/computer back to the GPO.

neo [mvp outlook] · Feb 22, 2005

Did the site check the option to uninstall the managed software when it
falls out of scope? If yes, just remove the computer/user from the software
install gpo. This will cause the policy module to roll the software install
back. Once that is done, reboot the workstation and then re-add the
user/computer back to the GPO.

neo [mvp outlook] · Feb 22, 2005

Did the site check the option to uninstall the managed software when it
falls out of scope? If yes, just remove the computer/user from the software
install gpo. This will cause the policy module to roll the software install
back. Once that is done, reboot the workstation and then re-add the
user/computer back to the GPO.

neo [mvp outlook] · Feb 22, 2005

Did the site check the option to uninstall the managed software when it
falls out of scope? If yes, just remove the computer/user from the software
install gpo. This will cause the policy module to roll the software install
back. Once that is done, reboot the workstation and then re-add the
user/computer back to the GPO.

neo [mvp outlook] · Feb 22, 2005

Did the site check the option to uninstall the managed software when it
falls out of scope? If yes, just remove the computer/user from the software
install gpo. This will cause the policy module to roll the software install
back. Once that is done, reboot the workstation and then re-add the
user/computer back to the GPO.

neo [mvp outlook] · Feb 22, 2005

Did the site check the option to uninstall the managed software when it
falls out of scope? If yes, just remove the computer/user from the software
install gpo. This will cause the policy module to roll the software install
back. Once that is done, reboot the workstation and then re-add the
user/computer back to the GPO.

neo [mvp outlook] · Feb 22, 2005

Did the site check the option to uninstall the managed software when it
falls out of scope? If yes, just remove the computer/user from the software
install gpo. This will cause the policy module to roll the software install
back. Once that is done, reboot the workstation and then re-add the
user/computer back to the GPO.

neo [mvp outlook] · Feb 22, 2005

Did the site check the option to uninstall the managed software when it
falls out of scope? If yes, just remove the computer/user from the software
install gpo. This will cause the policy module to roll the software install
back. Once that is done, reboot the workstation and then re-add the
user/computer back to the GPO.

Jason Galbreath · Feb 22, 2005