Re: Trouble with sbs2k in Terminal Server app mode.
- From: "Steve_S" <stephen178671no_spam@xxxxxxxxxxxxxx>
- Date: Tue, 26 Apr 2005 19:18:11 +0100
And did you set up TS licensing by any chance by default it will work for 90
days on Temp TS CALS which the Terminal server will give out, then it will
stop until you purchase some TS CALS which you will need to then install on
the terminal server.
--
HTH
Rgds
Steve_S
"br" <brianNOSPAM@xxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:uuVVJ2nSFHA.336@xxxxxxxxxxxxxxxxxxxxxxx
>I migrated an SBS 2000 server to a new SBS 2003 server. That was mostly
>smooth and easy.
>
> I then reformated the old SBS 2000 server and reinstalled the 2000 OS and
> then STOPPED before installing the SBS components.
>
> At that point I made the server a member server of the 2003 domain set up
> Terminal Services for application mode, installed my applications, set my
> policies, etc, and then let users go nuts. I did not install any licenses
> since all the clients are using XP PRO and should supposedly be issued a
> free license.
>
> This worked GREAT for a couple of months, then all of a sudden we are
> getting the can't issue a license error (The remote computer disconnected
> the session because of an error in the licensing protocol). Before you
> post that I should delete the MSLicensing key on the clients, let me say
> that that doesn't work.
>
> It's irritating because it worked for a long time, then just quit.
>
>
>
.
- Follow-Ups:
- References:
- Prev by Date: Re: Recording LogonLogoff
- Next by Date: SBS Pop3 Service and Outlook Express
- Previous by thread: Trouble with sbs2k in Terminal Server app mode.
- Next by thread: Re: Trouble with sbs2k in Terminal Server app mode.
- Index(es):
Relevant Pages
|
