Trouble with sbs2k in Terminal Server app mode.

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.

Steve_S
Tue Apr 26 13:18:11 CDT 2005

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@NOSPAMecspcsolutions.com> wrote in message
news:uuVVJ2nSFHA.336@TK2MSFTNGP09.phx.gbl...
>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.
>
>
>

Henry
Tue Apr 26 18:41:27 CDT 2005

You're in Violation of the EULA to start with as you cannot just run the
Windows 2000 portion of SBS without installing the SBServer thus making
it the Root of Forest for the Domain.

--
Henry Craven {SBS-MVP}
CI Information Technology
----------------------------------------------------
Melbourne SBS Users Group
http://groups.yahoo.com/group/melb-SBSusers/

"br" <brianNOSPAM@NOSPAMecspcsolutions.com> wrote in message
news:uuVVJ2nSFHA.336@TK2MSFTNGP09.phx.gbl...
>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.
>
>
>

br
Thu Apr 28 12:00:48 CDT 2005

So, this $1200 piece of software becomes a shiny set of coasters? That's
useful. EULA or not, we spent a lot of money on this software and server,
and we need to be able to get more use out of it.

If I make this a PDC of it's own domain, then how do I get it to be joined
to the 2003 domain in some useful way in order for the users from the 2003
domain to login to the 2000 terminal services and interact with the 2003
domain?


"Henry Craven [SBS-MVP]" <IUnknown@Dot.Nyet> wrote in message
news:%23i1h8lrSFHA.3156@TK2MSFTNGP15.phx.gbl...
> You're in Violation of the EULA to start with as you cannot just run the
> Windows 2000 portion of SBS without installing the SBServer thus making it
> the Root of Forest for the Domain.
>
> --
> Henry Craven {SBS-MVP}
> CI Information Technology
> ----------------------------------------------------
> Melbourne SBS Users Group
> http://groups.yahoo.com/group/melb-SBSusers/
>
> "br" <brianNOSPAM@NOSPAMecspcsolutions.com> wrote in message
> news:uuVVJ2nSFHA.336@TK2MSFTNGP09.phx.gbl...
>>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.
>>
>>
>>
>
>

br
Thu Apr 28 12:03:32 CDT 2005

Was I wrong to believe the advertising that said that 2000 Terminal Serivces
issues free licenses to 2K and XP Pro clients?

I don't think it's going to allow me to install TS CAL's anyway in this
configuration. Any experience with that?




"Steve_S" <stephen178671no_spam@btinternet.com> wrote in message
news:e7d74woSFHA.576@TK2MSFTNGP15.phx.gbl...
> 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@NOSPAMecspcsolutions.com> wrote in message
> news:uuVVJ2nSFHA.336@TK2MSFTNGP09.phx.gbl...
>>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.
>>
>>
>>
>
>

Steve
Thu Apr 28 15:17:56 CDT 2005

br wrote:

> Was I wrong to believe the advertising that said that 2000 Terminal
Serivces
> issues free licenses to 2K and XP Pro clients?

XP Pro includes a TS2K CAL, Win2K Pro doesn't.

But you still need to install TS Licensing anyway.

--
Steve Foster [SBS MVP]
---------------------------------------
MVPs do not work for Microsoft. Please reply only to the newsgroups.

Steve
Thu Apr 28 15:18:48 CDT 2005

br wrote:

> So, this $1200 piece of software becomes a shiny set of coasters? That's
> useful. EULA or not, we spent a lot of money on this software and server,
> and we need to be able to get more use out of it.

Did you buy the SBS2003 Version Upgrade, or did you buy a full, fresh
SBS2003?

If you bought the Version Upgrade, then your $1200 piece of software is
now subsumed into your new $600 piece of software, and you no longer have
a legal licence for SBS2000 at all.

And you got to save $900 on buying SBS2003 Premium, some of which you
could use to buy Windows Server 2003 Standard to use for your TS
Application Server.

If you didn't buy the Version Upgrade, then not?

--
Steve Foster [SBS MVP]
---------------------------------------
MVPs do not work for Microsoft. Please reply only to the newsgroups.

br
Thu Apr 28 18:22:18 CDT 2005

I bought a full new version pre-installed in the new hardware. Didn't do an
upgrade. Did a migration.

Expected to be able to use the other software for Terminal Services since
that is something it's tech specs and advertising said it can do. I'm not
trying to do anything illegal or untoward here, just trying to find a way to
continue to use the software we paid for. If it's physically impossible then
fine, we'll spend more money, but your changing the subject is not all that
helpful in finding out what needs to happen next.

