For RD Licensing and RD Gateway you may use the graphical tools as in previous versions, or the old powershell commands (import-module RemoteDesktopServices). The GUI and powershell tools for those are still present in 2012.To configure and manage a standalone RDSH server you may use a combination of local group policy (gpedit.msc), WMI commands, registryĮdits, and config file edits, as needed. Most of the old powershell commands and GUI programs that would have allowed you to configure/manageĪ standalone RDSH server have been removed.Įxception to the above is for RD Licensing and RD Gateway. This includes most (if not all) of the new powershell commands and server manager. The thing to keep in mind is that most of the tools provided to make managing/configuring RDSH servers easier in 2012 will Is true for Virtual Desktops (VMs), they are designed to be managed as a collection.
Acutally,Server 2012 RDS is designed under the basic premise that RDS servers will be joined to a domain, at least one RD Connection Broker will be present, and that RDSH servers will be managed as a collection using Server Manager (and/or powershell).
0 kommentar(er)
