However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base:.
NoteWhen you change the value in the registry as described in the following steps, you will not change the setting that is shown in the Terminal server configuration interface.
To reset the registry values, follow these steps:. Click Start , click Run , type regedit, and then click OK. Right-click the PolicyAcOn registry entry, and then click Modify. In the Value data box, type 4, and then click OK. Note A setting of 2 indicates a Per Device configuration. A setting of 4 indicates a Per User configuration. Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
For additional information about terminal server licensing, click the following article number to view the article in the Microsoft Knowledge Base:. Resolution Hotfix information A supported hotfix is available from Microsoft. Prerequisites No prerequisites are required. Restart requirement You do not have to restart your computer after you apply this hotfix. Hotfix replacement information This hotfix does not replace any other hotfixes.
File information The English version of this hotfix has the file attributes or later file attributes that are listed in the following table. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base: How to back up and restore the registry in Windows After you apply the hotfix, you must reset the PolicyAcOn registry entry to the correct setting of either 4 Per User or 2 Per Device to configure the licensing mode.
To reset the registry values, follow these steps: Click Start , click Run , type regedit, and then click OK. Quit Registry Editor. This design provides redundant license servers to terminal servers in both sites, while reducing normal WAN traffic for CAL allocation.
However, just as before, there is no guarantee of CAL availability on the surviving license server in the event of a failure. Figure 5 provides a marginally higher level of redundancy by adding a second license server to each site that will issue temporary CALs only.
In the event of a license server failure, at the very least temporary CALs can be issued from the local site, while permanent CALs allocation may need to traverse the WAN.
Figure 5. Finally, augmenting Figure 5 by including permanent CALs on the additional site license servers could further improve redundancy, but it comes at the risk of increased management overhead to maintain the license servers. Remember, each additional license server that contains permanent CALs must be regularly backed up.
A fine line must be drawn between the level of redundancy necessary to maintain the environment, and the level of complexity the redundancy inflicts on the environment. The following recommendations and best practices will assist you in ensuring your licensing services infrastructure is resilient enough to withstand a single license server failure. Part one covered establishing resiliency in the licensing infrastructure.
Part two will focus on recoverability of license server to facilitate rapid restoration in the event of a failed license server. Very good article! And i have a question about temporal CALs : On a terminal server with a remote defined licence server that is the central licence server with per-user CALs, for high availability, if we add a local licence server with no CAL that will serve temporal CALs when the remote is down, do the GracePeriod will be checked to serve or not temporal CALS?
Best regards,. Your email address will not be published. Learn about the latest security threats, system optimization tricks, and the hottest new technologies in the industry. Over 1,, fellow IT Pros are already on-board, don't be left out! TechGenix reaches millions of IT Professionals every month, and has set the standard for providing free technical content through its growing family of websites, empowering them with the answers and tools that are needed to set up, configure, maintain and enhance their networks.
Challenges with Licensing Services License server availability is critical for the successful operation of a terminal server environment. Post Views: 8, Leave a Reply Cancel reply Your email address will not be published. Join Our Newsletter Learn about the latest security threats, system optimization tricks, and the hottest new technologies in the industry.
I understand that by submitting this form my personal information is subject to the TechGenix Privacy Policy. I plan to purchase an additional 10 per user CALs prior to the grace period expiration.
The license diagnoser shows no problems, all check marks are green. Are we OK after the grace period expires? Notify me of followup comments via e-mail. You can also subscribe without commenting. Leave this field empty.
Home About. Licensing mode for the Remote Desktop Session Host is not configured. Remote Desktop Service will stop working in days. If your RDS server is in a workgroup, the licensing report is not generated. Related Reading. January 10, December 22, Usman Ghani May 9, - am Thank you for saving my day, I tested on Windows server and worked perfectly. Jose Rosario June 19, - am What a lifesaver this page was.
So simple! Stephan July 4, - am Fantastic, Thank you, with your explanation, it was possible to license our server. Sudiro Sudiro July 18, - am awesome.. Jose July 26, - pm Funciono perfecto, en verdad me ayudo a quitarme un dolor de cabeza.
0コメント