Creating Powershell script for bulk uninstall

[Anonymous]

Hi There,
 
i am requested to remove all trace of existing Autodesk products on my company , the installation made were anarchic without control so what exist is unknown.
 
We have SCCM in place and my plan is to create a powershell script which look after all products with publisher = Autodesk , isolate the uninstallStrings , arrange it to be silent and ran it , i made a first script and it works like a charm against one suite i did install for test purposes
 
what i noticed is , alternatively , for this specific suite (Inventor LT 2015) , instead of running all that uninstall strings (can be msiexec /X or setup /P /Q) , i can isolate the GUID (present on HKLM\Software\....\Uninstall (and on the other with WoW6432Node)) which represent a MSI product then ran msiexec /X against all of them
 
Second approach like a charm but is valid ONLY if all the components of Autodesk are MSI , that avoid me to manage any other uninstallstrings which are not msiexec
 
make sense ?
 
so my question is to know if , historically , ALL the Autodesk products are MSI ?
 
Hoping i make sense
 
Rgds,
 

[david.lau]

Create a deployment of Inventor LT 2016.  In the deployment folder, there are unisntall scipts for SCCM.

[Anonymous]

Hi David , Inventor 2015 was an example , i need to uninstall more than 300 autodesk registered softwares from more than 1K computers.

Is anyone can confirm me that Autodesk only use windows installer technology to install their products ?

Regards,
XT

[m_latz]

Just  one additional hint.

You write "... look after all products with publisher = Autodesk , ... "

But you have also 3rd party programs installed with Autodesk products, were the publisher is not Autodesk.

i.e.:

"Eco Materials Adviser for Autodesk Inventor 2013" from publisher "Granta Design Limited"

"FARO LS X.X.XXX.XX" from publisher "FARO scanner Production"

...

...

regards

Markus

[Anonymous]

if install was proper then those products should be uninstalled per uninstallation of parent software (maybe not via msiexec but from setup.exe)
 
i noticed that setup.exe actually triggers msi install (and uninstall) in the backend
 
but thanks for this information , i will add a second check on querying *autodesk* on DisplayName , this should not hurt ...
 
Rgds,
XT

[david.lau]

We are using MSI technology to install software.

[Anonymous]

You wouldnt happen to be able to share this uninstall script of yours?