{"id":770,"date":"2017-11-06T12:30:19","date_gmt":"2017-11-06T10:30:19","guid":{"rendered":"https:\/\/asenger.de\/blog\/?p=770"},"modified":"2022-10-13T15:57:26","modified_gmt":"2022-10-13T13:57:26","slug":"how-to-run-tsadmin-msc-and-tsconfig-msc-snap-ins-on-windows-server-20122016-rds","status":"publish","type":"post","link":"https:\/\/asenger.de\/blog\/how-to-run-tsadmin-msc-and-tsconfig-msc-snap-ins-on-windows-server-20122016-rds\/","title":{"rendered":"How To Run TSADMIN.msc and TSCONFIG.msc Snap-Ins on Windows Server 2012\/2016 RDS"},"content":{"rendered":"

Quelle: http:\/\/woshub.com\/how-to-run-tsadmin-msc-and-tsconfig-msc-snap-ins-on-windows-server-2012-rds\/<\/p>\n

Many administrators of Windows terminal servers might have noticed that starting from Windows Server 2012, the management snap-ins tsadmin.msc<\/strong> (Remote Desktop Services Manager) and tsconfig.msc<\/strong> (Remote Desktop Session Host Configuration) disappeared from RDS servers. MS developers have decided that the majority of RDS server settings could be managed using Server Manager or group policy editor console (gpedit.msc), but the old snap-ins are more convenient and familiar.<\/p>\n

Let\u2019s see how to get tsadmin.msc and tsconfig.msc snap-ins back to RDS servers running  Windows Server 2012\/ R2.<\/p>\n

\"Get<\/a><\/p>\n

To do it, you have to copy 7 files and registry keys from any server running Windows Server 2008 R2<\/strong> to the same directory C:\\Windows\\System32 on Windows 2012 Server.  Copy the following 7 files:<\/p>\n