In this article the author will look at some ways of collecting valuable information for troubleshooting issues in RDS environments when running Windows Server 2012 (up until now Windows Server 8 Beta).
Since the terminology-change that came with Window Server 2008 R2, the term Terminal Services is no longer applied and TS is changed into RD. The fact that people still refer to Terminal Services, although they are running the R2 edition of Windows Server 2008, still often makes things confusing. With terminology-change also came an expanded set of features and possibilities. What was called Terminal Services in Windows Server 2003 is not what we know these days as Remote Desktop Services. Not only new (server manager) roles and features have been introduced in Windows Server 2008, but Remote Desktop Services (RDS) now also comes into two flavors. There is Virtual Desktop Infrastructure (VDI), which is based on the RD Virtualization Host role, and there is Session Virtualization that is based on the RD Session Host role. Both of these flavors share many parts of the global RDS deployment of course. Roles like the RD Connection Broker, RD WebAccess etc. can be used for VDI- as well as Session Virtualization Scenario’s. In this article we will look at some ways of collecting valuable information for troubleshooting issues in RDS environments when running Windows Server 2012 (up until now Windows Server 8 Beta).
The different roles that are part of the Remote Desktop Services Platform have several log files, trace files and also event logs where information, statuses and errors are stored. This information can be rather useful when troubleshooting an installation or configuration.
- Remote Desktop Management Services (RDMS) on Windows Server 2012
- Introducing MSTSC /admin
- Microsoft expands on RemoteFX for RDSH
- Microsoft explains RemoteFX for RDSH a little bit more
- Taking a closer look at what Windows 8 will bring regarding management of RDS