I'm asking a perfectly reasonable question, and you are simply rebutting my
standing rather than engaging the issue. Please allow someone else to answer
if you aren't interested in being helpful.

Thanks.


"Steve Foster [SBS MVP]" <steve.foster@picamar.co.uk> wrote in message
news:xn0e1jrdj11itds00a@msnews.microsoft.com...
> br wrote:
>
>> So, this $1200 piece of software becomes a shiny set of coasters? That's
>> useful. EULA or not, we spent a lot of money on this software and server,
>> and we need to be able to get more use out of it.
>
> Did you buy the SBS2003 Version Upgrade, or did you buy a full, fresh
> SBS2003?
>
> If you bought the Version Upgrade, then your $1200 piece of software is
> now subsumed into your new $600 piece of software, and you no longer have
> a legal licence for SBS2000 at all.
>
> And you got to save $900 on buying SBS2003 Premium, some of which you
> could use to buy Windows Server 2003 Standard to use for your TS
> Application Server.
>
> If you didn't buy the Version Upgrade, then not?
>
> --
> Steve Foster [SBS MVP]
> ---------------------------------------
> MVPs do not work for Microsoft. Please reply only to the newsgroups.

Henry
Thu Apr 28 19:28:12 CDT 2005

Steve's question is quite legitimate, and would have been my own next
question.

Understanding whether you can legally use ( or resell ) the SBS 2K
software -at all- is important to any solution we might be able to
suggest going forward.

So, as I see it you can:
a. Sell the SBS 2K software and put the money towards a Terminal
Server to run in the SBS 2K3 Domain

-or- Depending on what you need from the Terminal Server
b. Set up the SBS 2K as a separate Domain doing Terminal Services
for LOB Apps ( disabling Exchange etc...) and have users needing TS log
onto that domain using their SBS 2K CALs.

--
Henry Craven {SBS-MVP}
CI Information Technology
----------------------------------------------------
Melbourne SBS Users Group
http://groups.yahoo.com/group/melb-SBSusers/


"br" <brianNOSPAM@NOSPAMecspcsolutions.com> wrote in message
news:eh0slkETFHA.2560@TK2MSFTNGP09.phx.gbl...
>I bought a full new version pre-installed in the new hardware. Didn't
>do an upgrade. Did a migration.
>
> Expected to be able to use the other software for Terminal Services
> since that is something it's tech specs and advertising said it can
> do. I'm not trying to do anything illegal or untoward here, just
> trying to find a way to continue to use the software we paid for. If
> it's physically impossible then fine, we'll spend more money, but your
> changing the subject is not all that helpful in finding out what needs
> to happen next.
>
> I'm asking a perfectly reasonable question, and you are simply
> rebutting my standing rather than engaging the issue. Please allow
> someone else to answer if you aren't interested in being helpful.
>
> Thanks.
>
>
> "Steve Foster [SBS MVP]" <steve.foster@picamar.co.uk> wrote in message
> news:xn0e1jrdj11itds00a@msnews.microsoft.com...
>> br wrote:
>>
>>> So, this $1200 piece of software becomes a shiny set of coasters?
>>> That's
>>> useful. EULA or not, we spent a lot of money on this software and
>>> server,
>>> and we need to be able to get more use out of it.
>>
>> Did you buy the SBS2003 Version Upgrade, or did you buy a full, fresh
>> SBS2003?
>>
>> If you bought the Version Upgrade, then your $1200 piece of software
>> is now subsumed into your new $600 piece of software, and you no
>> longer have a legal licence for SBS2000 at all.
>>
>> And you got to save $900 on buying SBS2003 Premium, some of which you
>> could use to buy Windows Server 2003 Standard to use for your TS
>> Application Server.
>>
>> If you didn't buy the Version Upgrade, then not?
>>
>> --
>> Steve Foster [SBS MVP]
>> ---------------------------------------
>> MVPs do not work for Microsoft. Please reply only to the newsgroups.
>
>

Steve
Thu Apr 28 23:00:02 CDT 2005

br wrote:

> I bought a full new version pre-installed in the new hardware. Didn't do
an
> upgrade. Did a migration.

Whether a direct upgrade or migration was done is not directly relevant to
how you purchased SBS2003. But knowing that you bought a fresh licence is
useful.

> Expected to be able to use the other software for Terminal Services since
> that is something it's tech specs and advertising said it can do. I'm not
> trying to do anything illegal or untoward here, just trying to find a
way to
> continue to use the software we paid for. If it's physically impossible
then
> fine, we'll spend more money, but your changing the subject is not all
that
> helpful in finding out what needs to happen next.

