AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |
Back to Blog
![]() ![]() Here is an example of a config.xml file for silently uninstalling Office 2007 ProPlus: You will also need to create a config.xml file for each product you want to uninstall and set it to perform the uninstall silently. ![]() You can only target one product at a time, but can run setup multiple One way to do this with a script is to utilize the Office 2007 setup controllers /uninstall switch. ![]() You will also need to target and remove the SKU you are trying to install if it is already installed on these machines. What SKU of Office 2007 is currently installed on 5% of your machines? Is it a mix of standalone apps or is it a suite? The reason I ask is you will need to target Only work well for installing Office 2007. You are also correct that OptionState ID’s When you are installing Office, setup can only uninstall previous versions of Office, not the version being installed. Question: What is the best approach for uninstalling individual Office 2007 components by leveraging scripting? It appears the Option State value is only for install and not uninstall. In the config.xml there is an "Option State" setting that I thought would allow me to uninstall specific Office components but research and testing In the MSOCache directory and then creating a config.xml file to point at that names the target Office suite. I have been looking to accomplish this by leveraging the setup.exe With the Office 2007 OCT I can uninstall individual components that are prior to Office 2007 but not at 2007. InfoPath, Publisher, Visio Viewer, etc.) and reinstall with the standard set of install bits. I am looking to uninstall Word, Excel, PPT and Outlook off these machines (I.E. I am preparing Office 2007 packages to deploy to a client of approx 1200 seats via SMS 2003.Ībout 5% of the target machines have 2007 installed already.
0 Comments
Read More
Leave a Reply. |