<?xml version="1.0" encoding="utf-16"?>
<GPO xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="http://www.microsoft.com/GroupPolicy/Settings">
  <Identifier>
    <Identifier xmlns="http://www.microsoft.com/GroupPolicy/Types">{31B2F340-016D-11D2-945F-00C04FB984F9}</Identifier>
    <Domain xmlns="http://www.microsoft.com/GroupPolicy/Types">FISMA.local</Domain>
  </Identifier>
  <Name>Default Domain Policy</Name>
  <IncludeComments>true</IncludeComments>
  <CreatedTime>2012-09-28T19:40:06</CreatedTime>
  <ModifiedTime>2012-11-15T16:23:43</ModifiedTime>
  <ReadTime>2012-11-15T16:29:42.623931Z</ReadTime>
  <SecurityDescriptor>
    <SDDL xmlns="http://www.microsoft.com/GroupPolicy/Types/Security">O:DAG:DAD:PAI(A;;CCLCSWRPWPLORCWDWO;;;DA)(A;CIIO;CCDCLCSWRPWPDTLOSDRCWDWO;;;DA)(A;;CCLCSWRPWPLORCWDWO;;;EA)(A;CIIO;CCDCLCSWRPWPDTLOSDRCWDWO;;;EA)(A;;CCLCSWRPWPLORCWDWO;;;DA)(A;CIIO;CCDCLCSWRPWPDTLOSDRCWDWO;;;CO)(A;CI;CCDCLCSWRPWPDTLOSDRCWDWO;;;SY)(A;CI;LCRPLORC;;;AU)(OA;CI;CR;edacfd8f-ffb3-11d1-b41d-00a0c968f939;;AU)(A;CI;LCRPLORC;;;ED)S:AI(OU;CIIDSA;WPWD;;f30e3bc2-9ff0-11d1-b603-0000f80367c1;WD)(OU;CIIOIDSA;WP;f30e3bbe-9ff0-11d1-b603-0000f80367c1;bf967aa5-0de6-11d0-a285-00aa003049e2;WD)(OU;CIIOIDSA;WP;f30e3bbf-9ff0-11d1-b603-0000f80367c1;bf967aa5-0de6-11d0-a285-00aa003049e2;WD)</SDDL>
    <Owner xmlns="http://www.microsoft.com/GroupPolicy/Types/Security">
      <SID xmlns="http://www.microsoft.com/GroupPolicy/Types">S-1-5-21-1921634877-3105374726-856025148-512</SID>
      <Name xmlns="http://www.microsoft.com/GroupPolicy/Types">FISMA\Domain Admins</Name>
    </Owner>
    <Group xmlns="http://www.microsoft.com/GroupPolicy/Types/Security">
      <SID xmlns="http://www.microsoft.com/GroupPolicy/Types">S-1-5-21-1921634877-3105374726-856025148-512</SID>
      <Name xmlns="http://www.microsoft.com/GroupPolicy/Types">FISMA\Domain Admins</Name>
    </Group>
    <PermissionsPresent xmlns="http://www.microsoft.com/GroupPolicy/Types/Security">true</PermissionsPresent>
    <Permissions xmlns="http://www.microsoft.com/GroupPolicy/Types/Security">
      <InheritsFromParent>false</InheritsFromParent>
      <TrusteePermissions>
        <Trustee>
          <SID xmlns="http://www.microsoft.com/GroupPolicy/Types">S-1-5-18</SID>
          <Name xmlns="http://www.microsoft.com/GroupPolicy/Types">NT AUTHORITY\SYSTEM</Name>
        </Trustee>
        <Type xsi:type="PermissionType">
          <PermissionType>Allow</PermissionType>
        </Type>
        <Inherited>false</Inherited>
        <Applicability>
          <ToSelf>true</ToSelf>
          <ToDescendantObjects>false</ToDescendantObjects>
          <ToDescendantContainers>true</ToDescendantContainers>
          <ToDirectDescendantsOnly>false</ToDirectDescendantsOnly>
        </Applicability>
        <Standard>
          <GPOGroupedAccessEnum>Edit, delete, modify security</GPOGroupedAccessEnum>
        </Standard>
        <AccessMask>0</AccessMask>
      </TrusteePermissions>
      <TrusteePermissions>
        <Trustee>
          <SID xmlns="http://www.microsoft.com/GroupPolicy/Types">S-1-5-11</SID>
          <Name xmlns="http://www.microsoft.com/GroupPolicy/Types">NT AUTHORITY\Authenticated Users</Name>
        </Trustee>
        <Type xsi:type="PermissionType">
          <PermissionType>Allow</PermissionType>
        </Type>
        <Inherited>false</Inherited>
        <Applicability>
          <ToSelf>true</ToSelf>
          <ToDescendantObjects>false</ToDescendantObjects>
          <ToDescendantContainers>true</ToDescendantContainers>
          <ToDirectDescendantsOnly>false</ToDirectDescendantsOnly>
        </Applicability>
        <Standard>
          <GPOGroupedAccessEnum>Apply Group Policy</GPOGroupedAccessEnum>
        </Standard>
        <AccessMask>0</AccessMask>
      </TrusteePermissions>
      <TrusteePermissions>
        <Trustee>
          <SID xmlns="http://www.microsoft.com/GroupPolicy/Types">S-1-5-9</SID>
          <Name xmlns="http://www.microsoft.com/GroupPolicy/Types">NT AUTHORITY\ENTERPRISE DOMAIN CONTROLLERS</Name>
        </Trustee>
        <Type xsi:type="PermissionType">
          <PermissionType>Allow</PermissionType>
        </Type>
        <Inherited>false</Inherited>
        <Applicability>
          <ToSelf>true</ToSelf>
          <ToDescendantObjects>false</ToDescendantObjects>
          <ToDescendantContainers>true</ToDescendantContainers>
          <ToDirectDescendantsOnly>false</ToDirectDescendantsOnly>
        </Applicability>
        <Standard>
          <GPOGroupedAccessEnum>Read</GPOGroupedAccessEnum>
        </Standard>
        <AccessMask>0</AccessMask>
      </TrusteePermissions>
    </Permissions>
    <AuditingPresent xmlns="http://www.microsoft.com/GroupPolicy/Types/Security">false</AuditingPresent>
  </SecurityDescriptor>
  <FilterDataAvailable>true</FilterDataAvailable>
  <Computer>
    <VersionDirectory>26</VersionDirectory>
    <VersionSysvol>26</VersionSysvol>
    <Enabled>true</Enabled>
    <ExtensionData>
      <Extension xmlns:q1="http://www.microsoft.com/GroupPolicy/Settings/Security" xsi:type="q1:SecuritySettings">
        <q1:Account>
          <q1:Name>ClearTextPassword</q1:Name>
          <q1:SettingBoolean>false</q1:SettingBoolean>
          <q1:Type>Password</q1:Type>
        </q1:Account>
        <q1:Account>
          <q1:Name>LockoutBadCount</q1:Name>
          <q1:SettingNumber>3</q1:SettingNumber>
          <q1:Type>Account Lockout</q1:Type>
        </q1:Account>
        <q1:Account>
          <q1:Name>LockoutDuration</q1:Name>
          <q1:SettingNumber>4294967295</q1:SettingNumber>
          <q1:Type>Account Lockout</q1:Type>
        </q1:Account>
        <q1:Account>
          <q1:Name>MaximumPasswordAge</q1:Name>
          <q1:SettingNumber>60</q1:SettingNumber>
          <q1:Type>Password</q1:Type>
        </q1:Account>
        <q1:Account>
          <q1:Name>MinimumPasswordAge</q1:Name>
          <q1:SettingNumber>1</q1:SettingNumber>
          <q1:Type>Password</q1:Type>
        </q1:Account>
        <q1:Account>
          <q1:Name>MinimumPasswordLength</q1:Name>
          <q1:SettingNumber>14</q1:SettingNumber>
          <q1:Type>Password</q1:Type>
        </q1:Account>
        <q1:Account>
          <q1:Name>PasswordComplexity</q1:Name>
          <q1:SettingBoolean>true</q1:SettingBoolean>
          <q1:Type>Password</q1:Type>
        </q1:Account>
        <q1:Account>
          <q1:Name>PasswordHistorySize</q1:Name>
          <q1:SettingNumber>0</q1:SettingNumber>
          <q1:Type>Password</q1:Type>
        </q1:Account>
        <q1:Account>
          <q1:Name>ResetLockoutCount</q1:Name>
          <q1:SettingNumber>60</q1:SettingNumber>
          <q1:Type>Account Lockout</q1:Type>
        </q1:Account>
        <q1:Audit>
          <q1:Name>AuditAccountLogon</q1:Name>
          <q1:SuccessAttempts>true</q1:SuccessAttempts>
          <q1:FailureAttempts>true</q1:FailureAttempts>
        </q1:Audit>
        <q1:Audit>
          <q1:Name>AuditAccountManage</q1:Name>
          <q1:SuccessAttempts>true</q1:SuccessAttempts>
          <q1:FailureAttempts>true</q1:FailureAttempts>
        </q1:Audit>
        <q1:Audit>
          <q1:Name>AuditDSAccess</q1:Name>
          <q1:SuccessAttempts>false</q1:SuccessAttempts>
          <q1:FailureAttempts>false</q1:FailureAttempts>
        </q1:Audit>
        <q1:Audit>
          <q1:Name>AuditLogonEvents</q1:Name>
          <q1:SuccessAttempts>true</q1:SuccessAttempts>
          <q1:FailureAttempts>false</q1:FailureAttempts>
        </q1:Audit>
        <q1:Audit>
          <q1:Name>AuditObjectAccess</q1:Name>
          <q1:SuccessAttempts>false</q1:SuccessAttempts>
          <q1:FailureAttempts>false</q1:FailureAttempts>
        </q1:Audit>
        <q1:Audit>
          <q1:Name>AuditPolicyChange</q1:Name>
          <q1:SuccessAttempts>true</q1:SuccessAttempts>
          <q1:FailureAttempts>false</q1:FailureAttempts>
        </q1:Audit>
        <q1:Audit>
          <q1:Name>AuditPrivilegeUse</q1:Name>
          <q1:SuccessAttempts>false</q1:SuccessAttempts>
          <q1:FailureAttempts>false</q1:FailureAttempts>
        </q1:Audit>
        <q1:Audit>
          <q1:Name>AuditProcessTracking</q1:Name>
          <q1:SuccessAttempts>false</q1:SuccessAttempts>
          <q1:FailureAttempts>false</q1:FailureAttempts>
        </q1:Audit>
        <q1:Audit>
          <q1:Name>AuditSystemEvents</q1:Name>
          <q1:SuccessAttempts>true</q1:SuccessAttempts>
          <q1:FailureAttempts>false</q1:FailureAttempts>
        </q1:Audit>
        <q1:UserRightsAssignment>
          <q1:Name>SeAssignPrimaryTokenPrivilege</q1:Name>
          <q1:Member>
            <SID xmlns="http://www.microsoft.com/GroupPolicy/Types">S-1-5-20</SID>
            <Name xmlns="http://www.microsoft.com/GroupPolicy/Types">NT AUTHORITY\NETWORK SERVICE</Name>
          </q1:Member>
          <q1:Member>
            <SID xmlns="http://www.microsoft.com/GroupPolicy/Types">S-1-5-19</SID>
            <Name xmlns="http://www.microsoft.com/GroupPolicy/Types">NT AUTHORITY\LOCAL SERVICE</Name>
          </q1:Member>
        </q1:UserRightsAssignment>
        <q1:UserRightsAssignment>
          <q1:Name>SeAuditPrivilege</q1:Name>
          <q1:Member>
            <SID xmlns="http://www.microsoft.com/GroupPolicy/Types">S-1-5-20</SID>
            <Name xmlns="http://www.microsoft.com/GroupPolicy/Types">NT AUTHORITY\NETWORK SERVICE</Name>
          </q1:Member>
          <q1:Member>
            <SID xmlns="http://www.microsoft.com/GroupPolicy/Types">S-1-5-19</SID>
            <Name xmlns="http://www.microsoft.com/GroupPolicy/Types">NT AUTHORITY\LOCAL SERVICE</Name>
          </q1:Member>
        </q1:UserRightsAssignment>
        <q1:UserRightsAssignment>
          <q1:Name>SeBackupPrivilege</q1:Name>
          <q1:Member>
            <SID xmlns="http://www.microsoft.com/GroupPolicy/Types">S-1-5-32-544</SID>
            <Name xmlns="http://www.microsoft.com/GroupPolicy/Types">BUILTIN\Administrators</Name>
          </q1:Member>
        </q1:UserRightsAssignment>
        <q1:UserRightsAssignment>
          <q1:Name>SeBatchLogonRight</q1:Name>
          <q1:Member>
            <SID xmlns="http://www.microsoft.com/GroupPolicy/Types">S-1-5-32-544</SID>
            <Name xmlns="http://www.microsoft.com/GroupPolicy/Types">BUILTIN\Administrators</Name>
          </q1:Member>
        </q1:UserRightsAssignment>
        <q1:UserRightsAssignment>
          <q1:Name>SeChangeNotifyPrivilege</q1:Name>
          <q1:Member>
            <SID xmlns="http://www.microsoft.com/GroupPolicy/Types">S-1-5-32-544</SID>
            <Name xmlns="http://www.microsoft.com/GroupPolicy/Types">BUILTIN\Administrators</Name>
          </q1:Member>
          <q1:Member>
            <SID xmlns="http://www.microsoft.com/GroupPolicy/Types">S-1-5-20</SID>
            <Name xmlns="http://www.microsoft.com/GroupPolicy/Types">NT AUTHORITY\NETWORK SERVICE</Name>
          </q1:Member>
          <q1:Member>
            <SID xmlns="http://www.microsoft.com/GroupPolicy/Types">S-1-5-19</SID>
            <Name xmlns="http://www.microsoft.com/GroupPolicy/Types">NT AUTHORITY\LOCAL SERVICE</Name>
          </q1:Member>
          <q1:Member>
            <SID xmlns="http://www.microsoft.com/GroupPolicy/Types">S-1-5-11</SID>
            <Name xmlns="http://www.microsoft.com/GroupPolicy/Types">NT AUTHORITY\Authenticated Users</Name>
          </q1:Member>
        </q1:UserRightsAssignment>
        <q1:UserRightsAssignment>
          <q1:Name>SeCreateGlobalPrivilege</q1:Name>
          <q1:Member>
            <SID xmlns="http://www.microsoft.com/GroupPolicy/Types">S-1-5-6</SID>
            <Name xmlns="http://www.microsoft.com/GroupPolicy/Types">NT AUTHORITY\SERVICE</Name>
          </q1:Member>
          <q1:Member>
            <SID xmlns="http://www.microsoft.com/GroupPolicy/Types">S-1-5-32-544</SID>
            <Name xmlns="http://www.microsoft.com/GroupPolicy/Types">BUILTIN\Administrators</Name>
          </q1:Member>
          <q1:Member>
            <SID xmlns="http://www.microsoft.com/GroupPolicy/Types">S-1-5-20</SID>
            <Name xmlns="http://www.microsoft.com/GroupPolicy/Types">NT AUTHORITY\NETWORK SERVICE</Name>
          </q1:Member>
          <q1:Member>
            <SID xmlns="http://www.microsoft.com/GroupPolicy/Types">S-1-5-19</SID>
            <Name xmlns="http://www.microsoft.com/GroupPolicy/Types">NT AUTHORITY\LOCAL SERVICE</Name>
          </q1:Member>
        </q1:UserRightsAssignment>
        <q1:UserRightsAssignment>
          <q1:Name>SeCreatePagefilePrivilege</q1:Name>
          <q1:Member>
            <SID xmlns="http://www.microsoft.com/GroupPolicy/Types">S-1-5-32-544</SID>
            <Name xmlns="http://www.microsoft.com/GroupPolicy/Types">BUILTIN\Administrators</Name>
          </q1:Member>
        </q1:UserRightsAssignment>
        <q1:UserRightsAssignment>
          <q1:Name>SeCreateSymbolicLinkPrivilege</q1:Name>
          <q1:Member>
            <SID xmlns="http://www.microsoft.com/GroupPolicy/Types">S-1-5-32-544</SID>
            <Name xmlns="http://www.microsoft.com/GroupPolicy/Types">BUILTIN\Administrators</Name>
          </q1:Member>
        </q1:UserRightsAssignment>
        <q1:UserRightsAssignment>
          <q1:Name>SeDenyBatchLogonRight</q1:Name>
          <q1:Member>
            <SID xmlns="http://www.microsoft.com/GroupPolicy/Types">S-1-5-32-546</SID>
            <Name xmlns="http://www.microsoft.com/GroupPolicy/Types">BUILTIN\Guests</Name>
          </q1:Member>
        </q1:UserRightsAssignment>
        <q1:UserRightsAssignment>
          <q1:Name>SeDenyInteractiveLogonRight</q1:Name>
          <q1:Member>
            <SID xmlns="http://www.microsoft.com/GroupPolicy/Types">S-1-5-32-546</SID>
            <Name xmlns="http://www.microsoft.com/GroupPolicy/Types">BUILTIN\Guests</Name>
          </q1:Member>
        </q1:UserRightsAssignment>
        <q1:UserRightsAssignment>
          <q1:Name>SeDenyNetworkLogonRight</q1:Name>
          <q1:Member>
            <SID xmlns="http://www.microsoft.com/GroupPolicy/Types">S-1-5-32-546</SID>
            <Name xmlns="http://www.microsoft.com/GroupPolicy/Types">BUILTIN\Guests</Name>
          </q1:Member>
        </q1:UserRightsAssignment>
        <q1:UserRightsAssignment>
          <q1:Name>SeDenyRemoteInteractiveLogonRight</q1:Name>
          <q1:Member>
            <SID xmlns="http://www.microsoft.com/GroupPolicy/Types">S-1-5-32-546</SID>
            <Name xmlns="http://www.microsoft.com/GroupPolicy/Types">BUILTIN\Guests</Name>
          </q1:Member>
        </q1:UserRightsAssignment>
        <q1:UserRightsAssignment>
          <q1:Name>SeImpersonatePrivilege</q1:Name>
          <q1:Member>
            <SID xmlns="http://www.microsoft.com/GroupPolicy/Types">S-1-5-6</SID>
            <Name xmlns="http://www.microsoft.com/GroupPolicy/Types">NT AUTHORITY\SERVICE</Name>
          </q1:Member>
          <q1:Member>
            <SID xmlns="http://www.microsoft.com/GroupPolicy/Types">S-1-5-32-544</SID>
            <Name xmlns="http://www.microsoft.com/GroupPolicy/Types">BUILTIN\Administrators</Name>
          </q1:Member>
          <q1:Member>
            <SID xmlns="http://www.microsoft.com/GroupPolicy/Types">S-1-5-20</SID>
            <Name xmlns="http://www.microsoft.com/GroupPolicy/Types">NT AUTHORITY\NETWORK SERVICE</Name>
          </q1:Member>
          <q1:Member>
            <SID xmlns="http://www.microsoft.com/GroupPolicy/Types">S-1-5-19</SID>
            <Name xmlns="http://www.microsoft.com/GroupPolicy/Types">NT AUTHORITY\LOCAL SERVICE</Name>
          </q1:Member>
        </q1:UserRightsAssignment>
        <q1:UserRightsAssignment>
          <q1:Name>SeIncreaseBasePriorityPrivilege</q1:Name>
          <q1:Member>
            <SID xmlns="http://www.microsoft.com/GroupPolicy/Types">S-1-5-32-544</SID>
            <Name xmlns="http://www.microsoft.com/GroupPolicy/Types">BUILTIN\Administrators</Name>
          </q1:Member>
        </q1:UserRightsAssignment>
        <q1:UserRightsAssignment>
          <q1:Name>SeIncreaseQuotaPrivilege</q1:Name>
          <q1:Member>
            <SID xmlns="http://www.microsoft.com/GroupPolicy/Types">S-1-5-32-544</SID>
            <Name xmlns="http://www.microsoft.com/GroupPolicy/Types">BUILTIN\Administrators</Name>
          </q1:Member>
          <q1:Member>
            <SID xmlns="http://www.microsoft.com/GroupPolicy/Types">S-1-5-20</SID>
            <Name xmlns="http://www.microsoft.com/GroupPolicy/Types">NT AUTHORITY\NETWORK SERVICE</Name>
          </q1:Member>
          <q1:Member>
            <SID xmlns="http://www.microsoft.com/GroupPolicy/Types">S-1-5-19</SID>
            <Name xmlns="http://www.microsoft.com/GroupPolicy/Types">NT AUTHORITY\LOCAL SERVICE</Name>
          </q1:Member>
        </q1:UserRightsAssignment>
        <q1:UserRightsAssignment>
          <q1:Name>SeIncreaseWorkingSetPrivilege</q1:Name>
          <q1:Member>
            <SID xmlns="http://www.microsoft.com/GroupPolicy/Types">S-1-5-32-544</SID>
            <Name xmlns="http://www.microsoft.com/GroupPolicy/Types">BUILTIN\Administrators</Name>
          </q1:Member>
          <q1:Member>
            <SID xmlns="http://www.microsoft.com/GroupPolicy/Types">S-1-5-19</SID>
            <Name xmlns="http://www.microsoft.com/GroupPolicy/Types">NT AUTHORITY\LOCAL SERVICE</Name>
          </q1:Member>
        </q1:UserRightsAssignment>
        <q1:UserRightsAssignment>
          <q1:Name>SeInteractiveLogonRight</q1:Name>
          <q1:Member>
            <SID xmlns="http://www.microsoft.com/GroupPolicy/Types">S-1-5-32-544</SID>
            <Name xmlns="http://www.microsoft.com/GroupPolicy/Types">BUILTIN\Administrators</Name>
          </q1:Member>
        </q1:UserRightsAssignment>
        <q1:UserRightsAssignment>
          <q1:Name>SeLoadDriverPrivilege</q1:Name>
          <q1:Member>
            <SID xmlns="http://www.microsoft.com/GroupPolicy/Types">S-1-5-32-544</SID>
            <Name xmlns="http://www.microsoft.com/GroupPolicy/Types">BUILTIN\Administrators</Name>
          </q1:Member>
        </q1:UserRightsAssignment>
        <q1:UserRightsAssignment>
          <q1:Name>SeMachineAccountPrivilege</q1:Name>
          <q1:Member>
            <SID xmlns="http://www.microsoft.com/GroupPolicy/Types">S-1-5-32-544</SID>
            <Name xmlns="http://www.microsoft.com/GroupPolicy/Types">BUILTIN\Administrators</Name>
          </q1:Member>
        </q1:UserRightsAssignment>
        <q1:UserRightsAssignment>
          <q1:Name>SeManageVolumePrivilege</q1:Name>
          <q1:Member>
            <SID xmlns="http://www.microsoft.com/GroupPolicy/Types">S-1-5-32-544</SID>
            <Name xmlns="http://www.microsoft.com/GroupPolicy/Types">BUILTIN\Administrators</Name>
          </q1:Member>
        </q1:UserRightsAssignment>
        <q1:UserRightsAssignment>
          <q1:Name>SeNetworkLogonRight</q1:Name>
          <q1:Member>
            <SID xmlns="http://www.microsoft.com/GroupPolicy/Types">S-1-5-32-544</SID>
            <Name xmlns="http://www.microsoft.com/GroupPolicy/Types">BUILTIN\Administrators</Name>
          </q1:Member>
          <q1:Member>
            <SID xmlns="http://www.microsoft.com/GroupPolicy/Types">S-1-5-11</SID>
            <Name xmlns="http://www.microsoft.com/GroupPolicy/Types">NT AUTHORITY\Authenticated Users</Name>
          </q1:Member>
        </q1:UserRightsAssignment>
        <q1:UserRightsAssignment>
          <q1:Name>SeProfileSingleProcessPrivilege</q1:Name>
          <q1:Member>
            <SID xmlns="http://www.microsoft.com/GroupPolicy/Types">S-1-5-32-544</SID>
            <Name xmlns="http://www.microsoft.com/GroupPolicy/Types">BUILTIN\Administrators</Name>
          </q1:Member>
        </q1:UserRightsAssignment>
        <q1:UserRightsAssignment>
          <q1:Name>SeRemoteInteractiveLogonRight</q1:Name>
          <q1:Member>
            <SID xmlns="http://www.microsoft.com/GroupPolicy/Types">S-1-5-32-544</SID>
            <Name xmlns="http://www.microsoft.com/GroupPolicy/Types">BUILTIN\Administrators</Name>
          </q1:Member>
        </q1:UserRightsAssignment>
        <q1:UserRightsAssignment>
          <q1:Name>SeRemoteShutdownPrivilege</q1:Name>
          <q1:Member>
            <SID xmlns="http://www.microsoft.com/GroupPolicy/Types">S-1-5-32-544</SID>
            <Name xmlns="http://www.microsoft.com/GroupPolicy/Types">BUILTIN\Administrators</Name>
          </q1:Member>
        </q1:UserRightsAssignment>
        <q1:UserRightsAssignment>
          <q1:Name>SeRestorePrivilege</q1:Name>
          <q1:Member>
            <SID xmlns="http://www.microsoft.com/GroupPolicy/Types">S-1-5-32-544</SID>
            <Name xmlns="http://www.microsoft.com/GroupPolicy/Types">BUILTIN\Administrators</Name>
          </q1:Member>
        </q1:UserRightsAssignment>
        <q1:UserRightsAssignment>
          <q1:Name>SeSecurityPrivilege</q1:Name>
          <q1:Member>
            <SID xmlns="http://www.microsoft.com/GroupPolicy/Types">S-1-5-32-544</SID>
            <Name xmlns="http://www.microsoft.com/GroupPolicy/Types">BUILTIN\Administrators</Name>
          </q1:Member>
        </q1:UserRightsAssignment>
        <q1:UserRightsAssignment>
          <q1:Name>SeShutdownPrivilege</q1:Name>
          <q1:Member>
            <SID xmlns="http://www.microsoft.com/GroupPolicy/Types">S-1-5-32-544</SID>
            <Name xmlns="http://www.microsoft.com/GroupPolicy/Types">BUILTIN\Administrators</Name>
          </q1:Member>
        </q1:UserRightsAssignment>
        <q1:UserRightsAssignment>
          <q1:Name>SeSystemEnvironmentPrivilege</q1:Name>
          <q1:Member>
            <SID xmlns="http://www.microsoft.com/GroupPolicy/Types">S-1-5-32-544</SID>
            <Name xmlns="http://www.microsoft.com/GroupPolicy/Types">BUILTIN\Administrators</Name>
          </q1:Member>
        </q1:UserRightsAssignment>
        <q1:UserRightsAssignment>
          <q1:Name>SeSystemProfilePrivilege</q1:Name>
          <q1:Member>
            <SID xmlns="http://www.microsoft.com/GroupPolicy/Types">S-1-5-32-544</SID>
            <Name xmlns="http://www.microsoft.com/GroupPolicy/Types">BUILTIN\Administrators</Name>
          </q1:Member>
        </q1:UserRightsAssignment>
        <q1:UserRightsAssignment>
          <q1:Name>SeSystemTimePrivilege</q1:Name>
          <q1:Member>
            <SID xmlns="http://www.microsoft.com/GroupPolicy/Types">S-1-5-32-544</SID>
            <Name xmlns="http://www.microsoft.com/GroupPolicy/Types">BUILTIN\Administrators</Name>
          </q1:Member>
          <q1:Member>
            <SID xmlns="http://www.microsoft.com/GroupPolicy/Types">S-1-5-19</SID>
            <Name xmlns="http://www.microsoft.com/GroupPolicy/Types">NT AUTHORITY\LOCAL SERVICE</Name>
          </q1:Member>
        </q1:UserRightsAssignment>
        <q1:UserRightsAssignment>
          <q1:Name>SeTakeOwnershipPrivilege</q1:Name>
          <q1:Member>
            <SID xmlns="http://www.microsoft.com/GroupPolicy/Types">S-1-5-32-544</SID>
            <Name xmlns="http://www.microsoft.com/GroupPolicy/Types">BUILTIN\Administrators</Name>
          </q1:Member>
        </q1:UserRightsAssignment>
        <q1:UserRightsAssignment>
          <q1:Name>SeTimeZonePrivilege</q1:Name>
          <q1:Member>
            <SID xmlns="http://www.microsoft.com/GroupPolicy/Types">S-1-5-32-544</SID>
            <Name xmlns="http://www.microsoft.com/GroupPolicy/Types">BUILTIN\Administrators</Name>
          </q1:Member>
          <q1:Member>
            <SID xmlns="http://www.microsoft.com/GroupPolicy/Types">S-1-5-19</SID>
            <Name xmlns="http://www.microsoft.com/GroupPolicy/Types">NT AUTHORITY\LOCAL SERVICE</Name>
          </q1:Member>
        </q1:UserRightsAssignment>
        <q1:UserRightsAssignment>
          <q1:Name>SeUndockPrivilege</q1:Name>
          <q1:Member>
            <SID xmlns="http://www.microsoft.com/GroupPolicy/Types">S-1-5-32-544</SID>
            <Name xmlns="http://www.microsoft.com/GroupPolicy/Types">BUILTIN\Administrators</Name>
          </q1:Member>
        </q1:UserRightsAssignment>
        <q1:SecurityOptions>
          <q1:KeyName>MACHINE\Software\Microsoft\Windows NT\CurrentVersion\Setup\RecoveryConsole\SecurityLevel</q1:KeyName>
          <q1:SettingNumber>0</q1:SettingNumber>
          <q1:Display>
            <q1:Name>Recovery console: Allow automatic administrative logon</q1:Name>
            <q1:Units />
            <q1:DisplayBoolean>false</q1:DisplayBoolean>
          </q1:Display>
        </q1:SecurityOptions>
        <q1:SecurityOptions>
          <q1:KeyName>MACHINE\Software\Microsoft\Windows NT\CurrentVersion\Setup\RecoveryConsole\SetCommand</q1:KeyName>
          <q1:SettingNumber>0</q1:SettingNumber>
          <q1:Display>
            <q1:Name>Recovery console: Allow floppy copy and access to all drives and all folders</q1:Name>
            <q1:Units />
            <q1:DisplayBoolean>false</q1:DisplayBoolean>
          </q1:Display>
        </q1:SecurityOptions>
        <q1:SecurityOptions>
          <q1:KeyName>MACHINE\Software\Microsoft\Windows NT\CurrentVersion\Winlogon\AllocateCDRoms</q1:KeyName>
          <q1:SettingString>"1"</q1:SettingString>
          <q1:Display>
            <q1:Name>Devices: Restrict CD-ROM access to locally logged-on user only</q1:Name>
            <q1:Units />
            <q1:DisplayBoolean>true</q1:DisplayBoolean>
          </q1:Display>
        </q1:SecurityOptions>
        <q1:SecurityOptions>
          <q1:KeyName>MACHINE\Software\Microsoft\Windows NT\CurrentVersion\Winlogon\AllocateDASD</q1:KeyName>
          <q1:SettingString>"0"</q1:SettingString>
          <q1:Display>
            <q1:Name>Devices: Allowed to format and eject removable media</q1:Name>
            <q1:Units />
            <q1:DisplayString>Administrators</q1:DisplayString>
          </q1:Display>
        </q1:SecurityOptions>
        <q1:SecurityOptions>
          <q1:KeyName>MACHINE\Software\Microsoft\Windows NT\CurrentVersion\Winlogon\AllocateFloppies</q1:KeyName>
          <q1:SettingString>"1"</q1:SettingString>
          <q1:Display>
            <q1:Name>Devices: Restrict floppy access to locally logged-on user only</q1:Name>
            <q1:Units />
            <q1:DisplayBoolean>true</q1:DisplayBoolean>
          </q1:Display>
        </q1:SecurityOptions>
        <q1:SecurityOptions>
          <q1:KeyName>MACHINE\Software\Microsoft\Windows NT\CurrentVersion\Winlogon\CachedLogonsCount</q1:KeyName>
          <q1:SettingString>"0"</q1:SettingString>
          <q1:Display>
            <q1:Name>Interactive logon: Number of previous logons to cache (in case domain controller is not available)</q1:Name>
            <q1:Units>logons</q1:Units>
            <q1:DisplayNumber>0</q1:DisplayNumber>
          </q1:Display>
        </q1:SecurityOptions>
        <q1:SecurityOptions>
          <q1:KeyName>MACHINE\Software\Microsoft\Windows NT\CurrentVersion\Winlogon\ForceUnlockLogon</q1:KeyName>
          <q1:SettingNumber>0</q1:SettingNumber>
          <q1:Display>
            <q1:Name>Interactive logon: Require Domain Controller authentication to unlock workstation</q1:Name>
            <q1:Units />
            <q1:DisplayBoolean>false</q1:DisplayBoolean>
          </q1:Display>
        </q1:SecurityOptions>
        <q1:SecurityOptions>
          <q1:KeyName>MACHINE\Software\Microsoft\Windows NT\CurrentVersion\Winlogon\PasswordExpiryWarning</q1:KeyName>
          <q1:SettingNumber>14</q1:SettingNumber>
          <q1:Display>
            <q1:Name>Interactive logon: Prompt user to change password before expiration</q1:Name>
            <q1:Units>days</q1:Units>
            <q1:DisplayNumber>14</q1:DisplayNumber>
          </q1:Display>
        </q1:SecurityOptions>
        <q1:SecurityOptions>
          <q1:KeyName>MACHINE\Software\Microsoft\Windows NT\CurrentVersion\Winlogon\ScreenSaverGracePeriod</q1:KeyName>
          <q1:SettingString>"0"</q1:SettingString>
        </q1:SecurityOptions>
        <q1:SecurityOptions>
          <q1:KeyName>MACHINE\Software\Microsoft\Windows NT\CurrentVersion\Winlogon\ScRemoveOption</q1:KeyName>
          <q1:SettingString>"1"</q1:SettingString>
          <q1:Display>
            <q1:Name>Interactive logon: Smart card removal behavior</q1:Name>
            <q1:Units />
            <q1:DisplayString>Lock Workstation</q1:DisplayString>
          </q1:Display>
        </q1:SecurityOptions>
        <q1:SecurityOptions>
          <q1:KeyName>MACHINE\Software\Microsoft\Windows\CurrentVersion\Policies\System\ConsentPromptBehaviorAdmin</q1:KeyName>
          <q1:SettingNumber>2</q1:SettingNumber>
          <q1:Display>
            <q1:Name>User Account Control: Behavior of the elevation prompt for administrators in Admin Approval Mode</q1:Name>
            <q1:Units />
            <q1:DisplayString>Prompt for consent on the secure desktop</q1:DisplayString>
          </q1:Display>
        </q1:SecurityOptions>
        <q1:SecurityOptions>
          <q1:KeyName>MACHINE\Software\Microsoft\Windows\CurrentVersion\Policies\System\ConsentPromptBehaviorUser</q1:KeyName>
          <q1:SettingNumber>0</q1:SettingNumber>
          <q1:Display>
            <q1:Name>User Account Control: Behavior of the elevation prompt for standard users</q1:Name>
            <q1:Units />
            <q1:DisplayString>Automatically deny elevation requests</q1:DisplayString>
          </q1:Display>
        </q1:SecurityOptions>
        <q1:SecurityOptions>
          <q1:KeyName>MACHINE\Software\Microsoft\Windows\CurrentVersion\Policies\System\DisableCAD</q1:KeyName>
          <q1:SettingNumber>0</q1:SettingNumber>
          <q1:Display>
            <q1:Name>Interactive logon: Do not require CTRL+ALT+DEL</q1:Name>
            <q1:Units />
            <q1:DisplayBoolean>false</q1:DisplayBoolean>
          </q1:Display>
        </q1:SecurityOptions>
        <q1:SecurityOptions>
          <q1:KeyName>MACHINE\Software\Microsoft\Windows\CurrentVersion\Policies\System\DontDisplayLastUserName</q1:KeyName>
          <q1:SettingNumber>1</q1:SettingNumber>
          <q1:Display>
            <q1:Name>Interactive logon: Do not display last user name</q1:Name>
            <q1:Units />
            <q1:DisplayBoolean>true</q1:DisplayBoolean>
          </q1:Display>
        </q1:SecurityOptions>
        <q1:SecurityOptions>
          <q1:KeyName>MACHINE\Software\Microsoft\Windows\CurrentVersion\Policies\System\EnableInstallerDetection</q1:KeyName>
          <q1:SettingNumber>1</q1:SettingNumber>
          <q1:Display>
            <q1:Name>User Account Control: Detect application installations and prompt for elevation</q1:Name>
            <q1:Units />
            <q1:DisplayBoolean>true</q1:DisplayBoolean>
          </q1:Display>
        </q1:SecurityOptions>
        <q1:SecurityOptions>
          <q1:KeyName>MACHINE\Software\Microsoft\Windows\CurrentVersion\Policies\System\EnableLUA</q1:KeyName>
          <q1:SettingNumber>1</q1:SettingNumber>
          <q1:Display>
            <q1:Name>User Account Control: Run all administrators in Admin Approval Mode</q1:Name>
            <q1:Units />
            <q1:DisplayBoolean>true</q1:DisplayBoolean>
          </q1:Display>
        </q1:SecurityOptions>
        <q1:SecurityOptions>
          <q1:KeyName>MACHINE\Software\Microsoft\Windows\CurrentVersion\Policies\System\EnableSecureUIAPaths</q1:KeyName>
          <q1:SettingNumber>1</q1:SettingNumber>
          <q1:Display>
            <q1:Name>User Account Control: Only elevate UIAccess applications that are installed in secure locations</q1:Name>
            <q1:Units />
            <q1:DisplayBoolean>true</q1:DisplayBoolean>
          </q1:Display>
        </q1:SecurityOptions>
        <q1:SecurityOptions>
          <q1:KeyName>MACHINE\Software\Microsoft\Windows\CurrentVersion\Policies\System\EnableUIADesktopToggle</q1:KeyName>
          <q1:SettingNumber>0</q1:SettingNumber>
          <q1:Display>
            <q1:Name>User Account Control: Allow UIAccess applications to prompt for elevation without using the secure desktop</q1:Name>
            <q1:Units />
            <q1:DisplayBoolean>false</q1:DisplayBoolean>
          </q1:Display>
        </q1:SecurityOptions>
        <q1:SecurityOptions>
          <q1:KeyName>MACHINE\Software\Microsoft\Windows\CurrentVersion\Policies\System\EnableVirtualization</q1:KeyName>
          <q1:SettingNumber>1</q1:SettingNumber>
          <q1:Display>
            <q1:Name>User Account Control: Virtualize file and registry write failures to per-user locations</q1:Name>
            <q1:Units />
            <q1:DisplayBoolean>true</q1:DisplayBoolean>
          </q1:Display>
        </q1:SecurityOptions>
        <q1:SecurityOptions>
          <q1:KeyName>MACHINE\Software\Microsoft\Windows\CurrentVersion\Policies\System\FilterAdministratorToken</q1:KeyName>
          <q1:SettingNumber>1</q1:SettingNumber>
          <q1:Display>
            <q1:Name>User Account Control: Admin Approval Mode for the Built-in Administrator account</q1:Name>
            <q1:Units />
            <q1:DisplayBoolean>true</q1:DisplayBoolean>
          </q1:Display>
        </q1:SecurityOptions>
        <q1:SecurityOptions>
          <q1:KeyName>MACHINE\Software\Microsoft\Windows\CurrentVersion\Policies\System\Kerberos\Parameters\SupportedEncryptionTypes</q1:KeyName>
          <q1:SettingNumber>2147483644</q1:SettingNumber>
          <q1:Display>
            <q1:Name>Network security: Configure encryption types allowed for Kerberos</q1:Name>
            <q1:Units />
            <q1:DisplayFields>
              <q1:Field>
                <q1:Name>DES_CBC_CRC</q1:Name>
                <q1:Value>false</q1:Value>
              </q1:Field>
              <q1:Field>
                <q1:Name>DES_CBC_MD5</q1:Name>
                <q1:Value>false</q1:Value>
              </q1:Field>
              <q1:Field>
                <q1:Name>RC4_HMAC_MD5</q1:Name>
                <q1:Value>true</q1:Value>
              </q1:Field>
              <q1:Field>
                <q1:Name>AES128_HMAC_SHA1</q1:Name>
                <q1:Value>true</q1:Value>
              </q1:Field>
              <q1:Field>
                <q1:Name>AES256_HMAC_SHA1</q1:Name>
                <q1:Value>true</q1:Value>
              </q1:Field>
              <q1:Field>
                <q1:Name>Future encryption types</q1:Name>
                <q1:Value>true</q1:Value>
              </q1:Field>
            </q1:DisplayFields>
          </q1:Display>
        </q1:SecurityOptions>
        <q1:SecurityOptions>
          <q1:KeyName>MACHINE\Software\Microsoft\Windows\CurrentVersion\Policies\System\LegalNoticeCaption</q1:KeyName>
          <q1:SettingString>"Datapipe Security Notice"</q1:SettingString>
          <q1:Display>
            <q1:Name>Interactive logon: Message title for users attempting to log on</q1:Name>
            <q1:Units />
            <q1:DisplayString>"Datapipe Security Notice"</q1:DisplayString>
          </q1:Display>
        </q1:SecurityOptions>
        <q1:SecurityOptions>
          <q1:KeyName>MACHINE\Software\Microsoft\Windows\CurrentVersion\Policies\System\LegalNoticeText</q1:KeyName>
          <q1:SettingStrings>
            <q1:Value>Unauthorized access to this computer system and software is prohibited by Title 18 United States Code Section 1030 Fraud and Related Activity in Connection with Computers. This system is for the use of authorized users only. Individuals using this computer system without authority or in excess of their authority are subject to having all of their activities on this system monitored and recorded by system personnel. In the course of monitoring individuals improperly using this system or in the case of system maintenance the activities of authorize users may also be monitored.</q1:Value>
          </q1:SettingStrings>
          <q1:Display>
            <q1:Name>Interactive logon: Message text for users attempting to log on</q1:Name>
            <q1:Units />
            <q1:DisplayStrings>
              <q1:Value>Unauthorized access to this computer system and software is prohibited by Title 18 United States Code Section 1030 Fraud and Related Activity in Connection with Computers. This system is for the use of authorized users only. Individuals using this computer system without authority or in excess of their authority are subject to having all of their activities on this system monitored and recorded by system personnel. In the course of monitoring individuals improperly using this system or in the case of system maintenance the activities of authorize users may also be monitored.</q1:Value>
            </q1:DisplayStrings>
          </q1:Display>
        </q1:SecurityOptions>
        <q1:SecurityOptions>
          <q1:KeyName>MACHINE\Software\Microsoft\Windows\CurrentVersion\Policies\System\ScForceOption</q1:KeyName>
          <q1:SettingNumber>0</q1:SettingNumber>
          <q1:Display>
            <q1:Name>Interactive logon: Require smart card</q1:Name>
            <q1:Units />
            <q1:DisplayBoolean>false</q1:DisplayBoolean>
          </q1:Display>
        </q1:SecurityOptions>
        <q1:SecurityOptions>
          <q1:KeyName>MACHINE\Software\Microsoft\Windows\CurrentVersion\Policies\System\ShutdownWithoutLogon</q1:KeyName>
          <q1:SettingNumber>0</q1:SettingNumber>
          <q1:Display>
            <q1:Name>Shutdown: Allow system to be shut down without having to log on</q1:Name>
            <q1:Units />
            <q1:DisplayBoolean>false</q1:DisplayBoolean>
          </q1:Display>
        </q1:SecurityOptions>
        <q1:SecurityOptions>
          <q1:KeyName>MACHINE\Software\Microsoft\Windows\CurrentVersion\Policies\System\UndockWithoutLogon</q1:KeyName>
          <q1:SettingNumber>0</q1:SettingNumber>
          <q1:Display>
            <q1:Name>Devices: Allow undock without having to log on</q1:Name>
            <q1:Units />
            <q1:DisplayBoolean>false</q1:DisplayBoolean>
          </q1:Display>
        </q1:SecurityOptions>
        <q1:SecurityOptions>
          <q1:KeyName>MACHINE\Software\Microsoft\Windows\CurrentVersion\Policies\System\ValidateAdminCodeSignatures</q1:KeyName>
          <q1:SettingNumber>0</q1:SettingNumber>
          <q1:Display>
            <q1:Name>User Account Control: Only elevate executables that are signed and validated</q1:Name>
            <q1:Units />
            <q1:DisplayBoolean>false</q1:DisplayBoolean>
          </q1:Display>
        </q1:SecurityOptions>
        <q1:SecurityOptions>
          <q1:KeyName>MACHINE\Software\Policies\Microsoft\Cryptography\ForceKeyProtection</q1:KeyName>
          <q1:SettingNumber>2</q1:SettingNumber>
          <q1:Display>
            <q1:Name>System cryptography: Force strong key protection for user keys stored on the computer</q1:Name>
            <q1:Units />
            <q1:DisplayString>User must enter a password each time they use a key</q1:DisplayString>
          </q1:Display>
        </q1:SecurityOptions>
        <q1:SecurityOptions>
          <q1:KeyName>MACHINE\Software\Policies\Microsoft\Windows\Safer\CodeIdentifiers\AuthenticodeEnabled</q1:KeyName>
          <q1:SettingNumber>0</q1:SettingNumber>
          <q1:Display>
            <q1:Name>System settings: Use Certificate Rules on Windows Executables for Software Restriction Policies</q1:Name>
            <q1:Units />
            <q1:DisplayBoolean>false</q1:DisplayBoolean>
          </q1:Display>
        </q1:SecurityOptions>
        <q1:SecurityOptions>
          <q1:KeyName>MACHINE\SYSTEM\CurrentControlSet\Control\CrashControl\AutoReboot</q1:KeyName>
          <q1:SettingNumber>1</q1:SettingNumber>
        </q1:SecurityOptions>
        <q1:SecurityOptions>
          <q1:KeyName>MACHINE\System\CurrentControlSet\Control\FileSystem\NtfsDisable8dot3NameCreation</q1:KeyName>
          <q1:SettingNumber>1</q1:SettingNumber>
        </q1:SecurityOptions>
        <q1:SecurityOptions>
          <q1:KeyName>MACHINE\System\CurrentControlSet\Control\Lsa\AuditBaseObjects</q1:KeyName>
          <q1:SettingNumber>0</q1:SettingNumber>
          <q1:Display>
            <q1:Name>Audit: Audit the access of global system objects</q1:Name>
            <q1:Units />
            <q1:DisplayBoolean>false</q1:DisplayBoolean>
          </q1:Display>
        </q1:SecurityOptions>
        <q1:SecurityOptions>
          <q1:KeyName>MACHINE\System\CurrentControlSet\Control\Lsa\CrashOnAuditFail</q1:KeyName>
          <q1:SettingNumber>0</q1:SettingNumber>
          <q1:Display>
            <q1:Name>Audit: Shut down system immediately if unable to log security audits</q1:Name>
            <q1:Units />
            <q1:DisplayBoolean>false</q1:DisplayBoolean>
          </q1:Display>
        </q1:SecurityOptions>
        <q1:SecurityOptions>
          <q1:KeyName>MACHINE\System\CurrentControlSet\Control\Lsa\DisableDomainCreds</q1:KeyName>
          <q1:SettingNumber>1</q1:SettingNumber>
          <q1:Display>
            <q1:Name>Network access: Do not allow storage of passwords and credentials for network authentication</q1:Name>
            <q1:Units />
            <q1:DisplayBoolean>true</q1:DisplayBoolean>
          </q1:Display>
        </q1:SecurityOptions>
        <q1:SecurityOptions>
          <q1:KeyName>MACHINE\System\CurrentControlSet\Control\Lsa\EveryoneIncludesAnonymous</q1:KeyName>
          <q1:SettingNumber>0</q1:SettingNumber>
          <q1:Display>
            <q1:Name>Network access: Let Everyone permissions apply to anonymous users</q1:Name>
            <q1:Units />
            <q1:DisplayBoolean>false</q1:DisplayBoolean>
          </q1:Display>
        </q1:SecurityOptions>
        <q1:SecurityOptions>
          <q1:KeyName>MACHINE\System\CurrentControlSet\Control\Lsa\FIPSAlgorithmPolicy\Enabled</q1:KeyName>
          <q1:SettingNumber>1</q1:SettingNumber>
          <q1:Display>
            <q1:Name>System cryptography: Use FIPS compliant algorithms for encryption, hashing, and signing</q1:Name>
            <q1:Units />
            <q1:DisplayBoolean>true</q1:DisplayBoolean>
          </q1:Display>
        </q1:SecurityOptions>
        <q1:SecurityOptions>
          <q1:KeyName>MACHINE\System\CurrentControlSet\Control\Lsa\ForceGuest</q1:KeyName>
          <q1:SettingNumber>0</q1:SettingNumber>
          <q1:Display>
            <q1:Name>Network access: Sharing and security model for local accounts</q1:Name>
            <q1:Units />
            <q1:DisplayString>Classic - local users authenticate as themselves</q1:DisplayString>
          </q1:Display>
        </q1:SecurityOptions>
        <q1:SecurityOptions>
          <q1:KeyName>MACHINE\System\CurrentControlSet\Control\Lsa\FullPrivilegeAuditing</q1:KeyName>
          <q1:SettingNumber>0</q1:SettingNumber>
          <q1:Display>
            <q1:Name>Audit: Audit the use of Backup and Restore privilege</q1:Name>
            <q1:Units />
            <q1:DisplayBoolean>false</q1:DisplayBoolean>
          </q1:Display>
        </q1:SecurityOptions>
        <q1:SecurityOptions>
          <q1:KeyName>MACHINE\System\CurrentControlSet\Control\Lsa\LimitBlankPasswordUse</q1:KeyName>
          <q1:SettingNumber>1</q1:SettingNumber>
          <q1:Display>
            <q1:Name>Accounts: Limit local account use of blank passwords to console logon only</q1:Name>
            <q1:Units />
            <q1:DisplayBoolean>true</q1:DisplayBoolean>
          </q1:Display>
        </q1:SecurityOptions>
        <q1:SecurityOptions>
          <q1:KeyName>MACHINE\System\CurrentControlSet\Control\Lsa\LmCompatibilityLevel</q1:KeyName>
          <q1:SettingNumber>4</q1:SettingNumber>
          <q1:Display>
            <q1:Name>Network security: LAN Manager authentication level</q1:Name>
            <q1:Units />
            <q1:DisplayString>Send NTLMv2 response only. Refuse LM</q1:DisplayString>
          </q1:Display>
        </q1:SecurityOptions>
        <q1:SecurityOptions>
          <q1:KeyName>MACHINE\System\CurrentControlSet\Control\Lsa\MSV1_0\NTLMMinClientSec</q1:KeyName>
          <q1:SettingNumber>537395200</q1:SettingNumber>
          <q1:Display>
            <q1:Name>Network security: Minimum session security for NTLM SSP based (including secure RPC) clients</q1:Name>
            <q1:Units />
            <q1:DisplayFields>
              <q1:Field>
                <q1:Name>Require NTLMv2 session security</q1:Name>
                <q1:Value>true</q1:Value>
              </q1:Field>
              <q1:Field>
                <q1:Name>Require 128-bit encryption</q1:Name>
                <q1:Value>true</q1:Value>
              </q1:Field>
            </q1:DisplayFields>
          </q1:Display>
        </q1:SecurityOptions>
        <q1:SecurityOptions>
          <q1:KeyName>MACHINE\System\CurrentControlSet\Control\Lsa\MSV1_0\NTLMMinServerSec</q1:KeyName>
          <q1:SettingNumber>537395200</q1:SettingNumber>
          <q1:Display>
            <q1:Name>Network security: Minimum session security for NTLM SSP based (including secure RPC) servers</q1:Name>
            <q1:Units />
            <q1:DisplayFields>
              <q1:Field>
                <q1:Name>Require NTLMv2 session security</q1:Name>
                <q1:Value>true</q1:Value>
              </q1:Field>
              <q1:Field>
                <q1:Name>Require 128-bit encryption</q1:Name>
                <q1:Value>true</q1:Value>
              </q1:Field>
            </q1:DisplayFields>
          </q1:Display>
        </q1:SecurityOptions>
        <q1:SecurityOptions>
          <q1:KeyName>MACHINE\System\CurrentControlSet\Control\Lsa\NoLMHash</q1:KeyName>
          <q1:SettingNumber>1</q1:SettingNumber>
          <q1:Display>
            <q1:Name>Network security: Do not store LAN Manager hash value on next password change</q1:Name>
            <q1:Units />
            <q1:DisplayBoolean>true</q1:DisplayBoolean>
          </q1:Display>
        </q1:SecurityOptions>
        <q1:SecurityOptions>
          <q1:KeyName>MACHINE\System\CurrentControlSet\Control\Lsa\pku2u\AllowOnlineID</q1:KeyName>
          <q1:SettingNumber>0</q1:SettingNumber>
          <q1:Display>
            <q1:Name>Network Security: Allow PKU2U authentication requests to this computer to use online identities</q1:Name>
            <q1:Units />
            <q1:DisplayBoolean>false</q1:DisplayBoolean>
          </q1:Display>
        </q1:SecurityOptions>
        <q1:SecurityOptions>
          <q1:KeyName>MACHINE\System\CurrentControlSet\Control\Lsa\RestrictAnonymous</q1:KeyName>
          <q1:SettingNumber>1</q1:SettingNumber>
          <q1:Display>
            <q1:Name>Network access: Do not allow anonymous enumeration of SAM accounts and shares</q1:Name>
            <q1:Units />
            <q1:DisplayBoolean>true</q1:DisplayBoolean>
          </q1:Display>
        </q1:SecurityOptions>
        <q1:SecurityOptions>
          <q1:KeyName>MACHINE\System\CurrentControlSet\Control\Lsa\RestrictAnonymousSAM</q1:KeyName>
          <q1:SettingNumber>1</q1:SettingNumber>
          <q1:Display>
            <q1:Name>Network access: Do not allow anonymous enumeration of SAM accounts</q1:Name>
            <q1:Units />
            <q1:DisplayBoolean>true</q1:DisplayBoolean>
          </q1:Display>
        </q1:SecurityOptions>
        <q1:SecurityOptions>
          <q1:KeyName>MACHINE\System\CurrentControlSet\Control\Lsa\SCENoApplyLegacyAuditPolicy</q1:KeyName>
          <q1:SettingNumber>1</q1:SettingNumber>
          <q1:Display>
            <q1:Name>Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings</q1:Name>
            <q1:Units />
            <q1:DisplayBoolean>true</q1:DisplayBoolean>
          </q1:Display>
        </q1:SecurityOptions>
        <q1:SecurityOptions>
          <q1:KeyName>MACHINE\System\CurrentControlSet\Control\Lsa\UseMachineId</q1:KeyName>
          <q1:SettingNumber>1</q1:SettingNumber>
          <q1:Display>
            <q1:Name>Network security: Allow Local System to use computer identity for NTLM</q1:Name>
            <q1:Units />
            <q1:DisplayBoolean>true</q1:DisplayBoolean>
          </q1:Display>
        </q1:SecurityOptions>
        <q1:SecurityOptions>
          <q1:KeyName>MACHINE\System\CurrentControlSet\Control\Print\Providers\LanMan Print Services\Servers\AddPrinterDrivers</q1:KeyName>
          <q1:SettingNumber>1</q1:SettingNumber>
          <q1:Display>
            <q1:Name>Devices: Prevent users from installing printer drivers</q1:Name>
            <q1:Units />
            <q1:DisplayBoolean>true</q1:DisplayBoolean>
          </q1:Display>
        </q1:SecurityOptions>
        <q1:SecurityOptions>
          <q1:KeyName>MACHINE\System\CurrentControlSet\Control\SecurePipeServers\Winreg\AllowedExactPaths\Machine</q1:KeyName>
          <q1:SettingStrings>
            <q1:Value>System\CurrentControlSet\Control\ProductOptions</q1:Value>
            <q1:Value>System\CurrentControlSet\Control\Server Applications</q1:Value>
            <q1:Value>Software\Microsoft\Windows NT\CurrentVersion</q1:Value>
          </q1:SettingStrings>
          <q1:Display>
            <q1:Name>Network access: Remotely accessible registry paths</q1:Name>
            <q1:Units />
            <q1:DisplayStrings>
              <q1:Value>System\CurrentControlSet\Control\ProductOptions</q1:Value>
              <q1:Value>System\CurrentControlSet\Control\Server Applications</q1:Value>
              <q1:Value>Software\Microsoft\Windows NT\CurrentVersion</q1:Value>
            </q1:DisplayStrings>
          </q1:Display>
        </q1:SecurityOptions>
        <q1:SecurityOptions>
          <q1:KeyName>MACHINE\System\CurrentControlSet\Control\SecurePipeServers\Winreg\AllowedPaths\Machine</q1:KeyName>
          <q1:SettingStrings>
            <q1:Value>Software\Microsoft\Windows NT\CurrentVersion\Print</q1:Value>
            <q1:Value>Software\Microsoft\Windows NT\CurrentVersion\Windows</q1:Value>
            <q1:Value>System\CurrentControlSet\Control\Print\Printers</q1:Value>
            <q1:Value>System\CurrentControlSet\Services\Eventlog</q1:Value>
            <q1:Value>Software\Microsoft\OLAP Server</q1:Value>
            <q1:Value>System\CurrentControlSet\Control\ContentIndex</q1:Value>
            <q1:Value>System\CurrentControlSet\Control\Terminal Server</q1:Value>
            <q1:Value>System\CurrentControlSet\Control\Terminal Server\UserConfig</q1:Value>
            <q1:Value>System\CurrentControlSet\Control\Terminal Server\DefaultUserConfiguration</q1:Value>
            <q1:Value>Software\Microsoft\Windows NT\CurrentVersion\Perflib</q1:Value>
            <q1:Value>System\CurrentControlSet\Services\SysmonLog</q1:Value>
          </q1:SettingStrings>
          <q1:Display>
            <q1:Name>Network access: Remotely accessible registry paths and sub-paths</q1:Name>
            <q1:Units />
            <q1:DisplayStrings>
              <q1:Value>Software\Microsoft\Windows NT\CurrentVersion\Print</q1:Value>
              <q1:Value>Software\Microsoft\Windows NT\CurrentVersion\Windows</q1:Value>
              <q1:Value>System\CurrentControlSet\Control\Print\Printers</q1:Value>
              <q1:Value>System\CurrentControlSet\Services\Eventlog</q1:Value>
              <q1:Value>Software\Microsoft\OLAP Server</q1:Value>
              <q1:Value>System\CurrentControlSet\Control\ContentIndex</q1:Value>
              <q1:Value>System\CurrentControlSet\Control\Terminal Server</q1:Value>
              <q1:Value>System\CurrentControlSet\Control\Terminal Server\UserConfig</q1:Value>
              <q1:Value>System\CurrentControlSet\Control\Terminal Server\DefaultUserConfiguration</q1:Value>
              <q1:Value>Software\Microsoft\Windows NT\CurrentVersion\Perflib</q1:Value>
              <q1:Value>System\CurrentControlSet\Services\SysmonLog</q1:Value>
            </q1:DisplayStrings>
          </q1:Display>
        </q1:SecurityOptions>
        <q1:SecurityOptions>
          <q1:KeyName>MACHINE\System\CurrentControlSet\Control\Session Manager\Kernel\ObCaseInsensitive</q1:KeyName>
          <q1:SettingNumber>1</q1:SettingNumber>
          <q1:Display>
            <q1:Name>System objects: Require case insensitivity for non-Windows subsystems</q1:Name>
            <q1:Units />
            <q1:DisplayBoolean>true</q1:DisplayBoolean>
          </q1:Display>
        </q1:SecurityOptions>
        <q1:SecurityOptions>
          <q1:KeyName>MACHINE\System\CurrentControlSet\Control\Session Manager\Memory Management\ClearPageFileAtShutdown</q1:KeyName>
          <q1:SettingNumber>0</q1:SettingNumber>
          <q1:Display>
            <q1:Name>Shutdown: Clear virtual memory pagefile</q1:Name>
            <q1:Units />
            <q1:DisplayBoolean>false</q1:DisplayBoolean>
          </q1:Display>
        </q1:SecurityOptions>
        <q1:SecurityOptions>
          <q1:KeyName>MACHINE\System\CurrentControlSet\Control\Session Manager\ProtectionMode</q1:KeyName>
          <q1:SettingNumber>1</q1:SettingNumber>
          <q1:Display>
            <q1:Name>System objects: Strengthen default permissions of internal system objects (e.g. Symbolic Links)</q1:Name>
            <q1:Units />
            <q1:DisplayBoolean>true</q1:DisplayBoolean>
          </q1:Display>
        </q1:SecurityOptions>
        <q1:SecurityOptions>
          <q1:KeyName>MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\SafeDllSearchMode</q1:KeyName>
          <q1:SettingNumber>1</q1:SettingNumber>
        </q1:SecurityOptions>
        <q1:SecurityOptions>
          <q1:KeyName>MACHINE\System\CurrentControlSet\Control\Session Manager\SubSystems\optional</q1:KeyName>
          <q1:SettingStrings />
          <q1:Display>
            <q1:Name>System settings: Optional subsystems</q1:Name>
            <q1:Units />
            <q1:DisplayStrings />
          </q1:Display>
        </q1:SecurityOptions>
        <q1:SecurityOptions>
          <q1:KeyName>MACHINE\System\CurrentControlSet\Services\IPSEC\NoDefaultExempt</q1:KeyName>
          <q1:SettingNumber>3</q1:SettingNumber>
        </q1:SecurityOptions>
        <q1:SecurityOptions>
          <q1:KeyName>MACHINE\System\CurrentControlSet\Services\LanManServer\Parameters\AutoDisconnect</q1:KeyName>
          <q1:SettingNumber>15</q1:SettingNumber>
          <q1:Display>
            <q1:Name>Microsoft network server: Amount of idle time required before suspending session</q1:Name>
            <q1:Units>minutes</q1:Units>
            <q1:DisplayNumber>15</q1:DisplayNumber>
          </q1:Display>
        </q1:SecurityOptions>
        <q1:SecurityOptions>
          <q1:KeyName>MACHINE\System\CurrentControlSet\Services\LanManServer\Parameters\EnableForcedLogOff</q1:KeyName>
          <q1:SettingNumber>1</q1:SettingNumber>
          <q1:Display>
            <q1:Name>Microsoft network server: Disconnect clients when logon hours expire</q1:Name>
            <q1:Units />
            <q1:DisplayBoolean>true</q1:DisplayBoolean>
          </q1:Display>
        </q1:SecurityOptions>
        <q1:SecurityOptions>
          <q1:KeyName>MACHINE\System\CurrentControlSet\Services\LanManServer\Parameters\EnableSecuritySignature</q1:KeyName>
          <q1:SettingNumber>1</q1:SettingNumber>
          <q1:Display>
            <q1:Name>Microsoft network server: Digitally sign communications (if client agrees)</q1:Name>
            <q1:Units />
            <q1:DisplayBoolean>true</q1:DisplayBoolean>
          </q1:Display>
        </q1:SecurityOptions>
        <q1:SecurityOptions>
          <q1:KeyName>MACHINE\System\CurrentControlSet\Services\LanManServer\Parameters\NullSessionPipes</q1:KeyName>
          <q1:SettingStrings />
          <q1:Display>
            <q1:Name>Network access: Named Pipes that can be accessed anonymously</q1:Name>
            <q1:Units />
            <q1:DisplayStrings />
          </q1:Display>
        </q1:SecurityOptions>
        <q1:SecurityOptions>
          <q1:KeyName>MACHINE\System\CurrentControlSet\Services\LanManServer\Parameters\NullSessionShares</q1:KeyName>
          <q1:SettingStrings />
          <q1:Display>
            <q1:Name>Network access: Shares that can be accessed anonymously</q1:Name>
            <q1:Units />
            <q1:DisplayStrings />
          </q1:Display>
        </q1:SecurityOptions>
        <q1:SecurityOptions>
          <q1:KeyName>MACHINE\System\CurrentControlSet\Services\LanManServer\Parameters\RequireSecuritySignature</q1:KeyName>
          <q1:SettingNumber>1</q1:SettingNumber>
          <q1:Display>
            <q1:Name>Microsoft network server: Digitally sign communications (always)</q1:Name>
            <q1:Units />
            <q1:DisplayBoolean>true</q1:DisplayBoolean>
          </q1:Display>
        </q1:SecurityOptions>
        <q1:SecurityOptions>
          <q1:KeyName>MACHINE\System\CurrentControlSet\Services\LanManServer\Parameters\RestrictNullSessAccess</q1:KeyName>
          <q1:SettingNumber>1</q1:SettingNumber>
          <q1:Display>
            <q1:Name>Network access: Restrict anonymous access to Named Pipes and Shares</q1:Name>
            <q1:Units />
            <q1:DisplayBoolean>true</q1:DisplayBoolean>
          </q1:Display>
        </q1:SecurityOptions>
        <q1:SecurityOptions>
          <q1:KeyName>MACHINE\System\CurrentControlSet\Services\LanmanWorkstation\Parameters\EnablePlainTextPassword</q1:KeyName>
          <q1:SettingNumber>0</q1:SettingNumber>
          <q1:Display>
            <q1:Name>Microsoft network client: Send unencrypted password to third-party SMB servers</q1:Name>
            <q1:Units />
            <q1:DisplayBoolean>false</q1:DisplayBoolean>
          </q1:Display>
        </q1:SecurityOptions>
        <q1:SecurityOptions>
          <q1:KeyName>MACHINE\System\CurrentControlSet\Services\LanmanWorkstation\Parameters\EnableSecuritySignature</q1:KeyName>
          <q1:SettingNumber>1</q1:SettingNumber>
          <q1:Display>
            <q1:Name>Microsoft network client: Digitally sign communications (if server agrees)</q1:Name>
            <q1:Units />
            <q1:DisplayBoolean>true</q1:DisplayBoolean>
          </q1:Display>
        </q1:SecurityOptions>
        <q1:SecurityOptions>
          <q1:KeyName>MACHINE\System\CurrentControlSet\Services\LanmanWorkstation\Parameters\RequireSecuritySignature</q1:KeyName>
          <q1:SettingNumber>1</q1:SettingNumber>
          <q1:Display>
            <q1:Name>Microsoft network client: Digitally sign communications (always)</q1:Name>
            <q1:Units />
            <q1:DisplayBoolean>true</q1:DisplayBoolean>
          </q1:Display>
        </q1:SecurityOptions>
        <q1:SecurityOptions>
          <q1:KeyName>MACHINE\System\CurrentControlSet\Services\LDAP\LDAPClientIntegrity</q1:KeyName>
          <q1:SettingNumber>1</q1:SettingNumber>
          <q1:Display>
            <q1:Name>Network security: LDAP client signing requirements</q1:Name>
            <q1:Units />
            <q1:DisplayString>Negotiate signing</q1:DisplayString>
          </q1:Display>
        </q1:SecurityOptions>
        <q1:SecurityOptions>
          <q1:KeyName>MACHINE\System\CurrentControlSet\Services\Netbt\Parameters\NoNameReleaseOnDemand</q1:KeyName>
          <q1:SettingNumber>1</q1:SettingNumber>
        </q1:SecurityOptions>
        <q1:SecurityOptions>
          <q1:KeyName>MACHINE\System\CurrentControlSet\Services\Netlogon\Parameters\DisablePasswordChange</q1:KeyName>
          <q1:SettingNumber>0</q1:SettingNumber>
          <q1:Display>
            <q1:Name>Domain member: Disable machine account password changes</q1:Name>
            <q1:Units />
            <q1:DisplayBoolean>false</q1:DisplayBoolean>
          </q1:Display>
        </q1:SecurityOptions>
        <q1:SecurityOptions>
          <q1:KeyName>MACHINE\System\CurrentControlSet\Services\Netlogon\Parameters\MaximumPasswordAge</q1:KeyName>
          <q1:SettingNumber>30</q1:SettingNumber>
          <q1:Display>
            <q1:Name>Domain member: Maximum machine account password age</q1:Name>
            <q1:Units>days</q1:Units>
            <q1:DisplayNumber>30</q1:DisplayNumber>
          </q1:Display>
        </q1:SecurityOptions>
        <q1:SecurityOptions>
          <q1:KeyName>MACHINE\System\CurrentControlSet\Services\Netlogon\Parameters\RequireSignOrSeal</q1:KeyName>
          <q1:SettingNumber>1</q1:SettingNumber>
          <q1:Display>
            <q1:Name>Domain member: Digitally encrypt or sign secure channel data (always)</q1:Name>
            <q1:Units />
            <q1:DisplayBoolean>true</q1:DisplayBoolean>
          </q1:Display>
        </q1:SecurityOptions>
        <q1:SecurityOptions>
          <q1:KeyName>MACHINE\System\CurrentControlSet\Services\Netlogon\Parameters\RequireStrongKey</q1:KeyName>
          <q1:SettingNumber>1</q1:SettingNumber>
          <q1:Display>
            <q1:Name>Domain member: Require strong (Windows 2000 or later) session key</q1:Name>
            <q1:Units />
            <q1:DisplayBoolean>true</q1:DisplayBoolean>
          </q1:Display>
        </q1:SecurityOptions>
        <q1:SecurityOptions>
          <q1:KeyName>MACHINE\System\CurrentControlSet\Services\Netlogon\Parameters\SealSecureChannel</q1:KeyName>
          <q1:SettingNumber>1</q1:SettingNumber>
          <q1:Display>
            <q1:Name>Domain member: Digitally encrypt secure channel data (when possible)</q1:Name>
            <q1:Units />
            <q1:DisplayBoolean>true</q1:DisplayBoolean>
          </q1:Display>
        </q1:SecurityOptions>
        <q1:SecurityOptions>
          <q1:KeyName>MACHINE\System\CurrentControlSet\Services\Netlogon\Parameters\SignSecureChannel</q1:KeyName>
          <q1:SettingNumber>1</q1:SettingNumber>
          <q1:Display>
            <q1:Name>Domain member: Digitally sign secure channel data (when possible)</q1:Name>
            <q1:Units />
            <q1:DisplayBoolean>true</q1:DisplayBoolean>
          </q1:Display>
        </q1:SecurityOptions>
        <q1:SecurityOptions>
          <q1:KeyName>MACHINE\SYSTEM\CurrentControlSet\Services\RasMan\Parameters\DisableSavePassword</q1:KeyName>
          <q1:SettingNumber>1</q1:SettingNumber>
        </q1:SecurityOptions>
        <q1:SecurityOptions>
          <q1:KeyName>MACHINE\System\CurrentControlSet\Services\Tcpip\Parameters\DisableIPSourceRouting</q1:KeyName>
          <q1:SettingNumber>2</q1:SettingNumber>
        </q1:SecurityOptions>
        <q1:SecurityOptions>
          <q1:KeyName>MACHINE\System\CurrentControlSet\Services\Tcpip\Parameters\EnableICMPRedirect</q1:KeyName>
          <q1:SettingNumber>1</q1:SettingNumber>
        </q1:SecurityOptions>
        <q1:SecurityOptions>
          <q1:KeyName>MACHINE\System\CurrentControlSet\Services\Tcpip\Parameters\KeepAliveTime</q1:KeyName>
          <q1:SettingNumber>300000</q1:SettingNumber>
        </q1:SecurityOptions>
        <q1:SecurityOptions>
          <q1:KeyName>MACHINE\System\CurrentControlSet\Services\Tcpip\Parameters\SynAttackProtect</q1:KeyName>
          <q1:SettingNumber>1</q1:SettingNumber>
        </q1:SecurityOptions>
        <q1:SecurityOptions>
          <q1:KeyName>MACHINE\System\CurrentControlSet\Services\Tcpip\Parameters\TcpMaxDataRetransmissions</q1:KeyName>
          <q1:SettingNumber>3</q1:SettingNumber>
        </q1:SecurityOptions>
        <q1:SecurityOptions>
          <q1:KeyName>MACHINE\System\CurrentControlSet\Services\Tcpip6\Parameters\TcpMaxDataRetransmissions</q1:KeyName>
          <q1:SettingNumber>3</q1:SettingNumber>
        </q1:SecurityOptions>
        <q1:SecurityOptions>
          <q1:SystemAccessPolicyName>EnableAdminAccount</q1:SystemAccessPolicyName>
          <q1:SettingNumber>1</q1:SettingNumber>
        </q1:SecurityOptions>
        <q1:SecurityOptions>
          <q1:SystemAccessPolicyName>EnableGuestAccount</q1:SystemAccessPolicyName>
          <q1:SettingNumber>0</q1:SettingNumber>
        </q1:SecurityOptions>
        <q1:SecurityOptions>
          <q1:SystemAccessPolicyName>ForceLogoffWhenHourExpire</q1:SystemAccessPolicyName>
          <q1:SettingNumber>1</q1:SettingNumber>
        </q1:SecurityOptions>
        <q1:SecurityOptions>
          <q1:SystemAccessPolicyName>LSAAnonymousNameLookup</q1:SystemAccessPolicyName>
          <q1:SettingNumber>0</q1:SettingNumber>
        </q1:SecurityOptions>
        <q1:SecurityOptions>
          <q1:SystemAccessPolicyName>NewAdministratorName</q1:SystemAccessPolicyName>
          <q1:SettingString>"dpadmin"</q1:SettingString>
        </q1:SecurityOptions>
        <q1:SecurityOptions>
          <q1:SystemAccessPolicyName>NewGuestName</q1:SystemAccessPolicyName>
          <q1:SettingString>"dpguest"</q1:SettingString>
        </q1:SecurityOptions>
        <q1:Registry>
          <q1:Path>MACHINE\SOFTWARE</q1:Path>
          <q1:SecurityDescriptor>
            <SDDL xmlns="http://www.microsoft.com/GroupPolicy/Types/Security">D:PAR(A;CI;KA;;;BA)(A;CIIO;KA;;;CO)(A;CI;KA;;;SY)(A;CI;KR;;;BU)S:AR(AU;CIFA;KA;;;WD)</SDDL>
            <PermissionsPresent xmlns="http://www.microsoft.com/GroupPolicy/Types/Security">true</PermissionsPresent>
            <Permissions xmlns="http://www.microsoft.com/GroupPolicy/Types/Security">
              <InheritsFromParent>false</InheritsFromParent>
              <TrusteePermissions>
                <Trustee>
                  <SID xmlns="http://www.microsoft.com/GroupPolicy/Types">S-1-5-32-544</SID>
                  <Name xmlns="http://www.microsoft.com/GroupPolicy/Types">BUILTIN\Administrators</Name>
                </Trustee>
                <Type xsi:type="PermissionType">
                  <PermissionType>Allow</PermissionType>
                </Type>
                <Inherited>false</Inherited>
                <Applicability>
                  <ToSelf>true</ToSelf>
                  <ToDescendantObjects>false</ToDescendantObjects>
                  <ToDescendantContainers>true</ToDescendantContainers>
                  <ToDirectDescendantsOnly>false</ToDirectDescendantsOnly>
                </Applicability>
                <Standard>
                  <RegistryGroupedAccessEnum>Full Control</RegistryGroupedAccessEnum>
                </Standard>
                <AccessMask>983103</AccessMask>
              </TrusteePermissions>
              <TrusteePermissions>
                <Trustee>
                  <SID xmlns="http://www.microsoft.com/GroupPolicy/Types">S-1-3-0</SID>
                  <Name xmlns="http://www.microsoft.com/GroupPolicy/Types">CREATOR OWNER</Name>
                </Trustee>
                <Type xsi:type="PermissionType">
                  <PermissionType>Allow</PermissionType>
                </Type>
                <Inherited>false</Inherited>
                <Applicability>
                  <ToSelf>false</ToSelf>
                  <ToDescendantObjects>false</ToDescendantObjects>
                  <ToDescendantContainers>true</ToDescendantContainers>
                  <ToDirectDescendantsOnly>false</ToDirectDescendantsOnly>
                </Applicability>
                <Standard>
                  <RegistryGroupedAccessEnum>Full Control</RegistryGroupedAccessEnum>
                </Standard>
                <AccessMask>983103</AccessMask>
              </TrusteePermissions>
              <TrusteePermissions>
                <Trustee>
                  <SID xmlns="http://www.microsoft.com/GroupPolicy/Types">S-1-5-18</SID>
                  <Name xmlns="http://www.microsoft.com/GroupPolicy/Types">NT AUTHORITY\SYSTEM</Name>
                </Trustee>
                <Type xsi:type="PermissionType">
                  <PermissionType>Allow</PermissionType>
                </Type>
                <Inherited>false</Inherited>
                <Applicability>
                  <ToSelf>true</ToSelf>
                  <ToDescendantObjects>false</ToDescendantObjects>
                  <ToDescendantContainers>true</ToDescendantContainers>
                  <ToDirectDescendantsOnly>false</ToDirectDescendantsOnly>
                </Applicability>
                <Standard>
                  <RegistryGroupedAccessEnum>Full Control</RegistryGroupedAccessEnum>
                </Standard>
                <AccessMask>983103</AccessMask>
              </TrusteePermissions>
              <TrusteePermissions>
                <Trustee>
                  <SID xmlns="http://www.microsoft.com/GroupPolicy/Types">S-1-5-32-545</SID>
                  <Name xmlns="http://www.microsoft.com/GroupPolicy/Types">BUILTIN\Users</Name>
                </Trustee>
                <Type xsi:type="PermissionType">
                  <PermissionType>Allow</PermissionType>
                </Type>
                <Inherited>false</Inherited>
                <Applicability>
                  <ToSelf>true</ToSelf>
                  <ToDescendantObjects>false</ToDescendantObjects>
                  <ToDescendantContainers>true</ToDescendantContainers>
                  <ToDirectDescendantsOnly>false</ToDirectDescendantsOnly>
                </Applicability>
                <Standard>
                  <RegistryGroupedAccessEnum>Read</RegistryGroupedAccessEnum>
                </Standard>
                <AccessMask>131097</AccessMask>
              </TrusteePermissions>
            </Permissions>
            <AuditingPresent xmlns="http://www.microsoft.com/GroupPolicy/Types/Security">true</AuditingPresent>
            <Auditing xmlns="http://www.microsoft.com/GroupPolicy/Types/Security">
              <InheritsFromParent>true</InheritsFromParent>
              <TrusteeAuditing>
                <Trustee>
                  <SID xmlns="http://www.microsoft.com/GroupPolicy/Types">S-1-1-0</SID>
                  <Name xmlns="http://www.microsoft.com/GroupPolicy/Types">Everyone</Name>
                </Trustee>
                <Type xsi:type="AuditType">
                  <AuditType>Failure</AuditType>
                </Type>
                <Inherited>false</Inherited>
                <Applicability>
                  <ToSelf>true</ToSelf>
                  <ToDescendantObjects>false</ToDescendantObjects>
                  <ToDescendantContainers>true</ToDescendantContainers>
                  <ToDirectDescendantsOnly>false</ToDirectDescendantsOnly>
                </Applicability>
                <Standard>
                  <RegistryGroupedAccessEnum>Full Control</RegistryGroupedAccessEnum>
                </Standard>
                <AccessMask>983103</AccessMask>
              </TrusteeAuditing>
            </Auditing>
          </q1:SecurityDescriptor>
          <q1:Mode>Propogate</q1:Mode>
        </q1:Registry>
        <q1:Registry>
          <q1:Path>MACHINE\SYSTEM</q1:Path>
          <q1:SecurityDescriptor>
            <SDDL xmlns="http://www.microsoft.com/GroupPolicy/Types/Security">D:PAR(A;CI;KA;;;BA)(A;CIIO;KA;;;CO)(A;CI;KA;;;SY)(A;CI;KR;;;BU)S:AR(AU;CIFA;KA;;;WD)</SDDL>
            <PermissionsPresent xmlns="http://www.microsoft.com/GroupPolicy/Types/Security">true</PermissionsPresent>
            <Permissions xmlns="http://www.microsoft.com/GroupPolicy/Types/Security">
              <InheritsFromParent>false</InheritsFromParent>
              <TrusteePermissions>
                <Trustee>
                  <SID xmlns="http://www.microsoft.com/GroupPolicy/Types">S-1-5-32-544</SID>
                  <Name xmlns="http://www.microsoft.com/GroupPolicy/Types">BUILTIN\Administrators</Name>
                </Trustee>
                <Type xsi:type="PermissionType">
                  <PermissionType>Allow</PermissionType>
                </Type>
                <Inherited>false</Inherited>
                <Applicability>
                  <ToSelf>true</ToSelf>
                  <ToDescendantObjects>false</ToDescendantObjects>
                  <ToDescendantContainers>true</ToDescendantContainers>
                  <ToDirectDescendantsOnly>false</ToDirectDescendantsOnly>
                </Applicability>
                <Standard>
                  <RegistryGroupedAccessEnum>Full Control</RegistryGroupedAccessEnum>
                </Standard>
                <AccessMask>983103</AccessMask>
              </TrusteePermissions>
              <TrusteePermissions>
                <Trustee>
                  <SID xmlns="http://www.microsoft.com/GroupPolicy/Types">S-1-3-0</SID>
                  <Name xmlns="http://www.microsoft.com/GroupPolicy/Types">CREATOR OWNER</Name>
                </Trustee>
                <Type xsi:type="PermissionType">
                  <PermissionType>Allow</PermissionType>
                </Type>
                <Inherited>false</Inherited>
                <Applicability>
                  <ToSelf>false</ToSelf>
                  <ToDescendantObjects>false</ToDescendantObjects>
                  <ToDescendantContainers>true</ToDescendantContainers>
                  <ToDirectDescendantsOnly>false</ToDirectDescendantsOnly>
                </Applicability>
                <Standard>
                  <RegistryGroupedAccessEnum>Full Control</RegistryGroupedAccessEnum>
                </Standard>
                <AccessMask>983103</AccessMask>
              </TrusteePermissions>
              <TrusteePermissions>
                <Trustee>
                  <SID xmlns="http://www.microsoft.com/GroupPolicy/Types">S-1-5-18</SID>
                  <Name xmlns="http://www.microsoft.com/GroupPolicy/Types">NT AUTHORITY\SYSTEM</Name>
                </Trustee>
                <Type xsi:type="PermissionType">
                  <PermissionType>Allow</PermissionType>
                </Type>
                <Inherited>false</Inherited>
                <Applicability>
                  <ToSelf>true</ToSelf>
                  <ToDescendantObjects>false</ToDescendantObjects>
                  <ToDescendantContainers>true</ToDescendantContainers>
                  <ToDirectDescendantsOnly>false</ToDirectDescendantsOnly>
                </Applicability>
                <Standard>
                  <RegistryGroupedAccessEnum>Full Control</RegistryGroupedAccessEnum>
                </Standard>
                <AccessMask>983103</AccessMask>
              </TrusteePermissions>
              <TrusteePermissions>
                <Trustee>
                  <SID xmlns="http://www.microsoft.com/GroupPolicy/Types">S-1-5-32-545</SID>
                  <Name xmlns="http://www.microsoft.com/GroupPolicy/Types">BUILTIN\Users</Name>
                </Trustee>
                <Type xsi:type="PermissionType">
                  <PermissionType>Allow</PermissionType>
                </Type>
                <Inherited>false</Inherited>
                <Applicability>
                  <ToSelf>true</ToSelf>
                  <ToDescendantObjects>false</ToDescendantObjects>
                  <ToDescendantContainers>true</ToDescendantContainers>
                  <ToDirectDescendantsOnly>false</ToDirectDescendantsOnly>
                </Applicability>
                <Standard>
                  <RegistryGroupedAccessEnum>Read</RegistryGroupedAccessEnum>
                </Standard>
                <AccessMask>131097</AccessMask>
              </TrusteePermissions>
            </Permissions>
            <AuditingPresent xmlns="http://www.microsoft.com/GroupPolicy/Types/Security">true</AuditingPresent>
            <Auditing xmlns="http://www.microsoft.com/GroupPolicy/Types/Security">
              <InheritsFromParent>true</InheritsFromParent>
              <TrusteeAuditing>
                <Trustee>
                  <SID xmlns="http://www.microsoft.com/GroupPolicy/Types">S-1-1-0</SID>
                  <Name xmlns="http://www.microsoft.com/GroupPolicy/Types">Everyone</Name>
                </Trustee>
                <Type xsi:type="AuditType">
                  <AuditType>Failure</AuditType>
                </Type>
                <Inherited>false</Inherited>
                <Applicability>
                  <ToSelf>true</ToSelf>
                  <ToDescendantObjects>false</ToDescendantObjects>
                  <ToDescendantContainers>true</ToDescendantContainers>
                  <ToDirectDescendantsOnly>false</ToDirectDescendantsOnly>
                </Applicability>
                <Standard>
                  <RegistryGroupedAccessEnum>Full Control</RegistryGroupedAccessEnum>
                </Standard>
                <AccessMask>983103</AccessMask>
              </TrusteeAuditing>
            </Auditing>
          </q1:SecurityDescriptor>
          <q1:Mode>Propogate</q1:Mode>
        </q1:Registry>
      </Extension>
      <Name>Security</Name>
    </ExtensionData>
    <ExtensionData>
      <Extension xmlns:q2="http://www.microsoft.com/GroupPolicy/Settings/PublicKey" xsi:type="q2:PublicKeySettings">
        <q2:EFSSettings>
          <q2:AllowEFS>2</q2:AllowEFS>
          <q2:Options>0</q2:Options>
          <q2:CacheTimeout>0</q2:CacheTimeout>
          <q2:KeyLen>0</q2:KeyLen>
        </q2:EFSSettings>
        <q2:RootCertificateSettings>
          <q2:AllowNewCAs>true</q2:AllowNewCAs>
          <q2:TrustThirdPartyCAs>true</q2:TrustThirdPartyCAs>
          <q2:RequireUPNNamingConstraints>false</q2:RequireUPNNamingConstraints>
        </q2:RootCertificateSettings>
      </Extension>
      <Name>Public Key</Name>
    </ExtensionData>
    <ExtensionData>
      <Extension xmlns:q3="http://www.microsoft.com/GroupPolicy/Settings/Registry" xsi:type="q3:RegistrySettings">
        <q3:Policy>
          <q3:Name>Turn on Mapper I/O (LLTDIO) driver</q3:Name>
          <q3:State>Disabled</q3:State>
          <q3:Explain>This policy setting changes the operational behavior of the Mapper I/O network protocol driver.

