Windows XP Terminal Server

  • Thread starter Thread starter Monty
  • Start date Start date
Re: Windows XP Terminal Server

More correctly, CAN a Windows XP Pro system be a terminal server?
 
Re: Windows XP Terminal Server

No, it's not a SERVER

"Monty" <dale.schmitz@offutt.af.mil> wrote in message
news:538eae74-8aa8-4169-9065-a075dd351d9b@s37g2000prg.googlegroups.com...
> More correctly, CAN a Windows XP Pro system be a terminal server?
 
Re: Windows XP Terminal Server

Yes it can and its legal (if you want to be sure, ask MS Business Service,
i've done this two times the last three years).
Some products are www.xpunlimited.com and www.thinsoftinc.com
For the licensing you need for each server a Windows XP Professional License
and for user/device a RDL (Remote Desktop License, only available with
Volumelicense) or for each user/device a Windows XP Professional License.

Regards,

Andreas
 
Re: Windows XP Terminal Server

We have licenses from Server 2003 we're going to convert to XP Pro.
What I don't find, however, is the procedure to start terminal
licensing or how to enter the licenses. Also, it seems by default one
person can logon remotely, but no more. Is there a way to increase
that number?

Thanks
 
Re: Windows XP Terminal Server

You can't enter any licenses on XP. But to be in compliance with the
EULA, it is enough to have the paperwork that you actually own the
licenses. The technical implementation (or lack thereof) is totally
unrelated to the legal issues.

I'm not sure how you are going to "convert" your 2003 licenses to XP
and which 3rd party product you have bought to enable XP to run more
than a single session, so I can't answer your other questions.
Native XP Pro allows for a single session, either on the physical
console, or remote. It's a desktop system, after all.
_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email ___

Monty <dale.schmitz@offutt.af.mil> wrote on 15 feb 2008 in
microsoft.public.windows.terminal_services:

> We have licenses from Server 2003 we're going to convert to XP
> Pro. What I don't find, however, is the procedure to start
> terminal licensing or how to enter the licenses. Also, it seems
> by default one person can logon remotely, but no more. Is there
> a way to increase that number?
>
> Thanks
 
Re: Windows XP Terminal Server

Actually you DID answer my question: only one remote login at a time
on XP. We didn't buy any third party software to enable more; we'll
likely buy W2K Server and set things up that way.

By 'convert' my 2003 licenses, I meant trasnfer, as I've seen done
with other software when I move it to a new platform. I've no idea
how Microsoft works things, but that's the approach I'm going to
take.

Then again, if we just go to W2K, there's probably no need to
'convert' them, I'm guessing. I'd love to just stick with W2K3 R2,
but some critical software we need isn't certified for it...such is
life.

My thanks to all!
 
Re: Windows XP Terminal Server

I would strongly advise you to check with your local Microsoft
representative if the "convert" approach to licenses which you are
planning actually exists for Microsoft OS.

I don't know which licenses exactly you mean, but assuming that you
mean 2003 TS CALs, then you can use them as they are now, issued by
a 2003 LS, when you setup a W2K TS, provided that they are Per
Device TS CALs. A W2K TS doesn't recognize and can't handle Per
User TS CALs.

_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email ___

Monty <dale.schmitz@offutt.af.mil> wrote on 16 feb 2008 in
microsoft.public.windows.terminal_services:

> Actually you DID answer my question: only one remote login at a
> time on XP. We didn't buy any third party software to enable
> more; we'll likely buy W2K Server and set things up that way.
>
> By 'convert' my 2003 licenses, I meant trasnfer, as I've seen
> done with other software when I move it to a new platform. I've
> no idea how Microsoft works things, but that's the approach I'm
> going to take.
>
> Then again, if we just go to W2K, there's probably no need to
> 'convert' them, I'm guessing. I'd love to just stick with W2K3
> R2, but some critical software we need isn't certified for
> it...such is life.
>
> My thanks to all!
 
Back
Top