• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 446
  • Last Modified:

Specifying a license server for Citrix in Win2003

We have implemented Citrix XPa on Win2003.
We have a TS licensing server on our network
When I start up TS license manager, it says that there are no license serves available on the network.
If I go File->Connect, I can connect to the licenses server and in the history I can see that the server has issued licenses to machines on our network.
If I exit TS license manager and start it again, it again says that there are no license serves available on the network.

Can anyone tell me:
1: Are we using this license server?
2: Why cant license manager automatically find it on the network.
3: What can we do yo resolve the problem.

Thankss

john
0
metarushej
Asked:
metarushej
  • 3
  • 2
1 Solution
 
BLipmanCommented:
Your license server is probably not registered in your domain.  I think this is an option when you install it initially.  With Server 2003 you can specify a license server a couple of ways.  

If you have SP1 for Server 2003: Open Terminal Services Configuration and click on Server Settings, go into License Server Discovery Mode.  From here you can enter your server name/IP or you can set it to Automatic.  The bottom of the screen shows your discovered license servers (as read from your AD I believe, broadcast discovery for workgroup mode).  

If you do not have SP1 installed you must use the registry:

To set a preferred license server by using the registry (on Windows Server 2003)
 
 1.  On the license server, open Registry Editor. To open Registry Editor, click Start, click Run, type regedit, and then click OK.
 
2.  Locate, and then click, the following key in the registry:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\TermService\Parameters
 
3.  On the Edit menu, point to New, click Key, and then type LicenseServers to name the new key.
 
4.  Locate, and then click, the following key in the registry:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\TermService\Parameters\LicenseServers

On the Edit menu, point to New, click Key, and then type ServerNamewhere ServerName is one of the following:

• The FQDN of the server (for example, Server1.contoso.com)
 
• The NetBIOS name of the server(for example, Server1)
 
• The IP address of the server (for example, 206.73.118.1)
 
 
5.  Restart your computer.
 
http://technet2.microsoft.com/WindowsServer/en/Library/1003f927-9e59-42e1-b822-61a07113e1d01033.mspx?mfr=true
 
0
 
metarushejAuthor Commented:
thanks for your reply:

two queries:

1: When I add the entry for the servename the registry, should it be a key or a string value.
2: After I restart the server, should the server that was registered in the registry be displayed in the license server manager window?

Thanks,

john
0
 
BLipmanCommented:
1: When I add the entry for the servename the registry, should it be a key or a string value.
--- Interestingly enough, it needs to be a key!  Odd huh?

2: After I restart the server, should the server that was registered in the registry be displayed in the license server manager window?
---You still won't get the server you specify to come up in your TS Licensing Manager until you use Connect to point to it. (see below link for why)

Here is a link that shows where your TS Licensing Setting exists in an Active Directory:
http://www.windowsitpro.com/articles/images/termservlicldap.jpg

Does this help?  
0
 
metarushejAuthor Commented:
1: Strange indeed.
2: If the TS is not displayed in the TS license manager how can I confirm that my servers are using licenses from the license server and not still using the 90-day temporary licenses?

thanks

john
0
 
BLipmanCommented:
If they can't talk to a licensing server period you will get corresponding errors in your event viewer.  The 90 day temp. licenses are given by a licensing server so if you connect a new client you should be able to look at licensing and see the new temp. license.  
Do you have SP1 on your servers?  If so then you can use the GUI version instead of the registry; this lets you actually test connectivity to the server you specify.  
Another FYI, I think all clients get a temp. even when TCALs are there to issue...they aren't issued a real one until the temp. expires.  
Make sure you are testing with non-administrative accounts as admins, by design, can connect w/o a TCAL (2 concurrent sessions).  
0

Featured Post

What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

  • 3
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now