LLTDIO allows a computer to discover the topology of a network it's connected to. It also allows a computer to initiate Quality-of-Service requests such as bandwidth estimation and network health analysis.

If you enable this policy setting, additional options are available to fine-tune your selection. You may choose the "Allow operation while in domain" option to allow LLTDIO to operate on a network interface that's connected to a managed network. On the other hand, if a network interface is connected to an unmanaged network, you may choose the "Allow operation while in public network" and "Prohibit operation while in private network" options instead.

If you disable or do not configure this policy setting, the default behavior of LLTDIO will apply.</q3:Explain>
          <q3:Supported>At least Windows Vista</q3:Supported>
          <q3:Category>Network/Link-Layer Topology Discovery</q3:Category>
        </q3:Policy>
        <q3:Policy>
          <q3:Name>Turn on Responder (RSPNDR) driver</q3:Name>
          <q3:State>Disabled</q3:State>
          <q3:Explain>This policy setting changes the operational behavior of the Responder network protocol driver.

The Responder allows a computer to participate in Link Layer Topology Discovery requests so that it can be discovered and located on the network. It also allows a computer to participate in Quality-of-Service activities such as bandwidth estimation and network health analysis.

If you enable this policy setting, additional options are available to fine-tune your selection. You may choose the "Allow operation while in domain" option to allow the Responder to operate on a network interface that's connected to a managed network. On the other hand, if a network interface is connected to an unmanaged network, you may choose the "Allow operation while in public network" and "Prohibit operation while in private network" options instead.

