<div>
So is group policy is the only way to change it? <br />
<br />
In 2008, I could go to:<br />
&nbsp; Start<br />
&nbsp; Administrative Tools<br />
&nbsp; Remote Desktop Services<br />
&nbsp; Remote Desktop Session Host Configuration<br />
<br />
But in 2016, I do not see &quot;Remote Desktop Session Host Configuration&quot;. &nbsp;All I have is:<br />
Remote Desktop Licensing Manager<br />
and Remote Desktop Licensing Diagnoser<br />
<br />
I assume this is now done under &quot;Server Manager\Remote Desktop Services&quot; but I can't figure out where it is.
</div>


So is group policy is the only way to change it?

In 2008, I could go to:
  Start
  Administrative Tools
  Remote Desktop Services
  Remote Desktop Session Host Configuration

But in 2016, I do not see "Remote Desktop Session Host Configuration".  All I have is:
Remote Desktop Licensing Manager
and Remote Desktop Licensing Diagnoser

I assume this is now done under "Server Manager\Remote Desktop Services" but I can't figure out where it is.

<div>
The only place is the one I gave you.
</div>


<div>
<div class="content wysiwyg-content">
I cannot seem to figure out where I allow/disallow local resources mapping (specifically drives) from the HOST side of a 2016 RDP server. &nbsp;I know how to set it up on the client but my drives are not showing up when I RDP so, I assume it is disallowed on the host and I cannot find where to configure this. I've seen articles that explain where to find it on 2003, 2008 and 2012 but not 2016.<br />
<br />
Can someone please provide SPECIFIC directions where I might find this on a 2016 server?
</div>
</div>


I cannot seem to figure out where I allow/disallow local resources mapping (specifically drives) from the HOST side of a 2016 RDP server.  I know how to set it up on the client but my drives are not showing up when I RDP so, I assume it is disallowed on the host and I cannot find where to configure this. I've seen articles that explain where to find it on 2003, 2008 and 2012 but not 2016.

Can someone please provide SPECIFIC directions where I might find this on a 2016 server?

Mapping Local Resources to 2016 RDP Server

Remote access may refer to the connection to a data-processing system from a remote location, for example through a virtual private network remote desktop software, terminal emulation, or the activation of features of a business telephone system from outside the business's premises.

Remote Access

Microsoft Azure is a cloud computing platform and infrastructure for building, deploying and managing applications and services through datacenters. It provides both platform-as-a-service (PaaS) and infrastructure-as-a-service (IaaS) services and supports many different programming languages, tools and frameworks, including both Microsoft-specific and third-party software and systems. Cloud Services is a PaaS environment and can be used to create scalable applications and services; there are specific software development kits (SDKs) provided by Microsoft for Python, Java, Node.js and .NET. Azure also has file and storage services, data management, analytics and DNS services.

Azure

Windows Server 2016 is the successor to Windows Server 2012 R2. Built upon the same core code as Windows 10, Windows Server 2016 brings enhancements in security, servicing, and connectivity. A particular focus on this release was hybrid-cloud scenarios, and has close ties to Azure and other Microsoft cloud initiatives. This does not detract from the many improvements that are available for on-premises-only deployments

Windows Server 2016 comes in Datacenter, Standard, and Essentials editions, and for servicing, has adopted windows 10's cumulative model. The new nano-server install is designed to be remotely managed and is designed to be kept current through continuous feature updates. The full GUI install operates similarly to windows 10's "Long Term Servicing Branch" (LTSB) model with cumulative security updates.

Windows Server 2016 has also shifted from a per-processor-and-CAL licensing model to a per-core-and CAL licensing model. This brings Windows Server's licensing more in line with Microsoft's other products and makes hybrid-cloud license planning easier as well.