Thank you for your question. I am trying to involve someone familiar with this topic to further look at this issue. There might be some time delay. Appreciate your patience. Thank you for your understanding and support.
Alan Zhu. Forum Support. Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact tnmff microsoft. In the resulting dialog titled Select Role Services select the check box next to TS License Server and then click Next to proceed to the Configure discovery scope for TS licensing screen as illustrated in the following figure:.
The selections on this screen define whether licenses are to be issued to systems in the same workgroup, domain or domain forest as the license server. The correct selection here will depend on your network configuration. Once the selection has been made click Next followed by Install on the subsequent confirmation screen. On a server which is does not have the Terminal 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 Terminal 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 TS Licensing and click next. As described above, choose whether the server is to be accessible to terminal servers in the same workgroup, domain or domain forest as the license server. Click Next followed by Install to initiate the installation process. Once the TS License Server has been installed the next task is to activate it. Figure 4. Figure 5. Figure 6. Figure 7. Figure 8. Figure 9. Figure At the point we are ready to configure Terminal Services Licensing.
In this example I will use some dummy data, which does not meet the actual requirements for licensing Terminal Services client connections, but it will provide an example of how the process works.
Please do not use the same procedure that I show here to license your Terminal Services clients, because you will not be compliant with actual licensing requirements. Perform the following steps to configure the Terminal Services Licensing Mode:. The first noticeable change in the licensing process is the installation of the terminal server licensing service itself.
However, everything in Windows Server is role-based. Another thing that has changed is an additional rights requirement when installing a Domain-scope license server. The administrator performing the installation must have Domain Admin rights because part of the installation now involves adding the license server computer account to the Terminal Server License Servers security group in Active Directory. As with Windows Server , the following steps are necessary to complete the terminal services licensing process:.
As with Windows Server , Server caches the installation files for most roles so there is no need to supply the installation media when installing any of the Terminal Services Roles.
Once the installation is complete, you will notice a few differences in the files contained in the LServer directory compared to those from Windows Server This is a checkpoint file used to determine which transactions in the transaction log edb.
This file is updated each time a transaction is committed to disk and is used to quickly recover the integrity of the licensing database if the database was not shut down correctly.
This file will grow to 5 MB in size, at which time it will be renamed to edbxxxxx. Reserve transaction log files that serve as a drive space placeholder. There are two of these created, typically 5 MB in size, and are only used in the event the drive hosting the transaction logs runs out of space.
These files are used to facilitate a clean shutdown of the database.
0コメント