Prev: unable to logon using remote desktop - desktop heap exhaustion
Next: Prevent users from installing print drivers & Fallback terminal services enabled... print drivers still being added.
From: Mr_Huang on 7 Jan 2008 02:44 Dear guru, I have read several thread regarding this error, however, it cannot apply to my case. Three Terminal License servers deployed in my W2K3 domain, two in my AD and one in member server. Planned to phase out one of the AD (which contained TLS) with a new installation (same hostname WITHOUT the TLS). Having installed a new AD (same name without TLS) to my network, then I got this message "No Terminal Server license server is available in the current domain or workgroup. To connect to another license server, click Action, Click Connect, and then type the server name." when I launch the TS Licensing each time and it tried to connect to the old information instead. Tried LSView but nothing come up. However, I could able to see the other two LS in the "Terminal Service Configuration"-> "Server Settings" -> "Discovery Mode" and I could able to login to my Citrix, I assume my terminal (Citrix) server can locate the license server correctly. Checked with ADSIedit -> CN=Configuration -> CN=Sites -> Default-first- site -> CN=TS-Enterprise-License-Server Properties -> Site Server -> Distinguished name which contain all the hostnames of three License servers. It showed "cn=Delected Object" for my newly installed AD (same name without TLS) when clicking into the details attributes. Do you have any ideas? thanks huang
From: Ratnesh Yadav [MSFT] on 7 Jan 2008 03:23 Hi Huang, Terminal Server License Server (TSLS) manager tries to find out License Servers in following order, - Checks for Published License Servers in its site - Checks if its Domain Controller had License Server installed on it. So in your case, - Make sure new AD is in "Default-first-site" - You can delete the old entries (invalid) from "TS-Enterprise-License-Server" object - Then you can manually add License Server details; for doing so please check http://blogs.msdn.com/ts/archive/2007/02/27/manually-publishing-and-un-publishing-terminal-server-license-servers.aspx "Mr_Huang" <mr.huang.hk(a)gmail.com> wrote in message news:d30a180a-0854-40b4-898a-b03930fc2a2e(a)e23g2000prf.googlegroups.com... > Dear guru, > I have read several thread regarding this error, however, it cannot > apply to my case. > Three Terminal License servers deployed in my W2K3 domain, two in my > AD and one in member server. Planned to phase out one of the AD (which > contained TLS) with a new installation (same hostname WITHOUT the > TLS). > Having installed a new AD (same name without TLS) to my network, then > I got this message "No Terminal Server license server is available in > the current domain or workgroup. To connect to another license server, > click Action, Click Connect, and then type the server name." when I > launch the TS Licensing each time and it tried to connect to the old > information instead. > Tried LSView but nothing come up. > However, I could able to see the other two LS in the "Terminal Service > Configuration"-> "Server Settings" -> "Discovery Mode" and I could > able to login to my Citrix, I assume my terminal (Citrix) server can > locate the license server correctly. > Checked with ADSIedit -> CN=Configuration -> CN=Sites -> Default-first- > site -> CN=TS-Enterprise-License-Server Properties -> Site Server -> > Distinguished name which contain all the hostnames of three License > servers. It showed "cn=Delected Object" for my newly installed AD > (same name without TLS) when clicking into the details attributes. > Do you have any ideas? > thanks > huang
From: Mr_Huang on 7 Jan 2008 21:37
The error disappeared once I removed the "old entry" in my "TS- Enterprise-License-Server" -> "Default-first-site" Thank you very muchk On Jan 7, 4:23 pm, "Ratnesh Yadav [MSFT]" <ratneshya...(a)hotmail.com> wrote: > Hi Huang, > > Terminal Server License Server (TSLS) manager tries to find out License > Servers in following order, > - Checks for Published License Servers in its site > - Checks if its Domain Controller had License Server installed on it. > > So in your case, > - Make sure new AD is in "Default-first-site" > - You can delete the old entries (invalid) from > "TS-Enterprise-License-Server" object > - Then you can manually add License Server details; for doing so please > check > http://blogs.msdn.com/ts/archive/2007/02/27/manually-publishing-and-u... > > "Mr_Huang" <mr.huang...(a)gmail.com> wrote in message > > news:d30a180a-0854-40b4-898a-b03930fc2a2e(a)e23g2000prf.googlegroups.com... > > > > > Dear guru, > > I have read several thread regarding this error, however, it cannot > > apply to my case. > > Three Terminal License servers deployed in my W2K3 domain, two in my > > AD and one in member server. Planned to phase out one of the AD (which > > contained TLS) with a new installation (same hostname WITHOUT the > > TLS). > > Having installed a new AD (same name without TLS) to my network, then > > I got this message "No Terminal Server license server is available in > > the current domain or workgroup. To connect to another license server, > > click Action, Click Connect, and then type the server name." when I > > launch the TS Licensing each time and it tried to connect to the old > > information instead. > > Tried LSView but nothing come up. > > However, I could able to see the other two LS in the "Terminal Service > > Configuration"-> "Server Settings" -> "Discovery Mode" and I could > > able to login to my Citrix, I assume my terminal (Citrix) server can > > locate the license server correctly. > > Checked with ADSIedit -> CN=Configuration -> CN=Sites -> Default-first- > > site -> CN=TS-Enterprise-License-Server Properties -> Site Server -> > > Distinguished name which contain all the hostnames of three License > > servers. It showed "cn=Delected Object" for my newly installed AD > > (same name without TLS) when clicking into the details attributes. > > Do you have any ideas? > > thanks > > huang- Hide quoted text - > > - Show quoted text - |