Good morning! Faced with a some trouble while configuring Terminal Server (Windows Server 2012 based).

1. Windows Server 2003 R2 Sp2

I selected licensing mode 'Per User' and now I see this message: “The Remote Desktop Session Host server is in Per User licensing mode and No Redirector Mode, but license server “server name” does not have any installed licenses with the following attributes: Product version: Windows Server 2008 or Windows Server 2008 R2 Licensing mode: Per User License type: RDS CALs” So this is trial using of terminal server - I have 25 days yet but already today I can't connect to server using RDP. There is an error message about absent licensing server. How can I activate licenses in trial mode? Thank you for support. Hi, Thank you for posting in Windows Server Forum. From the error description it seems that your issue caused by setting up different Licensing mode.

Technical information about Terminal Services in Windows Server 2003, including What is Terminal Services, How Terminal Services Works, and Terminal. Aldebaran dijo. Hola a todos Bueno quien dice que no se puede craquear las licencias de terminal server 2003 1 yo tengo instalado el Windows 2003 server R2 (este lo.

We need to install the proper RDS CAL on the License server. If the license server has installed licenses of the other mode, changing the licensing mode for the terminal server may also resolve the issue. To change the Licensing mode we can use RD Licensing diagnoser or by PowerShell command. To change the licensing mode on RDSH/RDVH: $obj = gwmi -namespace 'Root/CIMV2/TerminalServices' Win32TerminalServiceSetting $obj.ChangeMode(value) - Value can be 2 - per Device, 4 - Per user Please refer below article for information.

RD Licensing Configuration on Windows Server 2012 Have you installed License server on Server 2012 and you have RDS CAL of Server 2008 R2? If that’s the case then first you need to purchase the RDS CAL for server 2012 and then you can configure on server 2012 because server 2012 R2 RDS CAL can work with lower version OS but Server 2008 R2 RDS CAL can’t work on Server 2012 R2. Please check computability matrix. RDS and TS CAL Interoperability Matrix Hope it helps! Dharmesh Solanki. Hi, Thank you for posting in Windows Server Forum. From the error description it seems that your issue caused by setting up different Licensing mode.

Jun 15, 2017 - Terminal server hack - FOR TESTING ONLY (Activate CAL) Please note to use these licenses only for educational and testing use. SERVER Start > Control Panel > Add or Remove Programs > Add or Remove Windows Components'. Add 'Terminal Server' & Terminal Server Licensing' Default licensing.

We need to install the proper RDS CAL on the License server. If the license server has installed licenses of the other mode, changing the licensing mode for the terminal server may also resolve the issue. To change the Licensing mode we can use RD Licensing diagnoser or by PowerShell command. To change the licensing mode on RDSH/RDVH: $obj = gwmi -namespace 'Root/CIMV2/TerminalServices' Win32TerminalServiceSetting $obj.ChangeMode(value) - Value can be 2 - per Device, 4 - Per user Please refer below article for information. RD Licensing Configuration on Windows Server 2012 Have you installed License server on Server 2012 and you have RDS CAL of Server 2008 R2?

If that’s the case then first you need to purchase the RDS CAL for server 2012 and then you can configure on server 2012 because server 2012 R2 RDS CAL can work with lower version OS but Server 2008 R2 RDS CAL can’t work on Server 2012 R2. Please check computability matrix. RDS and TS CAL Interoperability Matrix Hope it helps!

Dharmesh Solanki. Hi Guys, The common solution is to delete the “grace period” key from the registry which is essentially a crack to allow the server to have unlimited licensing. What we found to be a working solution to the below error is the following: The Remote Desktop Session Host server is in Per User licensing mode and No Redirector Mode, but license server ServerName.domain.com does not have any installed licenses with the following attributes: Product version: Windows Server 2012 Licensing mode: Per User License type: RDS CALs The fix: Inside of RDS licensing manager right click the server and select the manage licenses option. Select the rebuilt the licensing server option and hit next. It will ask you to confirm that you wish to delete all licenses on the server so make sure you have the info needed to reinstall the RDS CALs.

Once done you will have the option to reinstall the CALs, proceed as you would normally. Finally restart the “remote desktop licensing” service and head back to the RD licensing Diagnoser. You should now see that there are licenses available.

Windows Server 2003/2008 STD & ENT DOES NOT REQUIRE entry of license keys or codes for CLIENT ACCESS LICENSES. CAL tracking is the responsibility of the end-user, and CAL license documentation (contains a 'Tracking number' instead of a product key) should be kept in a secure location if needed for a license audit at a later time.End-user Client Access license documentation only contains a tracking number, and does not need to be entered into the server. 2003 CAL example: 2008 Example: Equipment Manufacturer (OEM) channel distribution of Windows Server 2003/2008 STD/ENT utilizes wherein it is not required to enter the product key found on the sticker on the side of the server during installation, nor is it needed to activate Server 2003. Server 2008 will, however, require activation via the internet or telephone.

To aid in tracking how many licenses are being used, end-users may elect to enable and utilize the license logging tool/service.Note, this service is disabled by default, and is entirely optional. Enable License Logging Service: Change Startup type from 'Disabled' to 'Automatic'. From the Programs Administrative tools open the License Tracking tool, then choose New License.

Enter the number of licenses purchase, then press OK. Client Access Licenses (CALs) Q. What is the difference between a Windows Server 2003 R2 license and a Windows CAL? Why do I need both?

The Windows Server 2003 R2 license gives the license holder the right to install and use the server software. The Windows CAL grants the right for a device or user to access the server software. The two-component license provides a low entry price and a way to pay for capacity used: the more devices or users accessing the server software, the greater the license fees or price. The model therefore offers license affordability to organizations of all sizes. When do I need to acquire a Windows CAL?

A Windows CAL is required when a user or device accesses or uses the server software. However, if access is through the Internet and is unauthenticated (for example, when browsing a public Web site), a Windows CAL is not required. Also, if that user is an external user, another option is to acquire an External Connector license. See the Windows External Connector License section below for more detail.

Further information is available at the External Connector License Overview. Are there any differences between the requirements for CALs in Windows 2000 Server versus CALs in Windows Server 2003 and Windows Server 2003 R2? The Windows Server CAL requirements are the same. What has changed, however, is the language that specifies when a CAL is required. The Windows 2000 Server license agreement defined the product services which required a CAL (e.g. File, print, remote access, terminal services, and authenticated access).

In practice, most customer usage of Windows 2000 Server accessed the file services and/or authentication features of the product and therefore required a CAL. Customer feedback indicated that it was difficult to know if a particular usage scenario met those definitions. So, for Windows Server 2003 and Windows Server 2003 R2, Microsoft has provided more specific language to clarify when customers require CALs. The End User License Agreement states that CALs are required for access or use of the server software and goes on to list usage examples. If I am using the server in a way that is not listed (e.g., as an application server), do I still need CALs? The list of examples in the License Terms is not exhaustive but is instead meant to illustrate some common uses of the server software.

If a device or user is accessing or using the server software, a CAL is required, unless: access is through the Internet and is unauthenticated, or access is to a server running Windows Server 2003 Web Edition, or access or use is by an External User and External Connector licenses are acquired instead of CALs. What is the difference between a Windows CAL and a Terminal Server (TS) CAL? A Windows CAL is required when a user or device is directly or indirectly accessing a Windows server.

Additionally, if the user or device is accessing or using the terminal server functionality of Windows Server Standard and Enterprise Editions, a TS CAL is also required. As an exception to these rules, up to two users or devices may access the server software only for server administration purposes, without requiring either a TS CAL or Windows CAL. What is the difference between a Device CAL and a User CAL? A Windows Device CAL permits one device (used by any user) to access or use the server software. A Windows User CAL permits one user (using any device) to access or use the server software; the same holds true for TS Device CALs and TS User CALs. Why is Microsoft introducing another type of CAL? Microsoft is introducing another type of CAL to provide choice to address customers' changing needs.

Some customers require a solution where employees need to gain access to the company's corporate network using devices that the company doesn't own or control, and for which a device-based CAL cannot be readily acquired. Other customers prefer to count employees rather than devices for licensing compliance, because it is simpler. Can I use a Windows Device CAL and a Windows User CAL on the same server? Windows Device and User CALs can be used on the same server. For ease of management and tracking though, Microsoft recommends that customers choose to acquire CALs on either a device or user basis.

Can I use a Terminal Server Device CAL (TS Device CAL) and a Terminal Server User CAL (TS User CAL) on the same terminal server? TS Device and User CALs can be used on the same server. For ease of management and tracking though, Microsoft recommends that customers choose to acquire CALs on either a device or user basis. Is there a difference in price between Device CALs and User CALs? Windows Server 2003 Device CALs and Windows Server 2003 User CALs are priced the same, just as Windows Server 2003 TS Device CALs and Windows Server 2003 TS User CALs are the same price.

My Windows Server 2003 R2 software came with a set number of CALs because I acquired it through a retail store or with a new piece of hardware. How do I designate those CALs to be User or Device CALs? When the software comes packaged with CALs, you choose whether those CALs are User or Device CALs after you make the purchase on the CAL End User License Agreement document. In other words, you choose the type of CAL once you get the product. What is the difference between 'types' of CALs and 'licensing modes' for CALs? The different types of CALs are outlined above.

See Device and User CALs. Different licensing modes only apply to Windows CALs and pertain to how to assign the Windows CALs. In Per Server mode, the Windows CALs acquired should equal the total number of users and/or devices accessing that server's software at a given time.

For example, in this mode, the maximum concurrent connections are equal to the number of Windows CALs acquired. In Per Device or Per User mode, Windows CALs should be acquired for each device or user, in order for that device or user to access all the servers deployed in this mode. There is no limit to the number of devices or users accessing a server at a given time.

Please visit the CAL overview page for further detail, including a helpful graphic depicting CAL licensing modes. What impact will User CALs have on Core CALs and Enterprise Agreements? Customers will be able to choose either Core Device CALs or Core User CALs for their Enterprise Agreement (EA) enrollments.

By standardizing at an enrollment level, Microsoft can help maintain the simplicity and ease of tracking provided by the Core CAL and EA. I have some extra Windows 2000 CALs that are not being used. Can I apply these to a Windows Server 2003 or Windows Server 2003 R2 server(s)? A CAL must be the same version (or later) as the server it is accessing. Therefore, access to a Windows 2003 Server or Windows Server 2003 R2 must be licensed with a Windows 2003 Device or User CAL. Can I downgrade a Windows CAL for use on a Windows 2000 server?

Both Windows Server 2003 User and Device CALs can be downgraded to access a Windows 2000 server. Can I downgrade a TS CAL for use on a Windows 2000 terminal server? You may downgrade Windows Server 2003 TS CALs. However, both TS User and Device CALs will act as device-based CALs when accessing a Windows 2000 terminal server, as TS User CALs are not supported. How do I designate Windows Server 2003 TS User or Device CALs or Windows 2000 TS CALs? During set-up, the Terminal Server Licensing Management (TSLM) will prompt you to choose. I have valid upgrade coverage (Upgrade Advantage or Software Assurance) on my CALs.

Windows Server 2003 R2 Sp2

Can I choose either User or Device CALs? How do I do that? You must designate your Windows CALs as Device or User when you upgrade them. If you exercise your one-time right to convert Device CALs to User CALs mid-contract, you simply record the change for your records.

When Software Assurance comes up for renewal, all the new specifications (for example, number of User CALs, number of Device CALs) are documented and revised in Microsoft Volume License Services' records. For TS CALs, when you request TS CAL tokens through Terminal Server Licensing Management, you are prompted to specify User or Device. Will I be allowed to switch between Windows Device CALs and Windows User CALs? What about TS CALs? Customers who have active Software Assurance coverage for Windows Server CALs under agreements signed on or before April 1, 2003 may change their Windows Device CALs to Windows User CALs at the time of the annual true-up process.

These transition rights can also be applied in the same way for switching from TS Device CALs to TS User CALs for TS CALs covered by SA under agreements signed on or before April 1, 2003. Customers with current Software Assurance for CALs acquired after April 1, 2003 may switch their Device CALs to User CALs and User CAL to Device CALs upon renewal of their Software Assurance coverage for those CALs. What are TS transition CALs? Is everyone eligible to acquire them? As part of the TS CAL Transition Plan, customers who had rights to Windows XP Professional licenses as of April 24, 2003 get rights to complimentary Windows Server 2003 TS CALs. These customers can then acquire Software Assurance, if they wish, for these complimentary TS CALs to gain the benefits of upgrade protection by acquiring these special TS transition CALs. In other words, the only customers eligible to acquire TS transition CALs are those customers who qualified to receive complimentary Windows Server 2003 TS CALs.