Terminal server 2000 and XP client licensing

[takman_777]

I have just taken over a 25 node network that is set up with Windows 2000
SBS, and Windows 2000 Terminal Server on 2 boxes. the main server runs the
applications needed for the local group, and the Terminal server facilitates
remote users who access the same program and data structure set up as a
terminal service via vpn connections. they have a firewall set to administer
dhcp address to the remote hosts.

my question is this, i have noticed that the Terminal Server is set to run
in Remote Administration mode, yet it was set up in Application Server mode
almost 2 years ago when it was set up. my understanding is this... in RA
mode, the server should not be requiring TS Licenses, yet i have a laptop
that has an expiring temp license while the license sits on the server
waiting to be distributed.

the sessions are created on WinXp machines and either way, they should have
Terminal Server licensing built in as part of the O/S. Any ideas as to why
this is or how to correct it as i have read nothing that has helped me thus
far.

thanks in advance for the assistance and the much needed guidence on this
issue.

they are close to refresh and upgrade of both the server and the client
machines... i would hate to think that will solve the issue!!

cheers
--
We, like all Windows products, need a gentle massage now and then.

 

[Jeff Pitsch]

Re: Terminal server 2000 and XP client licensing

How many users can connect at one time? if the server is in remote
admin mode, then no more than 2 should be able to connect. it's
entirely possible that this has always been how it's been setup.

If you want to put back into application mode, you'll need to go through
add/remove programs, windows components and adjust it to application mode.

Jeff Pitsch
Microsoft MVP - Terminal Services

takman_777 wrote:
> I have just taken over a 25 node network that is set up with Windows 2000
> SBS, and Windows 2000 Terminal Server on 2 boxes. the main server runs the
> applications needed for the local group, and the Terminal server facilitates
> remote users who access the same program and data structure set up as a
> terminal service via vpn connections. they have a firewall set to administer
> dhcp address to the remote hosts.
>
> my question is this, i have noticed that the Terminal Server is set to run
> in Remote Administration mode, yet it was set up in Application Server mode
> almost 2 years ago when it was set up. my understanding is this... in RA
> mode, the server should not be requiring TS Licenses, yet i have a laptop
> that has an expiring temp license while the license sits on the server
> waiting to be distributed.
>
> the sessions are created on WinXp machines and either way, they should have
> Terminal Server licensing built in as part of the O/S. Any ideas as to why
> this is or how to correct it as i have read nothing that has helped me thus
> far.
>
> thanks in advance for the assistance and the much needed guidence on this
> issue.
>
> they are close to refresh and upgrade of both the server and the client
> machines... i would hate to think that will solve the issue!!
>
> cheers

 

[takman_777]

Re: Terminal server 2000 and XP client licensing

right now, it SHOULD be set in application mode and no one can explain to me
why it is Remote Administration mode!!! there are generally 3 or 4
connections at a time which is why i am perplexed!!

the main question i have is does the terminal server recognize the sessions
that are created as being from a win2000 terminal server or the xp pro o/s
they are connecting with!? why are the xp machines even being asked for a
license as they are already a part of the O/S???

i suspect some corruption has taken place as the fellow looking after this
before me had very little experience or knowledge of what to do and was very
good at just turning things on and off randomly hoping to kick something the
right way!

i am not against the re-establishment of the Application Mode, but i am
concerned that the xp machines are being required to have a licence at all.
temporary licenses should not be needed on a machine that is running xp on a
2k term server! is there something in the rdp session that is requiring this?
has this missed a patch or upgrade to recognize the xp client?

as always, i await the reply! thank you!
--
We, like all Windows products, need a gentle massage now and then.


"Jeff Pitsch" wrote:

> How many users can connect at one time? if the server is in remote
> admin mode, then no more than 2 should be able to connect. it's
> entirely possible that this has always been how it's been setup.
>
> If you want to put back into application mode, you'll need to go through
> add/remove programs, windows components and adjust it to application mode.
>
> Jeff Pitsch
> Microsoft MVP - Terminal Services
>
> takman_777 wrote:
> > I have just taken over a 25 node network that is set up with Windows 2000
> > SBS, and Windows 2000 Terminal Server on 2 boxes. the main server runs the
> > applications needed for the local group, and the Terminal server facilitates
> > remote users who access the same program and data structure set up as a
> > terminal service via vpn connections. they have a firewall set to administer
> > dhcp address to the remote hosts.
> >
> > my question is this, i have noticed that the Terminal Server is set to run
> > in Remote Administration mode, yet it was set up in Application Server mode
> > almost 2 years ago when it was set up. my understanding is this... in RA
> > mode, the server should not be requiring TS Licenses, yet i have a laptop
> > that has an expiring temp license while the license sits on the server
> > waiting to be distributed.
> >
> > the sessions are created on WinXp machines and either way, they should have
> > Terminal Server licensing built in as part of the O/S. Any ideas as to why
> > this is or how to correct it as i have read nothing that has helped me thus
> > far.
> >
> > thanks in advance for the assistance and the much needed guidence on this
> > issue.
> >
> > they are close to refresh and upgrade of both the server and the client
> > machines... i would hate to think that will solve the issue!!
> >
> > cheers
>

 

[Jeff Pitsch]

Re: Terminal server 2000 and XP client licensing

The licenses are not part of the OS. The licensing mechanism still
happens. A temp is handed out initially and then a perm. The perm
expires every 52-89 days and then is renewed at that time. this does
not change because you are running Win2k terminal services.

Hopefully that makes sense.

Jeff Pitsch
Microsoft MVP - Terminal Services

takman_777 wrote:
> right now, it SHOULD be set in application mode and no one can explain to me
> why it is Remote Administration mode!!! there are generally 3 or 4
> connections at a time which is why i am perplexed!!
>
> the main question i have is does the terminal server recognize the sessions
> that are created as being from a win2000 terminal server or the xp pro o/s
> they are connecting with!? why are the xp machines even being asked for a
> license as they are already a part of the O/S???
>
> i suspect some corruption has taken place as the fellow looking after this
> before me had very little experience or knowledge of what to do and was very
> good at just turning things on and off randomly hoping to kick something the
> right way!
>
> i am not against the re-establishment of the Application Mode, but i am
> concerned that the xp machines are being required to have a licence at all.
> temporary licenses should not be needed on a machine that is running xp on a
> 2k term server! is there something in the rdp session that is requiring this?
> has this missed a patch or upgrade to recognize the xp client?
>
> as always, i await the reply! thank you!

 

[takman_777]

Re: Terminal server 2000 and XP client licensing

well, the laptop that was getting the message about the temporary license was
refused access to the term serv via vpn. there is a license on the term
server waiting to be distributed as i thought it would be done automatically
as suggested.

any more ideas? as i have stated, the server is in remote management mode
and should not even be asking for licensing in the first place.

i have thought about upgrading the server to win2003 sbs as an aside as the
machine is on the backside of the hardware maintenance schedule.

any more thoughts are very much welcomed as i a beginning to think this
issue is not resolvable in the current setup.
--
We, like all Windows products, need a gentle massage now and then.


"Jeff Pitsch" wrote:

> The licenses are not part of the OS. The licensing mechanism still
> happens. A temp is handed out initially and then a perm. The perm
> expires every 52-89 days and then is renewed at that time. this does
> not change because you are running Win2k terminal services.
>
> Hopefully that makes sense.
>
> Jeff Pitsch
> Microsoft MVP - Terminal Services
>
> takman_777 wrote:
> > right now, it SHOULD be set in application mode and no one can explain to me
> > why it is Remote Administration mode!!! there are generally 3 or 4
> > connections at a time which is why i am perplexed!!
> >
> > the main question i have is does the terminal server recognize the sessions
> > that are created as being from a win2000 terminal server or the xp pro o/s
> > they are connecting with!? why are the xp machines even being asked for a
> > license as they are already a part of the O/S???
> >
> > i suspect some corruption has taken place as the fellow looking after this
> > before me had very little experience or knowledge of what to do and was very
> > good at just turning things on and off randomly hoping to kick something the
> > right way!
> >
> > i am not against the re-establishment of the Application Mode, but i am
> > concerned that the xp machines are being required to have a licence at all.
> > temporary licenses should not be needed on a machine that is running xp on a
> > 2k term server! is there something in the rdp session that is requiring this?
> > has this missed a patch or upgrade to recognize the xp client?
> >
> > as always, i await the reply! thank you!
>

 

