I'm experiencing a problem I can't seem to find the answer too, - I'm hoping that someone might have seen similar or can maybe offer a spark of brilliance that will point me in the right direction!?
We recently upgraded our Domain Controllers from Windows 2000 to Windows 2003.
We used a "swing" method, - which basically means we "swung" the FSMO roles and AD over to a temporary box, - upgraded our DC's with a "fresh" build, - and "swung" AD & the FSMO roles back to the fresh builds. This all worked very well, and AD etc is working perfectly, plus we are left with a nice new fresh build.
Unfortunately, we made a silly oversight, - the Terminal Server License Server was running on one of these boxes (which has now of course been completely scrapped). I have re-installed TSLS and have the temporary built-in Windows 2000 licenses at the moment which I am soon to Activate properly (the clients which use TSLS are Windows 2000).
Although the TSLS component is now installed, the clients are not picking it up, - the ones in application mode are taking about 10 mins to log in ("Loading your personal settings..").
Eventvwr is telling me the following:
Event ID 213 - Replication of license information failed because the License Logging Service on server (DCSERVER) could not be contacted.
Event ID 1000
Windows cannot determine the user of computer name Return value 1753
I have hard coded a "Default License Server" via the registry on one of the clients following this article - this has seemed to resolve the "Event ID 213" messages, however, I was still experiencing extremely slow log-in, and only two concurrent connections.
I implemented this "solution" from Microsoft but there was no change in behaviour.
Starting the Licensing Logging Service on the server doesnt make any difference, and from what I gather shouldnt need to be started anyway.
I have searched high and low but cannot seem to find anything.
Any thoughts? Any help much appreciated!?
Cheers
We recently upgraded our Domain Controllers from Windows 2000 to Windows 2003.
We used a "swing" method, - which basically means we "swung" the FSMO roles and AD over to a temporary box, - upgraded our DC's with a "fresh" build, - and "swung" AD & the FSMO roles back to the fresh builds. This all worked very well, and AD etc is working perfectly, plus we are left with a nice new fresh build.
Unfortunately, we made a silly oversight, - the Terminal Server License Server was running on one of these boxes (which has now of course been completely scrapped). I have re-installed TSLS and have the temporary built-in Windows 2000 licenses at the moment which I am soon to Activate properly (the clients which use TSLS are Windows 2000).
Although the TSLS component is now installed, the clients are not picking it up, - the ones in application mode are taking about 10 mins to log in ("Loading your personal settings..").
Eventvwr is telling me the following:
Event ID 213 - Replication of license information failed because the License Logging Service on server (DCSERVER) could not be contacted.
Event ID 1000
Windows cannot determine the user of computer name Return value 1753
I have hard coded a "Default License Server" via the registry on one of the clients following this article - this has seemed to resolve the "Event ID 213" messages, however, I was still experiencing extremely slow log-in, and only two concurrent connections.
I implemented this "solution" from Microsoft but there was no change in behaviour.
Starting the Licensing Logging Service on the server doesnt make any difference, and from what I gather shouldnt need to be started anyway.
I have searched high and low but cannot seem to find anything.
Any thoughts? Any help much appreciated!?
Cheers
