 |
 | Home | Contact Us | FAQ | Search & Site Map | Link to Us |
 | Sign In | Join | Other 45 Sites in Network |
Windows Server Forum / Windows 2000 / Terminal Services / October 2004Upgraded to Win2003; how to get this to work with a Win2000 DC Terminal Services Server ?
TS Win2000 Server (client) was upgraded to Win2003 Standard Server. Now when I try to connect to the Win2003 server via remote desktop I am getting: The remote session was disconnected because there are no terminal server client access licenses available for this computer. Please contact the server administrator Let me know confirm: Based on the article below, Win2003-based terminal server cannot communicate with a Win2000 Domain Controller. The problem is this: Besides this Win2003 Server that can't connect to the Windows 2000 TS DC anynore, I still have Windows 2000 based TS. If I install a member Win2003 Server as a Terminal Service Server, is my Win2000 TS clients going to connect to my Win2000 TS DC, or should I switch them to the Win20003 Term. Server member server ? Please advise if any glitches are expected in case I have two terminal licenses server running (one WIn2000DC and a Win2003 Server). How to deploy Windows Server 2003 Terminal Services A Windows Server 2003-based terminal server communicates only with a Windows Server 2003-based Terminal Server License Server. You cannot install Windows Server 2003 TS CALs on a Windows 2000-based Terminal Server License Server. When you upgrade Windows 2000-based terminal servers to Windows Server 2003, you must install and activate Windows Server 2003 Terminal Server License Server or upgrade an existing Windows 2000 License Server to Windows Server 2003. Windows Server 2003 Terminal Server License Servers can communicate with both Windows 2000-based and Windows Server 2003-based terminal servers. When you deploy Windows Server 2003 Terminal Services in a Windows 2000 domain, you have the following licensing options: . Upgrade existing Windows 2000 domain controllers that host the Windows 2000 license server to Windows Server 2003 domain controllers. . Install Windows Server 2003 Terminal Server License Server on a member server that is running Windows Server 2003. . Demote the Windows 2000-based license server to a member server, upgrade this computer to Windows Server 2003, and then add additional domain controllers as required. Windows Server 2003-based terminal servers can automatically discover a Terminal Server License Server that is installed on a member server that is running Windows Server 2003 and that is configured as an Enterprise License Server in the Active Directory directory services site. I *think* that I understand what you mean, but let me verify it: When you write "Win2003 Server that can't connect to the Windows 2000 TS DC anynore", do you mean "...can't connect to the Windows 2000 TS Licensing Server"? Windows 2003 has no problem communicating with a W2K Domain Controller (or it couldn't be a member of your domain at all), but it must connect to a 2003 Licensing Server. You can install the 2003 Licensing Service on the existing 2003 Terminal Server, since it doesn't have to run on a Domain Controller (as W2K LS requires). You can keep both licensing servers, one on W2K and one on 2003, or put all your licenses on the 2003 Licensing server. Both scenarios should work. You are aware that you also need to buy and install 2003 TS CAL on the 2003 Licensing Server for all clients, I assume? Here's an excellent white paper with many examples about mixed W2K and 2003 domains: Windows Server 2003 Terminal Server Licensing White paper http://www.microsoft.com/windowsserver2003/techinfo/overview/terms ervlic.mspx -- Vera Noest MCSE, CCEA, Microsoft MVP - Terminal Server http://hem.fyristorg.com/vera/IT --- please respond in newsgroup, NOT by private email --- "Marlon Brown" <marlon_brown@hotmail.com> wrote on 28 okt 2004 in microsoft.public.win2000.termserv.clients: > TS Win2000 Server (client) was upgraded to Win2003 Standard > Server. [quoted text clipped - 59 lines] > configured as an Enterprise License Server in the Active > Directory directory services site. You understood my problem perfectly. Thanks ! > You are aware that you also need to buy and install 2003 TS CAL on > the 2003 Licensing Server for all clients, I assume? Not sure what the above means ? That means that I need to install the 2003 TS CAL that my WinCE and WinXPE are using... that's what I did even on Win2K TS... One more question: Imagine that I install 2003 Terminal Services Server on the ScrewupGuysGroup and then I keep my production Win2K DC as the terminal services server running for the rest of my customers. Later I upgrade my Win2K DC to Win2003 DC (on Win2003 I know I can put the terminal server services on stand alone if I want to). My question is this, in the future can I keep *two* 2003 Terminal Services Servers in my domain ? If so, I will let the ScrewupGuysGroup manage their own TS Server and I will use a separate Win2003 TS Server to manage the rest of my organization. I couldn't do that before on Win2K because it had to be done in DC, controlled by the network group. Imagine that I have my existing clients that > I *think* that I understand what you mean, but let me verify it: > [quoted text clipped - 95 lines] > > configured as an Enterprise License Server in the Active > > Directory directory services site. Marlon, you seem to use the word "terminal services server" when you instead mean "Terminal Server Licensing Server"! These are 2 very different functions. If I understand you correct, yes, you can have 2 separate TS Licensing Server in your Domain, and you can directly controll which TS contracts which LS by hardcoding the Preferred Licensing Server into the TS. What I mean with 2003 TS CALs is just that. Many people believe that their purchased Windows 2000 TS CALs also will work when they connect to a 2003 TS. They won't. -- Vera Noest MCSE,CCEA, Microsoft MVP - Terminal Server http://hem.fyristorg.com/vera/IT *----------- Please reply in newsgroup -------------* "Marlon Brown" <marlon_brown@hotmail.com> wrote on 29 okt 2004: > You understood my problem perfectly. Thanks ! >> You are aware that you also need to buy and install 2003 TS CAL [quoted text clipped - 44 lines] >> >> Windows Server 2003 Terminal Server Licensing White paper http://www.microsoft.com/windowsserver2003/techinfo/overview/ter >> ms ervlic.mspx >> [quoted text clipped - 72 lines] >> > that is configured as an Enterprise License Server in the >> > Active Directory directory services site. |
Reply to this Message |
 Sign In
 Join
 My Latest Posts My Monitored Threads My Blog My Photo Gallery My Profile My Homepage Start New Thread Enable EMail Alerts Rate this Thread
|
©2009 Advenet LLC Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.