RE: Remove security policy



Hi,

You should actually view it from the IP Security Policy snap-in. Open up the
snap-in and delete the policy from there.

Alternatively, you can use ipseccmd itself to delete the policy (either the
-u or -o switch):

http://technet.microsoft.com/en-us/library/bb490922.aspx

Regards,

Salvador Manaois III
MCSE MCSA CEH MCITP | Enterprise/Server Admin
Bytes & Badz : http://badzmanaois.blogspot.com


"sul" wrote:

hi,

i have a securiy policy that is not showing up anywhere on Domain Security
Policy mmc or GPMC. I can see it being applied to member computers upon
running "ipseccmd show all"

Is there a way to delete this "invisible" policy using adsiedit? or some
other means?

thanks!


.



Relevant Pages

  • Re: IPSEC Policy to secure TS
    ... >"How to Create and Enable IPSec Policy to Secure ... >After the IP Security Policy Wizard starts, ... >2) the client policy is rather broad and might need ...
    (microsoft.public.win2000.security)
  • Re: IPSEC Policy to secure TS
    ... "How to Create and Enable IPSec Policy to Secure Terminal Services ... After the IP Security Policy Wizard starts, ... Click to expand Security Settings in the left pane, right-click the Client ...
    (microsoft.public.win2000.security)
  • Re: Limit number of login attemps on Windows server 2003 - where to set this up?
    ... An example change which you would make using the DC Security Policy and not ... and the Domain Controller Security Policy only applies to Domain ... > server exists to serve the clients, so what would you change on the DC, ...
    (microsoft.public.windows.server.general)
  • Re: [fw-wiz] Security and Audit Policy
    ... Enabling firewall rules without a solid security policy and management ... nameserver (I don't like clients resolving directly in any circumstance.) ...
    (Firewall-Wizards)
  • Re: Backup Exec service fails on startup
    ... I suppose the place to start is with the local security policy and/or the domain controller security policy and check for enabled ... Even though you say this is just on one server, it is usually a good idea to make sure the service account is in a separate AD ...
    (microsoft.public.windows.server.general)

Loading