Hmmm, I'm not sure SBS2000 was ever really advertised as a TS Server. MS
have been strongly recommending against using it that way for a long time.
When fully loaded with the rest of its' SBS activities, there's not really
significant room for it to be a TS too. Not to mention the security
concerns associated with users being logged on locally to a DC. But that's
really tangential to your issue.

> I'm asking a perfectly reasonable question, and you are simply rebutting
my
> standing rather than engaging the issue. Please allow someone else to
answer
> if you aren't interested in being helpful.

I am interested in being helpful, but without knowing how you got from
SBS2000 to SBS2003 the picture was looking distinctly blurry.

There's nothing technically stopping you from simply flattening the
SBS2000 box, installing Windows Server 2000 from the SBS2000 media, and
leaving the SBS install at that point. You can make the box a member
server in the 2003 domain, and you can configure TS. Legally, it's
probably just about within the letter of the EULA, though it's not being
used as MS intended (and under most circumstances, this would be an
expensive way to get a TS server).

> > If you didn't buy the Version Upgrade, then not?

Oops, typo there - that should have read "any particular reason why not?".

--
Steve Foster [SBS MVP]
---------------------------------------
MVPs do not work for Microsoft. Please reply only to the newsgroups.

br
Mon May 02 12:58:58 CDT 2005


"Steve Foster [SBS MVP]" <steve.foster@picamar.co.uk> wrote in message
news:xn0e1kg7518o1i000@msnews.microsoft.com...
> br wrote:

>
> There's nothing technically stopping you from simply flattening the
> SBS2000 box, installing Windows Server 2000 from the SBS2000 media, and
> leaving the SBS install at that point. You can make the box a member
> server in the 2003 domain, and you can configure TS. Legally, it's
> probably just about within the letter of the EULA, though it's not being
> used as MS intended (and under most circumstances, this would be an
> expensive way to get a TS server).


Thanks. This helps. That is exactly how we have it installed. I stopped the
install before the SBS components, made it a member server, and turned on
the TS server in app mode and turned on licensing, but from day one, I was
not able to actually look at the licensing, however it worked great for
about 2 months. I would think it was the 90 day thing, except that I have
deleted those keys from the clients per the MS articles and it doesn't reset
anything. Connecting from even the domain controller doesn't work.

At this point, we will probably just buy another copy, because I have to get
it running. To that end a couple of licensing questions. Is there an upgrade
option from 2K SBS to 2K straight? The other question I'm really confused
about is the licensing for TS. Someone mentioned that even though XP is
supposed to get a free license, I still have to buy a license? I'm lost on
that one, or maybe I'm reading it wrong.

Steve
Mon May 02 13:52:37 CDT 2005

br wrote:

>
> At this point, we will probably just buy another copy, because I have to
get
> it running. To that end a couple of licensing questions. Is there an
upgrade
> option from 2K SBS to 2K straight? The other question I'm really confused
> about is the licensing for TS. Someone mentioned that even though XP is
> supposed to get a free license, I still have to buy a license? I'm lost
on
> that one, or maybe I'm reading it wrong.

No, there is no upgrade option from SBS2000 to Windows Server.

XP Pro includes a TS2000 CAL. So you don't have to buy TS CALs if you're
running a Windows 2000 Server Terminal Server, though you do still need to
setup TS Licensing. If you buy Windows Server 2003 TS, you would need to
buy TS CALs regardless, except for XP Pro machines purchased prior to
April 2003 (where MS will give you a TS CAL on application).

--
Steve Foster [SBS MVP]
---------------------------------------
MVPs do not work for Microsoft. Please reply only to the newsgroups.

Rick
Mon May 02 15:41:55 CDT 2005

BR,Steve,Henry;

I was under the impression(and I am probably wrong) that aside from
licensing issues, Using the SBS Installation to create a "member" server
would not work properly. i.e. there is some type of MS tagging in the OS
that indicates that it must be the SBS DC without domain "trusts" and other
SBS restrictions.

I know BR's question centers around licensing, however, even if he/she can
determine and obbtain proper licensing, I am not certain the system will
function fully and properly.

Certainly the SBS components(Exchange,IIS,ISA et.al) are NOT permitted to be
loaded separately.

just my $0.02

RickD

"br" <brianNOSPAM@NOSPAMecspcsolutions.com> wrote in message
news:#QnmOD0TFHA.2680@tk2msftngp13.phx.gbl...
>
> "Steve Foster [SBS MVP]" <steve.foster@picamar.co.uk> wrote in message
> news:xn0e1kg7518o1i000@msnews.microsoft.com...
> > br wrote:
>
> >
> > There's nothing technically stopping you from simply flattening the
> > SBS2000 box, installing Windows Server 2000 from the SBS2000 media, and
> > leaving the SBS install at that point. You can make the box a member
> > server in the 2003 domain, and you can configure TS. Legally, it's
> > probably just about within the letter of the EULA, though it's not being
> > used as MS intended (and under most circumstances, this would be an
> > expensive way to get a TS server).
>
>
> Thanks. This helps. That is exactly how we have it installed. I stopped
the
> install before the SBS components, made it a member server, and turned on
> the TS server in app mode and turned on licensing, but from day one, I was
> not able to actually look at the licensing, however it worked great for
> about 2 months. I would think it was the 90 day thing, except that I have
> deleted those keys from the clients per the MS articles and it doesn't
reset
> anything. Connecting from even the domain controller doesn't work.
>
> At this point, we will probably just buy another copy, because I have to
get
> it running. To that end a couple of licensing questions. Is there an
upgrade
> option from 2K SBS to 2K straight? The other question I'm really confused
> about is the licensing for TS. Someone mentioned that even though XP is
> supposed to get a free license, I still have to buy a license? I'm lost on
> that one, or maybe I'm reading it wrong.
>
>
>
>
>

br
Tue May 03 14:34:44 CDT 2005

On a kind of a side note. What is the effect of truning on TS Licensing in
the SBS 2003 server? I wanted to try a little experiment, but don't want to
lose access to that server. Would we still be able to use our 2
administrator sessions like we can now if licensing were turned on? Once on,
can it be turned off with no ill effects?
"br" <brianNOSPAM@NOSPAMecspcsolutions.com> wrote in message
news:%23QnmOD0TFHA.2680@tk2msftngp13.phx.gbl...
>
> "Steve Foster [SBS MVP]" <steve.foster@picamar.co.uk> wrote in message
> news:xn0e1kg7518o1i000@msnews.microsoft.com...
>> br wrote:
>
>>
>> There's nothing technically stopping you from simply flattening the
>> SBS2000 box, installing Windows Server 2000 from the SBS2000 media, and
>> leaving the SBS install at that point. You can make the box a member
>> server in the 2003 domain, and you can configure TS. Legally, it's
>> probably just about within the letter of the EULA, though it's not being
>> used as MS intended (and under most circumstances, this would be an
>> expensive way to get a TS server).
>
>
> Thanks. This helps. That is exactly how we have it installed. I stopped
> the install before the SBS components, made it a member server, and turned
> on the TS server in app mode and turned on licensing, but from day one, I
> was not able to actually look at the licensing, however it worked great
> for about 2 months. I would think it was the 90 day thing, except that I
> have deleted those keys from the clients per the MS articles and it
> doesn't reset anything. Connecting from even the domain controller doesn't
> work.
>
> At this point, we will probably just buy another copy, because I have to
> get it running. To that end a couple of licensing questions. Is there an
> upgrade option from 2K SBS to 2K straight? The other question I'm really
> confused about is the licensing for TS. Someone mentioned that even though
> XP is supposed to get a free license, I still have to buy a license? I'm
> lost on that one, or maybe I'm reading it wrong.
>
>
>
>
>

Steve
Tue May 03 17:05:58 CDT 2005

br wrote:

> On a kind of a side note. What is the effect of truning on TS Licensing
in
> the SBS 2003 server? I wanted to try a little experiment, but don't want
to
> lose access to that server. Would we still be able to use our 2
> administrator sessions like we can now if licensing were turned on? Once
on,
> can it be turned off with no ill effects?

TS Licensing has no effect on the SBS.


--
Steve Foster [SBS MVP]
---------------------------------------
MVPs do not work for Microsoft. Please reply only to the newsgroups.

br
Mon May 09 17:17:43 CDT 2005

Thanks to all for the various info. Especially the info that turning on
licensing server in 2k3 sbs will not hurt anything.

I did that, and the licensing server is now issuing Term Server 2000
temporary licenses for the sbs2k box. Working great. Will have to see what
happens in three months when the temp licenses expire. Hopefully that will
just require running a registry script on the clients every few months.



"br" <brianNOSPAM@NOSPAMecspcsolutions.com> wrote in message
news:uuVVJ2nSFHA.336@TK2MSFTNGP09.phx.gbl...
>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.
>
>
>