Microsoft Windows Terminal Services



  1. 1306 Error Microsoft-windows-terminal Services-session Broker-client
  2. Windows Terminal Microsoft Docs

If local Group Policies for Terminal Services settings were established, these must be loaded at the right time, of course. This happens during logon with keys found under HKLM SOFTWARE Policies Microsoft Windows NT Terminal Services and the EnableAdminTSRemote key under HKLM SOFTWARE Policies Microsoft Windows Installer. Windows Terminal Server Initialization As the Windows Terminal Server boots and loads the core operating system, the Terminal Server service (Termsrv.exe) is started and creates listening stacks (one per protocol and transport pair) that listen for incoming connections. Terminal services configuration: Start-menu, Administrative Templates, Remote Desktop Services, Remote Desktop Session Host Configuration or follow this 'computer config policies admin templates windows components terminal services terminal server printer redirection:': Open Group Policy Management or write gpmc.msc in search. From Wikipedia, the free encyclopedia Remote Desktop Services (RDS), known as Terminal Services in Windows Server 2008 and earlier, is one of the components of Microsoft Windows that allow a user to take control of a remote computer or virtual machine over a network connection.

Event Id36
SourceMicrosoft-Windows-TerminalServices-PnPDevices
DescriptionRedirection of additional supported devices is disabled by policy.
Event InformationAccording to Microsoft :
Cause :
This event is logged when redirection of additional supported devices is disabled by policy.
Resolution :
Change the appropriate configuration or Group Policy setting
To resolve this issue, enable redirection of supported Plug and Play devices by using the Terminal Services Configuration tool or by using Group Policy.
Note : If you want to continue to prevent the redirection of supported Plug and Play devices, then no futher action is required.
To perform these procedures, you must have membership in the local Administrators group, or you must have been delegated the appropriate authority.
Change the settings in Terminal Services Configuration
To check settings by using Terminal Services Configuration:
  1. On the terminal server, open Terminal Services Configuration. To open Terminal Services Configuration, click Start, point to Administrative Tools, point to Terminal Services, and then click Terminal Services Configuration.
  2. If the User Account Control dialog box appears, confirm that the action it displays is what you want, and then click Continue.
  3. Under Connections, right-click the connection and then click Properties.
  4. Click the Client Settings tab.
  5. Under Redirection, if the Supported Plug and Play Devices check box is selected, clear the Supported Plug and Play Devices check box.
  6. Click Apply, then click OK.
Change the settings in Group Policy
If the redirection of supported Plug and Play devices has been disabled by using Group Policy, change the Group Policy that is being applied to the terminal server so that supported Plug and Play devices can be redirected.
Redirection of supported Plug and Play devices can be controlled by the following Group Policy settings:
  • The Do not allow supported Plug and Play device redirectionGroup Policy setting. This Group Policy setting is located in Computer ConfigurationAdministrative TemplatesWindows ComponentsTerminal ServicesTerminal ServerDevice and Resource Redirection. Note that the Group Policy setting will take precedence over the setting configured in Terminal Services Configuration.
  • The Group Policy settings located in Computer ConfigurationAdministrative TemplatesSystemDevice InstallationDevice Installation Restrictions.
To configure the Group Policy setting in Active Directory Domain Services (AD DS), use the Group Policy Management Console (GPMC). To configure the Group Policy setting locally on a terminal server, use the Local Group Policy Editor.
Verify :
To verify that supported Plug and Play device redirection is working properly, use either of the following methods:
Method one
Establish a remote session with the terminal server and check that the redirected device is available and is functioning as expected.
Method two
Check the status of the device by using Device Manager.
To perform this procedure, you must have membership in the local Administrators group, or you must have been delegated the appropriate authority.
To use Device Manager to check the status of the device:
  1. On the terminal server, open Device Manager. To open Device Manager, click Start, click Run, type devmgmt.msc, and then click OK.
  2. If the User Account Control dialog box appears, confirm that the action it displays is what you want, and then click Continue.
  3. On the View menu, click Devices by connection.
  4. Locate the device under the User Mode Bus controller node.
  5. Double-click the device and verify that Device status indicates that the device is working properly.
Reference LinksEvent ID 36 from Source Microsoft-Windows-TerminalServices-PnPDevices

Microsoft Windows Terminal Server is a core component of Windows Desktop products and Microsoft Windows Server that allows remote computers to connect to a Windows operating system computer using a remote terminal session. With the remote terminal session, remote computers can run applications on the remote machine and run multiple remote connections independently of each other.

