Can I uninstall a software(.exe) on a client?

I need a solution

Hi, all.

With Software Management solution, I am able to deliver software to my users. I also understand that we can uninstall software on user’s PC if we discovered they are using software that they are not supposed to?

Question is, how? If it is an msi installation, we can do msiexec /u <msi package> quick delivery task from Notification Server but how about exe installations, what can we do to uninstall exe installation software?

Any help would be appreciated.

0

Related:

Issue creating Client update package after upgrading SEP 14

I need a solution

Hello everyone,

     First, I want to say that I have a case open with Symantec already for this but they can’t find a resolution. I can’t believe we are the only organization having this issue.

On May 1st 2018 I upgraded my SEP 14 from 14.0 to 14.0.1.2 with the assistance of Symantec. Before upgrading to the newest version, I had no issues. We made esure we did a backup of everything before starting. Now that we are on on 14.0.1.2 everything is fine, except that I cannot create client upgrade packages. Which may not sound like a big deal but it is since the only way I can do any client upgrades, as new packages come out, is to uninstall SEP from the clients and install the newest version…..not feasible at all. It has been over a month since opening a case with Symantec but they cannot find a resolution. Has anyone else seen this issue recently? 

When I try to create an upgrade package I get the attached error

0

1528375231

Related:

Some remnants of PGP remain on my system after uninstall

I need a solution

Hi All,

I have uninstalled Symantec PGP from a laptop but when i try to enctpy with the new software my client has opted for i get a message saying that PGP is still installed on the system.

Please could you advise if there are any uninstalled tools for this software, or if anyone has seen this before and certain folders/files need to be removed.

Thanks in advance, 

Thomas

0

Related:

ApiDiscovery-1.0 feature not working after installing it from local feature repository

Hello,

a few weeks ago I’ve tested the Swagger feature successfully. Today I tried to activate it in another liberty instance but had a lot of trouble until it worked. Although everything was installed properly and no errors have been visible in the log files the documentation for the JAX-RS annotated endpoints wasn’t generated. In the end it had nothing to do with the webapp or the feature itself but with the way I did install it. As I am behind a corporate proxy I tried to download the feature to a local repository and install it from there (to make it easier for other developers).

So at first I’ve used installUtility:

installUtility download apiDiscovery-1.0 –location=C:TemplocalRepo
Then I’ve installed the feature from the local directory via:

installUtility install apiDiscovery-1.0 –from=C:TemplocalRepo
The lafiles directory looks like the following (less directories than in the other Liberty instance):
![alt text][1]

After uninstalling the feature and installing directly from web repository with the following commands:

installUtility uninstall apiDiscovery-1.0
installUtility install apiDiscovery-1.0
Lafiles (additional directories have been created):

![alt text][2]

Now it works like in the other instance and generates documentation for REST services nicely.

As it is important for us to have a local repository (proxy & firewall reasons) it would be great if someone has an idea how to correctly downloading/ installing the feature in/from a local repo. Independently I wouldn’t expect that the installation result is somehow related to the repository location.

Any ideas are appreciated! Thanks a lot.

[1]: /answers/storage/temp/18018-afterinstallationfromlocalrepository.png
[2]: /answers/storage/temp/18023-afterinstallationfromwebrepository.png

Related:

How to upgrade a component using the xxxx-multipleComponents steps

We are installing multiple components to a server using the InstallMultipleComponents step selecting the components by a tag. Now I would like to create a upgrade step that brings a selected set of components to a new level. As this should also work with snapshots, components that are given in the same version should just stay untouched. Here what should happen:

If a component has a different version as already installed, do:
if the version was already installed: uninstall
install the new version.

As we have about 20 components this should work with the (un)installMultipleComponents step, but I found no way to get this working.

Related:

Downgrade 14 MP2 to 12.1.6 MP7

I need a solution

Hi 

after upgrade sepm 12.1 MP7 to 14 MP1 i got report from almost client their pdf and word files opening got very slow , so upgrade it to 14 MP2 and that was same till i disable auto protect option it worked randomly , i decide to downgrade client to previous version (12.1)  , i create a bat file to uninstall sep client 14 and it uninstalled successfully and after that try to deploy sep package 12.1 through SEPM  it also successfully deployed but it didn’t shown in sepm console , i check SEP_Inst log and it told me the newer version installed and roll backed , as a test i ran cleawipe and after that package installed successfully , i confused about it beacuase i removed sep 14 , please help me 

SEPM ENV : windows 2012 R2 DC

Client ENV : windows 7 32Bit 

0

Related:

Not able to uninstall when installed in other drive apart from C drive

I need a solution

Hello,

I’m facing a problem in unwise.exe where i’m able to uninstall from C:Program files(x86)my project but not able to uninstall from d:New projectmy project as it says INSTALL.Log not found. If i remove the space in D drive path, i’m able to uninstall. My query is C: drive also contains space and i’m able to uninstall but then why not from D: drive when approach is same. Even i tried giving in double quote but it didnt worked. Please resolve this issue as soon  as possible.

0

Related: