MCTS Windows Server 2008 Migrating User Accounts
Decide whether the server(s) that host TS Licensing can be shared. Essentially, a server can be shared either between farms or between services. This means if you have multiple farms, you can choose to use one or multiple licensing servers to lessen the burden of the role on other servers and keep them concentrated on the role they?re already using. Additionally, you need to decide whether you want your licensing server to be dedi- cated or instead to host additional Terminal Services servers.
Determine where to place the TS Licensing role in the network. Ideally, the best place to put your Microsoft Exam licensing server is on a LAN where every computer can easily and quickly access it. However, if your organization is separated by a WAN, you will need to install multiple licensing services at each point of the WAN to alleviate the burden of communicating this information across distances.
Determine the fault tolerance requirements of TS Licensing. A good practice to use whenever you?d like to establish fault tolerance for TS Licensing is to acquire two serv- ers, divide the licenses between each of those servers, and then publish each in Active Directory. This greatly reduces the chances of services being unavailable in case of a failure.
When using TS Licensing per-user mode, administrators can monitor licenses that are being propagated through a network via a particular license server. This allows administra- tors to check for EULA compliance as well as proper usage of particular licenses throughout the enterprise. Windows Server 2008 can also produce a per-user license usage report via the TS Licensing Manager, which is useful if an administrator suspects that some licenses are being used improperly throughout their enterprise.
Terminal Services Licensing Services Events
A couple of issues tend to come up when using Terminal Services Licensing. You’ll want MCSE 2003 to know the following two event IDs when administering a licensing server:
Event ID 28:
Manager This event sounds a lot more complicated than it really is. All event ID 28 means
is that Terminal Services is unable to connect to the Service Control Manager. More often than not, the best solution for this is to reboot the server and make certain that the TS Licensing role has started.
Event ID 37: Fun
with cryptic errors! Normally, this event occurs when certain groups are given incorrect permissions. You can resolve this problem by making sure the correct permissions are established. If all else fails and the security is set correctly, rebooting will most likely ?x the issue.
Processing your request, Please wait....
