We presently have Win2k servers running terminal services (most in Admin
mode and a few Citrix servers in App Server mode) and a win2k Terminal
services License Manager on a non-domain controller. I guess the existing TS
License Manager has to be upgraded or replaced before we use terminal
services (even in the equivalent of Admin mode) on a Win2003 server?
We're planning to use Win2003 servers in terminal services Admin mode before
upgrading the Citrix servers to Win2003. Would we have 2 License Managers or
would the new win2003 License Manager handle both? If there were two License
Managers running concurrently it'd mean that we'd have details of our TS
CALs entered in two systems so I'm guessing it's a case of having just one
new TS License Manager.
Does the Win2003 TS License Manager need to be installed on a domain
controller (or is that only a requirement of active directory services)?
Can we decide now that we'll be using User CALs in future without changing
any of our systems (especially the existing License Manager) until
installing the new/second License Manager (when I suppose we'd have to
select User as opposed to Device and the number of licenses we have)?
Would we only "convert" when we install the new Win2003 License Manager or
do we do that now?
As soon as you install a 2003 TS, you will need a 2003 TS Licensing Server
as well. 2003 LS can handle both W2K and 2003 TS CALs, so there's no need
to keep your old W2K LS.
2003 LS does not have to be installed on a DC, buth there are some details
that you should read about (Eneterprise versus Domain LS). Check the
Windows Server 2003 Terminal Server Licensing White paper at
http://www.microsoft.com/windowsserver2003/techinfo/overview/termservlic.ms
px
There's no reason to change to "per user" TS CALs if "per device" is more
appropriate for your company. In fact, you can mix them.
--
Vera Noest
MCSE,CCEA, Microsoft MVP - Terminal Server
http://hem.fyristorg.com/vera/IT
*----------- Please reply in newsgroup -------------*
"Andy Banks" <andy....@plato.co.uk> wrote in
news:OITkrt0V...@tk2msftngp13.phx.gbl: