Re: Terminal Service provided an invalid license
- From: "Vera Noest [MVP]" <vera.noest@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Tue, 09 Oct 2007 12:55:06 -0700
I don't think that you have to require new licenses, and I don't
even think that it would solve the problem, at least not as the
only step.
Try deleting the locally stored license from the clients. It's
stored in:
HKEY_LOCAL_MACHINE\Software\Microsoft\MSLicensing
On a thin client, you might have to reset the client to the factory
defaults to get rid of the locally stored license.
If this solves the problem, you won't have to require new licenses.
But you would need to reset all thin clients in a disaster recovery
situation. For fat clients, you could write a logon script which
deletes the license. You would need to built in some intelligence
in the script, so that it only deletes the license the first time
the client logs on to your restored TS.
All clients will then grab a new temporary license at first logon
and try to change that into a permanent license the second time
they logon. You probably don't have enough permanent licenses
available on the restored LS in such a situation, but it will give
you 90 days to fix the original problem with your server and switch
back from your disaster recovery servers to your normal production
servers. At at point, you would probably face the same problem
again, and that would be the time to require new licenses from the
Clearinghouse.
Requiring and installing new licenses from the Clearinghouse in
your disaster recovery situation cannot affect the production
environment, assuming that you have made sure that the production
Terminal Servers cannot use the restored LS as a Licensing Server.
_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email ___
=?Utf-8?B?RGF2ZQ==?= <Dave@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote on 09
okt 2007 in microsoft.public.windows.terminal_services:
I deleted the certificates from the TS license server with no.
luck. The same error is logged. I even tried deleting the
certificates from the TS itself also with no success. If I
contact the MS Clearinghouse to reactivate the licenses on the
disaster recovery server would that affect the licenses on the
production network?
thanks
Dave
"Dave" wrote:
Vera, thank you for the response. I will try that asap post the
results.
"Vera Noest [MVP]" wrote:
This usually means that some certificates on the TS Licensing
Server are corrupt (maybe because of a time stamp issue
following the restore of the image?).
If that's the case, the solution is simply to delete the
certificates from the server:
http://support.microsoft.com/?kbid=323597
_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email ___
=?Utf-8?B?RGF2ZQ==?= <Dave@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote
on 05 okt 2007 in microsoft.public.windows.terminal_services:
We have run into a problem with Terminal Services during
our testing of our disaster recovery plan. We are using a
server imaging product Acronis True Image Server to image
our 2003DC, 2000 Terminal Server (Citrix XPe) and a 2000DC.
We then have restored those images to our disaster center
recovery servers. All appeared fine until we tried to login
to the Terminal server via a thin client. We are unable to
connect and the Terminal server event log shows error 1003
"terminal services provided an invalid license". I would
think that since the imaging is a block by block image of
the production server that all data including licenses
would be transfered to the recovery server when the image
is restored. However this error does seem to be a license
issue. Any suggestions. Thanks
- References:
- Re: Terminal Service provided an invalid license
- From: Vera Noest [MVP]
- Re: Terminal Service provided an invalid license
- Prev by Date: Re: HP 1015 laser doesn't show up in list of printers when remotely connected
- Next by Date: Re: Auto login on a per-user basis
- Previous by thread: Re: Terminal Service provided an invalid license
- Next by thread: Virtual Channels with C#
- Index(es):
Relevant Pages
|
