Moving to 2003 domain

[shuman]

I have already moved to the 2003 domain. Some of the devices are now hitting
the 90 day temp license issue. I have read the post that deals with this. I
need to remove the TS licensing from the 2000 TS server. But I have already
installed the TS licensing on the 2003 AD server. If I remove the licensing
from 2000, will I need to manually point the 2000 server to the 2003 server
to request the TS licenses for the devices? I would rather not re-install
the TS licensing on the AD 2003 server.

Thanks!

[Vera Noest [MVP]]

Did you also install TS CALs on the 2003 LS? If so, which type of
TS CALs (W2K, 2003 Per User or 2003 Per Device)?

Assuming that the W2K TS is a member server in the same domain as
the 2003 DC which runs the TS Licensing Service, it should be
autodetected.
But if you previously have hardcoded the name of the old W2K LS
into the registry of the W2K TS, then you have to remove this
registry key again, to enable autodetection of the 2003 LS.

239107 - Establishing Preferred Windows 2000 Terminal Services
License Server
http://support.microsoft.com/?kbid=239107
_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email ___

Post by shuman
I have already moved to the 2003 domain. Some of the devices
are now hitting the 90 day temp license issue. I have read the
post that deals with this. I need to remove the TS licensing
from the 2000 TS server. But I have already installed the TS
licensing on the 2003 AD server. If I remove the licensing from
2000, will I need to manually point the 2000 server to the 2003
server to request the TS licenses for the devices? I would
rather not re-install the TS licensing on the AD 2003 server.
Thanks!

[shuman]

I have 2003 TS Per User CALS on the 2003 LS. Those were added prior to the
events below.

Last night I removed the LS from the W2K server. I added the
"DefaultLicenseServer" to both of my W2K TServers, pointing to the AD server
running LS. Rebooted both servers. The two devices that were having an issue
connecting are a WBT and an XP Pro workstation. On the XP Pro I deleted the
license cache info. The XP Pro connected, but received another temp license
due to expire in Feb 2006. The WBT still does not connect.

Post by Vera Noest [MVP]
Did you also install TS CALs on the 2003 LS? If so, which type of
TS CALs (W2K, 2003 Per User or 2003 Per Device)?
Assuming that the W2K TS is a member server in the same domain as
the 2003 DC which runs the TS Licensing Service, it should be
autodetected.
But if you previously have hardcoded the name of the old W2K LS
into the registry of the W2K TS, then you have to remove this
registry key again, to enable autodetection of the 2003 LS.
239107 - Establishing Preferred Windows 2000 Terminal Services
License Server
http://support.microsoft.com/?kbid=239107
_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email ___

Post by shuman
I have already moved to the 2003 domain. Some of the devices
are now hitting the 90 day temp license issue. I have read the
post that deals with this. I need to remove the TS licensing
from the 2000 TS server. But I have already installed the TS
licensing on the 2003 AD server. If I remove the licensing from
2000, will I need to manually point the 2000 server to the 2003
server to request the TS licenses for the devices? I would
rather not re-install the TS licensing on the AD 2003 server.
Thanks!

[shuman]

Vera,

I reset the WBT to factory defaults and now I can connect to the W2K TS.
However, the LS issued a temp license to the WBT.

What am I missing here?

Post by shuman
I have 2003 TS Per User CALS on the 2003 LS. Those were added prior to the
events below.
Last night I removed the LS from the W2K server. I added the
"DefaultLicenseServer" to both of my W2K TServers, pointing to the AD server
running LS. Rebooted both servers. The two devices that were having an issue
connecting are a WBT and an XP Pro workstation. On the XP Pro I deleted the
license cache info. The XP Pro connected, but received another temp license
due to expire in Feb 2006. The WBT still does not connect.

Post by Vera Noest [MVP]
Did you also install TS CALs on the 2003 LS? If so, which type of
TS CALs (W2K, 2003 Per User or 2003 Per Device)?
Assuming that the W2K TS is a member server in the same domain as
the 2003 DC which runs the TS Licensing Service, it should be
autodetected.
But if you previously have hardcoded the name of the old W2K LS
into the registry of the W2K TS, then you have to remove this
registry key again, to enable autodetection of the 2003 LS.
239107 - Establishing Preferred Windows 2000 Terminal Services
License Server
http://support.microsoft.com/?kbid=239107
_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email ___

Post by shuman
I have already moved to the 2003 domain. Some of the devices
are now hitting the 90 day temp license issue. I have read the
post that deals with this. I need to remove the TS licensing
from the 2000 TS server. But I have already installed the TS
licensing on the 2003 AD server. If I remove the licensing from
2000, will I need to manually point the 2000 server to the 2003
server to request the TS licenses for the devices? I would
rather not re-install the TS licensing on the AD 2003 server.
Thanks!

[Vera Noest [MVP]]

This is not going to work, because a W2K Terminal Server can not
use Per User TS CALs. Those were introduced with 2003 TS, and a W2K
TS simply doesn't recognize them.

So you must have Per Device TS CALs for clients connecting to a W2K
TS.
If you have Software Assurance on your TS CALs, then you are
allowed to switch from Per User to Per Device. You will have to
phone the Clearinghouse to get your licenses re-issued.

_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email ___

Post by shuman
Vera,
I reset the WBT to factory defaults and now I can connect to the
W2K TS. However, the LS issued a temp license to the WBT.
What am I missing here?

Post by shuman
I have 2003 TS Per User CALS on the 2003 LS. Those were added
prior to the events below.
Last night I removed the LS from the W2K server. I added the
"DefaultLicenseServer" to both of my W2K TServers, pointing to
the AD server running LS. Rebooted both servers. The two
devices that were having an issue connecting are a WBT and an
XP Pro workstation. On the XP Pro I deleted the license cache
info. The XP Pro connected, but received another temp license
due to expire in Feb 2006. The WBT still does not connect.

Post by Vera Noest [MVP]
Did you also install TS CALs on the 2003 LS? If so, which
type of TS CALs (W2K, 2003 Per User or 2003 Per Device)?
Assuming that the W2K TS is a member server in the same
domain as the 2003 DC which runs the TS Licensing Service, it
should be autodetected.
But if you previously have hardcoded the name of the old W2K
LS into the registry of the W2K TS, then you have to remove
this registry key again, to enable autodetection of the 2003
LS.
239107 - Establishing Preferred Windows 2000 Terminal
Services License Server
http://support.microsoft.com/?kbid=239107
_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email ___

Post by shuman
I have already moved to the 2003 domain. Some of the
devices are now hitting the 90 day temp license issue. I
have read the post that deals with this. I need to remove
the TS licensing from the 2000 TS server. But I have
already installed the TS licensing on the 2003 AD server.
If I remove the licensing from 2000, will I need to
manually point the 2000 server to the 2003 server to
request the TS licenses for the devices? I would rather
not re-install the TS licensing on the AD 2003 server.
Thanks!

[shuman]

Thank You Vera! I'm sure this was probably conveyed in other posts that I
had read and I just didn't put it together with my issue.

Thanks for your time.

Post by Vera Noest [MVP]
This is not going to work, because a W2K Terminal Server can not
use Per User TS CALs. Those were introduced with 2003 TS, and a W2K
TS simply doesn't recognize them.
So you must have Per Device TS CALs for clients connecting to a W2K
TS.
If you have Software Assurance on your TS CALs, then you are
allowed to switch from Per User to Per Device. You will have to
phone the Clearinghouse to get your licenses re-issued.
_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email ___

Post by shuman
Vera,
I reset the WBT to factory defaults and now I can connect to the
W2K TS. However, the LS issued a temp license to the WBT.
What am I missing here?

Post by shuman
I have 2003 TS Per User CALS on the 2003 LS. Those were added
prior to the events below.
Last night I removed the LS from the W2K server. I added the
"DefaultLicenseServer" to both of my W2K TServers, pointing to
the AD server running LS. Rebooted both servers. The two
devices that were having an issue connecting are a WBT and an
XP Pro workstation. On the XP Pro I deleted the license cache
info. The XP Pro connected, but received another temp license
due to expire in Feb 2006. The WBT still does not connect.

Post by Vera Noest [MVP]
Did you also install TS CALs on the 2003 LS? If so, which
type of TS CALs (W2K, 2003 Per User or 2003 Per Device)?
Assuming that the W2K TS is a member server in the same
domain as the 2003 DC which runs the TS Licensing Service, it
should be autodetected.
But if you previously have hardcoded the name of the old W2K
LS into the registry of the W2K TS, then you have to remove
this registry key again, to enable autodetection of the 2003
LS.
239107 - Establishing Preferred Windows 2000 Terminal
Services License Server
http://support.microsoft.com/?kbid=239107
_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email ___

Post by shuman
I have already moved to the 2003 domain. Some of the
devices are now hitting the 90 day temp license issue. I
have read the post that deals with this. I need to remove
the TS licensing from the 2000 TS server. But I have
already installed the TS licensing on the 2003 AD server.
If I remove the licensing from 2000, will I need to
manually point the 2000 server to the 2003 server to
request the TS licenses for the devices? I would rather
not re-install the TS licensing on the AD 2003 server.
Thanks!