Terminal Server Licensing

Terminal Server Licensing - XP home

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

Banks, J - 23 Feb 2006 22:11 GMT

Running Win2k Terminal Server in a 2003 AD domain. The Terminal License
server is a DC using User Cals. XP and 2K machines access fine however
client XP Home machines receive "Remote computer disconnected the session
because of an error in the licensing protocol". i have gone through all
troubleshooting articles on Technet in regaurds to checking conenctivity with
License server all is fine. One thing i did notice is that when i tried a XP
Home machine it was issued a Temp Device Cal even though i have User Cals are
loaded.

any help would be appreciated.

Reply to this Message

Scott Harding - 23 Feb 2006 22:47 GMT

You may have to delete the local copy of the temporary license on the Home
machine. I remmeber having to do this with some Win98/2000 machines that
were issued temporary licences. I believe this is the article.
http://support.microsoft.com/kb/187614/en-us

Signature

Scott Harding
MCSE, MCSA, A+, Network+
Microsoft MVP - Windows Server Networking

> Running Win2k Terminal Server in a 2003 AD domain. The Terminal License
> server is a DC using User Cals. XP and 2K machines access fine however
[quoted text clipped - 9 lines]
>
> any help would be appreciated.

Reply to this Message

TP - 24 Feb 2006 00:32 GMT

Windows 2000 terminal server DOES NOT use Per-User TS CALs.
You need to have Per Device TS CALs available on your ts licensing
server.

Your XP Pro and Win2k machines are issued free TS CALs that
allow them to connect to a Win2k TS server. XP Home, Win9x, Mac,
etc., require a purchased Per Device TS CAL to connect to a Win2k
TS server.

-TP

> Running Win2k Terminal Server in a 2003 AD domain. The Terminal
> License server is a DC using User Cals. XP and 2K machines access
[quoted text clipped - 7 lines]
>
> any help would be appreciated.

Reply to this Message