Jul 31, 2018 We recently upgrade our terminal servers (6 user servers, 4 of which are on a load balance) from Windows Server 2008R2 to Windows Server 2016. Previously I had the ability to see who was logged in to which server when logged in as admin.
In Windows Server 2016 & 2012 the Terminal Services role has been replaced by the Remote Desktop Session Host (RDSH) role service and is part of Remote Desktop Services (RDS). A Remote Desktop Session Host (RDSH) server, provides to remote users the ability to access the applications on the RDS host server and the company resources from anywhere by using an RDP client.
Your activation key will be sent directly to the email address associated with your purchase almost instantly. Brand New: This product includes A Brand New Unused Windows Server 2016 Remote Desktop Services - 5 User CALs, Legitimate Genuine Retail Key. Jun 14, 2017 Installing Terminal server running Windows Server 2016 1. Prepare - DC21: Domain Comtroller - DC22: Domain Member ( Install Terminal server ); IP 10.0.0.2.
-->
Remote Desktop Services (RDS) is the platform of choice for building virtualization solutions for every end customer need, including delivering individual virtualized applications, providing secure mobile and remote desktop access, and providing end users the ability to run their applications and desktops from the cloud.
RDS offers deployment flexibility, cost efficiency, and extensibility—all delivered through a variety of deployment options, including Windows Server 2016 for on-premises deployments, Microsoft Azure for cloud deployments, and a robust array of partner solutions.
Depending on your environment and preferences, you can set up the RDS solution for session-based virtualization, as a virtual desktop infrastructure (VDI), or as a combination of the two:
Session-based virtualization: Leverage the compute power of Windows Server to provide a cost-effective multi-session environment to drive your users' everyday workloads.
VDI: Leverage Windows client to provide the high performance, app compatibility, and familiarity that your users have come to expect of their Windows desktop experience.
Within these virtualization environments, you have additional flexibility in what you publish to your users:
Desktops: Give your users a full desktop experience with a variety of applications that you install and manage. Ideal for users that rely on these computers as their primary workstations or that are coming from thin clients, such as with MultiPoint Services.
RemoteApps: Specify individual applications that are hosted/run on the virtualized machine but appear as if they're running on the user's desktop like local applications. The apps have their own taskbar entry and can be resized and moved across monitors. Ideal for deploying and managing key applications in the secure, remote environment while allowing users to work from and customize their own desktops.
For environments where cost-effectiveness is crucial and you want to extend the benefits of deploying full desktops in a session-based virtualization environment, you can use MultiPoint Services to deliver the best value.
With these options and configurations, you have the flexibility to deploy the desktops and applications your users need in a remote, secure, and cost-effective fashion.
Windows Server 2016 Terminal Services Reviews
Next steps
Here are some next steps to help you get a better understanding of RDS and even start deploying your own environment:
Windows Server 2016 Terminal Services Role
Understand the supported configurations for RDS with the various Windows and Windows Server versions
Plan and design an RDS environment to accommodate various requirements, such as high availability and multi-factor authentication.
Review the Remote Desktop Services architecture models that work best for your desired environment.
Start to deploy your RDS environment with ARM and Azure Marketplace.