Microsoft introduced this concept by releasing terminal services as a part of the Windows Server operating system. Terminal services have been an integral part of Windows Server OS editions beginning with Windows NT 4.0. With the release of Windows Server 2008 R2, terminal services were renamed remote desktop services (RDS). Before implementing this technology, it is essential to know what a terminal server is and why you should use one.

Why use a terminal server?

Terminal servers enable businesses to centrally host applications and resources and publish them to remote client devices, regardless of the location and platform of the end-user device. A terminal server provides multiple benefits. First, terminal servers provide end-users with access to company resources from anywhere and from any device. Second, they facilitate a single point of maintenance and allow you to monitor the infrastructure from a central dashboard. Third, applications are installed once and regularly updated on the server, so there is no need to install or update a program on each machine in the network. In addition, with concurrent licenses instead of per-device ones, businesses can reduce licensing costs, and thin clients allow businesses to optimize costs and power savings for a better ROI. Moreover, the lifespan of desktop hardware extends is extended, and network security is significantly improved.

What is terminal server architecture?

It is also important to understand the terminal server architecture. The terminal server architecture consists of three crucial components:

  1. A multi-core server where resources are centrally hosted.
  2. A remote desktop protocol that enables data transmission between the server and the client.
  3. A client software on each remote client device. This client program allows the device to connect to the server via the RDP protocol.

In addition, there is the Terminal Services Licensing Service, which provides the server with the TS CAL licenses for devices to connect to it. The sessions list is saved in the Sessions Directory Service. This list is indexed by username, allowing the user to reconnect to the same server.

What is terminal server licensing?

Each user/device connecting to the TS server should have an RDS CAL. The terminal server licensing role is installed on an RDS license server. The role of this TS licensing server is to store and track all RDS CALs installed for a group of servers. A single licensing server can serve multiple TS servers. The license server should be activated to provide permanent RDS CALs; otherwise, it issues temporary RDS CALs. It is important to know what terminal server licensing is to estimate costs.

To deliver virtual desktops and applications to remote users, terminal services uses the RDP protocol. It works on TCP/IP and listens on port 3389. The RDP protocol was improved to provide a rich graphical experience to end-users. The new version, RemoteFX, was introduced in Windows Server 2008 R2 SP1. Using RemoteFX technology, businesses can seamlessly deliver graphic-intensive applications such as AutoCAD and the Adobe Suite to remote client devices.

Terminal services use case

Let’s say, for instance, that a company has a geographically dispersed network of 1,000 users connected over WAN. The company develops a new application which is to be used by all employees. The application is not web-based, and employees work from different locations. Raid card for mac. The company has to provide access to that application for every user/device. Terminal services are an excellent solution to this issue. With one server, a TS server OS license, TS licensing server, and RDS CALs for each user/device, you can set up a terminal service environment to centrally host applications and deliver them to remote client devices with ease.

Parallels Remote Application Server brings the best of a terminal server

Many businesses still use a Windows OS, but there are several challenges associated with the terminal server setup. While the complexity of installing and configuring multiple components is the primary challenge, the cost of RDS CALs is another burden. Secondly, a TS environment only supports Windows and Mac environments. Parallels Remote Application Server allows you to use the TS environment while eliminating its limitations. Parallels Remote Application Server is easy to install and manage. By using a simple wizard, you can set up the tool in five minutes. Secondly, all the virtualization components come auto-configured out of the box. Another important advantage of Parallels Remote Application Server is the support of a range of client devices, including iOS, Android, and Chromebooks. Most importantly, Parallels Remote Application Server is cost-effective.

References

Microsoft Windows Terminal Services

Nancy drew for mac os. terminal server | http://searchvirtualdesktop.techtarget.com/definition/terminal-server

How Terminal Services Works | https://technet.microsoft.com/en-us/library/cc755399(v=ws.10).aspx New apple os for mac.

1306 Error Microsoft-windows-terminal Services-session Broker-client

How Terminal Server Works | http://www.brianmadden.com/blogs/terminal_services_for_microsoft_windows_server_2003_advanced_technical_design_guide/pages/how-terminal-server-works.aspx

Windows Terminal Microsoft Docs

The 12 Advantages of Terminal Services | http://www.emazzanti.net/the-12-advantages-of-terminal-services/

10 reasons why Windows Terminal Services is becoming more popular | http://www.techrepublic.com/blog/10-things/10-reasons-why-windows-terminal-services-is-becoming-more-popular/