Term Service License Server - AD still looking at old server?

  • Thread starter Thread starter Scott Townsend
  • Start date Start date
S

Scott Townsend

At one point we switched our Terminal Server License Server from Machine A
to Machine B.

I contact MS to get the server Registered and moved the License files over
and it seems to be fine.

My issue is that some of my clients still seem to be looking at the old
server A to see if it can get a License from it, or to see if its license is
still valid. When I try to connect to the Terminal Server I just get a
Connection Timeout. I'm using an old Wyse ThinClient.

I can connect to other Servers an Admin Mode, just not to servers in
Application mode.

How can I make sure that Server A is out of AD so it does not look for it
anymore??

Thanks,
Scott<-
 
Hi,

If have few questions for you
1) Did recreated the computer account for the new server ?
2) Is the new server has the same ipaddress of that old server ?
3) Is the entries in the dns server for both terminal servers are ok?


This posting is provided "AS IS" with no warranties, and confers no rights.
 
Hi,

If have few questions for you
1) Did recreated the computer account for the new server ?
2) Is the new server has the same ipaddress of that old server ?
3) Is the entries in the dns server for both terminal servers are ok?


This posting is provided "AS IS" with no warranties, and confers no rights.
Click to expand...


We have three AD Servers. AD, AD2, AD3.

AD is the oldest and the one we want to get rid of. Its pretty much
backup to everthing. AD3 has all the Roles, AD2 is also GC.

So I installed TS LS on AD and it was workgin great. Then We wanted to
move the Licenses to AD3. I installed TS LS on AD3, and then Called MS
to get all of the Licenses moved over to the new server.

So the old AD machine is still on the network, though the TS LS
Service is Disabled.

The TS that are on the network are fine in DNS, you can get to them
via Server Name, FQDN, and IP.

From any Win2K or XP Client, I can connect just fine. Its when I use
the Wyse ThinTerms that I run into issues.

Thanks,
Scott<-
 
It lools like a License (TSLS) discovery issue.
I would advice you call up MS Support again - i believe TSLS cases are
free.

Else, you can also do this

0. Since you mentioned you already called into MS and had the
Licensing installed on the 2003 TSLS, the TSLS should already be
activated.

1. From a Windows 2000/XP workstation export and then delete this key
from the registry (the entire mslicensing key)
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSLicensing
Make sure you are not in a Terminal Session at this point of time

2. Try to connect to the Terminal Server again with this machine. If
it doent allow you to login, do step 3,4,5. (ps: you would again be
granted access if you import the mslicensing key we exported in step
1)

3. Considering step 2 is a YES ie you are denied access to login to
the TS, sitting on the TS follow these steps

http://support.microsoft.com/support/kb/articles/q239/1/07.asp
If you TS is a Windows 2003 box, then do this
http://support.microsoft.com/default.aspx?kbid=279561

4. On the TS, go to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSLicensing
and delete the MSLICENSING key (again export to be safe)

5. Now try and login from the XP, 2000 Workstation where we deleted
the MSLICENSING from. Before you attempt to login, ensure there is no
MSLICENSING key at the location mentioned. These steps would help you
override the licensing server discovery issue

6. If answer to 2 is NO ie: you are granted access from the 2k/xp box
after deleting MSLICENSING key, and still are unable to login from
Thin Clients, you can use this hotfix after verifying the SYMPTOMS.

http://support.microsoft.com/?kbid=827355


Good luck

--
Gautam Anand
e: gautam at hotpop dot com
---------------------------------
| (e-mail address removed) (Abhijeet Nigam [MSFT]) wrote in
message | > Hi,
| >
| > If have few questions for you
| > 1) Did recreated the computer account for the new server ?
| > 2) Is the new server has the same ipaddress of that old server ?
| > 3) Is the entries in the dns server for both terminal servers are
ok?
| >
| >
| > This posting is provided "AS IS" with no warranties, and confers
no rights.
|
|
| We have three AD Servers. AD, AD2, AD3.
|
| AD is the oldest and the one we want to get rid of. Its pretty much
| backup to everthing. AD3 has all the Roles, AD2 is also GC.
|
| So I installed TS LS on AD and it was workgin great. Then We wanted
to
| move the Licenses to AD3. I installed TS LS on AD3, and then Called
MS
| to get all of the Licenses moved over to the new server.
|
| So the old AD machine is still on the network, though the TS LS
| Service is Disabled.
|
| The TS that are on the network are fine in DNS, you can get to them
| via Server Name, FQDN, and IP.
|
| From any Win2K or XP Client, I can connect just fine. Its when I use
| the Wyse ThinTerms that I run into issues.
|
| Thanks,
| Scott<-
 
Thank you for your reply.

I too thought it was a discovery issue. After trying to figure out how the
discovery process worked and not getting anywhere I was going to just force
the terminal server to use the new License Server.

Went into the Registry to the place where you add in the LS that you want
the TS to use and low and behold it was already being forced to use the old
TSLS.

I removed the Registry entry and bada boom bada bing, all was well in TSLS
land!

Thanks again for your reply!

Scott<-
Gautam Anand said:
It lools like a License (TSLS) discovery issue.
I would advice you call up MS Support again - i believe TSLS cases are
free.

Else, you can also do this

0. Since you mentioned you already called into MS and had the
Licensing installed on the 2003 TSLS, the TSLS should already be
activated.

1. From a Windows 2000/XP workstation export and then delete this key
from the registry (the entire mslicensing key)
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSLicensing
Make sure you are not in a Terminal Session at this point of time

2. Try to connect to the Terminal Server again with this machine. If
it doent allow you to login, do step 3,4,5. (ps: you would again be
granted access if you import the mslicensing key we exported in step
1)

3. Considering step 2 is a YES ie you are denied access to login to
the TS, sitting on the TS follow these steps

http://support.microsoft.com/support/kb/articles/q239/1/07.asp
If you TS is a Windows 2003 box, then do this
http://support.microsoft.com/default.aspx?kbid=279561

4. On the TS, go to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSLicensing
and delete the MSLICENSING key (again export to be safe)

5. Now try and login from the XP, 2000 Workstation where we deleted
the MSLICENSING from. Before you attempt to login, ensure there is no
MSLICENSING key at the location mentioned. These steps would help you
override the licensing server discovery issue

6. If answer to 2 is NO ie: you are granted access from the 2k/xp box
after deleting MSLICENSING key, and still are unable to login from
Thin Clients, you can use this hotfix after verifying the SYMPTOMS.

http://support.microsoft.com/?kbid=827355


Good luck

--
Gautam Anand
e: gautam at hotpop dot com
---------------------------------
| (e-mail address removed) (Abhijeet Nigam [MSFT]) wrote in
message | > Hi,
| >
| > If have few questions for you
| > 1) Did recreated the computer account for the new server ?
| > 2) Is the new server has the same ipaddress of that old server ?
| > 3) Is the entries in the dns server for both terminal servers are
ok?
| >
| >
| > This posting is provided "AS IS" with no warranties, and confers
no rights.
|
|
| We have three AD Servers. AD, AD2, AD3.
|
| AD is the oldest and the one we want to get rid of. Its pretty much
| backup to everthing. AD3 has all the Roles, AD2 is also GC.
|
| So I installed TS LS on AD and it was workgin great. Then We wanted
to
| move the Licenses to AD3. I installed TS LS on AD3, and then Called
MS
| to get all of the Licenses moved over to the new server.
|
| So the old AD machine is still on the network, though the TS LS
| Service is Disabled.
|
| The TS that are on the network are fine in DNS, you can get to them
| via Server Name, FQDN, and IP.
|
| From any Win2K or XP Client, I can connect just fine. Its when I use
| the Wyse ThinTerms that I run into issues.
|
| Thanks,
| Scott<-
Click to expand...
 
Back
Top