SCCM 2007 - Uninstall software from remote machines

Yes, You need to create a uninstall package using the installed files on the system.

Create a new package and use uninstall switches in conjunction with uninstaller exe if there is one available.

You could also use Flexera package studio to script this in an automated MSI using snapshot technology.

I would highly recommend Flexera package studio actually anybody using SCCM should be using this. Download a free trial and you will see its power.

What software is it? I may be able to give an exact answer.

thanks guys the software is Colligo Engage briefcase for offline files.

Hi Nag,

thank you very much for the help. Question, if I wanted to test the command line uninstall, what path would I need to navigate to on the local C drive? also for the roll out package, would I need to add the licence key to the command in the SCCM program?

Check the registry uninstall location. There may be a guid that does  not need the path.

If you do not specify the licence key then they program may not install at all or may install as a trial version only. It totally depends on the program.

Hi Nag,

So if the GUID is in the uninstall location, it wont need the path in cmd to uninstall? but if the GUID is not there, it will need a path? is that correct?

yes. But the uninstall location is created when you install the program.

99% sure that it is always there with GUID and not the msi file name.

cool ill give it a go and report back shortly.

Hi Nagendra, so I have created a package and tested with only my machine and as soon as the package was deployed, it installed but automatically force restarted my machine.

This is the command I ran in the program: msiexec.exe /qn ALLUSERS=2 /m MSIDIXWD /i "Colligo_x64.msi" LICENSE_KEY=<license key>

any ideas? I want it to install but not auto force restart.

You want to install it or uninstall it?

Hi Nag,

So it worked when I pushed it to two machines but it failed on another machine.

Description  
The program for advertisement "***200BF" failed ("***000F7" - "Per-system unattended"). The failure description was "Fatal error during installation. ". User context: NT AUTHORITY\SYSTEM Possible cause: The program generated an installation status Management Information Format (MIF) file with a status value of Failed. Solution: For more information about the failure, refer to the documentation for the program you are distributing.  

He has restarted but still doing the same thing. How can I get more info?

Hi Guys, I may have a solution for this. I think a pre req was not installed before pushing the main msi file. Let me test and update shortly. thanks

thanks!!