Hi All I have assigned a task to uninstall the MS office from all the client systems. I searched for command line & found command as <Setup location>\setup.exe /uninstall <product ID>. Now the situation is that I have multiple versions of MS office installed across all my client systems. So I have some questions as bellow, need you help into this .. If multiple version available on the client, is there any variable available (Which can be used in place of Product ID) to uninstall any product of MS office installed Do we have to use a separate package for all the respective MS office versions to uninstall or we can use a single uninstall package of higher version i.e. MS office 2010. I want a single MS office uninstall package which can uninstall any version of MS office installed. Thanks in advance!Regards Rushikesh..

I concur with Torsten. For #2. you could also use a custom batch file, but the task sequence would be easier. One important thing to point out: packages contain source files, that's it, no more, no less. Programs run commands. Saying that you want an uninstall "package" is mis-leading and not indicative of what actually happens. This is a common mis-use of the term package.Jason | http://blog.configmgrftw.com | Twitter @JasonSandys

Thanks for all your reply's! I will search for the script. meanwhile can you please explain the steps included in task sequence? Also, can i use the setup files of MS office 2010 ENT edition to remove any version of office (e.g. office XP, office 2007 plus, office 2007 ent, office 2010 ent, office 2010 plus, office 2010 std, etc, etc....) @Jason - Yes, may be my wording is wrong or mis-leading.Actually what i am trying to say is that I want to create a single software package (Under software distribution node in SCCM console) & single program that will uninstall any version or product installed on client system. Hope you got my point. Regards Rushikesh..

Thanks for great info John, I have some query as below. 1) in this case i will need a MSI file for all the versions. 2) we will not need to create a software package (under Software Deploymnent node). Only Task sequence with correct comand & condition will work. 3) I assume if the same product installed on multiple systems then the GUID will be same for each. The reason for this question is that if i use command suggested by you like " msiexec /x {PRODUCTGUID}" the PRODUUCTGUID will work for all those systems. Please correct me if i am wrong/misunderstood on any point.Regards Rushikesh..

Rushikesh, You won't need an MSI for all the versions. In a Task Sequence you can create steps for each task in the list. In the example I showed above there is only one step (created by selecting the Add button in the upper left below where it says JDTEST in the title bar). You would create a step for each version of Office. In each step the Installed Software (from the Options -> Add Condition -> Run Command Line) would be populated using the MSI from each version. Then, when the task sequence runs on the client, steps that do not match the version of Office on the machine are skipped. The one that does match is processed and the correct Command Line will then run and uninstall the software. You wouldn't need to thave any source files in the package so you won't be copying Office installation files all over the place. It is just a local command on the machine.John DeVito

Thanks for the wonderful explanation, Got your point. As we are adding condition for Installed Software we will need an MSI file for the respective version, right?2^nd thing, I searched for a uninstall string in registry, I found it like "C:\Program Files\Common Files\Microsoft Shared\OFFICE14\Office Setup Controller\setup.exe" /uninstall PROPLUS /dll OSETUP.DLL how can I use msiexec.exe instead of setup.exe? Thanks again..:)Regards Rushikesh..

Rushikesh, You can still use that uninstall string from the registry. It doesn't have to be msiexec. You would need the MSI from each respective version to use this method. You can use it from C:\Windows\Installer on the machines with the versions installed. Show Hidden and System files to get to the file from Explorer, or you can manually type the path in the address bar. Add a column for Subject to the view. Then you can look in the subject column for the product. See the example from Explorer shown below: Copy the MSI files to the ConfigMgr server and import them as Task Sequence step conditions as shown earlier. You'll see the following: John DeVito

Hi John, OK, I will do this & post the update here.It may take more time (round one week) as I have to do it in customer environment. Really appreciated your help John & all who replyed to this post.. Regards Rushikesh..

Hi All, I am too glad to inform you that the Task sequence has worked so nice.............:) :) :) :) :) :) thanks to all of your help ! Thanks Forum...!!!!!! Thanks John for such great help......Regards Rushikesh..