windows 2000 terminal services

[Guest Ed Mcspadden]

We currently have one windows server 2000 sp4. Terminal Services is used in

administration mode w/remote desktop to check backups, etc...

 

We now have a need for a couple of users to be able to connect remotely from

their PCs at home and use goldmine and quickbooks.

 

Questions:

 

What licensing will need to be purchased?

 

If terminal services is running in application mode, will this effect the

ability to connect for administration purposes?

 

Are there any helpful how-to guides available for setup procedures?

 

Thank you for your help. I do appreciate it greatly.

[Guest Vera Noest [MVP]]

Re: windows 2000 terminal services

 

Licensing requirements:

* install and activate a TS Licensing Server, must run on a DC (no

costs involved)

* if all of your clients run W2K Pro or XP Pro or Vista Business,

you don't need to buy nor install any extra TS CALs. These clients

will receive a free TS CAL from the built-in pool of licenses on

the TS Licensing Server.

* if you have clients who run down-level OS (W9x, NT4, unix, Mac),

you need to buy and install a TS CAL for each of them.

 

Provided that you as Administrator connect from an XP Pro client,

and thus don't need a purchased TS CAL, you will be able to connect

for administrative purposes just like before.

 

Note that installing Terminal Services in Application Server mode

changes the internal tuning of the server, to give higher priority

to user sessions. That's one of the reasons that a TS should run on

a dedicated Terminal Server, and not be combined with roles like a

DC or an SQL server.

 

Also note that applications which you want to be used in a TS

session by multiple users must be installed *after* you install TS

in Application Server mode.

Before installing applications on a Terminal Server, you must put

the server into "install mode". In this mode, all changes made to

the registry and to ini-files will be monitored and copied to the

shadow area in the registry. This process ensures that all users

will receive their personal copy of those registry keys and ini-

files.

 

Quickbooks on a TS is notorious for it's need for manual

adjustments on the file system and registry permissions to make it

work. The amount of work you have to put into QB depends on the

version of QB that you are running. Older versions explicitly

forbid running QB on a TS, so check the EULA and the system

requirements for your version of QB before you make major changes.

 

Here are some links to get you on track:

 

Checklist: Install applications

http://technet2.microsoft.com/WindowsServer/en/Library/8ef377c7-

3815-4b1c-9cd5-b7950120c0c21033.mspx

 

Applications : QuickBooks

http://ts.veranoest.net/ts_apps_qb.htm

_________________________________________________________

Vera Noest

MCSE, CCEA, Microsoft MVP - Terminal Server

TS troubleshooting: http://ts.veranoest.net

___ please respond in newsgroup, NOT by private email ___

 

"Ed Mcspadden" <edmc@hotmail.com> wrote on 10 sep 2007 in

microsoft.public.windows.terminal_services:

> We currently have one windows server 2000 sp4. Terminal

> Services is used in administration mode w/remote desktop to

> check backups, etc...

>

> We now have a need for a couple of users to be able to connect

> remotely from their PCs at home and use goldmine and quickbooks.

>

> Questions:

>

> What licensing will need to be purchased?

>

> If terminal services is running in application mode, will this

> effect the ability to connect for administration purposes?

>

> Are there any helpful how-to guides available for setup

> procedures?

>

> Thank you for your help. I do appreciate it greatly.