If you disable or do not configure this policy setting, the default behavior for the Responder will apply.</q3:Explain>
          <q3:Supported>At least Windows Vista</q3:Supported>
          <q3:Category>Network/Link-Layer Topology Discovery</q3:Category>
        </q3:Policy>
        <q3:Policy>
          <q3:Name>Turn off Microsoft Peer-to-Peer Networking Services</q3:Name>
          <q3:State>Enabled</q3:State>
          <q3:Explain>This setting turns off Microsoft Peer-to-Peer Networking Services in its entirety, and will cause all dependent applications to stop working.

Peer-to-Peer protocols allow for applications in the areas of RTC, collaboration, content distribution and distributed processing.

If you enable this setting, peer-to-peer protocols will be turned off.

If you disable this setting or do not configure it, the peer-to-peer protocols will be turned on.</q3:Explain>
          <q3:Supported>At least Windows XP Professional with SP2</q3:Supported>
          <q3:Category>Network/Microsoft Peer-to-Peer Networking Services</q3:Category>
        </q3:Policy>
        <q3:Policy>
          <q3:Name>Prohibit installation and configuration of Network Bridge on your DNS domain network</q3:Name>
          <q3:State>Enabled</q3:State>
          <q3:Explain>Determines whether a user can install and configure the Network Bridge.

