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

 

[WillShakespeare]

If the above doesn't work, I'll email you the image...

Will

 

[WillShakespeare]

Also, I just read this paragraph in the TS White paper:

It is also possible to override this discovery process by specifying a preferred license server (or multiple license servers) on a terminal server by using a WMI script. For three scripts that you can use to set preferred license servers, delete preferred license servers, or query preferred license servers, see “Administration” later in this document.

Will post more details as I find them...

Will

 

[WillShakespeare]

More interesting stuff from the white-paper:

Important
Although it is possible for non-domain controllers to be license servers in Windows Server 2003, it is important to note that domain license servers are not automatically discovered. You must configure a preferred license server on all terminal servers that need to communicate with non-Domain controller license servers configured as domain license servers. Enterprise domain license servers deployed on non-domain controllers are automatically discovered.

 

[WillShakespeare]

and more...

Note
In determining the location of a license server, discoverability is the most critical factor. A domain, site, or workgroup hosting terminal servers must also host a license server. For most applications, it is suggested that each terminal server have at least two discoverable license servers to ensure high availability. The primary license server should be activated and have sufficient quantities of license tokens installed. The secondary license server should be activated, but should not have any license tokens installed. Using this model, the secondary license server will be able to issue temporary tokens to clients without license tokens if the primary license server is unavailable.

 

[WillShakespeare]

Here is a script that seems to work on my network... in fact here are three with their desciptions in the header bit. Save them as vbs and run with WScript 5.6.
You might try running script 3 first, to see if your License Server is enumerable (is that a word?)!

Will


Script 1 - AddLS.vbs:
'***********************************************************
'
' WMI VBscript to add a specified License server to
' Terminal server's registry
'
'***********************************************************
if Wscript.arguments.count<1 then

Wscript.echo "Script requires one argument, the LicenseServerName"
Wscript.echo "e.g. cscript AddLicenseServer LicenseServerName"
Wscript.quit
end if

Dim strServer
strServer=Wscript.arguments.Item(0)

for each terminal in GetObject("winmgmts:{impersonationLevel=impersonate}&quot.InstancesOf ("win32_TerminalServiceSetting&quot

result = terminal.AddDirectConnectLicenseServer (strServer)

WScript.Echo "Method returned result = " & result

if err <>0 then
WScript.Echo Err.Description, "0x" & Hex(Err.Number)
end if
next


Script 2 - DeleteLS.vbs:
'***********************************************************
'
' WMI VBscript to add a specified License server to
' Terminal server's registry
'
'***********************************************************
if Wscript.arguments.count<1 then

Wscript.echo "Script requires one argument, the LicenseServerName"
Wscript.echo "e.g. cscript DeleteLicenseServer LicenseServerName"
Wscript.quit
end if

Dim strServer
strServer=Wscript.arguments.Item(0)

for each terminal in GetObject("winmgmts:{impersonationLevel=impersonate}&quot.InstancesOf ("win32_TerminalServiceSetting&quot

result = terminal.DeleteDirectConnectLicenseServer (strServer)

WScript.Echo "Method returned result = " & result

if err <>0 then
WScript.Echo Err.Description, "0x" & Hex(Err.Number)
end if
next


Script 3 - QueryLS.vbs:
'***********************************************************
'
' WMI VBScript that queries the License servers configured
' for registry bypass.
'
' on the Terminal server
'
'***********************************************************
for each Terminal in GetObject("winmgmts:{impersonationLevel=impersonate}&quot.InstancesOf ("win32_TerminalServiceSetting&quot
WScript.Echo "The License Servers are = " & Terminal.DirectConnectLicenseServers
next

 

[Enigma256]

David, When you do the registry edit I mentioned above you will not see it taking any licenses, well in my case it has not taken any and it is working fine for me, I know that is prolly what you are not looking for.

 

[davidwilson11]

enigma

with regards to this as mentioned previously.....

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.

I still cannot get the terminal server 2003 to pick up the license server, every time it still wants me to activate it.

am i going mad.

 

[davidwilson11]

P.S. guys that link didnt work

 

[WillShakespeare]

Give the scripts a go...

 

[WillShakespeare]

I am an idiot! Might help if I used jpg extension instead of jpeg! Let's try again!

 

[Enigma256]

David have you tried changing the client TS from per Device to Per User?

 

[davidwilson11]

No i havent tried changing the client from per user to per device to per user. I will try it out tomorrow. I just had a thought, do i have to put the registry edit on both the domain controller and the 2003 box?

Just a though.

 

[davidwilson11]

ps is that an exact copy of your registry show in the image, where is the name of the liecense server for ts or am i being stupid...

 

[WillShakespeare]

The name of my server is TERMSERV
It is the "folder" (key) that is named for the server. There should be nothing inside the key. This is where I got confused originally!

Will

 

[davidwilson11]

Guys guys guys

you want some good news, i got it ye ha.

The server is now picked up thanks to you guys.

The server is however handing out temporary licenses and as i have read once the temp licenses run out it will move on and look for the installed licenses. am i correct for thinking this.

Can you let me know guys

Again thanks for being ever so helpful with this matter.

As i only visit this site once a week it has taken some time to solve however with your help this has been accomplished. Guys thanks a lot.

Speak to you soon.

David

 

[WillShakespeare]

If you want to make sure about the temp licences, see my FAQ:
faq931-4850

Make sure you understand the difference between Per User, and Per Device. It is the Per Device licences that are temp. When they finish, you won't be issued with full licences if you are using Per User, because these types of CAL are NOT Supported by MS yet!

Will

 

[davidwilson11]

well to make matters worse when i reregistered the cals i noticed that i have per device and per user. how can i remove the licenses as i have four different instances of them running.

hmmmmm

 

[WillShakespeare]

Don't worry. This is normal. The Per Device CALs will dissappear when they run out. Essentially in Per User mode, these are ignored. I confirmed this from the horses mouth as it were (Microsoft).
We have 6 running, and the won't expire until May.
You aren't breaking any EULA by having them there.

hth,

Will

 

[davidwilson11]

guys

i have been in thailand on holiday and havent had a change to thank you for all the time that you put into helping me with this problem. so once again thanks for the time and maybe we shall help one another again.

Cheers

David