You could then go ahead and install the WSE RemoteApp 2016 add-in on the server, and publish the applications that you install directly on the server as RemoteApp programs. At the first screen of Add Roles and Features wizard leave the Role-based or feature-based installation option and click Next. Open Server Manager and click on Add Roles and Features. For additional details see: The end result would be a fully functional “ Essentials” server, that is not a domain controller. Install Remote Desktop Licensing and Remote Desktop Session Host role services. ![]() The second server instance would then be joined to the domain controller that you have just set up (using native tools), and AFTER successfully joining it to the domain, you would then install the Windows Server Essentials Experience server role on it (deployed as a member server in the domain). ![]() The first server instance would be set up as your primary domain controller. For example, Windows Server 2016 Standard could be installed on two separate servers (bare metal or virtual machines). ![]() For those who may not be comfortable using RemoteApp functionality on a domain controller (seeing as Windows Server 2016 Essentials must be a domain controller), Windows Server 2016 Standard/Datacenter (with the Windows Server Essentials Experience server role) can be utilized as a member server instead (where the WSS server itself is not configured as a domain controller, but rather domain joined to a second server that is acting as the primary domain controller).
0 Comments
Leave a Reply. |