Important: This settings is location aware. It only applies when a computer is connected to the same DNS domain network it was connected to when the setting was refreshed on that computer. If a computer is connected to a DNS domain network other than the one it was connected to when the setting was refreshed, this setting does not apply.

The Network Bridge allows users to create a layer 2 MAC bridge, enabling them to connect two or more network segements together. This connection appears in the Network Connections folder.

If you disable this setting or do not configure it, the user will be able to create and modify the configuration of a Network Bridge. Enabling this setting does not remove an existing Network Bridge from the user's computer.</q3:Explain>
          <q3:Supported>At least Windows XP Professional or Windows Server 2003 family</q3:Supported>
          <q3:Category>Network/Network Connections</q3:Category>
        </q3:Policy>
        <q3:Policy>
          <q3:Name>Prohibit use of Internet Connection Sharing on your DNS domain network</q3:Name>
          <q3:State>Enabled</q3:State>
          <q3:Explain>Determines whether administrators can enable and configure the Internet Connection Sharing (ICS) feature of an Internet connection and if the ICS service can run on the computer.

ICS lets administrators configure their system as an Internet gateway for a small network and provides network services, such as name resolution and addressing through DHCP, to the local private network.

If you enable this setting, ICS cannot be enabled or configured by administrators, and the ICS service cannot run on the computer. The Advanced tab in the Properties dialog box for a LAN or remote access connection is removed. The Internet Connection Sharing page is removed from the New Connection Wizard. The Network Setup Wizard is disabled.

If you disable this setting or do not configure it and have two or more connections, administrators can enable ICS. The Advanced tab in the properties dialog box for a LAN or remote access connection is available. In addition, the user is presented with the option to enable Internet Connection Sharing in the Network Setup Wizard and Make New Connection Wizard. (The Network Setup Wizard is available only in Windows XP Professional.)

By default, ICS is disabled when you create a remote access connection, but administrators can use the Advanced tab to enable it. When running the New Connection Wizard or Network Setup Wizard, administrators can choose to enable ICS.

Note: Internet Connection Sharing is only available when two or more network connections are present.

Note: When the "Prohibit access to properties of a LAN connection," "Ability to change properties of an all user remote access connection," or "Prohibit changing properties of a private remote access connection" settings are set to deny access to the Connection Properties dialog box, the Advanced tab for the connection is blocked.

Note: Nonadministrators are already prohibited from configuring Internet Connection Sharing, regardless of this setting.

Note: Disabling this setting does not prevent Wireless Hosted Networking from using the ICS service for DHCP services. To prevent the ICS service from running, on the Network Permissions tab in the network's policy properties, select the "Don't use hosted networks" check box.</q3:Explain>
          <q3:Supported>Microsoft Windows Server 2003, Windows XP, and Windows 2000 Service Pack 1 operating systems only</q3:Supported>
          <q3:Category>Network/Network Connections</q3:Category>
        </q3:Policy>
        <q3:Policy>
          <q3:Name>Require domain users to elevate when setting a network's location</q3:Name>
          <q3:State>Enabled</q3:State>
          <q3:Explain>This policy setting determines whether to require domain users to elevate when setting a network's location.

If you enable this policy setting, domain users must elevate when setting a network's location.

If you disable or do not configure this policy setting, domain users can set a network's location without elevating.</q3:Explain>
          <q3:Supported>At least Windows 7 or Windows Server 2008 R2</q3:Supported>
          <q3:Category>Network/Network Connections</q3:Category>
        </q3:Policy>
        <q3:Policy>
          <q3:Name>6to4 State</q3:Name>
          <q3:State>Enabled</q3:State>
          <q3:Explain>This policy setting allows you to configure 6to4, an address assignment and router-to-router automatic tunneling technology that is used to provide unicast IPv6 connectivity between IPv6 sites and hosts across the IPv4 Internet. 6to4 uses the global address prefix: 2002:WWXX:YYZZ::/48 in which the letters are a hexadecimal representation of the global IPv4 address (w.x.y.z) assigned to a site.

If you disable or do not configure this policy setting, the local host setting is used.

If you enable this policy setting, you will be able to configure 6to4 with one of the following settings:

Policy Default State: 6to4 is enabled if the host has only link-local IPv6 connectivity and a public IPv4 address. If no global IPv6 address is present and no global IPv4 address is present, the host will not have a 6to4 interface. If no global IPv6 address is present and a global IPv4 address is present, the host will have a 6to4 interface.

Policy Enabled State: If a global IPv4 address is present, the host will have a 6to4 interface. If no global IPv4 address is present, the host will not have a 6to4 interface.

Policy Disabled State: 6to4 is turned off and connectivity with 6to4 will not be available.

</q3:Explain>
          <q3:Supported>At least Windows 7 or Windows Server 2008 R2</q3:Supported>
          <q3:Category>Network/TCPIP Settings/IPv6 Transition Technologies</q3:Category>
          <q3:DropDownList>
            <q3:Name>Select from the following states:</q3:Name>
            <q3:State>Enabled</q3:State>
            <q3:Value>
              <q3:Name>Disabled State</q3:Name>
            </q3:Value>
          </q3:DropDownList>
        </q3:Policy>
        <q3:Policy>
          <q3:Name>IP-HTTPS State</q3:Name>
          <q3:State>Enabled</q3:State>
          <q3:Explain>This policy setting allows you to configure IP-HTTPS, a tunneling technology that uses the HTTPS protocol to provide IP connectivity to a remote network.

If you disable or do not configure this policy setting, the local host settings is used.

If you enable this policy setting, you can specify an IP-HTTPS server URL. You will be able to configure IP-HTTPS with one of the following settings:

Policy Default State: The IP-HTTPS interface is used when there are no other connectivity options.

Policy Enabled State: The IP-HTTPS interface is always present, even if the host has other connectivity options.

Policy Disabled State: No IP-HTTPS interfaces are present on the host.

</q3:Explain>
          <q3:Supported>At least Windows 7 or Windows Server 2008 R2</q3:Supported>
          <q3:Category>Network/TCPIP Settings/IPv6 Transition Technologies</q3:Category>
          <q3:EditText>
            <q3:Name>Enter the IPHTTPS Url:</q3:Name>
            <q3:State>Enabled</q3:State>
            <q3:Value>www.datapipe.com</q3:Value>
          </q3:EditText>
          <q3:DropDownList>
            <q3:Name>Select Interface state from the following options:</q3:Name>
            <q3:State>Enabled</q3:State>
            <q3:Value>
              <q3:Name>Disabled State</q3:Name>
            </q3:Value>
          </q3:DropDownList>
        </q3:Policy>
        <q3:Policy>
          <q3:Name>ISATAP State</q3:Name>
          <q3:State>Enabled</q3:State>
          <q3:Explain>This policy setting allows you to configure Intra-Site Automatic Tunnel Addressing Protocol (ISATAP), an address-to-router and host-to-host, host-to-router and router-to-host automatic tunneling technology that is used to provide unicast IPv6 connectivity between IPv6 hosts across an IPv4 intranet.

If you disable or do not configure this policy setting, the local host setting is used.

If you enable this policy setting, you will be able to configure ISATAP with one of the following settings:

Policy Default State: If the ISATAP router name is resolved successfully, the host will have ISATAP configured with a link-local address and an address for each prefix received from the ISATAP router through stateless address auto-configuration. If the ISATAP router name is not resolved successfully, ISATAP connectivity is not available on the host using the corresponding IPv4 address.

Policy Enabled State: If the ISATAP name is resolved successfully, the host will have ISATAP configured with a link-local address and an address for each prefix received from the ISATAP router through stateless address auto-configuration. If the ISATAP name is not resolved successfully, the host will have an ISATAP interface configured with a link-local address.

Policy Disabled State: No ISATAP interfaces are present on the host.

</q3:Explain>
          <q3:Supported>At least Windows 7 or Windows Server 2008 R2</q3:Supported>
          <q3:Category>Network/TCPIP Settings/IPv6 Transition Technologies</q3:Category>
          <q3:DropDownList>
            <q3:Name>Select from the following states:</q3:Name>
            <q3:State>Enabled</q3:State>
            <q3:Value>
              <q3:Name>Disabled State</q3:Name>
            </q3:Value>
          </q3:DropDownList>
        </q3:Policy>
        <q3:Policy>
          <q3:Name>Teredo State</q3:Name>
          <q3:State>Enabled</q3:State>
          <q3:Explain>This policy setting allows you to configure Teredo, an address assignment and automatic tunneling technology that provides unicast IPv6 connectivity across the IPv4 Internet.

If you disable or do not configure this policy setting, the local host settings is used.

If you enable this policy setting, you will be able to configure Teredo with one of the following settings:


Default: The default state is "Client."

Disabled: No Teredo interfaces are present on the host.

Client: The Teredo interface is present only when the host is not on a network that includes a domain controller.

Enterprise Client: The Teredo interface is always present, even if the host is on a network that includes a domain controller.

</q3:Explain>
          <q3:Supported>At least Windows 7 or Windows Server 2008 R2</q3:Supported>
          <q3:Category>Network/TCPIP Settings/IPv6 Transition Technologies</q3:Category>
          <q3:DropDownList>
            <q3:Name>Select from the following states:</q3:Name>
            <q3:State>Enabled</q3:State>
            <q3:Value>
              <q3:Name>Disabled State</q3:Name>
            </q3:Value>
          </q3:DropDownList>
        </q3:Policy>
        <q3:Policy>
          <q3:Name>Extend Point and Print connection to search Windows Update</q3:Name>
          <q3:State>Disabled</q3:State>
          <q3:Explain>This policy setting allows you to manage where client computers search for Point and Printer drivers.

If you enable this policy setting, the client computer will continue to search for compatible Point and Print drivers from Windows Update after it fails to find the compatible driver from the local driver store and the server driver cache. 

If you disable this policy setting, the client computer will only search the local driver store and server driver cache for compatible Point and Print drivers. If it is unable to find a compatible driver, then the Point and Print connection will fail.

This policy setting is not configured by default, and the behavior depends on the version of Windows that you are using. 
By default, Windows Ultimate, Professional and Home SKUs will continue to search for compatible Point and Print drivers from Windows Update, if needed. However, you must explicitly enable this policy setting for other versions of Windows (for example Windows Enterprise, and all versions of Windows Server 2008 R2) to have the same behavior.
</q3:Explain>
          <q3:Supported>At least Windows 7 or Windows Server 2008 R2</q3:Supported>
          <q3:Category>Printers</q3:Category>
        </q3:Policy>
        <q3:Policy>
          <q3:Name>Allow remote access to the Plug and Play interface</q3:Name>
          <q3:State>Disabled</q3:State>
          <q3:Explain>This policy setting allows you to allow or deny remote access to the Plug and Play interface. 
	  
If you enable this policy setting, remote connections to the Plug and Play interface are allowed.
	  
If you disable or do not configure this policy setting, remote connections to the Plug and Play interface are not allowed.</q3:Explain>
          <q3:Supported>At least Windows Vista</q3:Supported>
          <q3:Category>System/Device Installation</q3:Category>
        </q3:Policy>
        <q3:Policy>
          <q3:Name>Do not send a Windows error report when a generic driver is installed on a device</q3:Name>
          <q3:State>Enabled</q3:State>
          <q3:Explain>This policy setting allows you to specify whether to send a Windows error report when a generic driver is installed on a device.

If you enable this policy setting, a Windows error report is not sent when a generic driver is installed.

If you disable or do not configure this policy setting, a Windows Error Report is sent when a generic driver is installed.</q3:Explain>
          <q3:Supported>At least Windows Vista</q3:Supported>
          <q3:Category>System/Device Installation</q3:Category>
        </q3:Policy>
        <q3:Policy>
          <q3:Name>Prevent creation of a system restore point during device activity that would normally prompt creation of a restore point</q3:Name>
          <q3:State>Disabled</q3:State>
          <q3:Explain>This policy setting allows you to prevent Windows from creating a system restore point during device activity that would normally prompt Windows to create a system restore point. Windows normally creates restore points for certain driver activity, such as the installation of an unsigned driver. A system restore point enables you to more easily restore your system to its state before the activity. 

If you enable this policy setting, Windows does not create a system restore point when one would normally be created.

If you disable or do not configure this policy setting, Windows creates a system restore point as it normally would.</q3:Explain>
          <q3:Supported>At least Windows Vista</q3:Supported>
          <q3:Category>System/Device Installation</q3:Category>
        </q3:Policy>
        <q3:Policy>
          <q3:Name>Prevent device metadata retrieval from the Internet</q3:Name>
          <q3:State>Enabled</q3:State>
          <q3:Explain>This policy setting allows you to prevent Windows from retrieving device metadata from the Internet.
          
If you enable this policy setting, Windows does not retrieve device metadata for installed devices from the Internet. This policy setting overrides the setting in the Device Installation Settings dialog box (Control Panel &gt; System and Security &gt; System &gt; Advanced System Settings &gt; Hardware tab).

If you disable or do not configure this policy setting, the setting in the Device Installation Settings dialog box controls whether Windows retrieves device metadata from the Internet.</q3:Explain>
          <q3:Supported>At least Windows 7 or Windows Server 2008 R2</q3:Supported>
          <q3:Category>System/Device Installation</q3:Category>
        </q3:Policy>
        <q3:Policy>
          <q3:Name>Prevent Windows from sending an error report when a device driver requests additional software during installation</q3:Name>
          <q3:State>Enabled</q3:State>
          <q3:Explain>This policy allows you to prevent Windows from sending an error report when a device driver requests additional software during installation.

If you enable this policy setting, Windows does not send an error report when a device driver that requests additional software is installed.

If you disable or do not configure this policy setting, Windows sends an error report when a device driver that requests additional software is installed.</q3:Explain>
          <q3:Supported>At least Windows 7 or Windows Server 2008 R2</q3:Supported>
          <q3:Category>System/Device Installation</q3:Category>
        </q3:Policy>
        <q3:Policy>
          <q3:Name>Specify search order for device driver source locations</q3:Name>
          <q3:State>Enabled</q3:State>
          <q3:Explain>This policy setting allows you to specify the order in which Windows searches source locations for device drivers. 

If you enable this policy setting, you can select whether Windows searches Windows Update first,  searches Windows Update last, or does not search Windows Update.

If you disable or do not configure this policy setting, members of the Administrators group can determine the order in which Windows searches source locations for device drivers.</q3:Explain>
          <q3:Supported>At least Windows 7 or Windows Server 2008 R2</q3:Supported>
          <q3:Category>System/Device Installation</q3:Category>
          <q3:DropDownList>
            <q3:Name>Select search order:</q3:Name>
            <q3:State>Enabled</q3:State>
            <q3:Value>
              <q3:Name>Do not search Windows Update</q3:Name>
            </q3:Value>
          </q3:DropDownList>
        </q3:Policy>
        <q3:Policy>
          <q3:Name>Registry policy processing</q3:Name>
          <q3:State>Enabled</q3:State>
          <q3:Explain>Determines when registry policies are updated.

This setting affects all policies in the Administrative Templates folder and any other policies that store values in the registry.

It overrides customized settings that the program implementing a registry policy set when it was installed.

If you enable this setting, you can use the check boxes provided to change the options. If you disable this setting or do not configure it, it has no effect on the system.

The "Do not apply during periodic background processing" option prevents the system from updating affected policies in the background while the computer is in use. When background updates are disabled, policy changes will not take effect until the next user logon or system restart.

The "Process even if the Group Policy objects have not changed" option updates and reapplies the policies even if the policies have not changed. Many policy implementations specify that they are updated only when changed. However, you might want to update unchanged policies, such as reapplying a desired setting in case a user has changed it.</q3:Explain>
          <q3:Supported>At least Windows 2000</q3:Supported>
          <q3:Category>System/Group Policy</q3:Category>
          <q3:CheckBox>
            <q3:Name>Do not apply during periodic background processing</q3:Name>
            <q3:State>Disabled</q3:State>
          </q3:CheckBox>
          <q3:CheckBox>
            <q3:Name>Process even if the Group Policy objects have not changed</q3:Name>
            <q3:State>Enabled</q3:State>
          </q3:CheckBox>
        </q3:Policy>
        <q3:Policy>
          <q3:Name>Turn off Automatic Root Certificates Update</q3:Name>
          <q3:State>Enabled</q3:State>
          <q3:Explain>Specifies whether to automatically update root certificates using the Windows Update Web site. 

Typically, a certificate is used when you use a secure Web site or when you send and receive secure e-mail. Anyone can issue certificates, but to have transactions that are as secure as possible, certificates must be issued by a trusted certificate authority (CA). Microsoft has included a list in Windows XP and other products of companies and organizations that it considers trusted authorities.

If you enable this setting, when you are presented with a certificate issued by an untrusted root authority your computer will not contact the Windows Update web site to see if Microsoft has added the CA to its list of trusted authorities.

If you disable or do not configure this setting, your computer will contact the Windows Update Web site.</q3:Explain>
          <q3:Supported>At least Windows XP Professional with SP2 or Windows Server 2003 family with SP1</q3:Supported>
          <q3:Category>System/Internet Communication Management/Internet Communication settings</q3:Category>
        </q3:Policy>
        <q3:Policy>
          <q3:Name>Turn off Event Viewer "Events.asp" links</q3:Name>
          <q3:State>Enabled</q3:State>
          <q3:Explain>Specifies whether "Events.asp" hyperlinks are available for events within the Event Viewer application.

The Event Viewer normally makes all HTTP(S) URLs into hot links that activate the Internet browser when clicked. In addition, "More Information" is placed at the end of the description text if the event is created by a Microsoft component. This text contains a link (URL) that, if clicked, sends information about the event to Microsoft, and allows users to learn more about why that event occurred.

If you enable this setting, event description URL links are not activated and the text "More Information" is not displayed at the end of the description.

If you disable or do not configure this setting, the user can click the hyperlink which prompts the user and then sends information about the event over the internet to Microsoft.  Also, see "Events.asp URL", "Events.asp program", and "Events.asp Program Command Line Parameters" settings in "Administrative Templates/Windows Components/Event Viewer".</q3:Explain>
          <q3:Supported>At least Windows XP Professional with SP2 or Windows Server 2003 family with SP1</q3:Supported>
          <q3:Category>System/Internet Communication Management/Internet Communication settings</q3:Category>
        </q3:Policy>
        <q3:Policy>
          <q3:Name>Turn off handwriting recognition error reporting</q3:Name>
          <q3:State>Enabled</q3:State>
          <q3:Explain>Turns off the handwriting recognition error reporting tool.

The handwriting recognition error reporting tool enables users to report errors encountered in Tablet PC Input Panel. The tool generates error reports and transmits them to Microsoft over a secure connection. Microsoft uses these error reports to improve handwriting recognition in future versions of Windows.

If you enable this policy, users cannot start the handwriting recognition error reporting tool or send error reports to Microsoft.

If you disable this policy, Tablet PC users can report handwriting recognition errors to Microsoft.

If you do not configure this policy Tablet PC users can report handwriting recognition errors to Microsoft.</q3:Explain>
          <q3:Supported>At least Windows Vista</q3:Supported>
          <q3:Category>System/Internet Communication Management/Internet Communication settings</q3:Category>
        </q3:Policy>
        <q3:Policy>
          <q3:Name>Turn off Help and Support Center "Did you know?" content</q3:Name>
          <q3:State>Enabled</q3:State>
          <q3:Explain>Specifies whether to show the "Did you know?" section of Help and Support Center.

This content is dynamically updated when users who are connected to the Internet open Help and Support Center, and provides up-to-date information about Windows and the computer.

If you enable this setting, the Help and Support Center will no longer retrieve nor display "Did you know?" content.

If you disable or do not configure this setting, the Help and Support Center will retrieve and display "Did you know?" content.

You might want to enable this setting for users who do not have Internet access, because the content in the "Did you know?" section will remain static indefinitely without an Internet connection.</q3:Explain>
          <q3:Supported>At least Windows XP Professional with SP2 or Windows Server 2003 family with SP1</q3:Supported>
          <q3:Category>System/Internet Communication Management/Internet Communication settings</q3:Category>
        </q3:Policy>
        <q3:Policy>
          <q3:Name>Turn off Help and Support Center Microsoft Knowledge Base search</q3:Name>
          <q3:State>Enabled</q3:State>
          <q3:Explain>Specifies whether users can perform a Microsoft Knowledge Base search from the Help and Support Center.

The Knowledge Base is an online source of technical support information and self-help tools for Microsoft products and is searched as part of all Help and Support Center searches with the default search options.

If you enable this setting, it will remove the Knowledge Base section from the Help and Support Center "Set search options" page and only help content on the local computer will be searched. 

If you disable this setting or do not configure it, the Knowledge Base will be searched if the user has a connection to the Internet and has not disabled the Knowledge Base search from the Search Options page.</q3:Explain>
          <q3:Supported>At least Windows XP Professional with SP2 or Windows Server 2003 family with SP1</q3:Supported>
          <q3:Category>System/Internet Communication Management/Internet Communication settings</q3:Category>
        </q3:Policy>
        <q3:Policy>
          <q3:Name>Turn off Internet Connection Wizard if URL connection is referring to Microsoft.com</q3:Name>
          <q3:State>Enabled</q3:State>
          <q3:Explain>Specifies whether the Internet Connection Wizard can connect to Microsoft to download a list of Internet Service Providers (ISPs).

If you enable this setting, the "Choose a list of Internet Service Providers" path in the Internet Connection Wizard will cause the wizard to exit.  This prevents users from retrieving the list of ISPs, which resides on Microsoft servers.

If you disable or do not configure this setting, users will be able to connect to Microsoft to download a list of ISPs for their area.</q3:Explain>
          <q3:Supported>At least Windows XP Professional with SP2 or Windows Server 2003 family with SP1</q3:Supported>
          <q3:Category>System/Internet Communication Management/Internet Communication settings</q3:Category>
        </q3:Policy>
        <q3:Policy>
          <q3:Name>Turn off Internet File Association service</q3:Name>
          <q3:State>Enabled</q3:State>
          <q3:Explain>Specifies whether to use the Microsoft Web service for finding an application to open a file with an unhandled file association.

When a user opens a file that has an extension that is not associated with any applications on the machine, the user is given the choice to choose a local application or use the Web service to find an application.

If you enable this setting, the link and the dialog for using the Web service to open an unhandled file association are removed.

If you disable or do not configure this setting, the user will be allowed to use the Web service.</q3:Explain>
          <q3:Supported>At least Windows XP Professional or Windows Server 2003 family</q3:Supported>
          <q3:Category>System/Internet Communication Management/Internet Communication settings</q3:Category>
        </q3:Policy>
        <q3:Policy>
          <q3:Name>Turn off the Windows Messenger Customer Experience Improvement Program</q3:Name>
          <q3:State>Enabled</q3:State>
          <q3:Explain>Specifies whether Windows Messenger collects anonymous information about how Windows Messenger software and service is used.

With the Customer Experience Improvement program, users can allow Microsoft to collect anonymous information about how the product is used.  This information is used to improve the product in future releases.

If you enable this setting, Windows Messenger will not collect usage information and the user settings to enable the collection of usage information will not be shown.

If you disable this setting, Windows Messenger will collect anonymous usage information and the setting will not be shown.

If you do not configure this setting, users will have the choice to opt-in and allow information to be collected.</q3:Explain>
          <q3:Supported>At least Windows XP Professional with SP2 or Windows Server 2003 family</q3:Supported>
          <q3:Category>System/Internet Communication Management/Internet Communication settings</q3:Category>
        </q3:Policy>
        <q3:Policy>
          <q3:Name>Turn off Windows Customer Experience Improvement Program</q3:Name>
          <q3:State>Enabled</q3:State>
          <q3:Explain>The Windows Customer Experience Improvement Program will collect information about your hardware configuration and how you use our software and services to identify trends and usage patterns. We will not collect your name, address, or any other personally identifiable information. There are no surveys to complete, no salesperson will call, and you can continue working without interruption. It is simple and user-friendly.

If you enable this setting, all users are opted out of Windows Customer Experience Improvement Program.

If you disable this setting, all users are opted into Windows Customer Experience Improvement Program.

If you do not configure this policy setting, administrator can use the Problem Reports and Solutions component in Control Panel to enable Windows Customer Experience Improvement Program for all users.</q3:Explain>
          <q3:Supported>At least Windows Vista</q3:Supported>
          <q3:Category>System/Internet Communication Management/Internet Communication settings</q3:Category>
        </q3:Policy>
        <q3:Policy>
          <q3:Name>Turn off Windows Error Reporting</q3:Name>
          <q3:State>Enabled</q3:State>
          <q3:Explain>Controls whether or not errors are reported to Microsoft.

Error Reporting is used to report information about a system or application that has failed or has stopped responding and is used to improve the quality of the product.

If you enable this setting, users will not be given the option to report errors.

If you disable or do not configure this setting, the errors may be reported to Microsoft via the Internet or to a corporate file share.

This setting overrides any user setting made from the Control Panel for error reporting.

Also see  "Configure Error Reporting", "Display Error Notification" and "Disable Windows Error Reporting" settings under Computer Configuration/Administrative Templates/Windows Components/Windows Error Reporting.</q3:Explain>
          <q3:Supported>At least Windows XP Professional or Windows Server 2003 family</q3:Supported>
          <q3:Category>System/Internet Communication Management/Internet Communication settings</q3:Category>
        </q3:Policy>
        <q3:Policy>
          <q3:Name>Always use classic logon</q3:Name>
          <q3:State>Enabled</q3:State>
          <q3:Explain>This setting forces the user to log on to the computer using the classic logon screen. By default, a workgroup is set to use the simple logon screen. This setting only works when the computer is not on a domain.</q3:Explain>
          <q3:Supported>At least Windows XP Professional or Windows Server 2003 family</q3:Supported>
          <q3:Category>System/Logon</q3:Category>
        </q3:Policy>
        <q3:Policy>
          <q3:Name>Do not process the legacy run list</q3:Name>
          <q3:State>Enabled</q3:State>
          <q3:Explain>Ignores the customized run list.

You can create a customized list of additional programs and documents that the system starts automatically when it runs on Windows Vista, Windows XP Professional, and Windows 2000 Professional. These programs are added to the standard run list of programs and services that the system starts.

If you enable this policy setting, the system ignores the run list for Windows Vista, Windows 2000 Professional, and Windows XP Professional.

If you disable or do not configure this policy setting, Windows Vista adds any customized run list configured to its run list.

This policy setting appears in the Computer Configuration and User Configuration folders. If both policy settings are configured, the policy setting in Computer Configuration takes precedence over the policy setting in User Configuration.

Note: To create a customized run list by using a policy, use the "Run these applications at startup" policy setting.

Also, see the "Do not process the run once list" policy setting.</q3:Explain>
          <q3:Supported>At least Windows 2000</q3:Supported>
          <q3:Category>System/Logon</q3:Category>
        </q3:Policy>
        <q3:Policy>
          <q3:Name>Do not process the run once list</q3:Name>
          <q3:State>Enabled</q3:State>
          <q3:Explain>Ignores customized run-once lists.

You can create a customized list of additional programs and documents that are started automatically the next time the system starts (but not thereafter). These programs are added to the standard list of programs and services that the system starts.

If you enable this setting, the system ignores the run-once list.

If you disable this setting or do not configure it, the system runs the programs in the run-once list.

This setting appears in the Computer Configuration and User Configuration folders. If both settings are configured, the setting in Computer Configuration takes precedence over the setting in User Configuration.

Note: Customized run-once lists are stored in the registry in HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\RunOnce.

Also, see the "Do not process the legacy run list" setting.</q3:Explain>
          <q3:Supported>At least Windows 2000</q3:Supported>
          <q3:Category>System/Logon</q3:Category>
        </q3:Policy>
        <q3:Policy>
          <q3:Name>Restrictions for Unauthenticated RPC clients</q3:Name>
          <q3:State>Enabled</q3:State>
          <q3:Explain>If you enable this setting, it directs the RPC Runtime on an RPC server to restrict unauthenticated RPC clients connecting to RPC servers running on a machine. A client will be considered an authenticated client if it uses a named pipe to communicate with the server or if it uses RPC Security. RPC Interfaces that have specifically asked to be accessible by unauthenticated clients may be exempt from this restriction, depending on the selected value for this policy.

If you disable this setting or do not configure it, the value of Authenticated will be used for Windows XP and the value of None will be used for Server SKUs that support this policy setting. If you enable it, the following values are available:

--  "None" allows all RPC clients to connect to RPC Servers running on the machine on which the policy is applied.

--  "Authenticated" allows only authenticated RPC Clients (per the definition above) to connect to RPC Servers running on the machine on which the policy is applied. Interfaces that have asked to be exempt from this restriction will be granted an exemption.

-- "Authenticated without exceptions" allows only authenticated RPC Clients (per the definition above) to connect to RPC Servers running on the machine on which the policy is applied. No exceptions are allowed.

Note: This policy setting will not be applied unti the system is rebooted.</q3:Explain>
          <q3:Supported>At least Windows XP Professional with SP2</q3:Supported>
          <q3:Category>System/Remote Procedure Call</q3:Category>
          <q3:DropDownList>
            <q3:Name>RPC Runtime Unauthenticated Client Restriction to Apply:</q3:Name>
            <q3:State>Enabled</q3:State>
            <q3:Value>
              <q3:Name>Authenticated</q3:Name>
            </q3:Value>
          </q3:DropDownList>
        </q3:Policy>
        <q3:Policy>
          <q3:Name>RPC Endpoint Mapper Client Authentication</q3:Name>
          <q3:State>Enabled</q3:State>
          <q3:Explain>Enabling this setting directs RPC Clients that need to communicate with the Endpoint Mapper Service to authenticate as long as the RPC call for which the endpoint needs to be resolved has authentication information.

Disabling this setting will cause RPC Clients that need to communicate with the Endpoint Mapper Service to not authenticate. The Endpoint Mapper Service on machines running Windows NT4 (all service packs) cannot process authentication information supplied in this manner. This means that enabling this setting on a client machine will prevent that client from communicating with a Windows NT4 server using RPC if endpoint resolution is needed.

By default, RPC Clients will not use authentication to communicate with the RPC Server Endpoint Mapper Service when asking for the endpoint of a server.

Note: This policy will not be applied until the system is rebooted. </q3:Explain>
          <q3:Supported>At least Windows XP Professional with SP2</q3:Supported>
          <q3:Category>System/Remote Procedure Call</q3:Category>
        </q3:Policy>
        <q3:Policy>
          <q3:Name>Microsoft Support Diagnostic Tool: Turn on MSDT interactive communication with Support Provider</q3:Name>
          <q3:State>Disabled</q3:State>
          <q3:Explain>Microsoft Support Diagnostic Tool (MSDT) gathers diagnostic data for analysis by support professionals.

If you leave this policy setting enabled, Users will be able to use MSDT to collect and send diagnostic data to a support professional to resolve a problem.

By default, the support provider is set to Microsoft Corporation.

If you disable this policy setting, MSDT will not be able to run in support mode and no data can be collected or sent to the support provider.

If you do not configure this policy setting, MSDT Support mode will be enabled by default.

No reboots or service restarts are required for this policy to take effect: changes take effect immediately.
</q3:Explain>
          <q3:Supported>At least Windows 7 or Windows Server 2008 R2</q3:Supported>
          <q3:Category>System/Troubleshooting and Diagnostics/Microsoft Support Diagnostic Tool</q3:Category>
        </q3:Policy>
        <q3:Policy>
          <q3:Name>Troubleshooting: Allow users to access online troubleshooting content on Microsoft servers from the Troubleshooting Control Panel (via the Windows Online Troubleshooting Service - WOTS)</q3:Name>
          <q3:State>Disabled</q3:State>
          <q3:Explain>This policy setting allows users who are connected to the Internet to access and search troubleshooting content that is hosted on Microsoft content servers. Users can access online troubleshooting content from within the Troubleshooting Control Panel UI by clicking 'Yes' when they are prompted by a message that states, 'Do you want the most up-to-date troubleshooting content?'

If you enable or do not configure this policy setting, users who are connected to the Internet can access and search troubleshooting content that is hosted on Microsoft content servers, from within the Troubleshooting Control Panel user interface.

If you disable this policy setting, users can only access and search troubleshooting content that is available locally on their computers, even if they are connected to the Internet. They will be prevented from connecting to the Microsoft servers that host the Windows Online Troubleshooting Service.
    </q3:Explain>
          <q3:Supported>At least Windows 7 or Windows Server 2008 R2</q3:Supported>
          <q3:Category>System/Troubleshooting and Diagnostics/Scripted Diagnostics</q3:Category>
        </q3:Policy>
        <q3:Policy>
          <q3:Name>Enable/Disable PerfTrack</q3:Name>
          <q3:State>Disabled</q3:State>
          <q3:Explain>This policy setting specifies whether to enable or disable tracking of responsiveness events.

If you enable this policy setting, responsiveness events are processed and aggregated. The aggregated data will be transmitted to Microsoft through SQM.

if you disable this policy setting, responsiveness events are not processed.

If you do not configure this policy setting, the DPS will enable Windows Performance PerfTrack by default.
      </q3:Explain>
          <q3:Supported>At least Windows Vista</q3:Supported>
          <q3:Category>System/Troubleshooting and Diagnostics/Windows Performance PerfTrack</q3:Category>
        </q3:Policy>
        <q3:Policy>
          <q3:Name>Turn off Program Inventory</q3:Name>
          <q3:State>Enabled</q3:State>
          <q3:Explain>This policy controls the state of the Program Inventory collector in the system.
      
The PDU inventories programs and files on the system and sends information about those files to Microsoft.  This information is used to help associate files to programs and diagnose application compatibility problems.

The PDU is on by default.

If you enable this policy setting, inventory collection will be turned off and data will not be sent to Microsoft. Enabling this setting also disables collection of installation data through PCA.

If you disable or do not configure this policy setting, inventory collection will be turned on.</q3:Explain>
          <q3:Supported>At least Windows 7 or Windows Server 2008 R2</q3:Supported>
          <q3:Category>Windows Components/Application Compatibility</q3:Category>
        </q3:Policy>
        <q3:Policy>
          <q3:Name>Default behavior for AutoRun</q3:Name>
          <q3:State>Enabled</q3:State>
          <q3:Explain>Sets the default behavior for Autorun commands.

Autorun commands are generally stored in autorun.inf files. They often launch the installation program or other routines.

Prior to Windows Vista, when media containing an autorun command is inserted, the system will automatically execute the program without user intervention.

This creates a major security concern as code may be executed without user's knowledge. The default behavior in Windows Vista is to prompt the user whether autorun command is to be run. The autorun command is represented as a handler in the Autoplay dialog.

If you enable this policy, an Administrator can change the default Windows Vista behavior for autorun to:

A) Completely disable autorun commands, or
B) Revert back to Pre-Windows Vista behavior of automatically executing the autorun command.

If you disable or not configure this policy, Windows Vista will prompt the user whether autorun command is to be run.</q3:Explain>
          <q3:Supported>At least Windows Vista</q3:Supported>
          <q3:Category>Windows Components/AutoPlay Policies</q3:Category>
          <q3:DropDownList>
            <q3:Name>Default AutoRun Behavior</q3:Name>
            <q3:State>Enabled</q3:State>
            <q3:Value>
              <q3:Name>Do not execute any autorun commands</q3:Name>
            </q3:Value>
          </q3:DropDownList>
        </q3:Policy>
        <q3:Policy>
          <q3:Name>Turn off Autoplay for non-volume devices</q3:Name>
          <q3:State>Enabled</q3:State>
          <q3:Explain>If this policy is enabled, autoplay will not be enabled for non-volume devices like MTP devices. If you disable or not configure this policy, autoplay will continue to be enabled for non-volume devices.</q3:Explain>
          <q3:Supported>At least Windows 7 or Windows Server 2008 R2</q3:Supported>
          <q3:Category>Windows Components/AutoPlay Policies</q3:Category>
        </q3:Policy>
        <q3:Policy>
          <q3:Name>Maximum Log Size (KB)</q3:Name>
          <q3:State>Enabled</q3:State>
          <q3:Explain>This policy setting specifies the maximum size of the log file in kilobytes.

If you enable this policy setting, you can configure the maximum log file size to be between 1 megabyte (1024 kilobytes) and 2 terabytes (2147483647 kilobytes) in kilobyte increments.

If you disable or do not configure this policy setting, the maximum size of the log file maximum size will be set to the local configuration value. This value can be changed by the local administrator using the log properties dialog and it defaults to 20 megabytes.</q3:Explain>
          <q3:Supported>At least Windows Vista</q3:Supported>
          <q3:Category>Windows Components/Event Log Service/Application</q3:Category>
          <q3:Numeric>
            <q3:Name>Maximum Log Size (KB)</q3:Name>
            <q3:State>Enabled</q3:State>
            <q3:Value>32768</q3:Value>
          </q3:Numeric>
        </q3:Policy>
        <q3:Policy>
          <q3:Name>Retain old events</q3:Name>
          <q3:State>Disabled</q3:State>
          <q3:Explain>This policy setting controls Event Log behavior when the log file reaches its maximum size.

When this policy setting is enabled and a log file reaches its maximum size, new events are not written to the log and are lost.

When this policy setting is disabled and a log file reaches its maximum size, new events overwrite old events.

Note: Old events may or may not be retained according to the “Backup log automatically when full” policy setting.</q3:Explain>
          <q3:Supported>At least Windows Vista</q3:Supported>
          <q3:Category>Windows Components/Event Log Service/Application</q3:Category>
        </q3:Policy>
        <q3:Policy>
          <q3:Name>Maximum Log Size (KB)</q3:Name>
          <q3:State>Enabled</q3:State>
          <q3:Explain>This policy setting specifies the maximum size of the log file in kilobytes.

If you enable this policy setting, you can configure the maximum log file size to be between 1 megabyte (1024 kilobytes) and 2 terabytes (2147483647 kilobytes) in kilobyte increments.

If you disable or do not configure this policy setting, the maximum size of the log file maximum size will be set to the local configuration value. This value can be changed by the local administrator using the log properties dialog and it defaults to 20 megabytes.</q3:Explain>
          <q3:Supported>At least Windows Vista</q3:Supported>
          <q3:Category>Windows Components/Event Log Service/Security</q3:Category>
          <q3:Numeric>
            <q3:Name>Maximum Log Size (KB)</q3:Name>
            <q3:State>Enabled</q3:State>
            <q3:Value>196608</q3:Value>
          </q3:Numeric>
        </q3:Policy>
        <q3:Policy>
          <q3:Name>Retain old events</q3:Name>
          <q3:State>Disabled</q3:State>
          <q3:Explain>This policy setting controls Event Log behavior when the log file reaches its maximum size.

When this policy setting is enabled and a log file reaches its maximum size, new events are not written to the log and are lost.

When this policy setting is disabled and a log file reaches its maximum size, new events overwrite old events.

Note: Old events may or may not be retained according to the “Backup log automatically when full” policy setting.</q3:Explain>
          <q3:Supported>At least Windows Vista</q3:Supported>
          <q3:Category>Windows Components/Event Log Service/Security</q3:Category>
        </q3:Policy>
        <q3:Policy>
          <q3:Name>Maximum Log Size (KB)</q3:Name>
          <q3:State>Enabled</q3:State>
          <q3:Explain>This policy setting specifies the maximum size of the log file in kilobytes.

If you enable this policy setting, you can configure the maximum log file size to be between 1 megabyte (1024 kilobytes) and 2 terabytes (2147483647 kilobytes) in kilobyte increments.

If you disable or do not configure this policy setting, the maximum size of the log file maximum size will be set to the local configuration value. This value can be changed by the local administrator using the log properties dialog and it defaults to 20 megabytes.</q3:Explain>
          <q3:Supported>At least Windows Vista</q3:Supported>
          <q3:Category>Windows Components/Event Log Service/Setup</q3:Category>
          <q3:Numeric>
            <q3:Name>Maximum Log Size (KB)</q3:Name>
            <q3:State>Enabled</q3:State>
            <q3:Value>32768</q3:Value>
          </q3:Numeric>
        </q3:Policy>
        <q3:Policy>
          <q3:Name>Maximum Log Size (KB)</q3:Name>
          <q3:State>Enabled</q3:State>
          <q3:Explain>This policy setting specifies the maximum size of the log file in kilobytes.

If you enable this policy setting, you can configure the maximum log file size to be between 1 megabyte (1024 kilobytes) and 2 terabytes (2147483647 kilobytes) in kilobyte increments.

If you disable or do not configure this policy setting, the maximum size of the log file maximum size will be set to the local configuration value. This value can be changed by the local administrator using the log properties dialog and it defaults to 20 megabytes.</q3:Explain>
          <q3:Supported>At least Windows Vista</q3:Supported>
          <q3:Category>Windows Components/Event Log Service/System</q3:Category>
          <q3:Numeric>
            <q3:Name>Maximum Log Size (KB)</q3:Name>
            <q3:State>Enabled</q3:State>
            <q3:Value>32768</q3:Value>
          </q3:Numeric>
        </q3:Policy>
        <q3:Policy>
          <q3:Name>Retain old events</q3:Name>
          <q3:State>Disabled</q3:State>
          <q3:Explain>This policy setting controls Event Log behavior when the log file reaches its maximum size.

When this policy setting is enabled and a log file reaches its maximum size, new events are not written to the log and are lost.

When this policy setting is disabled and a log file reaches its maximum size, new events overwrite old events.

Note: Old events may or may not be retained according to the “Backup log automatically when full” policy setting.</q3:Explain>
          <q3:Supported>At least Windows Vista</q3:Supported>
          <q3:Category>Windows Components/Event Log Service/System</q3:Category>
        </q3:Policy>
        <q3:Policy>
          <q3:Name>Turn off downloading of game information</q3:Name>
          <q3:State>Enabled</q3:State>
          <q3:Explain>Manages download of game box art and ratings from the Windows Metadata Services.

If you enable this setting, game information including box art and ratings will not be downloaded. 

If you disable or do not configure this setting, game information will be downloaded from Windows Metadata Services.</q3:Explain>
          <q3:Supported>At least Windows Vista</q3:Supported>
          <q3:Category>Windows Components/Game Explorer</q3:Category>
        </q3:Policy>
        <q3:Policy>
          <q3:Name>Turn off game updates</q3:Name>
          <q3:State>Enabled</q3:State>
          <q3:Explain>Manages download of game update information from Windows Metadata Services.

If you enable this setting, game update information will not be downloaded. 

If you disable or do not configure this setting, game update information will be downloaded from Windows Metadata Services.</q3:Explain>
          <q3:Supported>At least Windows Vista</q3:Supported>
          <q3:Category>Windows Components/Game Explorer</q3:Category>
        </q3:Policy>
        <q3:Policy>
          <q3:Name>Disable remote Desktop Sharing</q3:Name>
          <q3:State>Enabled</q3:State>
          <q3:Explain>Disables the remote desktop sharing feature of NetMeeting.  Users will not be able to set it up or use it for controlling their computers remotely.</q3:Explain>
          <q3:Supported>at least Windows NetMeeting v3.0</q3:Supported>
          <q3:Category>Windows Components/NetMeeting</q3:Category>
        </q3:Policy>
        <q3:Policy>
          <q3:Name>Do not allow passwords to be saved</q3:Name>
          <q3:State>Enabled</q3:State>
          <q3:Explain>Controls whether passwords can be saved on this computer from Remote Desktop Connection.

If you enable this setting the password saving checkbox in Remote Desktop Connection will be disabled and users will no longer be able to save passwords. When a user opens an RDP file using Remote Desktop Connection and saves his settings, any password that previously existed in the RDP file will be deleted.

If you disable this setting or leave it not configured, the user will be able to save passwords using Remote Desktop Connection.</q3:Explain>
          <q3:Supported>At least Windows XP Professional with SP2 or Windows Server 2003 family with SP1</q3:Supported>
          <q3:Category>Windows Components/Remote Desktop Services/Remote Desktop Connection Client</q3:Category>
        </q3:Policy>
        <q3:Policy>
          <q3:Name>Do not allow COM port redirection</q3:Name>
          <q3:State>Enabled</q3:State>
          <q3:Explain>Specifies whether to prevent the redirection of data to client COM ports from the remote computer in a Remote Desktop Services session.

You can use this setting to prevent users from redirecting data to COM port peripherals or mapping local COM ports while they are logged on to a Remote Desktop Services session. By default, Remote Desktop Services allows this COM port redirection.

If the status is set to Enabled, users cannot redirect server data to the local COM port.

If the status is set to Disabled, Remote Desktop Services always allows COM port redirection.

If the status is set to Not Configured, COM port redirection is not specified at the Group Policy level. However, an administrator can still disable COM port redirection using the Remote Desktop Session Host Configuration tool.</q3:Explain>
          <q3:Supported>At least Windows XP Professional or Windows Server 2003 family</q3:Supported>
          <q3:Category>Windows Components/Remote Desktop Services/Remote Desktop Session Host/Device and Resource Redirection</q3:Category>
        </q3:Policy>
        <q3:Policy>
          <q3:Name>Do not allow LPT port redirection</q3:Name>
          <q3:State>Enabled</q3:State>
          <q3:Explain>Specifies whether to prevent the redirection of data to client LPT ports during a Remote Desktop Services session.

You can use this setting to prevent users from mapping local LPT ports and redirecting data from the remote computer to local LPT port peripherals. By default, Remote Desktop Services allows this LPT port redirection.

If the status is set to Enabled, users in a Remote Desktop Services session cannot redirect server data to the local LPT port.

If the status is set to Disabled, LPT port redirection is always allowed.

If the status is set to Not Configured, LPT port redirection is not specified at the Group Policy level. However, an administrator can still disable local LPT port redirection using the Remote Desktop Session Host Configuration tool.</q3:Explain>
          <q3:Supported>At least Windows XP Professional or Windows Server 2003 family</q3:Supported>
          <q3:Category>Windows Components/Remote Desktop Services/Remote Desktop Session Host/Device and Resource Redirection</q3:Category>
        </q3:Policy>
        <q3:Policy>
          <q3:Name>Do not allow smart card device redirection</q3:Name>
          <q3:State>Disabled</q3:State>
          <q3:Explain>This policy setting allows you to control the redirection of smart card devices in a Remote Desktop Services session.

If you enable this policy setting, Remote Desktop Services users cannot use a smart card to log on to a Remote Desktop Services session.

If you disable or do not configure this policy setting, smart card device redirection is allowed. By default, Remote Desktop Services automatically redirects smart card devices on connection.

Note: The client computer must be running at least Microsoft Windows 2000 Server or at least Microsoft Windows XP Professional and the target server must be joined to a domain.</q3:Explain>
          <q3:Supported>At least Windows XP Professional or Windows Server 2003 family</q3:Supported>
          <q3:Category>Windows Components/Remote Desktop Services/Remote Desktop Session Host/Device and Resource Redirection</q3:Category>
        </q3:Policy>
        <q3:Policy>
          <q3:Name>Do not allow supported Plug and Play device redirection</q3:Name>
          <q3:State>Enabled</q3:State>
          <q3:Explain>This policy setting allows you to control the redirection of supported Plug and Play devices, such as Windows Portable Devices, to the remote computer in a Remote Desktop Services session.

By default, Remote Desktop Services allows redirection of supported Plug and Play devices. Users can use the "More" option on the Local Resources tab of Remote Desktop Connection to choose the supported Plug and Play devices to redirect to the remote computer.

If you enable this policy setting, users cannot redirect their supported Plug and Play devices to the remote computer.

If you disable this policy setting or do not configure this policy setting, users can redirect their supported Plug and Play devices to the remote computer.

Note: You can also disallow redirection of supported Plug and Play devices on the Client Settings tab in the Remote Desktop Session Host Configuration tool. You can disallow redirection of specific types of supported Plug and Play devices by using the "Computer Configuration\Administrative Templates\System\Device Installation\Device Installation Restrictions" policy settings.</q3:Explain>
          <q3:Supported>At least Windows Vista</q3:Supported>
          <q3:Category>Windows Components/Remote Desktop Services/Remote Desktop Session Host/Device and Resource Redirection</q3:Category>
        </q3:Policy>
        <q3:Policy>
          <q3:Name>Redirect only the default client printer</q3:Name>
          <q3:State>Enabled</q3:State>
          <q3:Explain>This policy setting allows you to specify whether the default client printer is the only printer redirected in Remote Desktop Services sessions.

If you enable this policy setting, only the default client printer is redirected in Remote Desktop Services sessions.

If you disable or do not configure this policy setting, all client printers are redirected in Remote Desktop Services sessions.
	  </q3:Explain>
          <q3:Supported>At least Microsoft Windows Server 2008</q3:Supported>
          <q3:Category>Windows Components/Remote Desktop Services/Remote Desktop Session Host/Printer Redirection</q3:Category>
        </q3:Policy>
        <q3:Policy>
          <q3:Name>Remove "Disconnect" option from Shut Down dialog</q3:Name>
          <q3:State>Enabled</q3:State>
          <q3:Explain>This policy setting allows you to remove the "Disconnect" option from the Shut Down Windows dialog box in Remote Desktop Services sessions.

You can use this policy setting to prevent users from using this familiar method to disconnect their client from an RD Session Host server.

If you enable this policy setting, "Disconnect" does not appear as an option in the drop-down list in the Shut Down Windows dialog box.

If you disable or do not configure this policy setting, "Disconnect" is not removed from the list in the Shut Down Windows dialog box.

Note: This policy setting affects only the Shut Down Windows dialog box. It does not prevent users from using other methods to disconnect from a Remote Desktop Services session. This policy setting also does not prevent disconnected sessions at the server. You can control how long a disconnected session remains active on the server by configuring the "Computer Configuration\Administrative Templates\Windows Components\Remote Desktop Services\RD Session Host\Session Time Limits\Set time limit for disconnected sessions" policy setting.</q3:Explain>
          <q3:Supported>At least Microsoft Windows 2000 Terminal Services</q3:Supported>
          <q3:Category>Windows Components/Remote Desktop Services/Remote Desktop Session Host/Remote Session Environment</q3:Category>
        </q3:Policy>
        <q3:Policy>
          <q3:Name>Require secure RPC communication</q3:Name>
          <q3:State>Enabled</q3:State>
          <q3:Explain>Specifies whether a Remote Desktop Session Host server requires secure RPC communication with all clients or allows unsecured communication.

You can use this setting to strengthen the security of RPC communication with clients by allowing only authenticated and encrypted requests.

If the status is set to Enabled, Remote Desktop Services accepts requests from RPC clients that support secure requests, and does not allow unsecured communication with untrusted clients.

If the status is set to Disabled, Remote Desktop Services always requests security for all RPC traffic. However, unsecured communication is allowed for RPC clients that do not respond to the request.

If the status is set to Not Configured, unsecured communication is allowed.

Note: The RPC interface is used for administering and configuring Remote Desktop Services.</q3:Explain>
          <q3:Supported>At least Windows Server 2003</q3:Supported>
          <q3:Category>Windows Components/Remote Desktop Services/Remote Desktop Session Host/Security</q3:Category>
        </q3:Policy>
        <q3:Policy>
          <q3:Name>Set client connection encryption level</q3:Name>
          <q3:State>Enabled</q3:State>
          <q3:Explain>Specifies whether to require the use of a specific encryption level to secure communications between clients and RD Session Host servers during Remote Desktop Protocol (RDP) connections.

If you enable this setting, all communications between clients and RD Session Host servers during remote connections must use the encryption method specified in this setting. By default, the encryption level is set to High. The following encryption methods are available:

* High: The High setting encrypts data sent from the client to the server and from the server to the client by using strong 128-bit encryption. Use this encryption level in environments that contain only 128-bit clients (for example, clients that run Remote Desktop Connection). Clients that do not support this encryption level cannot connect to RD Session Host servers.

* Client Compatible: The Client Compatible setting encrypts data sent between the client and the server at the maximum key strength supported by the client. Use this encryption level in environments that include clients that do not support 128-bit encryption.

* Low: The Low setting encrypts only data sent from the client to the server using 56-bit encryption.

If you disable or do not configure this setting, the encryption level to be used for remote connections to RD Session Host servers is not enforced through Group Policy. However, you can configure a required encryption level for these connections by using Remote Desktop Session Host Configuration tool.

Important
FIPS compliance can be configured through the "System cryptography: Use FIPS compliant algorithms for encryption, hashing, and signing" setting in Group Policy (under Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options) or through the "FIPS Compliant" setting in Remote Desktop Session Host Configuration. The FIPS Compliant setting encrypts and decrypts data sent from the client to the server and from the server to the client, with the Federal Information Processing Standard (FIPS) 140-1 encryption algorithms, using Microsoft cryptographic modules. Use this encryption level when communications between clients and RD Session Host servers require the highest level of encryption.  If FIPS compliance is already enabled through the Group Policy "System cryptography: Use FIPS compliant algorithms for encryption, hashing, and signing" setting, that setting overrides the encryption level specified in this Group Policy setting or in the Remote Desktop Session Host Configuration tool.</q3:Explain>
          <q3:Supported>At least Windows XP Professional or Windows Server 2003 family</q3:Supported>
          <q3:Category>Windows Components/Remote Desktop Services/Remote Desktop Session Host/Security</q3:Category>
          <q3:DropDownList>
            <q3:Name>Encryption Level</q3:Name>
            <q3:State>Enabled</q3:State>
            <q3:Value>
              <q3:Name>High Level</q3:Name>
            </q3:Value>
          </q3:DropDownList>
          <q3:Text>
            <q3:Name>Choose the encryption level from the drop-down list.</q3:Name>
          </q3:Text>
        </q3:Policy>
        <q3:Policy>
          <q3:Name>Set time limit for active but idle Remote Desktop Services sessions</q3:Name>
          <q3:State>Enabled</q3:State>
          <q3:Explain>This policy setting allows you to specify the maximum amount of time that an active Remote Desktop Services session can be idle (without user input) before it is automatically disconnected.

If you enable this policy setting, you must select the desired time limit in the Idle session limit drop-down list.  Remote Desktop Services will automatically disconnect active but idle sessions after the specified amount of time. The user receives a warning two minutes before the session disconnects, which allows the user to press a key or move the mouse to keep the session active. If you have a console session, idle session time limits do not apply.

If you disable or do not configure this policy setting, Remote Desktop Services allows sessions to remain active but idle for an unlimited time. You can specify time limits for active but idle sessions on the Sessions tab in the Remote Desktop Session Host Configuration tool.

If you want Remote Desktop Services to terminate-instead of disconnect-a session when the time limit is reached, you can configure the "Computer Configuration\Administrative Templates\Windows Components\Remote Desktop Services\Remote Desktop Session Host\Session Time Limits\Terminate session when time limits are reached" policy setting.

Note: This policy setting appears in both Computer Configuration and User Configuration. If both policy settings are configured, the Computer Configuration policy setting takes precedence.</q3:Explain>
          <q3:Supported>At least Windows XP Professional or Windows Server 2003 family</q3:Supported>
          <q3:Category>Windows Components/Remote Desktop Services/Remote Desktop Session Host/Session Time Limits</q3:Category>
          <q3:DropDownList>
            <q3:Name>Idle session limit:</q3:Name>
            <q3:State>Enabled</q3:State>
            <q3:Value>
              <q3:Name>15 minutes</q3:Name>
            </q3:Value>
          </q3:DropDownList>
        </q3:Policy>
        <q3:Policy>
          <q3:Name>Set time limit for disconnected sessions</q3:Name>
          <q3:State>Enabled</q3:State>
          <q3:Explain>This policy setting allows you to configure a time limit for disconnected Remote Desktop Services sessions.

You can use this policy setting to specify the maximum amount of time that a disconnected session is kept active on the server. By default, Remote Desktop Services allows users to disconnect from a Remote Desktop Services session without logging off and ending the session.

When a session is in a disconnected state, running programs are kept active even though the user is no longer actively connected. By default, these disconnected sessions are maintained for an unlimited time on the server.

If you enable this policy setting, disconnected sessions are deleted from the server after the specified amount of time. To enforce the default behavior that disconnected sessions are maintained for an unlimited time, select "Never". If you have a console session, disconnected session time limits do not apply.

If you disable or do not configure this policy setting, disconnected sessions are maintained for an unlimited time. You can specify time limits for disconnected sessions on the Sessions tab in the Remote Desktop Session Host Configuration tool.

Note: This policy setting appears in both Computer Configuration and User Configuration. If both policy settings are configured, the Computer Configuration policy setting takes precedence.</q3:Explain>
          <q3:Supported>At least Windows XP Professional or Windows Server 2003 family</q3:Supported>
          <q3:Category>Windows Components/Remote Desktop Services/Remote Desktop Session Host/Session Time Limits</q3:Category>
          <q3:DropDownList>
            <q3:Name>End a disconnected session</q3:Name>
            <q3:State>Enabled</q3:State>
            <q3:Value>
              <q3:Name>1 minute</q3:Name>
            </q3:Value>
          </q3:DropDownList>
        </q3:Policy>
        <q3:Policy>
          <q3:Name>Do not delete temp folder upon exit</q3:Name>
          <q3:State>Disabled</q3:State>
          <q3:Explain>Specifies whether Remote Desktop Services retains a user's per-session temporary folders at logoff.

You can use this setting to maintain a user's session-specific temporary folders on a remote computer, even if the user logs off from a session. By default, Remote Desktop Services deletes a user's temporary folders when the user logs off.

If the status is set to Enabled, users' per-session temporary folders are retained when the user logs off from a session.

If the status is set to Disabled, temporary folders are deleted when a user logs off, even if the administrator specifies otherwise in the Remote Desktop Session Host Configuration tool.

If the status is set to Not Configured, Remote Desktop Services deletes the temporary folders from the remote computer at logoff, unless specified otherwise by the server administrator.

Note: This setting only takes effect if per-session temporary folders are in use on the server. That is, if you enable the "Do not use temporary folders per session" setting, this setting has no effect.</q3:Explain>
          <q3:Supported>At least Windows Server 2003</q3:Supported>
          <q3:Category>Windows Components/Remote Desktop Services/Remote Desktop Session Host/Temporary folders</q3:Category>
        </q3:Policy>
        <q3:Policy>
          <q3:Name>Do not use temporary folders per session</q3:Name>
          <q3:State>Disabled</q3:State>
          <q3:Explain>This policy setting allows you to prevent Remote Desktop Services from creating session-specific temporary folders.

You can use this policy setting to disable the creation of separate temporary folders on a remote computer for each session. By default, Remote Desktop Services creates a separate temporary folder for each active session that a user maintains on a remote computer. These temporary folders are created on the remote computer in a Temp folder under the user's profile folder and are named with the "sessionid".

If you enable this policy setting, per-session temporary folders are not created. Instead, a user's temporary files for all sessions on the remote computer are stored in a common Temp folder under the user's profile folder on the remote computer.

If you disable this policy setting, per-session temporary folders are always created, even if you specify otherwise in the Remote Desktop Session Host Configuration tool.

If you do not configure this policy setting, per-session temporary folders are created unless you specify otherwise in the Remote Desktop Session Host Configuration tool.</q3:Explain>
          <q3:Supported>At least Windows Server 2003</q3:Supported>
          <q3:Category>Windows Components/Remote Desktop Services/Remote Desktop Session Host/Temporary folders</q3:Category>
        </q3:Policy>
        <q3:Policy>
          <q3:Name>Prevent Windows Anytime Upgrade from running.</q3:Name>
          <q3:State>Enabled</q3:State>
          <q3:Explain>By default Windows Anytime Upgrade is available for all administrators. 

If you enable this policy setting, Windows Anytime Upgrade will not run.

If you disable this policy setting or set it to Not Configured, Windows Anytime Upgrade will run.</q3:Explain>
          <q3:Supported>At least Windows 7 or Windows Server 2008 R2</q3:Supported>
          <q3:Category>Windows Components/Windows Anytime Upgrade</q3:Category>
        </q3:Policy>
        <q3:Policy>
          <q3:Name>Disable Windows Error Reporting</q3:Name>
          <q3:State>Enabled</q3:State>
          <q3:Explain>If this setting is enabled, Windows Error Reporting will not send any problem information to Microsoft.  Additionally, solution information will not be available in the Action Center control panel.</q3:Explain>
          <q3:Supported>At least Windows Vista</q3:Supported>
          <q3:Category>Windows Components/Windows Error Reporting</q3:Category>
        </q3:Policy>
        <q3:Policy>
          <q3:Name>Turn off shell protocol protected mode</q3:Name>
          <q3:State>Disabled</q3:State>
          <q3:Explain>This policy setting allows you to configure the amount of functionality that the shell protocol can have. When using the full functionality of this protocol, applications can open folders and launch files. The protected mode reduces the functionality of this protocol allowing applications to only open a limited set of folders. Applications are not able to open files with this protocol when it is in the protected mode. It is recommended to leave this protocol in the protected mode to increase the security of Windows.

If you enable this policy setting the protocol is fully enabled, allowing the opening of folders and files.

If you disable this policy setting the protocol is in the protected mode, allowing applications to only open a limited set of folders.

If you do not configure this policy setting the protocol is in the protected mode, allowing applications to only open a limited set of folders.</q3:Explain>
          <q3:Supported>At least Windows XP Professional with SP2</q3:Supported>
          <q3:Category>Windows Components/Windows Explorer</q3:Category>
        </q3:Policy>
        <q3:Policy>
          <q3:Name>Disable IE security prompt for Windows Installer scripts</q3:Name>
          <q3:State>Disabled</q3:State>
          <q3:Explain>Allows Web-based programs to install software on the computer without notifying the user.

By default, when a script hosted by an Internet browser tries to install a program on the system, the system warns users and allows them to select or refuse the installation. This setting suppresses the warning and allows the installation to proceed.

This setting is designed for enterprises that use Web-based tools to distribute programs to their employees. However, because this setting can pose a security risk, it should be applied cautiously.</q3:Explain>
          <q3:Supported>At least Windows 2000</q3:Supported>
          <q3:Category>Windows Components/Windows Installer</q3:Category>
        </q3:Policy>
        <q3:Policy>
          <q3:Name>Enable user control over installs</q3:Name>
          <q3:State>Disabled</q3:State>
          <q3:Explain>Permits users to change installation options that typically are available only to system administrators.

This setting bypasses some of the security features of Windows Installer. It permits installations to complete that otherwise would be halted due to a security violation.

The security features of Windows Installer prevent users from changing installation options typically reserved for system administrators, such as specifying the directory to which files are installed. If Windows Installer detects that an installation package has permitted the user to change a protected option, it stops the installation and displays a message. These security features operate only when the installation program is running in a privileged security context in which it has access to directories denied to the user.

This setting is designed for less restrictive environments. It can be used to circumvent errors in an installation program that prevents software from being installed.</q3:Explain>
          <q3:Supported>At least Windows 2000</q3:Supported>
          <q3:Category>Windows Components/Windows Installer</q3:Category>
        </q3:Policy>
        <q3:Policy>
          <q3:Name>Prohibit non-administrators from applying vendor signed updates</q3:Name>
          <q3:State>Enabled</q3:State>
          <q3:Explain>This setting controls the ability of non-administrators to install updates that have been digitally signed by the application vendor.

Non-administrator updates provide a mechanism for the author of an application to create digitally signed updates that can be applied by non-privileged users.

If you enable this policy setting, only administrators or users with administrative privileges can apply updates to Windows Installer based application. 

If you disable this policy setting, users without administrative privileges will be able to install non-administrator updates.</q3:Explain>
          <q3:Supported>Windows Installer v3.0</q3:Supported>
          <q3:Category>Windows Components/Windows Installer</q3:Category>
        </q3:Policy>
        <q3:Policy>
          <q3:Name>Do Not Show First Use Dialog Boxes</q3:Name>
          <q3:State>Enabled</q3:State>
          <q3:Explain>Do Not Show First Use Dialog Boxes

This policy prevents the Privacy Options and Installation Options dialog boxes from being displayed the first time a user starts Windows Media Player.

This policy prevents the dialog boxes which allow users to select privacy, file types, and other desktop options from being displayed when the Player is first started. Some of the options can be configured by using other Windows Media Player group policies.

When this policy is not configured or disabled, the dialog boxes are displayed when the user starts the Player for the first time.</q3:Explain>
          <q3:Supported>Windows Media Player 9 Series and later.</q3:Supported>
          <q3:Category>Windows Components/Windows Media Player</q3:Category>
        </q3:Policy>
        <q3:Policy>
          <q3:Name>Configure Automatic Updates</q3:Name>
          <q3:State>Disabled</q3:State>
          <q3:Explain>Specifies whether this computer will receive security updates and other important downloads through the Windows automatic updating service.

This setting lets you specify if automatic updates are enabled on this computer. If the service is enabled, you must select one of the four options in the Group Policy Setting:

2 = Notify before downloading any updates and notify again before installing them.

When Windows finds updates that apply to this computer, an icon appears in the status area with a message that updates are ready to be downloaded. Clicking the icon or message provides the option to select the specific updates to download. Windows then downloads the selected updates in the background. When the download is complete, the icon appears in the status area again, with notification that the updates are ready to be installed. Clicking the icon or message provides the option to select which updates to install.

3 = (Default setting) Download the updates automatically and notify when they are ready to be installed

Windows finds updates that apply to your computer and downloads these updates in the background (the user is not notified or interrupted during this process). When the download is complete, the icon appears in the status area, with notification that the updates are ready to be installed. Clicking the icon or message provides the option to select which updates to install.

4 = Automatically download updates and install them on the schedule specified below

Specify the schedule using the options in the Group Policy Setting. If no schedule is specified, the default schedule for all installations will be everyday at 3:00 AM. If any of the updates require a restart to complete the installation, Windows will restart the computer automatically. (If a user is logged on to the computer when Windows is ready to restart, the user will be notified and given the option to delay the restart.)

5 = Allow local administrators to select the configuration mode that Automatic Updates should notify and install updates

With this option, the local administrators will be allowed to use the Automatic Updates control panel to select a configuration option of their choice. For example they can choose their own scheduled installation time. Local administrators will not be allowed to disable Automatic Updates' configuration.

To use this setting, click Enabled, and then select one of the options (2, 3, 4 or 5). If you select 4, you can set a recurring schedule (if no schedule is specified, all installations will occur everyday at 3:00 AM).

If the status is set to Enabled, Windows recognizes when this computer is online and uses its Internet connection to search Windows Update for updates that apply to this computer.

If the status is set to Disabled, any updates that are available on Windows Update must be downloaded and installed manually. To do this, go to http://windowsupdate.microsoft.com or click Start, click Programs (or click All Programs), and then click Windows Update.

If the status is set to Not Configured, use of Automatic Updates is not specified at the Group Policy level. However, an administrator can still configure Automatic Updates through Control Panel.</q3:Explain>
          <q3:Supported>At least Windows 2000 Service Pack 3 or Windows XP Professional Service Pack 1</q3:Supported>
          <q3:Category>Windows Components/Windows Update</q3:Category>
        </q3:Policy>
        <q3:Policy>
          <q3:Name>Do not display 'Install Updates and Shut Down' option in Shut Down Windows dialog box</q3:Name>
          <q3:State>Disabled</q3:State>
          <q3:Explain>This policy setting allows you to manage whether the 'Install Updates and Shut Down' option is displayed in the Shut Down Windows dialog box.

If you enable this policy setting, 'Install Updates and Shut Down' will not appear as a choice in the Shut Down Windows dialog box, even if updates are available for installation when the user selects the Shut Down option in the Start menu.

If you disable or do not configure this policy setting, the 'Install Updates and Shut Down' option will be available in the Shut Down Windows dialog box if updates are available when the user selects the Shut Down option in the Start menu.</q3:Explain>
          <q3:Supported>At least Windows XP Professional with SP2</q3:Supported>
          <q3:Category>Windows Components/Windows Update</q3:Category>
        </q3:Policy>
      </Extension>
      <Name>Registry</Name>
    </ExtensionData>
  </Computer>
  <User>
    <VersionDirectory>1</VersionDirectory>
    <VersionSysvol>1</VersionSysvol>
    <Enabled>true</Enabled>
    <ExtensionData>
      <Extension xmlns:q4="http://www.microsoft.com/GroupPolicy/Settings/Registry" xsi:type="q4:RegistrySettings">
        <q4:Policy>
          <q4:Name>Enable screen saver</q4:Name>
          <q4:State>Enabled</q4:State>
          <q4:Explain>Enables desktop screen savers.

If you disable this setting, screen savers do not run. Also, this setting disables the Screen Saver section of the Screen Saver dialog in the Personalization or Display Control Panel. As a result, users cannot change the screen saver options.

If you do not configure it, this setting has no effect on the system.

If you enable it, a screen saver runs, provided the following two conditions hold: First, a valid screen saver on the client is specified through the "Screen Saver executable name" setting or through Control Panel on the client computer. Second, the screen saver timeout is set to a nonzero value through the setting or Control Panel.

Also, see the "Prevent changing Screen Saver" setting.</q4:Explain>
          <q4:Supported>At least Windows 2000 Service Pack 1</q4:Supported>
          <q4:Category>Control Panel/Personalization</q4:Category>
        </q4:Policy>
        <q4:Policy>
          <q4:Name>Password protect the screen saver</q4:Name>
          <q4:State>Enabled</q4:State>
          <q4:Explain>Determines whether screen savers used on the computer are password protected.

If you enable this setting, all screen savers are password protected. If you disable this setting, password protection cannot be set on any screen saver.

This setting also disables the "Password protected" checkbox on the Screen Saver dialog in the Personalization or Display Control Panel, preventing users from changing the password protection setting.

If you do not configure this setting, users can choose whether or not to set password protection on each screen saver.

To ensure that a computer will be password protected, enable the "Enable Screen Saver" setting and specify a timeout via the "Screen Saver timeout" setting.

Note: To remove the Screen Saver dialog, use the "Prevent changing Screen Saver" setting.</q4:Explain>
          <q4:Supported>At least Windows 2000 Service Pack 1</q4:Supported>
          <q4:Category>Control Panel/Personalization</q4:Category>
        </q4:Policy>
        <q4:Policy>
          <q4:Name>Screen saver timeout</q4:Name>
          <q4:State>Enabled</q4:State>
          <q4:Explain>Specifies how much user idle time must elapse before the screen saver is launched.

When configured, this idle time can be set from a minimum of 1 second to a maximum of 86,400 seconds, or 24 hours. If set to zero, the screen saver will not be started.

This setting has no effect under any of the following circumstances:

    - The setting is disabled or not configured.

    - The wait time is set to zero.

    - The "Enable Screen Saver" setting is disabled.

    - Neither the "Screen saver executable name" setting nor the Screen Saver dialog of the client computer's Personalization or Display Control Panel specifies a valid existing screen saver program on the client.

When not configured, whatever wait time is set on the client through the Screen Saver dialog in the Personalization or Display Control Panel is used. The default is 15 minutes.</q4:Explain>
          <q4:Supported>At least Windows 2000 Service Pack 1</q4:Supported>
          <q4:Category>Control Panel/Personalization</q4:Category>
          <q4:Text>
            <q4:Name>Number of seconds to wait to enable the screen saver</q4:Name>
          </q4:Text>
          <q4:Text>
            <q4:Name> </q4:Name>
          </q4:Text>
          <q4:Numeric>
            <q4:Name>Seconds:</q4:Name>
            <q4:State>Enabled</q4:State>
            <q4:Value>900</q4:Value>
          </q4:Numeric>
        </q4:Policy>
        <q4:Policy>
          <q4:Name>Turn off Help Experience Improvement Program</q4:Name>
          <q4:State>Enabled</q4:State>
          <q4:Explain>Specifies whether users can participate in the Help Experience Improvement program. The Help Experience Improvement program collects information about how customers use Windows Help so that Microsoft can improve it.

If this setting is enabled, this policy prevents users from participating in the Help Experience Improvement program.

If this setting is disabled or not configured, users will be able to turn on the Help Experience Improvement program feature from the Help and Support settings page.</q4:Explain>
          <q4:Supported>At least Windows Vista</q4:Supported>
          <q4:Category>System/Internet Communication Management/Internet Communication settings</q4:Category>
        </q4:Policy>
        <q4:Policy>
          <q4:Name>Turn off Help Ratings</q4:Name>
          <q4:State>Enabled</q4:State>
          <q4:Explain>Specifies whether users can provide ratings for Help content.

If this setting is enabled, this policy setting prevents ratings controls from being added to Help content.

If this setting is disabled or not configured, a rating control will be added to Help topics.

Users can use the control to provide feedback on the quality and usefulness of the Help and Support content.</q4:Explain>
          <q4:Supported>At least Windows Vista</q4:Supported>
          <q4:Category>System/Internet Communication Management/Internet Communication settings</q4:Category>
        </q4:Policy>
        <q4:Policy>
          <q4:Name>Hide mechanisms to remove zone information</q4:Name>
          <q4:State>Enabled</q4:State>
          <q4:Explain>This policy setting allows you to manage whether users can manually remove the zone information from saved file attachments by clicking the Unblock button in the file’s property sheet or by using a check box in the security warning dialog. Removing the zone information allows users to open potentially dangerous file attachments that Windows has blocked users from opening.

If you enable this policy setting Windows hides the checkbox and Unblock button.

If you disable this policy setting Windows shows the checkbox and Unblock button.

If you do not configure this policy setting Windows shows the checkbox and Unblock button.</q4:Explain>
          <q4:Supported>At least Windows XP Professional with SP2</q4:Supported>
          <q4:Category>Windows Components/Attachment Manager</q4:Category>
        </q4:Policy>
      </Extension>
      <Name>Registry</Name>
    </ExtensionData>
  </User>
  <LinksTo>
    <SOMName>FISMA</SOMName>
    <SOMPath>FISMA.local</SOMPath>
    <Enabled>true</Enabled>
    <NoOverride>false</NoOverride>
  </LinksTo>
</GPO>