Terminal Server Licensing - Windows 2003 Domain issue
From: Drew (muttsnutts_at_hotmail.com)
Date: 07/01/04
- Next message: Vit: "Remote Desktop Web Connection"
- Previous message: Jonathan Maltz [MS-MVP]: "Re: TS non-existent in SBS 2003"
- Next in thread: Javier Gomez [SBS MVP]: "Re: Terminal Server Licensing - Windows 2003 Domain issue"
- Reply: Javier Gomez [SBS MVP]: "Re: Terminal Server Licensing - Windows 2003 Domain issue"
- Reply: Vera Noest [MVP]: "Re: Terminal Server Licensing - Windows 2003 Domain issue"
- Messages sorted by: [ date ] [ thread ]
Date: 1 Jul 2004 12:51:31 -0700
We are shortly going to be upgrading our Windows 2000 domain to
Windows 2003. The domain has Windows 2000 DC's with the TS licensing
service on them. Clients are a mixture of Win2k and NT 4.0
workstation. Is there any method to license the NT4.0 workstations
once we move to Windows 2003 and demote the existing Win2k DC's to
member servers?
The method I am looking at is turning the old TSLS DC into a workgroup
and hard-coding all the Win2k TS servers to that license server. When
we install our W2k3 machines they will find the new license service
that we are going to put on the Win2k3 DC.
I would prefer to not change the present Terminal Servers but I cannot
find any other way around this issue?
Any suggestions gratefully received!
Cheers
Andy
- Next message: Vit: "Remote Desktop Web Connection"
- Previous message: Jonathan Maltz [MS-MVP]: "Re: TS non-existent in SBS 2003"
- Next in thread: Javier Gomez [SBS MVP]: "Re: Terminal Server Licensing - Windows 2003 Domain issue"
- Reply: Javier Gomez [SBS MVP]: "Re: Terminal Server Licensing - Windows 2003 Domain issue"
- Reply: Vera Noest [MVP]: "Re: Terminal Server Licensing - Windows 2003 Domain issue"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|