Transition to from Win2k3 SBS to Win2k3 for Terminal Services

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance



Sorry for my lack of knowledge, I'm new to all this, especially the licensing
stuff.

We have a very small domain with one DC running Win2k3 SBS and 5 clients.
The SBS is running a program the client PCs need to work with, so the 2
remote connections in administration mode don't fit our needs anymore.

I found we have to use the Transition Pack which will enable more
connections in the full version of Windows 2003 and also includes 5 Client
CALs (do I see this right?)

Or in short: Buying the Win2k3 Transition Pack, what else would I need, if I
wanted to use remote desktop from all of the 5 clients to the server?

Thanks alot,
Stefan
.



Relevant Pages

  • Re: Transition to from Win2k3 SBS to Win2k3 for Terminal Services
    ... IMO...buying the Transition Pack is a pretty expensive answer. ... > We have a very small domain with one DC running Win2k3 SBS and 5 clients. ... > remote connections in administration mode don't fit our needs anymore. ...
    (microsoft.public.windows.server.sbs)
  • Re: Remote Desktop Connect to client wont work
    ... > You might want to check the desktop computers to see if remote connections ... >> But I can not connect to the desktop of the clients. ... used ConnectComputer and the machines work fine when ... >> Paul P ...
    (microsoft.public.windows.server.sbs)
  • Re: remote X on 5.1-RELEASE
    ... clients can connect from any host ... > is the X server actually listening to remote connections? ... Terry Todd ...
    (freebsd-questions)
  • Re: Remote Desktop Connect to client wont work
    ... You might want to check the desktop computers to see if remote connections ... > But I can not connect to the desktop of the clients. ...
    (microsoft.public.windows.server.sbs)