[Jeff Pitsch]

Re: Terminal server 2000 and XP client licensing

Check the MSLicensing key in the registry to make sure that users have
full permissions. this was an issue a while back and you may be
experiencing it.

Jeff Pitsch
Microsoft MVP - Terminal Services

takman_777 wrote:
> well, the laptop that was getting the message about the temporary license was
> refused access to the term serv via vpn. there is a license on the term
> server waiting to be distributed as i thought it would be done automatically
> as suggested.
>
> any more ideas? as i have stated, the server is in remote management mode
> and should not even be asking for licensing in the first place.
>
> i have thought about upgrading the server to win2003 sbs as an aside as the
> machine is on the backside of the hardware maintenance schedule.
>
> any more thoughts are very much welcomed as i a beginning to think this
> issue is not resolvable in the current setup.

 

[takman_777]

Re: Terminal server 2000 and XP client licensing

Jeff

thank you for your reply, but i suspect the issue is much deeper!

when my client tried to connect today, she received the following:

"the remote computer disconnected the session because of and error in teh
licensing protocol. Please try connecting to the remote computer again or
contact your server admin."

i tried to verify the service is running and it was. what i did notice is
that when i logged on to the Terminal server itself, it shows it is running
in Application Server mode, but when i connect to the applet in the MMC on
the main server, the service is set to Remote Administration.

they have had this issue before, and the solution was to wipe and reload the
laptop! UGH! so it was not dealt with at the time. i am suspecting the
win2000 sbs server and terminal server are both in need of reinstallation as
they are constantly crashing and the antivirus is often not started after a
reboot. as of last friday there were no virus'.

any other ideas would be appreciated very much.
--
We, like all Windows products, need a gentle massage now and then.


"Jeff Pitsch" wrote:

> Check the MSLicensing key in the registry to make sure that users have
> full permissions. this was an issue a while back and you may be
> experiencing it.
>
> Jeff Pitsch
> Microsoft MVP - Terminal Services
>
> takman_777 wrote:
> > well, the laptop that was getting the message about the temporary license was
> > refused access to the term serv via vpn. there is a license on the term
> > server waiting to be distributed as i thought it would be done automatically
> > as suggested.
> >
> > any more ideas? as i have stated, the server is in remote management mode
> > and should not even be asking for licensing in the first place.
> >
> > i have thought about upgrading the server to win2003 sbs as an aside as the
> > machine is on the backside of the hardware maintenance schedule.
> >
> > any more thoughts are very much welcomed as i a beginning to think this
> > issue is not resolvable in the current setup.
>

 

[Jeff Pitsch]

Re: Terminal server 2000 and XP client licensing

Did you check the key? Have you tried simply deleting the user profile?

Jeff Pitsch
Microsoft MVP - Terminal Services

takman_777 wrote:
> Jeff
>
> thank you for your reply, but i suspect the issue is much deeper!
>
> when my client tried to connect today, she received the following:
>
> "the remote computer disconnected the session because of and error in teh
> licensing protocol. Please try connecting to the remote computer again or
> contact your server admin."
>
> i tried to verify the service is running and it was. what i did notice is
> that when i logged on to the Terminal server itself, it shows it is running
> in Application Server mode, but when i connect to the applet in the MMC on
> the main server, the service is set to Remote Administration.
>
> they have had this issue before, and the solution was to wipe and reload the
> laptop! UGH! so it was not dealt with at the time. i am suspecting the
> win2000 sbs server and terminal server are both in need of reinstallation as
> they are constantly crashing and the antivirus is often not started after a
> reboot. as of last friday there were no virus'.
>
> any other ideas would be appreciated very much.