An update is available that enables the Terminal Services license servers that are running Windows Server 2008 to be able to use client access licenses (CALs) for the Windows Server 2008 R2 Remote Desktop Services.After you install this update, you can install CALs for the Windows Server 2008 R2 Remote Desktop Services on the Terminal Services license servers that are running Windows Server 2008. Therefore, the Terminal Services license servers that are running Windows Server 2008 can issue Remote Desktop Services CALs to Windows Server 2008 R2 Remote Desktop Services servers.Note The Windows Server 2008 Terminal Services (TS) CALs and the Windows Server 2008 R2 Remote Desktop Services CALs are treated equal in all respects. Therefore, if you have Windows Server 2008 TS CALs, you can have all the functionalities that the Windows Server 2008 R2 Remote Desktop Services CALs provide.
terminal services windows server 2008 crack
BUY_WINSERV_2008R2Unless licensing is configured during the initial installation of the Remote Desktop Services role on Windows Server 2008 R2, a 120 day grace period is provided before a license server needs to be installed and activated. The purpose of this chapter, therefore, is to provide details on installing and activating a Windows Server 2008 R2 Remote Desktop Services License Server and subsequently installing Client Access Licenses (CALs).
The first step is to install the Remote Desktop Services License Services server role. The license server does not necessarily have to be installed on a system which is acting as a Remote Desktop Server. The installation can be performed using by selecting Roles from the tree in the left hand panel of the Server Manager tool.If the server is already configured with the Remote Desktop Services role, scroll down the Roles summary page to the Remote Desktop Services section click on the Add Role Services link. In the resulting dialog titled Select Role Services select the check box next to Remote Desktop Licensing and then click Next to proceed to the Configure discovery scope for RD licensing screen as illustrated in the following figure:In the first version of Windows Server 2008, it was necessary to specify a method by which RD Session Host servers (or Terminal Servers as they were known then) would auto-detect the server running the licensing server. With Windows Server 2008 R2, this approach is discouraged, and Microsoft now recommends that each RD Session Host be manually configured with information about the license server. In keeping with this recommendation, leave the Configure a discovery scope for this license server option unselected. Note, however, that this setting may be changed at a later time if required via the RD Licensing Manager tool. Click Next to proceed to the confirmation screen.On a server which is does not have the Remote Desktop Services role installed, open the Server Manager, select Roles from the tree in the left hand panel and select Add Roles. Click Next on the initial screen if it appears so that the Select Server Roles screen is displayed. From the list of roles select the check box next to Remote Desktop Services and click on the Next button.Read the information screen and then proceed to the Select Service Roles screen. Check the box next to Remote Desktop Licensing, click Next and follow the steps outlined above.On the confirmation screen, verify that the information matches your expectations and click Install to initiate the installation process.if(typeof ez_ad_units!='undefined')ez_ad_units.push([[160,600],'techotopia_com-box-1','ezslot_2',130,'0','0']);__ez_fad_position('div-gpt-ad-techotopia_com-box-1-0');report this adActivating the RD License ServerOnce the RD License Server has been installed the next task is to activate it. This task is performed using the RD Licensing Manager which may be launched via Start -> All Programs -> Administrative Tools -> Remote Desktop Services -> Remote Desktop Licensing Manager. Once started, the Remote Desktop Licensing Manager dialog will appear containing a list of detected license servers on the network. The only license server listed in the following figure is the one on the local server. Because this has yet to be activated it is listed with a red circle containing an X mark next to it:if(typeof ez_ad_units!='undefined')ez_ad_units.push([[300,250],'techotopia_com-box-4','ezslot_3',154,'0','0']);__ez_fad_position('div-gpt-ad-techotopia_com-box-4-0');To activate a license server, right click on the server in the list and select Activate Server. After reading the welcome screen click Next to proceed to the Connection Method screen. The activation process requires communication with Microsoft in one form or another. If the server has an internet connection then the activation can be performed over this connection. The default, recommended method, is to have the RD Licensing Manager automatically connect to gather the information. Failing that, another option is go to the web site using a browser and enter the product ID. Alternatively, if an internet connection is not available or a firewall prevents such access the activation may be performed over the telephone. If Automatic connection is selected, the following dialog will appear as the wizard attempts to contact Microsoft:Once the Microsoft activation server has been located a new dialog will appear prompting for user, company and geographic location information. Complete these details and click Next to proceed. The second screen requests more detailed, but optional information. Either complete this information or click Next to skip to the activation process. Once again the wizard will contact Microsoft and complete the activation. Once completed, the following completion screen will appear:Note that the Start Install Licenses Wizard now check box is selected by default. If you are ready to begin installing Client Access Licenses (CALs) now click on Next.
When I run the RD License Diagnoser from either server, I get the below error. Does anyone know what I'm missing? Is the 2012 server really looking for 2008 RDS CALs??? I didn't think that was possible.
It seems to me you install windows 2008 or 2008 R2 CALs in Windows server 2012. Quoted from this link "In other words, you could not user TS 2008 CAL or RDS 2008 CAL for server 2012 Remote Desktop Session Host server".
Thanks for your response. Your right, setting up a 2012 Session based RDS server is a lot more difficult than 2008 was. I installed all the roles for session based RDS services (except for the License manager) on my TS01 and installed the RD License manager on the Domain controller (DC01). I also edited the Deployment Properties to point the RD License to DC01. I get the below error when I do so.
Remote Desktop Services (RDS), known as Terminal Services in Windows Server 2008 and earlier,[1] is one of the components of Microsoft Windows that allow a user to initiate and control an interactive session[2] on a remote computer or virtual machine over a network connection. RDS was first released in 1998 as Terminal Server in Windows NT 4.0 Terminal Server Edition, a stand-alone edition of Windows NT 4.0 Server that allowed users to log in remotely. Starting with Windows 2000, it was integrated under the name of Terminal Services as an optional component in the server editions of the Windows NT family of operating systems,[3] receiving updates and improvements with each version of Windows.[4] Terminal Services were then renamed to Remote Desktop Services with Windows Server 2008 R2[5] in 2009.
The key server component of RDS is Terminal Server (termdd.sys), which listens on TCP port 3389. When a Remote Desktop Protocol (RDP) client connects to this port, it is tagged with a unique SessionID and associated with a freshly spawned console session (Session 0, keyboard, mouse and character mode UI only). The login subsystem (winlogon.exe) and the GDI graphics subsystem is then initiated, which handles the job of authenticating the user and presenting the GUI. These executables are loaded in a new session, rather than the console session. When creating the new session, the graphics and keyboard/mouse device drivers are replaced with RDP-specific drivers: RdpDD.sys and RdpWD.sys. The RdpDD.sys is the device driver and it captures the UI rendering calls into a format that is transmittable over RDP. RdpWD.sys acts as keyboard and mouse driver; it receives keyboard and mouse input over the TCP connection and presents them as keyboard or mouse inputs. It also allows creation of virtual channels, which allow other devices, such as disc, audio, printers, and COM ports to be redirected, i.e., the channels act as replacement for these devices. The channels connect to the client over the TCP connection; as the channels are accessed for data, the client is informed of the request, which is then transferred over the TCP connection to the application. This entire procedure is done by the terminal server and the client, with the RDP mediating the correct transfer, and is entirely transparent to the applications.[13] RDP communications are encrypted using 128-bit RC4 encryption. Windows Server 2003 onwards, it can use a FIPS 140 compliant encryption schemes.[6]
Once a client initiates a connection and is informed of a successful invocation of the terminal services stack at the server, it loads up the device as well as the keyboard/mouse drivers. The UI data received over RDP is decoded and rendered as UI, whereas the keyboard and mouse inputs to the Window hosting the UI is intercepted by the drivers, and transmitted over RDP to the server. It also creates the other virtual channels and sets up the redirection. RDP communication can be encrypted; using either low, medium or high encryption. With low encryption, user input (outgoing data) is encrypted using a weak (40-bit RC4) cipher. With medium encryption, UI packets (incoming data) are encrypted using this weak cipher as well. The setting "High encryption (Non-export)" uses 128-bit RC4 encryption and "High encryption (Export)" uses 40-bit RC4 encryption.[14] 2ff7e9595c
Comments