About unable to uninstall security policy package

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Hi All: I tried to uninstall a runtime security package from a user's
machine. Based on document I have read, all I need to do is right click on
MSI file, and choose uninstall from menu. After I chose uninstall, the
package seemed to uninstall itself. But when open .NET configuration 1.1, I
did not see the package got remove.

Thanks in advance
DK
 
Davis,

What package are you trying to remove? It is a valid runtime upgrade,
why do you want to uninstall it?
 
Not runtime package. A runtime security policy package which I created from
..NET configuration console. A package that can make user's machine trust .NET
assembly launch from NetWork.

Thanks

Nicholas Paldino said:
Davis,

What package are you trying to remove? It is a valid runtime upgrade,
why do you want to uninstall it?


--
- Nicholas Paldino [.NET/C# MVP]
- (e-mail address removed)

[email protected] said:
Hi All: I tried to uninstall a runtime security package from a user's
machine. Based on document I have read, all I need to do is right click on
MSI file, and choose uninstall from menu. After I chose uninstall, the
package seemed to uninstall itself. But when open .NET configuration 1.1,
I
did not see the package got remove.

Thanks in advance
DK
Click to expand...
Click to expand...
 
[email protected] said:
Hi All: I tried to uninstall a runtime security package from a user's
machine. Based on document I have read, all I need to do is right click on
MSI file, and choose uninstall from menu.
Click to expand...

What documentation would this be? I've never seen anything that would
suggest that a CAS policy applied via an MSI could be reversed by
uninstalling the MSI.

After I chose uninstall, the
package seemed to uninstall itself. But when open .NET configuration 1.1,
I
did not see the package got remove.
Click to expand...

When the MSI is installed, the policy level config file is overwritten. I
took a quick look through an auto-generated MSI, and I couldn't find any
evidence that the old config file is backed up, so there's presumably no
source for a restore. If you want to allow for reversal of your MSI-applied
policy changes, here are a couple of potential approaches:

1. Create your own custom MSI that does backup the old config file and is
able to restore it on uninstall. Of course, any changes applied to the
policy between the install and uninstall would be lost.

2. Instead of trying to roll back to the pre-install state, provide another
MSI that updates policy to some alternate desired state (presumably the
preferred baseline). This sort of thing would only work within an
organization with a well defined standard policy.

Yet another approach would be to apply and undo your changes using
caspol.exe rather than replacing the policy with MSI files.
 
Back
Top