| • | For Active Directory-based Group Policy:
| ||||||||||||
| • | For local computer policy:
|
| • | An IPSec policy might remain active even after the IPSec policy or Group Policy object to which it is assigned has been deleted. Therefore, you should unassign the IPSec policy before you delete either the policy or the Group Policy object. To prevent problems, use the following procedure:
If you delete the IPSec policy or Group Policy object without following this procedure, computers in the Active Directory container to which the IPSec policy is assigned might treat the IPSec policy as if it cannot be located and continue to use a cached copy. |
Note
| • | To start Active Directory Users and Computers, open a Remote Desktop Connection to either a Windows 2000 domain controller or a member server that has Windows 2000 Administration Tools installed. You must log on to the server as a domain administrator in order to complete this procedure. |
| • | You cannot administer Active Directory-based IPSec policy from a computer running Windows XP Home Edition. |
| • | To define Active Directory-based IPSec policy, you must have Group Policy administrative permissions. To manage local or remote IPSec policy for a computer, you must be a member of the Administrators group on the local or remote computer. |
| • | The settings will take effect the next time Group Policy is refreshed. |
| • | If a policy is currently assigned and you assign a new policy, the currently assigned policy is automatically unassigned. |
| • | You cannot assign a policy from the IP Security Policies on Active Directory snap-in, but can only configure policy. To assign policy for Active Directory containers, you must use the IP Security Policies on Active Directory within the Group Policy snap-in. |
| • | If you need to disable IPSec for only a specific computer, you can disable the IPSEC Services service on that computer. |
| • | |
| • |