terminal server licensing server 4

[davidwilson11]

Guys and gals

I have a problem with a 2003 box TS licensing server.....

DC is 2000 box
2003 member server

installation and activation of 2003 TS license server went well, no problems noted. however.....

When users connect to the server i had a look at the license server in TS, for some reason it was not connected, i connected it but the TS CALS were not being issued.

Not sure what steps to take, the only problem that i can forsee is the fact that i have not registered my copy of 2003 standard edition server.....

any help would be appreciated.

Thanks in advance

 

[davidwilson11]

guys

sorry i have not been able to postany messages, one of my servers fell over big style. two raid disks failed so i have spent all my time fixing that issue.

Back to the real stuff, i had a glance over some of the stuff you guys were discussing!

Have you had any luck enigma.... i am having the same problem with the registry, never mind... ill get there with that. Have you been able to test this with the licensing as yet i still havent tried the reg hack and the licensing server looks for activation over and over. As the same with you in around three months i will also look like an idiot, may be we can work on this together.

Let me know any results that you have had.

Mark i shal keep you up to speed as i will be trying the reg hack on tuesday afternoon.

Cheers.

thanks for all the replys.

P.s will microsoft help us with this matter.

 

[markdmac]

Hi Enigma256, so that did not expire it huh? I'd have thought it would have. Just curious, are there any other servers int he mix? For instance was the workstation authenticated by the same server that is the license server, or is there another server in the equation. When the workstation logged on, the login server should be setting the time, just something to consider/look at for your testing.

I hope you find this post helpful. Please let me know if it was.

Regards,

Mark

 

[Enigma256]

Mark Thanks for the reply. No there are no servers in the mix. I have setup dc as the TS license Server with per device and per User License Clients CAL licenses 50 each, One TS client in that domani with same IP subnet ( also put it in the same rack to make sure in the same subnet ) changed the clock ahead, does not get any license. On the TS client, I choose TS licensing manager ( in the registry I make it manually find the TS license Server ) says cannot find any license servers. I go into menu->connect type in the license server computer name, error message says Windows cannot connect to server. Trust exists between dc and the client. I hope that all made sense. I have no idea what else to do.

David Sorry to hear about the raid crash. Yes Microsoft will help but they will charge. I am going to try to see if I can call and get help from Microsoft. Will post if I can. Thanks for your help

 

[markdmac]

Enigma, one thing in your last post does not make sense to me. You say that on the client you made the registry change? This would be incorrect. The registry hack that I posted above is for a Terminal Server, not the client.

To better explain, when a client connects to a terminal server, that server (not the client) looks for a license Server, it then gets a license for the client and passes it on to the client. If you have only one server in your environment, and both the terminal server and license server are on that same box, then there is no need for you to do the registry hack. Doing the hack will not hurt, but you need to do it on the terminal server, not the client computer.

I hope you find this post helpful. Please let me know if it was.

Regards,

Mark

 

[WillShakespeare]

Hi Guys, to add to markdmac's comment, I note too that what was suggested was changing the clock on the client forward to clear a license? I can't see how this would work as the clock on the TS is what is used to compare licences. Surely setting this clock forward temporarily would be the key?
Problem is, you might cause other programs to think incorrectly about dates, if you have time-based subscriptions or some such.

Will

 

[markdmac]

Hi Will, just for clarification, the suggestion was to change the time on both the server and workstation.

I hope you find this post helpful. Please let me know if it was.

Regards,

Mark

 

[WillShakespeare]

That sounds about right. The post from Enigma said this though, and I just wanted to make sure he realised he might only be doing half a job!
Enigma said:
MarkdMac, Well I changed the date on the TS client to like 5 months ahead, it did not get a license from the TS License Server at all

Will

 

[davidwilson11]

Guys guys guys

i am getting lost here. Can i be bold and start from the begining.

DC win2k server with exchange 2k, domain license server.
Member server with 2003 terminal server and terminal services licensing server installed.

2003 box keeps asking me to activate the server, also it is not issuing the TS cals to clients.

Result

where do i put in the registry hack on the 2003 or the 2k DC. Next, can i simply stop all license logging services on both servers.

Help i was getting lost with all the users input.

Cheers

 

[Enigma256]

The TS client Computer name is Ntest that has joined a Domain Controller SSD (for short). NTest and SSD both are running Windows 2003 Enterprise server with latest patches and what not. Ntest has successfully joined SSD and can see all the users in the DOMAIN.
I have installed License Server on SSD with 50 Cal Licenses for Windows 2003 - Terminal Server per Device and Per User.
On Ntest, I installed Terminal Server ( Relaxed Secutiry ) and rebooted. I launch up Terminal Services Manager and it does not show up any license server, gives an error message saying Windows cannot connect to server. So in the link that I mentioned above a book on Terminal Server :
To override the discovery process, add subkeys to the HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\TermService\Parameters\LicenseServers subkey. Each subkey should be named with the hostname of the license server that you want the terminal server to use. Figure 1.11 shows a registry with two license servers defined.

I do the above mentioned addition to the registry and reboot Ntest. Now when I go into Terminal Service License Manager, it sees the license manager (ssd) in the discovery, but still cannot connect to it.

Will : sorry do not take it this the wrong way I did not understand what you meantioned above : I just wanted to make sure he realised he might only be doing half a job!

Thanks for your help Will and Mark, let me know what I did wrong? Thanks

 

[Enigma256]

Well Will, Once I changed the Terminal Server to Per User, you go into licensing manager, it finally sees the license server. Thanks

 

[WillShakespeare]

Will : sorry do not take it this the wrong way I did not understand what you meantioned above : I just wanted to make sure he realised he might only be doing half a job!

Hi Enigma! Don't worry! The point is to discuss, and help if possible. Look for your post in the list of posts that says, in entirety:

"MarkdMac, Well I changed the date on the TS client to like 5 months ahead, it did not get a license from the TS License Server at all." Dated Feb 16, 2004

MarkdMac suggested that you update the date on BOTH server and Client. In your post above, you only state you updated the date on the client. You don't mention updating the date on the server. So, what I was saying is that I was trying to make sure you didn't do only half a job and update the Client ONLY, and not the server as well. Does that make sense?

Will

 

[WillShakespeare]

Enigma... do I get a star then???

LOL! Just kidding!

Will

PS - I just hope you haven't taken any of my posts the wrong way... I hope you see my explanation above of the "half-job" comment that I wasn't suggesting you do half-a-job, or anything...! I was just trying to make sure you did both things (client AND server)
But anyway, it doesn't matter anymore because you say it works!
Great!

 

[Enigma256]

Will: I apologize I did not take your posts the wrong way. I just did not read them properly, so everything is cool. I gave you a star was well.

DavidWilson11: Sorry I think we sort of hijacked your thread but if I understand correctly you have a 2000 server as a Domain Controller and a 2003 which is a member of a 2000 DC. You have installed Terminal Server and Terminal Service Licensing on the 2003 box. I have the same set up as well. I suggest go ahead activate the TS License Server on the 2003 box. Install the licenses after calling Microsoft. I had to do the following regedit on all the servers that have TS installed that access this license server (hope that makes sense) Open regedit ->
HKEY_LOCAL_MACHINE\SYSTEM\CURRENTCONTROLSET\SERVICES\TERMSERVICE\PARAMETERS. Go to that path. On the right pane click new key and type in DefaultLicenseServer and the REG_SZ value is the name of the licenseserver or you could use the IP Address of the server as well.

That should fix your problem David

 

[davidwilson11]

enigma

cheers for that, i didnt mind you guys having a chat on the posting as i found it quite informative, and hey how many chats get three stars that involve me ha ha ha ha ha ha.

I will keep you posted on the result. Many thanks.

David

 

[davidwilson11]

I also have another question with regards to AD and DNS, on of my colegues recently did a repair on the 2K DC and Exchange. Now i have SID's appearing all over the place in active directory. They are not clearing up.........

Could this be downto bad DNS configuration or shall ihave to take a bath and reinstall the DC....

David

 

[WillShakespeare]

david,

You might be better posting this as a new thread. Mainly because the focus has been TS here, and so you may be missing out on AD and DNS experts that don't know much about TS!
Incidentally, if you have lots of SID users in your groups, I have written a little script that allows you to remove users from groups on any machine, including those SID accounts which essentially are there because the users are not recognised as part of the existing AD.
If you'd like it, I could email my script to you. It has a counterpart which will list all the members of a particular group as well. The way they work together is run the one that lists members of a domain Group or a Local Machine group, then if you have people in there that shouldn't be (like local Administrators which should be normal users) you can use this list to copy and paste the info into the dialog boxes of the second script which removes them.

Let me know, and if you use 'em, they have to be worth a star!

Will

 

[markdmac]

Start a new thread on this one and we will be happy to give you a hand with it. I agree with Wil and let's get more eyes on it for you.

I hope you find this post helpful. Please let me know if it was.

Regards,

Mark

 

[davidwilson11]

mark

can you as one last favour post a screen shot of your registry edit, still the damnned thing wont pick the licenses.

Cheers

 

[WillShakespeare]

 

[WillShakespeare]

hmmm...
try clicking here:

http://www.pantheonventures.com/images/regkey.jpeg