asked on

How do I uninstall Project 2016 from the command line

We deploy Project 2016 using an administrative install that points to a MST file. We created an SCCM application that simply runs "setup.exe" from the application source.

We're now in a position that we need to reclaim a bunch of licenses that are not being used. I found a similar discussion where the tech got the removal of Office 2016 it to work by creating a config.xml to point setup.exe at for the uninstall directions.

setup.exe /uninstall ProPlus /config config.xml

where their config.xml (which they had to create) looks like this :

<Configuration>

    <Display Level="none" CompletionNotice="no" SuppressModal="yes" AcceptEula="yes" />

    <Logging Level="Standard" Path="%temp%" />

</Configuration>

Open in new window

I'm going to test this today of course to see if it works at all. I'd like to know how others have solved this riddle in case there are better options.

If the command line works, I intend to use SCCM to execute it against a target collection.

RhoSysAdmin

ASKER

I can confirm the above works when creating the xml file exactly as listed above and running the following command :

setup.exe /uninstall PrjStd /config config.xml

I'm still interested to know if anyone does it differently, or if this is the best way to proceed.

Thanks!

Hayes Jupe

using the msi for both detection and uninstall is easier IMO - if your looking for alternate points of view.

RhoSysAdmin

ASKER

I agree using the MSI would be better from the SCCM perspective. But we used the "setup.exe" to create the administrative install. So that's why we followed the same path for removal.

ASKER CERTIFIED SOLUTION

RhoSysAdmin

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial