<?xml version="1.0" encoding="utf-16"?>
<GPO xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://www.microsoft.com/GroupPolicy/Settings">
  <Identifier>
    <Identifier xmlns="http://www.microsoft.com/GroupPolicy/Types">{B4D14A9E-790E-456B-84EA-0D297D436E45}</Identifier>
    <Domain xmlns="http://www.microsoft.com/GroupPolicy/Types">awesome.com</Domain>
  </Identifier>
  <Name>RDP</Name>
  <IncludeComments>true</IncludeComments>
  <CreatedTime>2024-03-13T19:24:25</CreatedTime>
  <ModifiedTime>2024-03-13T19:44:46</ModifiedTime>
  <ReadTime>2024-03-17T22:27:40.2093905Z</ReadTime>
  <SecurityDescriptor>
    <SDDL xmlns="http://www.microsoft.com/GroupPolicy/Types/Security">O:DAG:DAD:PAI(OA;CI;CR;edacfd8f-ffb3-11d1-b41d-00a0c968f939;;AU)(A;;CCDCLCSWRPWPDTLOSDRCWDWO;;;DA)(A;CI;CCDCLCSWRPWPDTLOSDRCWDWO;;;DA)(A;CI;CCDCLCSWRPWPDTLOSDRCWDWO;;;S-1-5-21-4055819597-835068841-4109543696-519)(A;CI;LCRPLORC;;;ED)(A;CI;LCRPLORC;;;AU)(A;CI;CCDCLCSWRPWPDTLOSDRCWDWO;;;SY)(A;CIIO;CCDCLCSWRPWPDTLOSDRCWDWO;;;CO)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-4055819597-835068841-4109543696-512</SID>
      <Name xmlns="http://www.microsoft.com/GroupPolicy/Types">AWESOME\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-4055819597-835068841-4109543696-512</SID>
      <Name xmlns="http://www.microsoft.com/GroupPolicy/Types">AWESOME\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-21-4055819597-835068841-4109543696-519</SID>
          <Name xmlns="http://www.microsoft.com/GroupPolicy/Types">AWESOME\Enterprise Admins</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-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>
      <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-21-4055819597-835068841-4109543696-512</SID>
          <Name xmlns="http://www.microsoft.com/GroupPolicy/Types">AWESOME\Domain Admins</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>
    </Permissions>
    <AuditingPresent xmlns="http://www.microsoft.com/GroupPolicy/Types/Security">false</AuditingPresent>
  </SecurityDescriptor>
  <FilterDataAvailable>true</FilterDataAvailable>
  <Computer>
    <VersionDirectory>2</VersionDirectory>
    <VersionSysvol>2</VersionSysvol>
    <Enabled>true</Enabled>
    <ExtensionData>
      <Extension xmlns:q1="http://www.microsoft.com/GroupPolicy/Settings/Security" xsi:type="q1:SecuritySettings" />
      <Name>Security</Name>
    </ExtensionData>
    <ExtensionData>
      <Extension xmlns:q2="http://www.microsoft.com/GroupPolicy/Settings/Services" xsi:type="q2:ServiceSettings">
        <q2:NTServices clsid="{2CFB484A-4E96-4b5d-A0B6-093D2F91E6AE}">
          <q2:NTService clsid="{AB6F0B67-341F-4e51-92F9-005FBFBA1A43}" name="TermService" image="2" changed="2023-10-06 01:26:27" uid="{9C780A19-EF11-4BA3-9945-06923F1723A1}">
            <q2:GPOSettingOrder>1</q2:GPOSettingOrder>
            <q2:Properties startupType="AUTOMATIC" serviceName="TermService" timeout="30" firstFailure="RESTART" secondFailure="RESTART" thirdFailure="RESTART" resetFailCountDelay="0" restartServiceDelay="60000" />
            <q2:Filters />
          </q2:NTService>
        </q2:NTServices>
      </Extension>
      <Name>Services</Name>
    </ExtensionData>
    <ExtensionData>
      <Extension xmlns:q3="http://www.microsoft.com/GroupPolicy/Settings/WindowsFirewall" xsi:type="q3:WindowsFirewallSettings">
        <q3:GlobalSettings>
          <q3:PolicyVersion>
            <q3:Value>538</q3:Value>
          </q3:PolicyVersion>
        </q3:GlobalSettings>
        <q3:DomainProfile>
          <q3:DefaultInboundAction>
            <q3:Value>true</q3:Value>
          </q3:DefaultInboundAction>
        </q3:DomainProfile>
        <q3:PublicProfile>
          <q3:DefaultInboundAction>
            <q3:Value>true</q3:Value>
          </q3:DefaultInboundAction>
        </q3:PublicProfile>
        <q3:PrivateProfile>
          <q3:DefaultInboundAction>
            <q3:Value>true</q3:Value>
          </q3:DefaultInboundAction>
        </q3:PrivateProfile>
        <q3:InboundFirewallRules>
          <q3:Version>2.26</q3:Version>
          <q3:Action>Allow</q3:Action>
          <q3:Name>@FirewallAPI.dll,-28778</q3:Name>
          <q3:Dir>In</q3:Dir>
          <q3:App>%SystemRoot%\system32\RdpSa.exe</q3:App>
          <q3:Protocol>6</q3:Protocol>
          <q3:Desc>@FirewallAPI.dll,-28779</q3:Desc>
          <q3:Active>true</q3:Active>
          <q3:Edge>true</q3:Edge>
          <q3:EmbedCtxt>@FirewallAPI.dll,-28752</q3:EmbedCtxt>
        </q3:InboundFirewallRules>
        <q3:InboundFirewallRules>
          <q3:Version>2.26</q3:Version>
          <q3:Action>Allow</q3:Action>
          <q3:Name>@FirewallAPI.dll,-28776</q3:Name>
          <q3:Dir>In</q3:Dir>
          <q3:App>%SystemRoot%\system32\svchost.exe</q3:App>
          <q3:Svc>termservice</q3:Svc>
          <q3:LPort>3389</q3:LPort>
          <q3:Protocol>17</q3:Protocol>
          <q3:Desc>@FirewallAPI.dll,-28777</q3:Desc>
          <q3:Active>true</q3:Active>
          <q3:EmbedCtxt>@FirewallAPI.dll,-28752</q3:EmbedCtxt>
        </q3:InboundFirewallRules>
        <q3:InboundFirewallRules>
          <q3:Version>2.26</q3:Version>
          <q3:Action>Allow</q3:Action>
          <q3:Name>@FirewallAPI.dll,-28775</q3:Name>
          <q3:Dir>In</q3:Dir>
          <q3:App>%SystemRoot%\system32\svchost.exe</q3:App>
          <q3:Svc>termservice</q3:Svc>
          <q3:LPort>3389</q3:LPort>
          <q3:Protocol>6</q3:Protocol>
          <q3:Desc>@FirewallAPI.dll,-28756</q3:Desc>
          <q3:Active>true</q3:Active>
          <q3:EmbedCtxt>@FirewallAPI.dll,-28752</q3:EmbedCtxt>
        </q3:InboundFirewallRules>
      </Extension>
      <Name>Windows Firewall</Name>
    </ExtensionData>
    <ExtensionData>
      <Extension xmlns:q4="http://www.microsoft.com/GroupPolicy/Settings/Registry" xsi:type="q4:RegistrySettings">
        <q4:Policy>
          <q4:Name>Allow users to connect remotely by using Remote Desktop Services</q4:Name>
          <q4:State>Enabled</q4:State>
          <q4:Explain>This policy setting allows you to configure remote access to computers by using Remote Desktop Services.

If you enable this policy setting, users who are members of the Remote Desktop Users group on the target computer can connect remotely to the target computer by using Remote Desktop Services.

If you disable this policy setting, users cannot connect remotely to the target computer by using Remote Desktop Services. The target computer will maintain any current connections, but will not accept any new incoming connections.

If you do not configure this policy setting, Remote Desktop Services uses the Remote Desktop setting on the target computer to determine whether the remote connection is allowed. This setting is found on the Remote tab in the System properties sheet. By default, remote connections are not allowed. 

Note: You can limit which clients are able to connect remotely by using Remote Desktop Services by configuring the policy setting at Computer Configuration\Administrative Templates\Windows Components\Remote Desktop Services\Remote Desktop Session Host\Security\Require user authentication for remote connections by using Network Level Authentication. 

You can limit the number of users who can connect simultaneously by configuring the policy setting at Computer Configuration\Administrative Templates\Windows Components\Remote Desktop Services\Remote Desktop Session Host\Connections\Limit number of connections, or by configuring the policy setting Maximum Connections by using the Remote Desktop Session Host WMI Provider.
</q4:Explain>
          <q4:Supported>At least Windows Server 2003 operating systems or Windows XP Professional</q4:Supported>
          <q4:Category>Windows Components/Remote Desktop Services/Remote Desktop Session Host/Connections</q4:Category>
        </q4:Policy>
        <q4:Policy>
          <q4:Name>Limit number of connections</q4:Name>
          <q4:State>Enabled</q4:State>
          <q4:Explain>Specifies whether Remote Desktop Services limits the number of simultaneous connections to the server.

You can use this setting to restrict the number of Remote Desktop Services sessions that can be active on a server. If this number is exceeded, addtional users who try to connect receive an error message telling them that the server is busy and to try again later. Restricting the number of sessions improves performance because fewer sessions are demanding system resources. By default, RD Session Host servers allow an unlimited number of Remote Desktop Services sessions, and Remote Desktop for Administration allows two Remote Desktop Services sessions.

To use this setting, enter the number of connections you want to specify as the maximum for the server. To specify an unlimited number of connections, type 999999.

If the status is set to Enabled, the maximum number of connections is limited to the specified number consistent with the version of Windows and the mode of Remote Desktop Services running on the server.

If the status is set to Disabled or Not Configured, limits to the number of connections are not enforced at the Group Policy level.

Note: This setting is designed to be used on RD Session Host servers (that is, on servers running Windows with Remote Desktop Session Host role service installed).</q4:Explain>
          <q4:Supported>At least Windows Server 2003</q4:Supported>
          <q4:Category>Windows Components/Remote Desktop Services/Remote Desktop Session Host/Connections</q4:Category>
          <q4:Numeric>
            <q4:Name>RD Maximum Connections allowed</q4:Name>
            <q4:State>Enabled</q4:State>
            <q4:Value>999999</q4:Value>
          </q4:Numeric>
          <q4:Text>
            <q4:Name>Type 999999 for unlimited connections.</q4:Name>
          </q4:Text>
        </q4:Policy>
        <q4:Policy>
          <q4:Name>Restrict Remote Desktop Services users to a single Remote Desktop Services session</q4:Name>
          <q4:State>Disabled</q4:State>
          <q4:Explain>This policy setting allows you to restrict users to a single Remote Desktop Services session.

If you enable this policy setting, users who log on remotely by using Remote Desktop Services will be restricted to a single session (either active or disconnected) on that server. If the user leaves the session in a disconnected state, the user automatically reconnects to that session at the next logon.

If you disable this policy setting, users are allowed to make unlimited simultaneous remote connections by using Remote Desktop Services.

If you do not configure this policy setting,  this policy setting is not specified at the Group Policy level.
</q4:Explain>
          <q4:Supported>At least Windows Server 2003</q4:Supported>
          <q4:Category>Windows Components/Remote Desktop Services/Remote Desktop Session Host/Connections</q4:Category>
        </q4:Policy>
        <q4:Policy>
          <q4:Name>Do not allow Clipboard redirection</q4:Name>
          <q4:State>Disabled</q4:State>
          <q4:Explain>This policy setting specifies whether to prevent the sharing of Clipboard contents (Clipboard redirection) between a remote computer and a client computer during a Remote Desktop Services session.

You can use this setting to prevent users from redirecting Clipboard data to and from the remote computer and the local computer. By default, Remote Desktop Services allows Clipboard redirection.

If you enable this policy setting, users cannot redirect Clipboard data.

If you disable this policy setting, Remote Desktop Services always allows Clipboard redirection.

If you do not configure this policy setting, Clipboard redirection is not specified at the Group Policy level. 
</q4:Explain>
          <q4:Supported>At least Windows Server 2003 operating systems or Windows XP Professional</q4:Supported>
          <q4:Category>Windows Components/Remote Desktop Services/Remote Desktop Session Host/Device and Resource Redirection</q4:Category>
        </q4:Policy>
        <q4:Policy>
          <q4:Name>Always prompt for password upon connection</q4:Name>
          <q4:State>Enabled</q4:State>
          <q4:Explain>This policy setting specifies whether Remote Desktop Services always prompts the client for a password upon connection.

You can use this setting to enforce a password prompt for users logging on to Remote Desktop Services, even if they already provided the password in the Remote Desktop Connection client.

By default, Remote Desktop Services allows users to automatically log on by entering a password in the Remote Desktop Connection client.

If you enable this policy setting, users cannot automatically log on to Remote Desktop Services by supplying their passwords in the Remote Desktop Connection client. They are prompted for a password to log on.

If you disable this policy setting, users can always log on to Remote Desktop Services automatically by supplying their passwords in the Remote Desktop Connection client.

If you do not configure this policy setting, automatic logon is not specified at the Group Policy level.
</q4:Explain>
          <q4:Supported>At least Windows Server 2003 operating systems or Windows XP Professional</q4:Supported>
          <q4:Category>Windows Components/Remote Desktop Services/Remote Desktop Session Host/Security</q4:Category>
        </q4:Policy>
        <q4:Policy>
          <q4:Name>Set client connection encryption level</q4:Name>
          <q4:State>Enabled</q4:State>
          <q4:Explain>Specifies whether to require the use of a specific encryption level to secure communications between client computers and RD Session Host servers during Remote Desktop Protocol (RDP) connections. This policy only applies when you are using native RDP encryption. However, native RDP encryption (as opposed to SSL encryption) is not recommended. This policy does not apply to SSL encryption.

If you enable this policy 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 by 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.

Important

FIPS compliance can be configured through the System cryptography. Use FIPS compliant algorithms for encryption, hashing, and signing settings in Group Policy (under Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options.) 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 encryption algorithms, by using Microsoft cryptographic modules. Use this encryption level when communications between clients and RD Session Host servers requires the highest level of encryption.
</q4:Explain>
          <q4:Supported>At least Windows Server 2003 operating systems or Windows XP Professional</q4:Supported>
          <q4:Category>Windows Components/Remote Desktop Services/Remote Desktop Session Host/Security</q4:Category>
          <q4:DropDownList>
            <q4:Name>Encryption Level</q4:Name>
            <q4:State>Enabled</q4:State>
            <q4:Value>
              <q4:Name>High Level</q4:Name>
            </q4:Value>
          </q4:DropDownList>
          <q4:Text>
            <q4:Name>Choose the encryption level from the drop-down list.</q4:Name>
          </q4:Text>
        </q4:Policy>
      </Extension>
      <Name>Registry</Name>
    </ExtensionData>
  </Computer>
  <User>
    <VersionDirectory>1</VersionDirectory>
    <VersionSysvol>1</VersionSysvol>
    <Enabled>true</Enabled>
  </User>
  <LinksTo>
    <SOMName>WIN-OST5JSRD26D</SOMName>
    <SOMPath>awesome.com/WIN-OST5JSRD26D</SOMPath>
    <Enabled>true</Enabled>
    <NoOverride>false</NoOverride>
  </LinksTo>
</GPO>