![]() ![]() No errors or any issues indicated in any event log The licensing server is shown as not being activated.Ĥ. Needs to connect to a TS Licensing server even though the Per User TS CALs will not be issued.Ģ. Per User licensing is unmanaged in Server 2003, so TS CALs will not be issued. If they chose Per User licensing, then they need to purchase/own a Per User RDS/TS CAL for each person that connects to the TS and runs applications. Will log warnings/errors as well if there is a problem. If the server is unable to find/contact a TS Licensing server it will log entries, likewise if TS Licensing is running on the server it Please check the System event log for warnings/errors from Source: TermService or Source: TermServLicensing. In Add/Remove Programs-Windows Components, is Terminal Server selected? If yes then TS is installed and the server is in application server mode, either Per User or Per Device licensing mode.Ĥ. Are any servers listed under Automatically discovered? If yes then this server or servers is likely what the TS is communicating with.ģ. Please double-click License server discovery mode. In the right pane, what does it say for Licensing? Per User, Per Device, or Remote Desktop for administration?Ģ. ![]() Please open Terminal Services Configuration (tscc.msc), click on Server Settings in the left pane. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |