<div>
Never a good practice to run anything else on Domain Controller accept DNS and DHCP (IMO). &nbsp;The more access to your Domain Controller the more points of the system being compromised and if it is compromised or something goes wrong with the additional roles that may mean downtime that you cannot afford.<br />
<br />
If you can setup a separate server to run this DA role I would do that.
</div>


Never a good practice to run anything else on Domain Controller accept DNS and DHCP (IMO).  The more access to your Domain Controller the more points of the system being compromised and if it is compromised or something goes wrong with the additional roles that may mean downtime that you cannot afford.

If you can setup a separate server to run this DA role I would do that.

<div>
And Never a good idea to run DirectAccess with anything else on a server. DirectAccess needs certain Firewall rules running to function correctly and that can interfere with other options. Your best bet is to run DirectAccess on a its own server and I also recommend you setup a separate Network Location Server &nbsp;in your network.
</div>


And Never a good idea to run DirectAccess with anything else on a server. DirectAccess needs certain Firewall rules running to function correctly and that can interfere with other options. Your best bet is to run DirectAccess on a its own server and I also recommend you setup a separate Network Location Server  in your network.

<div>
Please provide me with step-by-step instructions on how to <a href="https://www.experts-exchange.com/questions/29108187/Steps-on-how-to-setup-configure-Network-Location-Server-for-Direct-Access.html#questionAdd" rel="ugc">how to setup &amp;&nbsp;configure a Network Location Server for Direct Access here</a>.
</div>


Please provide me with step-by-step instructions on how to how to setup & configure a Network Location Server for Direct Access here [https://www.experts-exchange.com/questions/29108187/Steps-on-how-to-setup-configure-Network-Location-Server-for-Direct-Access.html#questionAdd].

<div>
<div class="content wysiwyg-content">
Is it best to deploy Microsoft Direct Access within its own virtual Server 2016 virtual server or can it be installed on a server that is currently running other Windows roles (such as Active Directory) or on a Hyper-V base server?
</div>
</div>


Is it best to deploy Microsoft Direct Access within its own virtual Server 2016 virtual server or can it be installed on a server that is currently running other Windows roles (such as Active Directory) or on a Hyper-V base server?

Best to deploy Direct Access within its own virtual server or can it be installed on server currently running other roles (such as AD)

This topic area includes legacy versions of Windows prior to Windows 2000: Windows 3/3.1, Windows 95 and Windows 98, plus any other Windows-related versions including Windows Mobile.

Windows OS

Active Directory (AD) is a Microsoft brand for identity-related capabilities. In the on-premises world, Windows Server AD provides a set of identity capabilities and services, and is hugely popular (88% of Fortune 1000 and 95% of enterprises use AD). This topic includes all things Active Directory including DNS, Group Policy, DFS, troubleshooting, ADFS, and all other topics under the Microsoft AD and identity umbrella.

Active Directory

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

The Microsoft Server topic includes all of the legacy versions of the operating system, including the Windows NT 3.1, NT 3.5, NT 4.0 and Windows 2000 and Windows Home Server versions.

Microsoft Server OS

Windows 10 is a personal computer operating system featuring the "universal application architecture" (UAP); apps can be designed to run across multiple devices with nearly identical code, including PCs, tablets, smartphones, embedded systems, Xbox One, Surface Hub and HoloLens. Windows 10 also includes a virtual desktop system, a window and desktop management feature called Task View, the Microsoft Edge web browser, support for fingerprint and face recognition login, voice-based search (Cortana), new security features for enterprise environments, and DirectX 12 and WDDM 2.0 to improve the operating system's graphics capabilities for games.

Windows 10

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.