![server 2012 terminal services manager missing server 2012 terminal services manager missing](https://msfreaks.files.wordpress.com/2013/12/rds-deployment-add-session-host.png)
![server 2012 terminal services manager missing server 2012 terminal services manager missing](https://etutorials.org/shared/images/tutorials/tutorial_64/f04rq04.jpg)
Scenario Based Deployment is all about installing a complete scenario instead of separate roles.
#SERVER 2012 TERMINAL SERVICES MANAGER MISSING WINDOWS#
As you might remember from my previous blogs and articles, the Scenario Based Deployment is new in Windows Server 2012 and is available as an option next to the “classic” role based deployment. In my lab environment, I did a Scenario Based Deployment of the RDS platform. The folder where this log file resides is %windir%\Logs (e.g. RDMS stands for Remote Desktop Management Services and is the new “plugin” that has been added to the brand new Window Windows 2012 Server Manager Console. You can find this log file on the machine where you performed the RDMS deployment. This log file is called RDMSDeploymentUI.txt. The main part of this article will be around a log file that contains information about the installation and configuration process. This information can be rather useful when troubleshooting an installation or configuration. 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. Troubleshooting the standard scenario installation 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). can be used for VDI- as well as Session Virtualization Scenario’s. Roles like the RD Connection Broker, RD WebAccess etc. Both of these flavors share many parts of the global RDS deployment of course. 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. 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. What was called Terminal Services in Windows Server 2003 is not what we know these days as Remote Desktop Services. With terminology-change also came an expanded set of features and possibilities. 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.
![server 2012 terminal services manager missing server 2012 terminal services manager missing](http://images.concurrency.com/2013/04/image72.png)
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.