Home | Site Map | Cisco How ToNet How To | Windows Vista | Case Studies | Forums | Services | Donations | Careers | About Us | Contact Us|

 

Terminal services 0703

Re: strange performance issues

Re: Stop and Start Terminal Services

Re: sql on TS

Re: Solution for slow link??

RE: Slow RDP from Vista to 2k3 SP2 R2 x64

Re: Shared Printer Not Showing in TS

Re: Set macro security

Re: Roaming Profile Directories are not deleted

Re: Remote desktop Web Connection

Re: Remote Desktop (2003 Server) stops working, bounces initial connection attempt

Re: RDP shows blue screen for 2 to 5 minutes before icons come up.

Re: RDP local drives missing

Re: RDP Compression

Re: RDP and Vista

Re: RDP 6.0.6000 changes user login info

 

 

From: Brian MXP <brian@nospam.broad.mit.edu>

To: none

Subject: Re: strange performance issues

Date: 09/27/2007 12:01:05

 

 

BW-

 

Another problem I ran into was the TCP Offload Engine that is being shipped on most Dells

being enabled - we had asynchronous network problems as well as general performance

problems that was a PITA to track down...

 

Did removing Adobe 8 help you out at all?

 

BM

 

Vera Noest [MVP] wrote:

> I've seen quite a few posts here lately complaining about

> performance issues with Acrobat Reader 8.

> That would be my first suspect.

> _________________________________________________________

> Vera Noest

> MCSE, CCEA, Microsoft MVP - Terminal Server

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

> *----------- Please reply in newsgroup -------------*

>

> =?Utf-8?B?Qlc=?= wrote on 20 aug

> 2007:

>

>> hi there,

>>

>> we are running a win2k3 sp1 terminal server with the usual apps

>> on it - MS office, acrobat reader, etc. it is a dual cpu xeon

>> with 4gb ram and we regularly have 40-45 users online

>> concurrently.

>>

>> however today the server began to run *very* slow to the point

>> of unuable even from admin console however the strange part was

>> that the cpu and ram were being reported as hardly used (10-30%

>> CPU and ~2gb ram free). a restart resolved issue but only for

>> an hour or so. restarted again and now has been working better

>> for about 2 hours, but every now and then it's like it freezes

>> for 10-20 seconds then carries on ok.

>>

>> only thing i have done is install acrobat reader 8.1 and

>> uninstalled iis (was just a default install and had not been

>> used). has anyone seen such a drop in performance for no

>> apparent reason?

>>

>> thanks.

 

 

 

Top


 

 

 

From: Munindra Das [MSFT] <munind@online.microsoft.com>

To: none

Subject: Re: strange performance issues

Date: 09/29/2007 17:17:21

 

 

Is the machine slowing down or is it slow only inside a TS session? Did you

collect any performance data on the machine?

 

--

This posting is provided "AS IS" with no warranties, and confers no rights.

"Brian MXP" wrote in message

news:%23TusCgSAIHA.320@TK2MSFTNGP04.phx.gbl...

> BW-

>

> Another problem I ran into was the TCP Offload Engine that is being

> shipped on most Dells being enabled - we had asynchronous network problems

> as well as general performance problems that was a PITA to track down...

>

> Did removing Adobe 8 help you out at all?

>

> BM

>

> Vera Noest [MVP] wrote:

>> I've seen quite a few posts here lately complaining about performance

>> issues with Acrobat Reader 8.

>> That would be my first suspect.

>> _________________________________________________________

>> Vera Noest

>> MCSE, CCEA, Microsoft MVP - Terminal Server

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

>> *----------- Please reply in newsgroup -------------*

>>

>> =?Utf-8?B?Qlc=?= wrote on 20 aug

>> 2007:

>>> hi there,

>>>

>>> we are running a win2k3 sp1 terminal server with the usual apps

>>> on it - MS office, acrobat reader, etc. it is a dual cpu xeon

>>> with 4gb ram and we regularly have 40-45 users online

>>> concurrently.

>>> however today the server began to run *very* slow to the point

>>> of unuable even from admin console however the strange part was

>>> that the cpu and ram were being reported as hardly used (10-30%

>>> CPU and ~2gb ram free). a restart resolved issue but only for

>>> an hour or so. restarted again and now has been working better

>>> for about 2 hours, but every now and then it's like it freezes for 10-20

>>> seconds then carries on ok.

>>>

>>> only thing i have done is install acrobat reader 8.1 and

>>> uninstalled iis (was just a default install and had not been

>>> used). has anyone seen such a drop in performance for no

>>> apparent reason?

>>> thanks.

 

 

 

Top


 

 

 

From: TP <tperson.knowspamn@mailandnews.com>

To: none

Subject: Re: Stop and Start Terminal Services

Date: 09/20/2007 09:05:15

 

 

No.

 

-TP

 

Noah wrote:

> I have a x64 2003 sp2 server that is not responding to Terminal

> Services Admin connections. I have been trying to restart the

> terminal services. They are grayed out and when i use a net stop

> command i get errors. Any way to stop and restart these services

> without a reboot?

>

> Thanks

 

 

 

Top


 

 

 

From: Noah <noah@carpathiahost.com>

To: none

Subject: Re: Stop and Start Terminal Services

Date: 09/20/2007 10:12:00

 

 

So a reboot is the only fix for this problem?

 

 

 

TP wrote:

> No.

>

> -TP

>

> Noah wrote:

>> I have a x64 2003 sp2 server that is not responding to Terminal

>> Services Admin connections. I have been trying to restart the

>> terminal services. They are grayed out and when i use a net stop

>> command i get errors. Any way to stop and restart these services

>> without a reboot?

>> Thanks

 

 

 

Top


 

 

 

From: Vera Noest [MVP] <vera.noest@remove-this.hem.utfors.se>

To: none

Subject: Re: Stop and Start Terminal Services

Date: 09/20/2007 14:26:34

 

 

Yes.

But before you do that I'd check some things.

Is the server listening on port 3389? Check with "netstat -an" in

a command window on the console.

Can you establish an rdp session

to the server from the console of the server itself?

Are there any

warnings or errors in the EventLog?

 

_________________________________________________________

Vera Noest

MCSE, CCEA, Microsoft MVP - Terminal Server

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

___ please respond in newsgroup, NOT by private email ___

 

Noah wrote on 20 sep 2007 in

microsoft.public.windows.terminal_services:

 

> So a reboot is the only fix for this problem?

>

>

>

> TP wrote:

>> No.

>>

>> -TP

>>

>> Noah wrote:

>>> I have a x64 2003 sp2 server that is not responding to

>>> Terminal Services Admin connections. I have been trying to

>>> restart the terminal services. They are grayed out and when i

>>> use a net stop command i get errors. Any way to stop and

>>> restart these services without a reboot?

>>> Thanks

 

 

 

Top


 

 

 

From: paulc <paulc@mmcwm.com>

To: none

Subject: Re: Stop and Start Terminal Services

Date: 09/20/2007 14:51:45

 

 

Well, if you know the service name to get the PID, you can use PSKILL (get

it here:

http://www.microsoft.com/technet/sysinternals/Processesandthreadsutilities.mspx?wt.svl=featured).

Works great if you need to kill a process on a server that for some reason

you can't or don't want to reboot.

 

 

"Vera Noest [MVP]" wrote in message

news:Xns99B1DA2065BDAveranoesthemutforsse@207.46.248.16...

> Yes.

> But before you do that I'd check some things.

> Is the server listening on port 3389? Check with "netstat -an" in

> a command window on the console.

> Can you establish an rdp session

> to the server from the console of the server itself?

> Are there any

> warnings or errors in the EventLog?

>

> _________________________________________________________

> Vera Noest

> MCSE, CCEA, Microsoft MVP - Terminal Server

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

> ___ please respond in newsgroup, NOT by private email ___

>

> Noah wrote on 20 sep 2007 in

> microsoft.public.windows.terminal_services:

>

>> So a reboot is the only fix for this problem?

>>

>>

>>

>> TP wrote:

>>> No.

>>>

>>> -TP

>>>

>>> Noah wrote:

>>>> I have a x64 2003 sp2 server that is not responding to

>>>> Terminal Services Admin connections. I have been trying to

>>>> restart the terminal services. They are grayed out and when i

>>>> use a net stop command i get errors. Any way to stop and

>>>> restart these services without a reboot?

>>>> Thanks

 

 

 

Top


 

 

 

From: Vera Noest [MVP] <vera.noest@remove-this.hem.utfors.se>

To: none

Subject: Re: Stop and Start Terminal Services

Date: 09/20/2007 15:40:30

 

 

The Terminal Services service is an integrated part of the core OS,

that's why it can't be stopped or restarted as most other services.

 

I would *not* recommend killing it. Chances are that you can't

restart it and that you put your server in an unstable state.

 

278657 - Terminal Services Cannot Be Manipulated

http://support.microsoft.com/?kbid=278657

_________________________________________________________

Vera Noest

MCSE, CCEA, Microsoft MVP - Terminal Server

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

___ please respond in newsgroup, NOT by private email ___

 

"paulc" wrote on 20 sep 2007 in

microsoft.public.windows.terminal_services:

 

> Well, if you know the service name to get the PID, you can use

> PSKILL (get it here:

> http://www.microsoft.com/technet/sysinternals/Processesandthreads

> utilities.mspx?wt.svl=featured). Works great if you need to kill

> a process on a server that for some reason you can't or don't

> want to reboot.

>

>

> "Vera Noest [MVP]" wrote

> in message

> news:Xns99B1DA2065BDAveranoesthemutforsse@207.46.248.16...

>> Yes.

>> But before you do that I'd check some things.

>> Is the server listening on port 3389? Check with "netstat -an"

>> in a command window on the console.

>> Can you establish an rdp session

>> to the server from the console of the server itself?

>> Are there any

>> warnings or errors in the EventLog?

>>

>> _________________________________________________________

>> Vera Noest

>> MCSE, CCEA, Microsoft MVP - Terminal Server

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

>> ___ please respond in newsgroup, NOT by private email ___

>>

>> Noah wrote on 20 sep 2007 in

>> microsoft.public.windows.terminal_services:

>>

>>> So a reboot is the only fix for this problem?

>>>

>>>

>>>

>>> TP wrote:

>>>> No.

>>>>

>>>> -TP

>>>>

>>>> Noah wrote:

>>>>> I have a x64 2003 sp2 server that is not responding to

>>>>> Terminal Services Admin connections. I have been trying to

>>>>> restart the terminal services. They are grayed out and when

>>>>> i use a net stop command i get errors. Any way to stop and

>>>>> restart these services without a reboot?

>>>>> Thanks

 

 

 

Top


 

 

 

From: paulc <paulc@mmcwm.com>

To: none

Subject: Re: Stop and Start Terminal Services

Date: 09/24/2007 08:48:02

 

 

Oops. Thanks, Vera. I stand corrected. (and very happy I've never

'pskilled' a TS service. :) )

"Vera Noest [MVP]" wrote in message

news:Xns99B1E6AB96267veranoesthemutforsse@207.46.248.16...

> The Terminal Services service is an integrated part of the core OS,

> that's why it can't be stopped or restarted as most other services.

>

> I would *not* recommend killing it. Chances are that you can't

> restart it and that you put your server in an unstable state.

>

> 278657 - Terminal Services Cannot Be Manipulated

> http://support.microsoft.com/?kbid=278657

> _________________________________________________________

> Vera Noest

> MCSE, CCEA, Microsoft MVP - Terminal Server

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

> ___ please respond in newsgroup, NOT by private email ___

>

> "paulc" wrote on 20 sep 2007 in

> microsoft.public.windows.terminal_services:

>

>> Well, if you know the service name to get the PID, you can use

>> PSKILL (get it here:

>> http://www.microsoft.com/technet/sysinternals/Processesandthreads

>> utilities.mspx?wt.svl=featured). Works great if you need to kill

>> a process on a server that for some reason you can't or don't

>> want to reboot.

>>

>>

>> "Vera Noest [MVP]" wrote

>> in message

>> news:Xns99B1DA2065BDAveranoesthemutforsse@207.46.248.16...

>>> Yes.

>>> But before you do that I'd check some things.

>>> Is the server listening on port 3389? Check with "netstat -an"

>>> in a command window on the console.

>>> Can you establish an rdp session

>>> to the server from the console of the server itself?

>>> Are there any

>>> warnings or errors in the EventLog?

>>>

>>> _________________________________________________________

>>> Vera Noest

>>> MCSE, CCEA, Microsoft MVP - Terminal Server

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

>>> ___ please respond in newsgroup, NOT by private email ___

>>>

>>> Noah wrote on 20 sep 2007 in

>>> microsoft.public.windows.terminal_services:

>>>

>>>> So a reboot is the only fix for this problem?

>>>>

>>>>

>>>>

>>>> TP wrote:

>>>>> No.

>>>>>

>>>>> -TP

>>>>>

>>>>> Noah wrote:

>>>>>> I have a x64 2003 sp2 server that is not responding to

>>>>>> Terminal Services Admin connections. I have been trying to

>>>>>> restart the terminal services. They are grayed out and when

>>>>>> i use a net stop command i get errors. Any way to stop and

>>>>>> restart these services without a reboot?

>>>>>> Thanks

 

 

 

Top


 

 

 

From: Noah <noah@carpathiahost.com>

To: none

Subject: Re: Stop and Start Terminal Services

Date: 09/24/2007 09:41:10

 

 

Thanks for the help guys. I was just a little confused as to WHY you

could not stop and start the services. As it is a reboot fixed the issue

and the system is running just fine. Thank you for all the help and the

informative links.

 

 

 

paulc wrote:

> Oops. Thanks, Vera. I stand corrected. (and very happy I've never

> 'pskilled' a TS service. :) )

> "Vera Noest [MVP]" wrote in message

> news:Xns99B1E6AB96267veranoesthemutforsse@207.46.248.16...

>> The Terminal Services service is an integrated part of the core OS,

>> that's why it can't be stopped or restarted as most other services.

>>

>> I would *not* recommend killing it. Chances are that you can't

>> restart it and that you put your server in an unstable state.

>>

>> 278657 - Terminal Services Cannot Be Manipulated

>> http://support.microsoft.com/?kbid=278657

>> _________________________________________________________

>> Vera Noest

>> MCSE, CCEA, Microsoft MVP - Terminal Server

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

>> ___ please respond in newsgroup, NOT by private email ___

>>

>> "paulc" wrote on 20 sep 2007 in

>> microsoft.public.windows.terminal_services:

>>

>>> Well, if you know the service name to get the PID, you can use

>>> PSKILL (get it here:

>>> http://www.microsoft.com/technet/sysinternals/Processesandthreads

>>> utilities.mspx?wt.svl=featured). Works great if you need to kill

>>> a process on a server that for some reason you can't or don't

>>> want to reboot.

>>>

>>>

>>> "Vera Noest [MVP]" wrote

>>> in message

>>> news:Xns99B1DA2065BDAveranoesthemutforsse@207.46.248.16...

>>>> Yes.

>>>> But before you do that I'd check some things.

>>>> Is the server listening on port 3389? Check with "netstat -an"

>>>> in a command window on the console.

>>>> Can you establish an rdp session

>>>> to the server from the console of the server itself?

>>>> Are there any

>>>> warnings or errors in the EventLog?

>>>>

>>>> _________________________________________________________

>>>> Vera Noest

>>>> MCSE, CCEA, Microsoft MVP - Terminal Server

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

>>>> ___ please respond in newsgroup, NOT by private email ___

>>>>

>>>> Noah wrote on 20 sep 2007 in

>>>> microsoft.public.windows.terminal_services:

>>>>

>>>>> So a reboot is the only fix for this problem?

>>>>>

>>>>>

>>>>>

>>>>> TP wrote:

>>>>>> No.

>>>>>>

>>>>>> -TP

>>>>>>

>>>>>> Noah wrote:

>>>>>>> I have a x64 2003 sp2 server that is not responding to

>>>>>>> Terminal Services Admin connections. I have been trying to

>>>>>>> restart the terminal services. They are grayed out and when

>>>>>>> i use a net stop command i get errors. Any way to stop and

>>>>>>> restart these services without a reboot?

>>>>>>> Thanks

>

>

 

 

 

Top


 

 

 

From: TP <tperson.knowspamn@mailandnews.com>

To: none

Subject: Re: Stop and Start Terminal Services

Date: 09/21/2007 10:15:35

 

 

I agree with Vera's comments.

 

I would add that this situation occurs sometimes when the

server is restarted for some reason (for example, an update),

but the restart fails. TS is disabled during the shutdown

process but is not re-enabled when it is aborted.

 

The result is a server that appears to be functioning fine,

you can access its files remotely, use IIS, etc., but not

connect to it via RDP.

 

-TP

 

Noah wrote:

> So a reboot is the only fix for this problem?

>

 

 

 

Top


 

 

 

From: Lanwench [MVP - Exchange] <lanwench@heybuddy.donotsendme.unsolicitedmailatyahoo.com>

To: none

Subject: Re: sql on TS

Date: 09/22/2007 10:24:53

 

 

Jez wrote:

> any pitfalls on running an SQL db on a terminal server?

> want to run MSTS with ms office and then sql client and sql db

> ?

 

Ideally, your terminal server shouldn't do anything else on the network -

shouldn't be a DC, a SQL server, file server, or anything. Just a big fat

shared workstation. This is for reasons of security as well as resource

load.

 

 

 

Top


 

 

 

From: Jez <Jez@discussions.microsoft.com>

To: none

Subject: Re: sql on TS

Date: 09/23/2007 00:56:00

 

 

not planning to make it a DC or a file server. Space and cost confinements

have bought me here!

 

"Lanwench [MVP - Exchange]" wrote:

 

> Jez wrote:

> > any pitfalls on running an SQL db on a terminal server?

> > want to run MSTS with ms office and then sql client and sql db

> > ?

>

> Ideally, your terminal server shouldn't do anything else on the network -

> shouldn't be a DC, a SQL server, file server, or anything. Just a big fat

> shared workstation. This is for reasons of security as well as resource

> load.

>

>

>

 

 

 

Top


 

 

 

From: Hank Arnold (MVP) <rasilon@aol.com>

To: none

Subject: Re: sql on TS

Date: 09/23/2007 05:54:10

 

 

Jez wrote:

> any pitfalls on running an SQL db on a terminal server?

> want to run MSTS with ms office and then sql client and sql db

> ?

 

Security ?

good idea....

 

--

 

Regards,

Hank Arnold

Microsoft MVP

Windows Server - Directory Services

 

 

 

Top


 

 

 

From: Soo Kuan Teo [MSFT] <sookuant@online.microsoft.com>

To: none

Subject: Re: sql on TS

Date: 09/23/2007 09:44:54

 

 

Sql server can co-exists with TS on the same box. Like Lanwench and Hank

Arnold suggested, if you start seeing performance issues when many users

accessing both at the same time, it may not be a bad idea to separate them.

Thanks

Soo Kuan

 

 

--

This posting is provided "AS IS" with no warranties, and confers no rights.

 

"Jez" wrote in message

news:473DF3DC-D012-43D4-92BA-A35C6D3FF2AE@microsoft.com...

> any pitfalls on running an SQL db on a terminal server?

> want to run MSTS with ms office and then sql client and sql db

> ?

 

 

 

Top


 

 

 

From: Helge Klein <Helge.Klein@googlemail.com>

To: none

Subject: Re: Solution for slow link??

Date: 09/23/2007 16:28:39

 

 

Yes, using terminal services could be a viable solution to your

problems. Prior to implementing a solution you need, however, to

understand it's implications. I recommend you read Brian Madden's

freely available book on terminal services to make up your mind:

 

http://brianmadden.com/Book/Terminal-Services-for-Microsoft-Windows-Server-2003-Advanced-Technical-Design-Guide

 

Several companies offer add-ons that greatly enhance the functionality

of the core MS terminal services. The best-known is Citrix, but there

are others, too. I recommend you have a look at what the market has to

offer. Brian's site may be a good source:

 

http://brianmadden.com

 

I hope this helps.

 

Helge

 

==================

Please visit my blog:

http://it-from-inside.blogspot.com

==================

 

On 23 Sep., 22:50, pete0085

wrote:

> This is more of a general question. We are a small organization with 3

> different locations and many users move between locations on a daily basis.

>

> The other 2 branches are connected via a T1 link. We use roaming profiles

> and often the logon time can be 5-10 minutes if not more. Accessing

> resources over the network can be very slow to the point the program stops

> responding for a few seconds.

>

> I really don't know anything about termincal services. I use remote desktop

> to connect to the server or another pc sometimes, but don't understand enough

> of how it works for a user to log on.

>

> We need to use roaming profiles since users log on to different pcs all the

> time. Would terminal services or terminal server be a better solution than

> connecting to resources over a T1 and if so, how does that even work, how

> would you set it up, etc.

>

> Like I said I understand remote desktop since I use it to connect to another

> pc, but how does this work for a user who wants to log on to the network like

> they normall would??

>

> Sorry for all the questions, I just don't understand this very well and need

> some advice.

 

 

 

 

Top


 

 

 

From: pete0085 <pete0085@discussions.microsoft.com>

To: none

Subject: Re: Solution for slow link??

Date: 09/24/2007 15:22:01

 

 

Thanks, that is very helpful.

 

Do you know why terminal services takes up less bandwidth then accessing all

services over a regular WAN line?

 

"Helge Klein" wrote:

 

> Yes, using terminal services could be a viable solution to your

> problems. Prior to implementing a solution you need, however, to

> understand it's implications. I recommend you read Brian Madden's

> freely available book on terminal services to make up your mind:

>

> http://brianmadden.com/Book/Terminal-Services-for-Microsoft-Windows-Server-2003-Advanced-Technical-Design-Guide

>

> Several companies offer add-ons that greatly enhance the functionality

> of the core MS terminal services. The best-known is Citrix, but there

> are others, too. I recommend you have a look at what the market has to

> offer. Brian's site may be a good source:

>

> http://brianmadden.com

>

> I hope this helps.

>

> Helge

>

> ==================

> Please visit my blog:

> http://it-from-inside.blogspot.com

> ==================

>

> On 23 Sep., 22:50, pete0085

> wrote:

> > This is more of a general question. We are a small organization with 3

> > different locations and many users move between locations on a daily basis.

> >

> > The other 2 branches are connected via a T1 link. We use roaming profiles

> > and often the logon time can be 5-10 minutes if not more. Accessing

> > resources over the network can be very slow to the point the program stops

> > responding for a few seconds.

> >

> > I really don't know anything about termincal services. I use remote desktop

> > to connect to the server or another pc sometimes, but don't understand enough

> > of how it works for a user to log on.

> >

> > We need to use roaming profiles since users log on to different pcs all the

> > time. Would terminal services or terminal server be a better solution than

> > connecting to resources over a T1 and if so, how does that even work, how

> > would you set it up, etc.

> >

> > Like I said I understand remote desktop since I use it to connect to another

> > pc, but how does this work for a user who wants to log on to the network like

> > they normall would??

> >

> > Sorry for all the questions, I just don't understand this very well and need

> > some advice.

>

>

>

 

 

 

Top


 

 

 

From: BrettB <BrettB@discussions.microsoft.com>

To: none

Subject: RE: Slow RDP from Vista to 2k3 SP2 R2 x64

Date: 09/28/2007 16:18:01

 

 

I'm having the same issue connecting to a freshly installed Windows Server

2003 R2 (32 bit) server after installing SP2 from microsofts site. I've

reinstalled a second time, and the issues pops up immediately after the SP2

install.

 

When connecting from a vista worksation to the server via RDP, mouse clicks

take about 5 seconds to run on the server. The keyboard functionality

however responds like you'd expect. So I can click something, wait 5

seconds, then click somewhere else. It's very annoying.

 

Connecting to the same server from XP or another W2k3 box works fine.

 

I have other W2k3 boxes with SP2, but all of them we're originally installed

with SP1, then upgraded to SP2. They work fine.

 

Please help!

 

"Brian" wrote:

 

> I have a Windows Vista desktop. I RDP into many servers 2000, 2003 x32 and

> x64. I have one server 2003 SP2 R2 Enterprise Edition x64 build

> 3790.srv03_sp2_rtm.070216-1710, when I or anyone RDP's into this server from

> a Vista computer the session is very slow. The screen refreshes fine, but a

> mouse click takes several seconds to reatct.

>

> I've found that if I run a "netsh interface tcp set global

> autotuninglevel=disabled" command on my Vista box the RDP session works fine.

> RDP from XP is also fine.

>

> I don't know why this is the only server I'm having problems with. I have

> one other 2003 SP2 R2 Enterprise x64 server and its build number is

> 3790.srv03_sp2_gdr.070321-2337.

>

> Does anyone know what the different build numbers mean. It seems like the

> problem server has an old build number??? Is there a way to upgrade to a

> newer build?

>

 

 

 

Top


 

 

 

From: BrettB <BrettB@discussions.microsoft.com>

To: none

Subject: RE: Slow RDP from Vista to 2k3 SP2 R2 x64

Date: 09/28/2007 16:25:00

 

 

For what its worth, setting the autotuninglevel=disabled command fixed it for

me. Are there any downsides to having that turned off?

 

"BrettB" wrote:

 

> I'm having the same issue connecting to a freshly installed Windows Server

> 2003 R2 (32 bit) server after installing SP2 from microsofts site. I've

> reinstalled a second time, and the issues pops up immediately after the SP2

> install.

>

> When connecting from a vista worksation to the server via RDP, mouse clicks

> take about 5 seconds to run on the server. The keyboard functionality

> however responds like you'd expect. So I can click something, wait 5

> seconds, then click somewhere else. It's very annoying.

>

> Connecting to the same server from XP or another W2k3 box works fine.

>

> I have other W2k3 boxes with SP2, but all of them we're originally installed

> with SP1, then upgraded to SP2. They work fine.

>

> Please help!

>

> "Brian" wrote:

>

> > I have a Windows Vista desktop. I RDP into many servers 2000, 2003 x32 and

> > x64. I have one server 2003 SP2 R2 Enterprise Edition x64 build

> > 3790.srv03_sp2_rtm.070216-1710, when I or anyone RDP's into this server from

> > a Vista computer the session is very slow. The screen refreshes fine, but a

> > mouse click takes several seconds to reatct.

> >

> > I've found that if I run a "netsh interface tcp set global

> > autotuninglevel=disabled" command on my Vista box the RDP session works fine.

> > RDP from XP is also fine.

> >

> > I don't know why this is the only server I'm having problems with. I have

> > one other 2003 SP2 R2 Enterprise x64 server and its build number is

> > 3790.srv03_sp2_gdr.070321-2337.

> >

> > Does anyone know what the different build numbers mean. It seems like the

> > problem server has an old build number??? Is there a way to upgrade to a

> > newer build?

> >

 

 

 

Top


 

 

 

From: moncho <moncho@NOspmanywhere.com>

To: none

Subject: Re: Shared Printer Not Showing in TS

Date: 09/25/2007 09:46:21

 

 

moncho wrote:

> I am sharing a USB DYMO 330 Turbo Label printer on a W2K Server.

>

> I added the shared printer to our W2K3 TS server but it will only

> show in the "Printers and Faxes" for administrators only.

>

> I have no idea why it will not show up for my non-admin

> users.

>

> I have setup a few local TCP/IP printers and had no problem.

>

> When I look at the port (under admin account) of the printer

> on the TS server, instead of showing \\server\sharedprintername

> it is showing USB001 instead. Could this be a problem?

>

 

Update.

 

It seems I had to add Domain Users to the Security Tab

on the printer in the W2K server. Apparently the Everyone

group was not doing the job.

 

I do have to add the printer for each individual TS user

in W2K3 though. That I do not understand.

 

moncho

 

 

 

Top


 

 

 

From: Jeff Pitsch <Jeff@Jeffpitschconsulting.com>

To: none

Subject: Re: Set macro security

Date: 09/27/2007 10:50:35

 

 

Is there possibly a gpo that is setting macro security?

 

Jeff Pitsch

Microsoft MVP - Terminal Server

Citrix Technology Professional

Provision Networks VIP

 

Forums not enough?

Get support from the experts at your business

http://jeffpitschconsulting.com

 

mikee wrote:

> We have a terminal server 2003 running office 2003. We set the macro

> security in word to medium, but after logging out it goes back to high. How

> do we get it to stay at medium? This is happening for all users. My

> administrator account gets the same result.

>

> Thanks in advance

 

 

 

Top


 

 

 

From: mikee <mikee@discussions.microsoft.com>

To: none

Subject: Re: Set macro security

Date: 09/27/2007 11:40:04

 

 

There are no group policies in place for the terminal servers. Any other ideas?

 

"Jeff Pitsch" wrote:

 

> Is there possibly a gpo that is setting macro security?

>

> Jeff Pitsch

> Microsoft MVP - Terminal Server

> Citrix Technology Professional

> Provision Networks VIP

>

> Forums not enough?

> Get support from the experts at your business

> http://jeffpitschconsulting.com

>

> mikee wrote:

> > We have a terminal server 2003 running office 2003. We set the macro

> > security in word to medium, but after logging out it goes back to high. How

> > do we get it to stay at medium? This is happening for all users. My

> > administrator account gets the same result.

> >

> > Thanks in advance

>

 

 

 

Top


 

 

 

From: Soo Kuan Teo [MSFT] <sookuant@online.microsoft.com>

To: none

Subject: Re: Set macro security

Date: 09/30/2007 11:32:58

 

 

Have you tried using the Custom Installation Wizard (CIW)?

Please check out the following links for more info:

http://office.microsoft.com/en-us/ork2003/HA011403071033.aspx

http://www.microsoft.com/technet/prodtechnol/office/office2003/operate/o3secdet.mspx#EZEAE

 

Thanks

Soo Kuan

 

 

 

--

This posting is provided "AS IS" with no warranties, and confers no rights.

 

"mikee" wrote in message

news:FAD47308-9CE7-4C54-91FB-A38E27ECFAFE@microsoft.com...

> There are no group policies in place for the terminal servers. Any other

> ideas?

>

> "Jeff Pitsch" wrote:

>

>> Is there possibly a gpo that is setting macro security?

>>

>> Jeff Pitsch

>> Microsoft MVP - Terminal Server

>> Citrix Technology Professional

>> Provision Networks VIP

>>

>> Forums not enough?

>> Get support from the experts at your business

>> http://jeffpitschconsulting.com

>>

>> mikee wrote:

>> > We have a terminal server 2003 running office 2003. We set the macro

>> > security in word to medium, but after logging out it goes back to high.

>> > How

>> > do we get it to stay at medium? This is happening for all users. My

>> > administrator account gets the same result.

>> >

>> > Thanks in advance

>>

 

 

 

Top


 

 

 

From: Munindra Das [MSFT] <munind@online.microsoft.com>

To: none

Subject: Re: server requirement

Date: 09/25/2007 12:56:33

 

 

The article at

http://technet2.microsoft.com/windowsserver/en/library/cb201937-8f68-4d0f-9521-99e090ddd6b11033.mspx?mfr=true

will provide you with some details on how to plan a terminal server. But it

will also depend on what Windows (2000, 2003) you are running and what

applications the users are likely to run. For a 2003 Terminal Server with 12

users, you will require a minimum of 128 MB memory.

 

I am not sure what you mean by "Could it be an another application server or

does it have to be a deditcated server". You can please provide a little

more detail.

 

--

This posting is provided "AS IS" with no warranties, and confers no rights.

"pete0085" wrote in message

news:1E25A8B3-6BF5-4A33-B8B1-9615384FDCCD@microsoft.com...

> Brief question about server requirement for a single terminal server.

>

> There would be a max of 12 users accessing the server at one time. With

> disk space not being an issue, what would be a recommendation for memory

> for

> such a server?

>

> Could it be an another application server or does it have to be a

> deditcated

> server?

>

> Can someone briefly explain why accessing resources through a terminal

> server doesn't take up as much bandwidth and is faster then accessing it

> over

> a Wan link?

 

 

 

Top


 

 

 

From: pete0085 <pete0085@discussions.microsoft.com>

To: none

Subject: Re: server requirement

Date: 09/25/2007 14:00:04

 

 

I mean does it have to be a deticated server or could I host it an another

server that acts as an application server for one of our programs or what is

typically recommended for a small environment where it will not be heavily

used.

 

Also, how does the server know you are not logging on remotely as you would

with remote desktop? Lets say a regular user wants to logon to the terminal

server, how does it figure out they are not trying to logon to the server to

perform maintenance on the server, etc.

 

That has confused me a bit. I'm guessing users use the remote desktop

connection to connect to the terminal server. I just want to ensure they are

logging on to their terminal session and not actually logging on to the

server itself. Does this make any sense with what I'm trying to say???

 

"Munindra Das [MSFT]" wrote:

 

> The article at

> http://technet2.microsoft.com/windowsserver/en/library/cb201937-8f68-4d0f-9521-99e090ddd6b11033.mspx?mfr=true

> will provide you with some details on how to plan a terminal server. But it

> will also depend on what Windows (2000, 2003) you are running and what

> applications the users are likely to run. For a 2003 Terminal Server with 12

> users, you will require a minimum of 128 MB memory.

>

> I am not sure what you mean by "Could it be an another application server or

> does it have to be a deditcated server". You can please provide a little

> more detail.

>

> --

> This posting is provided "AS IS" with no warranties, and confers no rights.

> "pete0085" wrote in message

> news:1E25A8B3-6BF5-4A33-B8B1-9615384FDCCD@microsoft.com...

> > Brief question about server requirement for a single terminal server.

> >

> > There would be a max of 12 users accessing the server at one time. With

> > disk space not being an issue, what would be a recommendation for memory

> > for

> > such a server?

> >

> > Could it be an another application server or does it have to be a

> > deditcated

> > server?

> >

> > Can someone briefly explain why accessing resources through a terminal

> > server doesn't take up as much bandwidth and is faster then accessing it

> > over

> > a Wan link?

>

>

 

 

 

Top


 

 

 

From: Vera Noest [MVP] <vera.noest@remove-this.hem.utfors.se>

To: none

Subject: Re: server requirement

Date: 09/25/2007 14:45:37

 

 

When users log on to the Terminal Server with the Remote Desktop

client, they *are* logging on remotely to the server itself!

There's really no difference between Remote Desktop connections (to

a server which is configured for "Remote Desktop for

Administration") and Terminal Server connections (to a server which

is configured for "Terminal Services, i.e. in application mode).

 

And the server has no way of knowing why someone logs on or what

they are going to do on the server, that's why *all* connections to

a server configured for terminal Services need a license. The only

exception is a single connection to the console of the server (with

mstsc /console), which is always free of TS CAL requirements.

 

Ideally, a Terminal Server should be a dedicated server, both for

performance and security reasons. But in small environments, this

isn't always realistic. So you can also use the same server as a

file server, but don't run TS on a Domain Controller, and don't

combine it with SQL or Exchange if you can avoid it.

_________________________________________________________

Vera Noest

MCSE, CCEA, Microsoft MVP - Terminal Server

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

___ please respond in newsgroup, NOT by private email ___

 

=?Utf-8?B?cGV0ZTAwODU=?=

wrote on 25 sep 2007 in

microsoft.public.windows.terminal_services:

 

> I mean does it have to be a deticated server or could I host it

> an another server that acts as an application server for one of

> our programs or what is typically recommended for a small

> environment where it will not be heavily used.

>

> Also, how does the server know you are not logging on remotely

> as you would with remote desktop? Lets say a regular user wants

> to logon to the terminal server, how does it figure out they are

> not trying to logon to the server to perform maintenance on the

> server, etc.

>

> That has confused me a bit. I'm guessing users use the remote

> desktop connection to connect to the terminal server. I just

> want to ensure they are logging on to their terminal session and

> not actually logging on to the server itself. Does this make

> any sense with what I'm trying to say???

>

> "Munindra Das [MSFT]" wrote:

>

>> The article at

>> http://technet2.microsoft.com/windowsserver/en/library/cb201937-

>> 8f68-4d0f-9521-99e090ddd6b11033.mspx?mfr=true will provide you

>> with some details on how to plan a terminal server. But it will

>> also depend on what Windows (2000, 2003) you are running and

>> what applications the users are likely to run. For a 2003

>> Terminal Server with 12 users, you will require a minimum of

>> 128 MB memory.

>>

>> I am not sure what you mean by "Could it be an another

>> application server or does it have to be a deditcated server".

>> You can please provide a little more detail.

>>

>> --

>> This posting is provided "AS IS" with no warranties, and

>> confers no rights. "pete0085"

>> wrote in message

>> news:1E25A8B3-6BF5-4A33-B8B1-9615384FDCCD@microsoft.com...

>> > Brief question about server requirement for a single terminal

>> > server.

>> >

>> > There would be a max of 12 users accessing the server at one

>> > time. With disk space not being an issue, what would be a

>> > recommendation for memory for

>> > such a server?

>> >

>> > Could it be an another application server or does it have to

>> > be a deditcated

>> > server?

>> >

>> > Can someone briefly explain why accessing resources through a

>> > terminal server doesn't take up as much bandwidth and is

>> > faster then accessing it over

>> > a Wan link?

 

 

 

Top


 

 

 

From: pete0085 <pete0085@discussions.microsoft.com>

To: none

Subject: Re: server requirement

Date: 09/25/2007 15:12:01

 

 

I would like to be able to test this. I remember reading something about

allowing you a 180 day trial before you purchase a license. How would that

work in this scennario where I or a couple users could try it out and see if

it would be a proper solution.

 

Someone else is giving me advice that the profile path for TS should not be

the same as the roaming profiles. How would a user logon or how would the

desktop follow the user if they aren't using the regular roaming profile. I

admit I'm confused about this among other things.

 

I've been reading an online book by brain madden that goes into detail about

the design, but isn't as helpful for an admin trying to setup a TS server.

 

A good link, article would be helpful.

"Vera Noest [MVP]" wrote:

 

> When users log on to the Terminal Server with the Remote Desktop

> client, they *are* logging on remotely to the server itself!

> There's really no difference between Remote Desktop connections (to

> a server which is configured for "Remote Desktop for

> Administration") and Terminal Server connections (to a server which

> is configured for "Terminal Services, i.e. in application mode).

>

> And the server has no way of knowing why someone logs on or what

> they are going to do on the server, that's why *all* connections to

> a server configured for terminal Services need a license. The only

> exception is a single connection to the console of the server (with

> mstsc /console), which is always free of TS CAL requirements.

>

> Ideally, a Terminal Server should be a dedicated server, both for

> performance and security reasons. But in small environments, this

> isn't always realistic. So you can also use the same server as a

> file server, but don't run TS on a Domain Controller, and don't

> combine it with SQL or Exchange if you can avoid it.

> _________________________________________________________

> Vera Noest

> MCSE, CCEA, Microsoft MVP - Terminal Server

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

> ___ please respond in newsgroup, NOT by private email ___

>

> =?Utf-8?B?cGV0ZTAwODU=?=

> wrote on 25 sep 2007 in

> microsoft.public.windows.terminal_services:

>

> > I mean does it have to be a deticated server or could I host it

> > an another server that acts as an application server for one of

> > our programs or what is typically recommended for a small

> > environment where it will not be heavily used.

> >

> > Also, how does the server know you are not logging on remotely

> > as you would with remote desktop? Lets say a regular user wants

> > to logon to the terminal server, how does it figure out they are

> > not trying to logon to the server to perform maintenance on the

> > server, etc.

> >

> > That has confused me a bit. I'm guessing users use the remote

> > desktop connection to connect to the terminal server. I just

> > want to ensure they are logging on to their terminal session and

> > not actually logging on to the server itself. Does this make

> > any sense with what I'm trying to say???

> >

> > "Munindra Das [MSFT]" wrote:

> >

> >> The article at

> >> http://technet2.microsoft.com/windowsserver/en/library/cb201937-

> >> 8f68-4d0f-9521-99e090ddd6b11033.mspx?mfr=true will provide you

> >> with some details on how to plan a terminal server. But it will

> >> also depend on what Windows (2000, 2003) you are running and

> >> what applications the users are likely to run. For a 2003

> >> Terminal Server with 12 users, you will require a minimum of

> >> 128 MB memory.

> >>

> >> I am not sure what you mean by "Could it be an another

> >> application server or does it have to be a deditcated server".

> >> You can please provide a little more detail.

> >>

> >> --

> >> This posting is provided "AS IS" with no warranties, and

> >> confers no rights. "pete0085"

> >> wrote in message

> >> news:1E25A8B3-6BF5-4A33-B8B1-9615384FDCCD@microsoft.com...

> >> > Brief question about server requirement for a single terminal

> >> > server.

> >> >

> >> > There would be a max of 12 users accessing the server at one

> >> > time. With disk space not being an issue, what would be a

> >> > recommendation for memory for

> >> > such a server?

> >> >

> >> > Could it be an another application server or does it have to

> >> > be a deditcated

> >> > server?

> >> >

> >> > Can someone briefly explain why accessing resources through a

> >> > terminal server doesn't take up as much bandwidth and is

> >> > faster then accessing it over

> >> > a Wan link?

>

 

 

 

Top


 

 

 

From: Vera Noest [MVP] <Vera.Noest@remove-this.hem.utfors.se>

To: none

Subject: Re: server requirement

Date: 09/25/2007 16:22:58

 

 

Yes, there is a grace period of 120 days, in which you can test and

use the Terminal Server, without the need to install TS licenses.

Just install Terminal Services, in Control Panel - Add/Remove

programs - Add Windows components.

 

And yes, users should have a TS profile which is different from

there normal profile. If you use the same profile for their

workstation and their TS sessions, a lot of settings will not work,

and the profiles will become corrupt over time.

These TS-specific profiles can be local to the Terminal Server, or

they can be roamin. Just store them on a different share on your

file server.

 

There is really not one single link which explains it all. That's

why there are numerous *books* written on the subject.

 

You can find a number of links to articles about planning,

installation, etc on my website. Or read Brian Madden's book again

:-) and then install TS on a test server and play around with it.

_________________________________________________________

Vera Noest

MCSE, CCEA, Microsoft MVP - Terminal Server

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

*----------- Please reply in newsgroup -------------*

 

=?Utf-8?B?cGV0ZTAwODU=?=

wrote on 25 sep 2007:

 

> I would like to be able to test this. I remember reading

> something about allowing you a 180 day trial before you purchase

> a license. How would that work in this scennario where I or a

> couple users could try it out and see if it would be a proper

> solution.

>

> Someone else is giving me advice that the profile path for TS

> should not be the same as the roaming profiles. How would a

> user logon or how would the desktop follow the user if they

> aren't using the regular roaming profile. I admit I'm confused

> about this among other things.

>

> I've been reading an online book by brain madden that goes into

> detail about the design, but isn't as helpful for an admin

> trying to setup a TS server.

>

> A good link, article would be helpful.

> "Vera Noest [MVP]" wrote:

>

>> When users log on to the Terminal Server with the Remote

>> Desktop client, they *are* logging on remotely to the server

>> itself! There's really no difference between Remote Desktop

>> connections (to a server which is configured for "Remote

>> Desktop for Administration") and Terminal Server connections

>> (to a server which is configured for "Terminal Services, i.e.

>> in application mode).

>>

>> And the server has no way of knowing why someone logs on or

>> what they are going to do on the server, that's why *all*

>> connections to a server configured for terminal Services need a

>> license. The only exception is a single connection to the

>> console of the server (with mstsc /console), which is always

>> free of TS CAL requirements.

>>

>> Ideally, a Terminal Server should be a dedicated server, both

>> for performance and security reasons. But in small

>> environments, this isn't always realistic. So you can also use

>> the same server as a file server, but don't run TS on a Domain

>> Controller, and don't combine it with SQL or Exchange if you

>> can avoid it.

>> _________________________________________________________ Vera

>> Noest MCSE, CCEA, Microsoft MVP - Terminal Server

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

>> ___ please respond in newsgroup, NOT by private email ___

>>

>> =?Utf-8?B?cGV0ZTAwODU=?=

>> wrote on 25 sep 2007 in

>> microsoft.public.windows.terminal_services:

>>

>> > I mean does it have to be a deticated server or could I host

>> > it an another server that acts as an application server for

>> > one of our programs or what is typically recommended for a

>> > small environment where it will not be heavily used.

>> >

>> > Also, how does the server know you are not logging on

>> > remotely as you would with remote desktop? Lets say a

>> > regular user wants to logon to the terminal server, how does

>> > it figure out they are not trying to logon to the server to

>> > perform maintenance on the server, etc.

>> >

>> > That has confused me a bit. I'm guessing users use the

>> > remote desktop connection to connect to the terminal server.

>> > I just want to ensure they are logging on to their terminal

>> > session and not actually logging on to the server itself.

>> > Does this make any sense with what I'm trying to say???

>> >

>> > "Munindra Das [MSFT]" wrote:

>> >

>> >> The article at

>> >> http://technet2.microsoft.com/windowsserver/en/library/cb2019

>> >> 37- 8f68-4d0f-9521-99e090ddd6b11033.mspx?mfr=true will

>> >> provide you with some details on how to plan a terminal

>> >> server. But it will also depend on what Windows (2000, 2003)

>> >> you are running and what applications the users are likely

>> >> to run. For a 2003 Terminal Server with 12 users, you will

>> >> require a minimum of 128 MB memory.

>> >>

>> >> I am not sure what you mean by "Could it be an another

>> >> application server or does it have to be a deditcated

>> >> server". You can please provide a little more detail.

>> >>

>> >> --

>> >> This posting is provided "AS IS" with no warranties, and

>> >> confers no rights. "pete0085"

>> >> wrote in message

>> >> news:1E25A8B3-6BF5-4A33-B8B1-9615384FDCCD@microsoft.com...

>> >> > Brief question about server requirement for a single

>> >> > terminal server.

>> >> >

>> >> > There would be a max of 12 users accessing the server at

>> >> > one time. With disk space not being an issue, what would

>> >> > be a recommendation for memory for

>> >> > such a server?

>> >> >

>> >> > Could it be an another application server or does it have

>> >> > to be a deditcated

>> >> > server?

>> >> >

>> >> > Can someone briefly explain why accessing resources

>> >> > through a terminal server doesn't take up as much

>> >> > bandwidth and is faster then accessing it over

>> >> > a Wan link?

 

 

 

Top


 

 

 

From: pete0085 <pete0085@discussions.microsoft.com>

To: none

Subject: Re: server requirement

Date: 09/25/2007 16:44:05

 

 

As for the TS profile path. Can it contain all the same files and folders as

the regular roaming profile, but have a different path? Will this cause a

problem. For ex if my profile path is \\server\profiles$\username. Then

have a path of \\server\tsprofiles$\username but include all the same files.

 

Think that helped with one question. I do want to test it first before

buying any licenses to see how it would work in our environment. As long as

it's a terminal server, it won't log me on to the console session of the

server, but instead a session inside the terminal server manager as long as I

buy licenses before the 120 days.

 

I can also install applications as I would on the client workstation and

they will be accessible without me doing anything else to it, correct?

"Vera Noest [MVP]" wrote:

 

> Yes, there is a grace period of 120 days, in which you can test and

> use the Terminal Server, without the need to install TS licenses.

> Just install Terminal Services, in Control Panel - Add/Remove

> programs - Add Windows components.

>

> And yes, users should have a TS profile which is different from

> there normal profile. If you use the same profile for their

> workstation and their TS sessions, a lot of settings will not work,

> and the profiles will become corrupt over time.

> These TS-specific profiles can be local to the Terminal Server, or

> they can be roamin. Just store them on a different share on your

> file server.

>

> There is really not one single link which explains it all. That's

> why there are numerous *books* written on the subject.

>

> You can find a number of links to articles about planning,

> installation, etc on my website. Or read Brian Madden's book again

> :-) and then install TS on a test server and play around with it.

> _________________________________________________________

> Vera Noest

> MCSE, CCEA, Microsoft MVP - Terminal Server

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

> *----------- Please reply in newsgroup -------------*

>

> =?Utf-8?B?cGV0ZTAwODU=?=

> wrote on 25 sep 2007:

>

> > I would like to be able to test this. I remember reading

> > something about allowing you a 180 day trial before you purchase

> > a license. How would that work in this scennario where I or a

> > couple users could try it out and see if it would be a proper

> > solution.

> >

> > Someone else is giving me advice that the profile path for TS

> > should not be the same as the roaming profiles. How would a

> > user logon or how would the desktop follow the user if they

> > aren't using the regular roaming profile. I admit I'm confused

> > about this among other things.

> >

> > I've been reading an online book by brain madden that goes into

> > detail about the design, but isn't as helpful for an admin

> > trying to setup a TS server.

> >

> > A good link, article would be helpful.

> > "Vera Noest [MVP]" wrote:

> >

> >> When users log on to the Terminal Server with the Remote

> >> Desktop client, they *are* logging on remotely to the server

> >> itself! There's really no difference between Remote Desktop

> >> connections (to a server which is configured for "Remote

> >> Desktop for Administration") and Terminal Server connections

> >> (to a server which is configured for "Terminal Services, i.e.

> >> in application mode).

> >>

> >> And the server has no way of knowing why someone logs on or

> >> what they are going to do on the server, that's why *all*

> >> connections to a server configured for terminal Services need a

> >> license. The only exception is a single connection to the

> >> console of the server (with mstsc /console), which is always

> >> free of TS CAL requirements.

> >>

> >> Ideally, a Terminal Server should be a dedicated server, both

> >> for performance and security reasons. But in small

> >> environments, this isn't always realistic. So you can also use

> >> the same server as a file server, but don't run TS on a Domain

> >> Controller, and don't combine it with SQL or Exchange if you

> >> can avoid it.

> >> _________________________________________________________ Vera

> >> Noest MCSE, CCEA, Microsoft MVP - Terminal Server

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

> >> ___ please respond in newsgroup, NOT by private email ___

> >>

> >> =?Utf-8?B?cGV0ZTAwODU=?=

> >> wrote on 25 sep 2007 in

> >> microsoft.public.windows.terminal_services:

> >>

> >> > I mean does it have to be a deticated server or could I host

> >> > it an another server that acts as an application server for

> >> > one of our programs or what is typically recommended for a

> >> > small environment where it will not be heavily used.

> >> >

> >> > Also, how does the server know you are not logging on

> >> > remotely as you would with remote desktop? Lets say a

> >> > regular user wants to logon to the terminal server, how does

> >> > it figure out they are not trying to logon to the server to

> >> > perform maintenance on the server, etc.

> >> >

> >> > That has confused me a bit. I'm guessing users use the

> >> > remote desktop connection to connect to the terminal server.

> >> > I just want to ensure they are logging on to their terminal

> >> > session and not actually logging on to the server itself.

> >> > Does this make any sense with what I'm trying to say???

> >> >

> >> > "Munindra Das [MSFT]" wrote:

> >> >

> >> >> The article at

> >> >> http://technet2.microsoft.com/windowsserver/en/library/cb2019

> >> >> 37- 8f68-4d0f-9521-99e090ddd6b11033.mspx?mfr=true will

> >> >> provide you with some details on how to plan a terminal

> >> >> server. But it will also depend on what Windows (2000, 2003)

> >> >> you are running and what applications the users are likely

> >> >> to run. For a 2003 Terminal Server with 12 users, you will

> >> >> require a minimum of 128 MB memory.

> >> >>

> >> >> I am not sure what you mean by "Could it be an another

> >> >> application server or does it have to be a deditcated

> >> >> server". You can please provide a little more detail.

> >> >>

> >> >> --

> >> >> This posting is provided "AS IS" with no warranties, and

> >> >> confers no rights. "pete0085"

> >> >> wrote in message

> >> >> news:1E25A8B3-6BF5-4A33-B8B1-9615384FDCCD@microsoft.com...

> >> >> > Brief question about server requirement for a single

> >> >> > terminal server.

> >> >> >

> >> >> > There would be a max of 12 users accessing the server at

> >> >> > one time. With disk space not being an issue, what would

> >> >> > be a recommendation for memory for

> >> >> > such a server?

> >> >> >

> >> >> > Could it be an another application server or does it have

> >> >> > to be a deditcated

> >> >> > server?

> >> >> >

> >> >> > Can someone briefly explain why accessing resources

> >> >> > through a terminal server doesn't take up as much

> >> >> > bandwidth and is faster then accessing it over

> >> >> > a Wan link?

>

 

 

 

Top


 

 

 

From: Vera Noest [MVP] <vera.noest@remove-this.hem.utfors.se>

To: none

Subject: Re: server requirement

Date: 09/25/2007 17:40:15

 

 

No, the profiles cannot contain the same files, so you can't copy

the workstation profile into the TS profile. That's the whole

point, many of the user-specific settings in the profiles are not

valid in the other environment.

If your users currently are in the habit of saving user documents,

like Word and Excel documents, in their profile, then it's high

time to give them a home directory and redirect their My Documents

folder to it. The user profile should not contain user documents,

especially not if it is a roaming profile. And you can make the

same folder, which contains the users documents, available to them

from both their workstation and their TS session.

 

I don't understand what you say about "As long as it's a terminal

server, it won't log me on to the console session of the server,

but instead a session inside the terminal server manager".

 

You can always make a connection to the console, with mstsc

/console. Doesn't matter if the server is configured for Remote

Desktop for Administration or for Terminal Services.

 

And NO, you can NOT install applications just like on any

workstation. The application installation procedure on a TS is

rather special, to ensure multi.user functionality. The server has

to be in "install mode" when you install applications, and no users

can be connected to it while you do so. Many applications also need

some additional adjustments after installation to make them work

properly.

 

I really suggest that you take your time to read up a bit on this,

and whatever you do, don't install and test on a production server!

Use any workstation-like PC and install Windows Server + TS on it,

just for testing purposes. Don't bother about performance at this

stage, it's sufficient if the testserver can handle 2 or 3

sessions.

_________________________________________________________

Vera Noest

MCSE, CCEA, Microsoft MVP - Terminal Server

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

___ please respond in newsgroup, NOT by private email ___

 

=?Utf-8?B?cGV0ZTAwODU=?=

wrote on 25 sep 2007 in

microsoft.public.windows.terminal_services:

 

> As for the TS profile path. Can it contain all the same files

> and folders as the regular roaming profile, but have a different

> path? Will this cause a problem. For ex if my profile path is

> \\server\profiles$\username. Then have a path of

> \\server\tsprofiles$\username but include all the same files.

>

> Think that helped with one question. I do want to test it first

> before buying any licenses to see how it would work in our

> environment. As long as it's a terminal server, it won't log me

> on to the console session of the server, but instead a session

> inside the terminal server manager as long as I buy licenses

> before the 120 days.

>

> I can also install applications as I would on the client

> workstation and they will be accessible without me doing

> anything else to it, correct?

>

> "Vera Noest [MVP]" wrote:

>

>> Yes, there is a grace period of 120 days, in which you can test

>> and use the Terminal Server, without the need to install TS

>> licenses. Just install Terminal Services, in Control Panel -

>> Add/Remove programs - Add Windows components.

>>

>> And yes, users should have a TS profile which is different from

>> there normal profile. If you use the same profile for their

>> workstation and their TS sessions, a lot of settings will not

>> work, and the profiles will become corrupt over time.

>> These TS-specific profiles can be local to the Terminal Server,

>> or they can be roamin. Just store them on a different share on

>> your file server.

>>

>> There is really not one single link which explains it all.

>> That's why there are numerous *books* written on the subject.

>>

>> You can find a number of links to articles about planning,

>> installation, etc on my website. Or read Brian Madden's book

>> again

>> :-) and then install TS on a test server and play around with

>> :it.

>> _________________________________________________________

>> Vera Noest

>> MCSE, CCEA, Microsoft MVP - Terminal Server

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

>> *----------- Please reply in newsgroup -------------*

>>

>> =?Utf-8?B?cGV0ZTAwODU=?=

>> wrote on 25 sep 2007:

>>

>> > I would like to be able to test this. I remember reading

>> > something about allowing you a 180 day trial before you

>> > purchase a license. How would that work in this scennario

>> > where I or a couple users could try it out and see if it

>> > would be a proper solution.

>> >

>> > Someone else is giving me advice that the profile path for TS

>> > should not be the same as the roaming profiles. How would a

>> > user logon or how would the desktop follow the user if they

>> > aren't using the regular roaming profile. I admit I'm

>> > confused about this among other things.

>> >

>> > I've been reading an online book by brain madden that goes

>> > into detail about the design, but isn't as helpful for an

>> > admin trying to setup a TS server.

>> >

>> > A good link, article would be helpful.

>> > "Vera Noest [MVP]" wrote:

>> >

>> >> When users log on to the Terminal Server with the Remote

>> >> Desktop client, they *are* logging on remotely to the server

>> >> itself! There's really no difference between Remote Desktop

>> >> connections (to a server which is configured for "Remote

>> >> Desktop for Administration") and Terminal Server connections

>> >> (to a server which is configured for "Terminal Services,

>> >> i.e. in application mode).

>> >>

>> >> And the server has no way of knowing why someone logs on or

>> >> what they are going to do on the server, that's why *all*

>> >> connections to a server configured for terminal Services

>> >> need a license. The only exception is a single connection to

>> >> the console of the server (with mstsc /console), which is

>> >> always free of TS CAL requirements.

>> >>

>> >> Ideally, a Terminal Server should be a dedicated server,

>> >> both for performance and security reasons. But in small

>> >> environments, this isn't always realistic. So you can also

>> >> use the same server as a file server, but don't run TS on a

>> >> Domain Controller, and don't combine it with SQL or Exchange

>> >> if you can avoid it.

>> >> _________________________________________________________

>> >> Vera Noest MCSE, CCEA, Microsoft MVP - Terminal Server

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

>> >> ___ please respond in newsgroup, NOT by private email ___

>> >>

>> >> =?Utf-8?B?cGV0ZTAwODU=?=

>> >> wrote on 25 sep 2007 in

>> >> microsoft.public.windows.terminal_services:

>> >>

>> >> > I mean does it have to be a deticated server or could I

>> >> > host it an another server that acts as an application

>> >> > server for one of our programs or what is typically

>> >> > recommended for a small environment where it will not be

>> >> > heavily used.

>> >> >

>> >> > Also, how does the server know you are not logging on

>> >> > remotely as you would with remote desktop? Lets say a

>> >> > regular user wants to logon to the terminal server, how

>> >> > does it figure out they are not trying to logon to the

>> >> > server to perform maintenance on the server, etc.

>> >> >

>> >> > That has confused me a bit. I'm guessing users use the

>> >> > remote desktop connection to connect to the terminal

>> >> > server. I just want to ensure they are logging on to their

>> >> > terminal session and not actually logging on to the server

>> >> > itself. Does this make any sense with what I'm trying to

>> >> > say???

>> >> >

>> >> > "Munindra Das [MSFT]" wrote:

>> >> >

>> >> >> The article at

>> >> >> http://technet2.microsoft.com/windowsserver/en/library/cb2

>> >> >> 019 37- 8f68-4d0f-9521-99e090ddd6b11033.mspx?mfr=true

>> >> >> will provide you with some details on how to plan a

>> >> >> terminal server. But it will also depend on what Windows

>> >> >> (2000, 2003) you are running and what applications the

>> >> >> users are likely to run. For a 2003 Terminal Server with

>> >> >> 12 users, you will require a minimum of 128 MB memory.

>> >> >>

>> >> >> I am not sure what you mean by "Could it be an another

>> >> >> application server or does it have to be a deditcated

>> >> >> server". You can please provide a little more detail.

>> >> >>

>> >> >> --

>> >> >> This posting is provided "AS IS" with no warranties, and

>> >> >> confers no rights. "pete0085"

>> >> >> wrote in message

>> >> >> news:1E25A8B3-6BF5-4A33-B8B1-9615384FDCCD@microsoft.com...

>> >> >> > Brief question about server requirement for a single

>> >> >> > terminal server.

>> >> >> >

>> >> >> > There would be a max of 12 users accessing the server

>> >> >> > at one time. With disk space not being an issue, what

>> >> >> > would be a recommendation for memory for

>> >> >> > such a server?

>> >> >> >

>> >> >> > Could it be an another application server or does it

>> >> >> > have to be a deditcated

>> >> >> > server?

>> >> >> >

>> >> >> > Can someone briefly explain why accessing resources

>> >> >> > through a terminal server doesn't take up as much

>> >> >> > bandwidth and is faster then accessing it over

>> >> >> > a Wan link?

 

 

 

Top


 

 

 

From: pete0085 <pete0085@discussions.microsoft.com>

To: none

Subject: Re: server requirement

Date: 09/25/2007 18:12:01

 

 

I will try to find some more reading or get a book in the future. Nothing

I'm going to do in the immediate future. Looking for a solution that doesn't

involve installing an additional data line.

 

The installing application part sounds tricky. I have applications that are

vendor specific and are not widely used outside other finanical institutions.

 

 

I have a test server set up at home on virtual pc and I don't remember

seeing anything about installing applications in "install mode" as you

mentioned.

 

 

 

"Vera Noest [MVP]" wrote:

 

> No, the profiles cannot contain the same files, so you can't copy

> the workstation profile into the TS profile. That's the whole

> point, many of the user-specific settings in the profiles are not

> valid in the other environment.

> If your users currently are in the habit of saving user documents,

> like Word and Excel documents, in their profile, then it's high

> time to give them a home directory and redirect their My Documents

> folder to it. The user profile should not contain user documents,

> especially not if it is a roaming profile. And you can make the

> same folder, which contains the users documents, available to them

> from both their workstation and their TS session.

>

> I don't understand what you say about "As long as it's a terminal

> server, it won't log me on to the console session of the server,

> but instead a session inside the terminal server manager".

>

> You can always make a connection to the console, with mstsc

> /console. Doesn't matter if the server is configured for Remote

> Desktop for Administration or for Terminal Services.

>

> And NO, you can NOT install applications just like on any

> workstation. The application installation procedure on a TS is

> rather special, to ensure multi.user functionality. The server has

> to be in "install mode" when you install applications, and no users

> can be connected to it while you do so. Many applications also need

> some additional adjustments after installation to make them work

> properly.

>

> I really suggest that you take your time to read up a bit on this,

> and whatever you do, don't install and test on a production server!

> Use any workstation-like PC and install Windows Server + TS on it,

> just for testing purposes. Don't bother about performance at this

> stage, it's sufficient if the testserver can handle 2 or 3

> sessions.

> _________________________________________________________

> Vera Noest

> MCSE, CCEA, Microsoft MVP - Terminal Server

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

> ___ please respond in newsgroup, NOT by private email ___

>

> =?Utf-8?B?cGV0ZTAwODU=?=

> wrote on 25 sep 2007 in

> microsoft.public.windows.terminal_services:

>

> > As for the TS profile path. Can it contain all the same files

> > and folders as the regular roaming profile, but have a different

> > path? Will this cause a problem. For ex if my profile path is

> > \\server\profiles$\username. Then have a path of

> > \\server\tsprofiles$\username but include all the same files.

> >

> > Think that helped with one question. I do want to test it first

> > before buying any licenses to see how it would work in our

> > environment. As long as it's a terminal server, it won't log me

> > on to the console session of the server, but instead a session

> > inside the terminal server manager as long as I buy licenses

> > before the 120 days.

> >

> > I can also install applications as I would on the client

> > workstation and they will be accessible without me doing

> > anything else to it, correct?

> >

> > "Vera Noest [MVP]" wrote:

> >

> >> Yes, there is a grace period of 120 days, in which you can test

> >> and use the Terminal Server, without the need to install TS

> >> licenses. Just install Terminal Services, in Control Panel -

> >> Add/Remove programs - Add Windows components.

> >>

> >> And yes, users should have a TS profile which is different from

> >> there normal profile. If you use the same profile for their

> >> workstation and their TS sessions, a lot of settings will not

> >> work, and the profiles will become corrupt over time.

> >> These TS-specific profiles can be local to the Terminal Server,

> >> or they can be roamin. Just store them on a different share on

> >> your file server.

> >>

> >> There is really not one single link which explains it all.

> >> That's why there are numerous *books* written on the subject.

> >>

> >> You can find a number of links to articles about planning,

> >> installation, etc on my website. Or read Brian Madden's book

> >> again

> >> :-) and then install TS on a test server and play around with

> >> :it.

> >> _________________________________________________________

> >> Vera Noest

> >> MCSE, CCEA, Microsoft MVP - Terminal Server

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

> >> *----------- Please reply in newsgroup -------------*

> >>

> >> =?Utf-8?B?cGV0ZTAwODU=?=

> >> wrote on 25 sep 2007:

> >>

> >> > I would like to be able to test this. I remember reading

> >> > something about allowing you a 180 day trial before you

> >> > purchase a license. How would that work in this scennario

> >> > where I or a couple users could try it out and see if it

> >> > would be a proper solution.

> >> >

> >> > Someone else is giving me advice that the profile path for TS

> >> > should not be the same as the roaming profiles. How would a

> >> > user logon or how would the desktop follow the user if they

> >> > aren't using the regular roaming profile. I admit I'm

> >> > confused about this among other things.

> >> >

> >> > I've been reading an online book by brain madden that goes

> >> > into detail about the design, but isn't as helpful for an

> >> > admin trying to setup a TS server.

> >> >

> >> > A good link, article would be helpful.

> >> > "Vera Noest [MVP]" wrote:

> >> >

> >> >> When users log on to the Terminal Server with the Remote

> >> >> Desktop client, they *are* logging on remotely to the server

> >> >> itself! There's really no difference between Remote Desktop

> >> >> connections (to a server which is configured for "Remote

> >> >> Desktop for Administration") and Terminal Server connections

> >> >> (to a server which is configured for "Terminal Services,

> >> >> i.e. in application mode).

> >> >>

> >> >> And the server has no way of knowing why someone logs on or

> >> >> what they are going to do on the server, that's why *all*

> >> >> connections to a server configured for terminal Services

> >> >> need a license. The only exception is a single connection to

> >> >> the console of the server (with mstsc /console), which is

> >> >> always free of TS CAL requirements.

> >> >>

> >> >> Ideally, a Terminal Server should be a dedicated server,

> >> >> both for performance and security reasons. But in small

> >> >> environments, this isn't always realistic. So you can also

> >> >> use the same server as a file server, but don't run TS on a

> >> >> Domain Controller, and don't combine it with SQL or Exchange

> >> >> if you can avoid it.

> >> >> _________________________________________________________

> >> >> Vera Noest MCSE, CCEA, Microsoft MVP - Terminal Server

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

> >> >> ___ please respond in newsgroup, NOT by private email ___

> >> >>

> >> >> =?Utf-8?B?cGV0ZTAwODU=?=

> >> >> wrote on 25 sep 2007 in

> >> >> microsoft.public.windows.terminal_services:

> >> >>

> >> >> > I mean does it have to be a deticated server or could I

> >> >> > host it an another server that acts as an application

> >> >> > server for one of our programs or what is typically

> >> >> > recommended for a small environment where it will not be

> >> >> > heavily used.

> >> >> >

> >> >> > Also, how does the server know you are not logging on

> >> >> > remotely as you would with remote desktop? Lets say a

> >> >> > regular user wants to logon to the terminal server, how

> >> >> > does it figure out they are not trying to logon to the

> >> >> > server to perform maintenance on the server, etc.

> >> >> >

> >> >> > That has confused me a bit. I'm guessing users use the

> >> >> > remote desktop connection to connect to the terminal

> >> >> > server. I just want to ensure they are logging on to their

> >> >> > terminal session and not actually logging on to the server

> >> >> > itself. Does this make any sense with what I'm trying to

> >> >> > say???

> >> >> >

> >> >> > "Munindra Das [MSFT]" wrote:

> >> >> >

> >> >> >> The article at

> >> >> >> http://technet2.microsoft.com/windowsserver/en/library/cb2

> >> >> >> 019 37- 8f68-4d0f-9521-99e090ddd6b11033.mspx?mfr=true

> >> >> >> will provide you with some details on how to plan a

> >> >> >> terminal server. But it will also depend on what Windows

> >> >> >> (2000, 2003) you are running and what applications the

> >> >> >> users are likely to run. For a 2003 Terminal Server with

> >> >> >> 12 users, you will require a minimum of 128 MB memory.

> >> >> >>

> >> >> >> I am not sure what you mean by "Could it be an another

> >> >> >> application server or does it have to be a deditcated

> >> >> >> server". You can please provide a little more detail.

> >> >> >>

> >> >> >> --

> >> >> >> This posting is provided "AS IS" with no warranties, and

> >> >> >> confers no rights. "pete0085"

> >> >> >> wrote in message

> >> >> >> news:1E25A8B3-6BF5-4A33-B8B1-9615384FDCCD@microsoft.com...

> >> >> >> > Brief question about server requirement for a single

> >> >> >> > terminal server.

> >> >> >> >

> >> >> >> > There would be a max of 12 users accessing the server

> >> >> >> > at one time. With disk space not being an issue, what

> >> >> >> > would be a recommendation for memory for

> >> >> >> > such a server?

> >> >> >> >

> >> >> >> > Could it be an another application server or does it

> >> >> >> > have to be a deditcated

> >> >> >> > server?

> >> >> >> >

> >> >> >> > Can someone briefly explain why accessing resources

> >> >> >> > through a terminal server doesn't take up as much

> >> >> >> > bandwidth and is faster then accessing it over

> >> >> >> > a Wan link?

>

 

 

 

Top


 

 

 

From: Vera Noest [MVP] <vera.noest@remove-this.hem.utfors.se>

To: none

Subject: Re: server requirement

Date: 09/26/2007 08:05:50

 

 

I would start by contacting the vendor of the applicatin and ask if

they support their application in a Terminal Server environment. If

they do, they should also be able to provide you with specific

installation instructions on a TS.

 

No, the server doesn't warn you about "install mode".

But failing to put the server into install mode can lead to

problems where all users share the same settings, because they are

all reading them and storing them in the same location. Or the

application only allows one user at a time, because that user then

has a file open which blocks other users from accessing the same

file. Or the application runs only for Administrators, because

normal users don't have access to the user-specific files on the

TS.

So some user-specific files must be duplicated to each users

\windows folder in their TS home directory when you install an

application on a TS, while it is sufficient with just a single copy

of the same file on a single-user workstation. This process is

automated by putting the server into install mode before installing

applications. The server then monitors all changes made by the

installation process to the registry and the file system, and makes

copies of those changes automatically available for users when they

logon to the server.

 

This is explained in more detail here:

 

186498 - Terminal Server Application Integration Information

http://support.microsoft.com/?kbid=186498

_________________________________________________________

Vera Noest

MCSE, CCEA, Microsoft MVP - Terminal Server

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

___ please respond in newsgroup, NOT by private email ___

 

=?Utf-8?B?cGV0ZTAwODU=?=

wrote on 26 sep 2007 in

microsoft.public.windows.terminal_services:

 

> I will try to find some more reading or get a book in the

> future. Nothing I'm going to do in the immediate future.

> Looking for a solution that doesn't involve installing an

> additional data line.

>

> The installing application part sounds tricky. I have

> applications that are vendor specific and are not widely used

> outside other finanical institutions.

>

>

> I have a test server set up at home on virtual pc and I don't

> remember seeing anything about installing applications in

> "install mode" as you mentioned.

>

>

>

> "Vera Noest [MVP]" wrote:

>

>> No, the profiles cannot contain the same files, so you can't

>> copy the workstation profile into the TS profile. That's the

>> whole point, many of the user-specific settings in the profiles

>> are not valid in the other environment.

>> If your users currently are in the habit of saving user

>> documents, like Word and Excel documents, in their profile,

>> then it's high time to give them a home directory and redirect

>> their My Documents folder to it. The user profile should not

>> contain user documents, especially not if it is a roaming

>> profile. And you can make the same folder, which contains the

>> users documents, available to them from both their workstation

>> and their TS session.

>>

>> I don't understand what you say about "As long as it's a

>> terminal server, it won't log me on to the console session of

>> the server, but instead a session inside the terminal server

>> manager".

>>

>> You can always make a connection to the console, with mstsc

>> /console. Doesn't matter if the server is configured for Remote

>> Desktop for Administration or for Terminal Services.

>>

>> And NO, you can NOT install applications just like on any

>> workstation. The application installation procedure on a TS is

>> rather special, to ensure multi.user functionality. The server

>> has to be in "install mode" when you install applications, and

>> no users can be connected to it while you do so. Many

>> applications also need some additional adjustments after

>> installation to make them work properly.

>>

>> I really suggest that you take your time to read up a bit on

>> this, and whatever you do, don't install and test on a

>> production server! Use any workstation-like PC and install

>> Windows Server + TS on it, just for testing purposes. Don't

>> bother about performance at this stage, it's sufficient if the

>> testserver can handle 2 or 3 sessions.

>> _________________________________________________________

>> Vera Noest

>> MCSE, CCEA, Microsoft MVP - Terminal Server

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

>> ___ please respond in newsgroup, NOT by private email ___

>>

>> =?Utf-8?B?cGV0ZTAwODU=?=

>> wrote on 25 sep 2007 in

>> microsoft.public.windows.terminal_services:

>>

>> > As for the TS profile path. Can it contain all the same

>> > files and folders as the regular roaming profile, but have a

>> > different path? Will this cause a problem. For ex if my

>> > profile path is \\server\profiles$\username. Then have a

>> > path of \\server\tsprofiles$\username but include all the

>> > same files.

>> >

>> > Think that helped with one question. I do want to test it

>> > first before buying any licenses to see how it would work in

>> > our environment. As long as it's a terminal server, it won't

>> > log me on to the console session of the server, but instead a

>> > session inside the terminal server manager as long as I buy

>> > licenses before the 120 days.

>> >

>> > I can also install applications as I would on the client

>> > workstation and they will be accessible without me doing

>> > anything else to it, correct?

>> >

>> > "Vera Noest [MVP]" wrote:

>> >

>> >> Yes, there is a grace period of 120 days, in which you can

>> >> test and use the Terminal Server, without the need to

>> >> install TS licenses. Just install Terminal Services, in

>> >> Control Panel - Add/Remove programs - Add Windows

>> >> components.

>> >>

>> >> And yes, users should have a TS profile which is different

>> >> from there normal profile. If you use the same profile for

>> >> their workstation and their TS sessions, a lot of settings

>> >> will not work, and the profiles will become corrupt over

>> >> time. These TS-specific profiles can be local to the

>> >> Terminal Server, or they can be roamin. Just store them on a

>> >> different share on your file server.

>> >>

>> >> There is really not one single link which explains it all.

>> >> That's why there are numerous *books* written on the

>> >> subject.

>> >>

>> >> You can find a number of links to articles about planning,

>> >> installation, etc on my website. Or read Brian Madden's book

>> >> again

>> >> :-) and then install TS on a test server and play around

>> >> :with it.

>> >> _________________________________________________________

>> >> Vera Noest

>> >> MCSE, CCEA, Microsoft MVP - Terminal Server

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

>> >> *----------- Please reply in newsgroup -------------*

>> >>

>> >> =?Utf-8?B?cGV0ZTAwODU=?=

>> >> wrote on 25 sep 2007:

>> >>

>> >> > I would like to be able to test this. I remember reading

>> >> > something about allowing you a 180 day trial before you

>> >> > purchase a license. How would that work in this scennario

>> >> > where I or a couple users could try it out and see if it

>> >> > would be a proper solution.

>> >> >

>> >> > Someone else is giving me advice that the profile path for

>> >> > TS should not be the same as the roaming profiles. How

>> >> > would a user logon or how would the desktop follow the

>> >> > user if they aren't using the regular roaming profile. I

>> >> > admit I'm confused about this among other things.

>> >> >

>> >> > I've been reading an online book by brain madden that goes

>> >> > into detail about the design, but isn't as helpful for an

>> >> > admin trying to setup a TS server.

>> >> >

>> >> > A good link, article would be helpful.

>> >> > "Vera Noest [MVP]" wrote:

>> >> >

>> >> >> When users log on to the Terminal Server with the Remote

>> >> >> Desktop client, they *are* logging on remotely to the

>> >> >> server itself! There's really no difference between

>> >> >> Remote Desktop connections (to a server which is

>> >> >> configured for "Remote Desktop for Administration") and

>> >> >> Terminal Server connections (to a server which is

>> >> >> configured for "Terminal Services, i.e. in application

>> >> >> mode).

>> >> >>

>> >> >> And the server has no way of knowing why someone logs on

>> >> >> or what they are going to do on the server, that's why

>> >> >> *all* connections to a server configured for terminal

>> >> >> Services need a license. The only exception is a single

>> >> >> connection to the console of the server (with mstsc

>> >> >> /console), which is always free of TS CAL requirements.

>> >> >>

>> >> >> Ideally, a Terminal Server should be a dedicated server,

>> >> >> both for performance and security reasons. But in small

>> >> >> environments, this isn't always realistic. So you can

>> >> >> also use the same server as a file server, but don't run

>> >> >> TS on a Domain Controller, and don't combine it with SQL

>> >> >> or Exchange if you can avoid it.

>> >> >> _________________________________________________________

>> >> >> Vera Noest MCSE, CCEA, Microsoft MVP - Terminal Server

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

>> >> >> ___ please respond in newsgroup, NOT by private email ___

>> >> >>

>> >> >> =?Utf-8?B?cGV0ZTAwODU=?=

>> >> >> wrote on 25 sep 2007

>> >> >> in microsoft.public.windows.terminal_services:

>> >> >>

>> >> >> > I mean does it have to be a deticated server or could I

>> >> >> > host it an another server that acts as an application

>> >> >> > server for one of our programs or what is typically

>> >> >> > recommended for a small environment where it will not

>> >> >> > be heavily used.

>> >> >> >

>> >> >> > Also, how does the server know you are not logging on

>> >> >> > remotely as you would with remote desktop? Lets say a

>> >> >> > regular user wants to logon to the terminal server, how

>> >> >> > does it figure out they are not trying to logon to the

>> >> >> > server to perform maintenance on the server, etc.

>> >> >> >

>> >> >> > That has confused me a bit. I'm guessing users use the

>> >> >> > remote desktop connection to connect to the terminal

>> >> >> > server. I just want to ensure they are logging on to

>> >> >> > their terminal session and not actually logging on to

>> >> >> > the server itself. Does this make any sense with what

>> >> >> > I'm trying to say???

>> >> >> >

>> >> >> > "Munindra Das [MSFT]" wrote:

>> >> >> >

>> >> >> >> The article at

>> >> >> >> http://technet2.microsoft.com/windowsserver/en/library/

>> >> >> >> cb2 019 37-

>> >> >> >> 8f68-4d0f-9521-99e090ddd6b11033.mspx?mfr=true

>> >> >> >> will provide you with some details on how to plan a

>> >> >> >> terminal server. But it will also depend on what

>> >> >> >> Windows (2000, 2003) you are running and what

>> >> >> >> applications the users are likely to run. For a 2003

>> >> >> >> Terminal Server with 12 users, you will require a

>> >> >> >> minimum of 128 MB memory.

>> >> >> >>

>> >> >> >> I am not sure what you mean by "Could it be an another

>> >> >> >> application server or does it have to be a deditcated

>> >> >> >> server". You can please provide a little more detail.

>> >> >> >>

>> >> >> >> --

>> >> >> >> This posting is provided "AS IS" with no warranties,

>> >> >> >> and confers no rights. "pete0085"

>> >> >> >> wrote in message

>> >> >> >> news:1E25A8B3-6BF5-4A33-B8B1-9615384FDCCD@microsoft.com

>> >> >> >> ...

>> >> >> >> > Brief question about server requirement for a single

>> >> >> >> > terminal server.

>> >> >> >> >

>> >> >> >> > There would be a max of 12 users accessing the

>> >> >> >> > server at one time. With disk space not being an

>> >> >> >> > issue, what would be a recommendation for memory for

>> >> >> >> > such a server?

>> >> >> >> >

>> >> >> >> > Could it be an another application server or does it

>> >> >> >> > have to be a deditcated

>> >> >> >> > server?

>> >> >> >> >

>> >> >> >> > Can someone briefly explain why accessing resources

>> >> >> >> > through a terminal server doesn't take up as much

>> >> >> >> > bandwidth and is faster then accessing it over

>> >> >> >> > a Wan link?

 

 

 

Top


 

 

 

From: pete0085 <pete0085@discussions.microsoft.com>

To: none

Subject: Re: server requirement

Date: 09/26/2007 12:32:02

 

 

Thanks for all your help. Unfortuantely I forgot that some of our programs

are IP specific. They are run correctly based on the ip address. This can

always be changed, but it would not work correctly through terminal services.

Not sure why I didn't think about this earlier. At least it was a good idea.

 

"Vera Noest [MVP]" wrote:

 

> I would start by contacting the vendor of the applicatin and ask if

> they support their application in a Terminal Server environment. If

> they do, they should also be able to provide you with specific

> installation instructions on a TS.

>

> No, the server doesn't warn you about "install mode".

> But failing to put the server into install mode can lead to

> problems where all users share the same settings, because they are

> all reading them and storing them in the same location. Or the

> application only allows one user at a time, because that user then

> has a file open which blocks other users from accessing the same

> file. Or the application runs only for Administrators, because

> normal users don't have access to the user-specific files on the

> TS.

> So some user-specific files must be duplicated to each users

> \windows folder in their TS home directory when you install an

> application on a TS, while it is sufficient with just a single copy

> of the same file on a single-user workstation. This process is

> automated by putting the server into install mode before installing

> applications. The server then monitors all changes made by the

> installation process to the registry and the file system, and makes

> copies of those changes automatically available for users when they

> logon to the server.

>

> This is explained in more detail here:

>

> 186498 - Terminal Server Application Integration Information

> http://support.microsoft.com/?kbid=186498

> _________________________________________________________

> Vera Noest

> MCSE, CCEA, Microsoft MVP - Terminal Server

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

> ___ please respond in newsgroup, NOT by private email ___

>

> =?Utf-8?B?cGV0ZTAwODU=?=

> wrote on 26 sep 2007 in

> microsoft.public.windows.terminal_services:

>

> > I will try to find some more reading or get a book in the

> > future. Nothing I'm going to do in the immediate future.

> > Looking for a solution that doesn't involve installing an

> > additional data line.

> >

> > The installing application part sounds tricky. I have

> > applications that are vendor specific and are not widely used

> > outside other finanical institutions.

> >

> >

> > I have a test server set up at home on virtual pc and I don't

> > remember seeing anything about installing applications in

> > "install mode" as you mentioned.

> >

> >

> >

> > "Vera Noest [MVP]" wrote:

> >

> >> No, the profiles cannot contain the same files, so you can't

> >> copy the workstation profile into the TS profile. That's the

> >> whole point, many of the user-specific settings in the profiles

> >> are not valid in the other environment.

> >> If your users currently are in the habit of saving user

> >> documents, like Word and Excel documents, in their profile,

> >> then it's high time to give them a home directory and redirect

> >> their My Documents folder to it. The user profile should not

> >> contain user documents, especially not if it is a roaming

> >> profile. And you can make the same folder, which contains the

> >> users documents, available to them from both their workstation

> >> and their TS session.

> >>

> >> I don't understand what you say about "As long as it's a

> >> terminal server, it won't log me on to the console session of

> >> the server, but instead a session inside the terminal server

> >> manager".

> >>

> >> You can always make a connection to the console, with mstsc

> >> /console. Doesn't matter if the server is configured for Remote

> >> Desktop for Administration or for Terminal Services.

> >>

> >> And NO, you can NOT install applications just like on any

> >> workstation. The application installation procedure on a TS is

> >> rather special, to ensure multi.user functionality. The server

> >> has to be in "install mode" when you install applications, and

> >> no users can be connected to it while you do so. Many

> >> applications also need some additional adjustments after

> >> installation to make them work properly.

> >>

> >> I really suggest that you take your time to read up a bit on

> >> this, and whatever you do, don't install and test on a

> >> production server! Use any workstation-like PC and install

> >> Windows Server + TS on it, just for testing purposes. Don't

> >> bother about performance at this stage, it's sufficient if the

> >> testserver can handle 2 or 3 sessions.

> >> _________________________________________________________

> >> Vera Noest

> >> MCSE, CCEA, Microsoft MVP - Terminal Server

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

> >> ___ please respond in newsgroup, NOT by private email ___

> >>

> >> =?Utf-8?B?cGV0ZTAwODU=?=

> >> wrote on 25 sep 2007 in

> >> microsoft.public.windows.terminal_services:

> >>

> >> > As for the TS profile path. Can it contain all the same

> >> > files and folders as the regular roaming profile, but have a

> >> > different path? Will this cause a problem. For ex if my

> >> > profile path is \\server\profiles$\username. Then have a

> >> > path of \\server\tsprofiles$\username but include all the

> >> > same files.

> >> >

> >> > Think that helped with one question. I do want to test it

> >> > first before buying any licenses to see how it would work in

> >> > our environment. As long as it's a terminal server, it won't

> >> > log me on to the console session of the server, but instead a

> >> > session inside the terminal server manager as long as I buy

> >> > licenses before the 120 days.

> >> >

> >> > I can also install applications as I would on the client

> >> > workstation and they will be accessible without me doing

> >> > anything else to it, correct?

> >> >

> >> > "Vera Noest [MVP]" wrote:

> >> >

> >> >> Yes, there is a grace period of 120 days, in which you can

> >> >> test and use the Terminal Server, without the need to

> >> >> install TS licenses. Just install Terminal Services, in

> >> >> Control Panel - Add/Remove programs - Add Windows

> >> >> components.

> >> >>

> >> >> And yes, users should have a TS profile which is different

> >> >> from there normal profile. If you use the same profile for

> >> >> their workstation and their TS sessions, a lot of settings

> >> >> will not work, and the profiles will become corrupt over

> >> >> time. These TS-specific profiles can be local to the

> >> >> Terminal Server, or they can be roamin. Just store them on a

> >> >> different share on your file server.

> >> >>

> >> >> There is really not one single link which explains it all.

> >> >> That's why there are numerous *books* written on the

> >> >> subject.

> >> >>

> >> >> You can find a number of links to articles about planning,

> >> >> installation, etc on my website. Or read Brian Madden's book

> >> >> again

> >> >> :-) and then install TS on a test server and play around

> >> >> :with it.

> >> >> _________________________________________________________

> >> >> Vera Noest

> >> >> MCSE, CCEA, Microsoft MVP - Terminal Server

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

> >> >> *----------- Please reply in newsgroup -------------*

> >> >>

> >> >> =?Utf-8?B?cGV0ZTAwODU=?=

> >> >> wrote on 25 sep 2007:

> >> >>

> >> >> > I would like to be able to test this. I remember reading

> >> >> > something about allowing you a 180 day trial before you

> >> >> > purchase a license. How would that work in this scennario

> >> >> > where I or a couple users could try it out and see if it

> >> >> > would be a proper solution.

> >> >> >

> >> >> > Someone else is giving me advice that the profile path for

> >> >> > TS should not be the same as the roaming profiles. How

> >> >> > would a user logon or how would the desktop follow the

> >> >> > user if they aren't using the regular roaming profile. I

> >> >> > admit I'm confused about this among other things.

> >> >> >

> >> >> > I've been reading an online book by brain madden that goes

> >> >> > into detail about the design, but isn't as helpful for an

> >> >> > admin trying to setup a TS server.

> >> >> >

> >> >> > A good link, article would be helpful.

> >> >> > "Vera Noest [MVP]" wrote:

> >> >> >

> >> >> >> When users log on to the Terminal Server with the Remote

> >> >> >> Desktop client, they *are* logging on remotely to the

> >> >> >> server itself! There's really no difference between

> >> >> >> Remote Desktop connections (to a server which is

> >> >> >> configured for "Remote Desktop for Administration") and

> >> >> >> Terminal Server connections (to a server which is

> >> >> >> configured for "Terminal Services, i.e. in application

> >> >> >> mode).

> >> >> >>

> >> >> >> And the server has no way of knowing why someone logs on

> >> >> >> or what they are going to do on the server, that's why

> >> >> >> *all* connections to a server configured for terminal

> >> >> >> Services need a license. The only exception is a single

> >> >> >> connection to the console of the server (with mstsc

> >> >> >> /console), which is always free of TS CAL requirements.

> >> >> >>

> >> >> >> Ideally, a Terminal Server should be a dedicated server,

> >> >> >> both for performance and security reasons. But in small

> >> >> >> environments, this isn't always realistic. So you can

> >> >> >> also use the same server as a file server, but don't run

> >> >> >> TS on a Domain Controller, and don't combine it with SQL

> >> >> >> or Exchange if you can avoid it.

> >> >> >> _________________________________________________________

> >> >> >> Vera Noest MCSE, CCEA, Microsoft MVP - Terminal Server

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

> >> >> >> ___ please respond in newsgroup, NOT by private email ___

> >> >> >>

> >> >> >> =?Utf-8?B?cGV0ZTAwODU=?=

> >> >> >> wrote on 25 sep 2007

> >> >> >> in microsoft.public.windows.terminal_services:

> >> >> >>

> >> >> >> > I mean does it have to be a deticated server or could I

> >> >> >> > host it an another server that acts as an application

> >> >> >> > server for one of our programs or what is typically

> >> >> >> > recommended for a small environment where it will not

> >> >> >> > be heavily used.

> >> >> >> >

> >> >> >> > Also, how does the server know you are not logging on

> >> >> >> > remotely as you would with remote desktop? Lets say a

> >> >> >> > regular user wants to logon to the terminal server, how

> >> >> >> > does it figure out they are not trying to logon to the

> >> >> >> > server to perform maintenance on the server, etc.

> >> >> >> >

> >> >> >> > That has confused me a bit. I'm guessing users use the

> >> >> >> > remote desktop connection to connect to the terminal

> >> >> >> > server. I just want to ensure they are logging on to

> >> >> >> > their terminal session and not actually logging on to

> >> >> >> > the server itself. Does this make any sense with what

> >> >> >> > I'm trying to say???

> >> >> >> >

> >> >> >> > "Munindra Das [MSFT]" wrote:

> >> >> >> >

> >> >> >> >> The article at

> >> >> >> >> http://technet2.microsoft.com/windowsserver/en/library/

> >> >> >> >> cb2 019 37-

> >> >> >> >> 8f68-4d0f-9521-99e090ddd6b11033.mspx?mfr=true

> >> >> >> >> will provide you with some details on how to plan a

> >> >> >> >> terminal server. But it will also depend on what

> >> >> >> >> Windows (2000, 2003) you are running and what

> >> >> >> >> applications the users are likely to run. For a 2003

> >> >> >> >> Terminal Server with 12 users, you will require a

> >> >> >> >> minimum of 128 MB memory.

> >> >> >> >>

> >> >> >> >> I am not sure what you mean by "Could it be an another

> >> >> >> >> application server or does it have to be a deditcated

> >> >> >> >> server". You can please provide a little more detail.

> >> >> >> >>

> >> >> >> >> --

> >> >> >> >> This posting is provided "AS IS" with no warranties,

> >> >> >> >> and confers no rights. "pete0085"

> >> >> >> >> wrote in message

> >> >> >> >> news:1E25A8B3-6BF5-4A33-B8B1-9615384FDCCD@microsoft.com

> >> >> >> >> ...

> >> >> >> >> > Brief question about server requirement for a single

> >> >> >> >> > terminal server.

> >> >> >> >> >

> >> >> >> >> > There would be a max of 12 users accessing the

> >> >> >> >> > server at one time. With disk space not being an

> >> >> >> >> > issue, what would be a recommendation for memory for

> >> >> >> >> > such a server?

> >> >> >> >> >

> >> >> >> >> > Could it be an another application server or does it

> >> >> >> >> > have to be a deditcated

> >> >> >> >> > server?

> >> >> >> >> >

> >> >> >> >> > Can someone briefly explain why accessing resources

> >> >> >> >> > through a terminal server doesn't take up as much

> >> >> >> >> > bandwidth and is faster then accessing it over

> >> >> >> >> > a Wan link?

>

 

 

 

Top


 

 

 

From: Vera Noest [MVP] <vera.noest@remove-this.hem.utfors.se>

To: none

Subject: Re: server requirement

Date: 09/26/2007 16:11:26

 

 

There are 3rd party add-ons which enable giving each session a

unique IP number.

Citrix is one, VIP-IT from Provision Networks another.

 

www.citrix.com

http://www.provisionnetworks.com/solutions/vip-it/vip-it.aspx

_________________________________________________________

Vera Noest

MCSE, CCEA, Microsoft MVP - Terminal Server

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

___ please respond in newsgroup, NOT by private email ___

 

=?Utf-8?B?cGV0ZTAwODU=?=

wrote on 26 sep 2007 in

microsoft.public.windows.terminal_services:

 

> Thanks for all your help. Unfortuantely I forgot that some of

> our programs are IP specific. They are run correctly based on

> the ip address. This can always be changed, but it would not

> work correctly through terminal services.

> Not sure why I didn't think about this earlier. At least it

> was a good idea.

>

> "Vera Noest [MVP]" wrote:

>

>> I would start by contacting the vendor of the applicatin and

>> ask if they support their application in a Terminal Server

>> environment. If they do, they should also be able to provide

>> you with specific installation instructions on a TS.

>>

>> No, the server doesn't warn you about "install mode".

>> But failing to put the server into install mode can lead to

>> problems where all users share the same settings, because they

>> are all reading them and storing them in the same location. Or

>> the application only allows one user at a time, because that

>> user then has a file open which blocks other users from

>> accessing the same file. Or the application runs only for

>> Administrators, because normal users don't have access to the

>> user-specific files on the TS.

>> So some user-specific files must be duplicated to each users

>> \windows folder in their TS home directory when you install an

>> application on a TS, while it is sufficient with just a single

>> copy of the same file on a single-user workstation. This

>> process is automated by putting the server into install mode

>> before installing applications. The server then monitors all

>> changes made by the installation process to the registry and

>> the file system, and makes copies of those changes

>> automatically available for users when they logon to the

>> server.

>>

>> This is explained in more detail here:

>>

>> 186498 - Terminal Server Application Integration Information

>> http://support.microsoft.com/?kbid=186498

>> _________________________________________________________

>> Vera Noest

>> MCSE, CCEA, Microsoft MVP - Terminal Server

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

>> ___ please respond in newsgroup, NOT by private email ___

>>

>> =?Utf-8?B?cGV0ZTAwODU=?=

>> wrote on 26 sep 2007 in

>> microsoft.public.windows.terminal_services:

>>

>> > I will try to find some more reading or get a book in the

>> > future. Nothing I'm going to do in the immediate future.

>> > Looking for a solution that doesn't involve installing an

>> > additional data line.

>> >

>> > The installing application part sounds tricky. I have

>> > applications that are vendor specific and are not widely used

>> > outside other finanical institutions.

>> >

>> >

>> > I have a test server set up at home on virtual pc and I don't

>> > remember seeing anything about installing applications in

>> > "install mode" as you mentioned.

>> >

>> >

>> >

>> > "Vera Noest [MVP]" wrote:

>> >

>> >> No, the profiles cannot contain the same files, so you can't

>> >> copy the workstation profile into the TS profile. That's the

>> >> whole point, many of the user-specific settings in the

>> >> profiles are not valid in the other environment.

>> >> If your users currently are in the habit of saving user

>> >> documents, like Word and Excel documents, in their profile,

>> >> then it's high time to give them a home directory and

>> >> redirect their My Documents folder to it. The user profile

>> >> should not contain user documents, especially not if it is a

>> >> roaming profile. And you can make the same folder, which

>> >> contains the users documents, available to them from both

>> >> their workstation and their TS session.

>> >>

>> >> I don't understand what you say about "As long as it's a

>> >> terminal server, it won't log me on to the console session

>> >> of the server, but instead a session inside the terminal

>> >> server manager".

>> >>

>> >> You can always make a connection to the console, with mstsc

>> >> /console. Doesn't matter if the server is configured for

>> >> Remote Desktop for Administration or for Terminal Services.

>> >>

>> >> And NO, you can NOT install applications just like on any

>> >> workstation. The application installation procedure on a TS

>> >> is rather special, to ensure multi.user functionality. The

>> >> server has to be in "install mode" when you install

>> >> applications, and no users can be connected to it while you

>> >> do so. Many applications also need some additional

>> >> adjustments after installation to make them work properly.

>> >>

>> >> I really suggest that you take your time to read up a bit on

>> >> this, and whatever you do, don't install and test on a

>> >> production server! Use any workstation-like PC and install

>> >> Windows Server + TS on it, just for testing purposes. Don't

>> >> bother about performance at this stage, it's sufficient if

>> >> the testserver can handle 2 or 3 sessions.

>> >> _________________________________________________________

>> >> Vera Noest

>> >> MCSE, CCEA, Microsoft MVP - Terminal Server

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

>> >> ___ please respond in newsgroup, NOT by private email ___

>> >>

>> >> =?Utf-8?B?cGV0ZTAwODU=?=

>> >> wrote on 25 sep 2007 in

>> >> microsoft.public.windows.terminal_services:

>> >>

>> >> > As for the TS profile path. Can it contain all the same

>> >> > files and folders as the regular roaming profile, but have

>> >> > a different path? Will this cause a problem. For ex if

>> >> > my profile path is \\server\profiles$\username. Then have

>> >> > a path of \\server\tsprofiles$\username but include all

>> >> > the same files.

>> >> >

>> >> > Think that helped with one question. I do want to test it

>> >> > first before buying any licenses to see how it would work

>> >> > in our environment. As long as it's a terminal server, it

>> >> > won't log me on to the console session of the server, but

>> >> > instead a session inside the terminal server manager as

>> >> > long as I buy licenses before the 120 days.

>> >> >

>> >> > I can also install applications as I would on the client

>> >> > workstation and they will be accessible without me doing

>> >> > anything else to it, correct?

>> >> >

>> >> > "Vera Noest [MVP]" wrote:

>> >> >

>> >> >> Yes, there is a grace period of 120 days, in which you

>> >> >> can test and use the Terminal Server, without the need to

>> >> >> install TS licenses. Just install Terminal Services, in

>> >> >> Control Panel - Add/Remove programs - Add Windows

>> >> >> components.

>> >> >>

>> >> >> And yes, users should have a TS profile which is

>> >> >> different from there normal profile. If you use the same

>> >> >> profile for their workstation and their TS sessions, a

>> >> >> lot of settings will not work, and the profiles will

>> >> >> become corrupt over time. These TS-specific profiles can

>> >> >> be local to the Terminal Server, or they can be roamin.

>> >> >> Just store them on a different share on your file server.

>> >> >>

>> >> >> There is really not one single link which explains it

>> >> >> all. That's why there are numerous *books* written on the

>> >> >> subject.

>> >> >>

>> >> >> You can find a number of links to articles about

>> >> >> planning, installation, etc on my website. Or read Brian

>> >> >> Madden's book again

>> >> >> :-) and then install TS on a test server and play around

>> >> >> :with it.

>> >> >> _________________________________________________________

>> >> >> Vera Noest

>> >> >> MCSE, CCEA, Microsoft MVP - Terminal Server

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

>> >> >> *----------- Please reply in newsgroup -------------*

>> >> >>

>> >> >> =?Utf-8?B?cGV0ZTAwODU=?=

>> >> >> wrote on 25 sep

>> >> >> 2007:

>> >> >>

>> >> >> > I would like to be able to test this. I remember

>> >> >> > reading something about allowing you a 180 day trial

>> >> >> > before you purchase a license. How would that work in

>> >> >> > this scennario where I or a couple users could try it

>> >> >> > out and see if it would be a proper solution.

>> >> >> >

>> >> >> > Someone else is giving me advice that the profile path

>> >> >> > for TS should not be the same as the roaming profiles.

>> >> >> > How would a user logon or how would the desktop follow

>> >> >> > the user if they aren't using the regular roaming

>> >> >> > profile. I admit I'm confused about this among other

>> >> >> > things.

>> >> >> >

>> >> >> > I've been reading an online book by brain madden that

>> >> >> > goes into detail about the design, but isn't as helpful

>> >> >> > for an admin trying to setup a TS server.

>> >> >> >

>> >> >> > A good link, article would be helpful.

>> >> >> > "Vera Noest [MVP]" wrote:

>> >> >> >

>> >> >> >> When users log on to the Terminal Server with the

>> >> >> >> Remote Desktop client, they *are* logging on remotely

>> >> >> >> to the server itself! There's really no difference

>> >> >> >> between Remote Desktop connections (to a server which

>> >> >> >> is configured for "Remote Desktop for Administration")

>> >> >> >> and Terminal Server connections (to a server which is

>> >> >> >> configured for "Terminal Services, i.e. in application

>> >> >> >> mode).

>> >> >> >>

>> >> >> >> And the server has no way of knowing why someone logs

>> >> >> >> on or what they are going to do on the server, that's

>> >> >> >> why *all* connections to a server configured for

>> >> >> >> terminal Services need a license. The only exception

>> >> >> >> is a single connection to the console of the server

>> >> >> >> (with mstsc /console), which is always free of TS CAL

>> >> >> >> requirements.

>> >> >> >>

>> >> >> >> Ideally, a Terminal Server should be a dedicated

>> >> >> >> server, both for performance and security reasons. But

>> >> >> >> in small environments, this isn't always realistic. So

>> >> >> >> you can also use the same server as a file server, but

>> >> >> >> don't run TS on a Domain Controller, and don't combine

>> >> >> >> it with SQL or Exchange if you can avoid it.

>> >> >> >> _______________________________________________________

>> >> >> >> __ Vera Noest MCSE, CCEA, Microsoft MVP - Terminal

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

>> >> >> >> ___ please respond in newsgroup, NOT by private email

>> >> >> >> ___

>> >> >> >>

>> >> >> >> =?Utf-8?B?cGV0ZTAwODU=?=

>> >> >> >> wrote on 25 sep

>> >> >> >> 2007 in microsoft.public.windows.terminal_services:

>> >> >> >>

>> >> >> >> > I mean does it have to be a deticated server or

>> >> >> >> > could I host it an another server that acts as an

>> >> >> >> > application server for one of our programs or what

>> >> >> >> > is typically recommended for a small environment

>> >> >> >> > where it will not be heavily used.

>> >> >> >> >

>> >> >> >> > Also, how does the server know you are not logging

>> >> >> >> > on remotely as you would with remote desktop? Lets

>> >> >> >> > say a regular user wants to logon to the terminal

>> >> >> >> > server, how does it figure out they are not trying

>> >> >> >> > to logon to the server to perform maintenance on the

>> >> >> >> > server, etc.

>> >> >> >> >

>> >> >> >> > That has confused me a bit. I'm guessing users use

>> >> >> >> > the remote desktop connection to connect to the

>> >> >> >> > terminal server. I just want to ensure they are

>> >> >> >> > logging on to their terminal session and not

>> >> >> >> > actually logging on to the server itself. Does this

>> >> >> >> > make any sense with what I'm trying to say???

>> >> >> >> >

>> >> >> >> > "Munindra Das [MSFT]" wrote:

>> >> >> >> >

>> >> >> >> >> The article at

>> >> >> >> >> http://technet2.microsoft.com/windowsserver/en/libra

>> >> >> >> >> ry/ cb2 019 37-

>> >> >> >> >> 8f68-4d0f-9521-99e090ddd6b11033.mspx?mfr=true

>> >> >> >> >> will provide you with some details on how to plan a

>> >> >> >> >> terminal server. But it will also depend on what

>> >> >> >> >> Windows (2000, 2003) you are running and what

>> >> >> >> >> applications the users are likely to run. For a

>> >> >> >> >> 2003 Terminal Server with 12 users, you will

>> >> >> >> >> require a minimum of 128 MB memory.

>> >> >> >> >>

>> >> >> >> >> I am not sure what you mean by "Could it be an

>> >> >> >> >> another application server or does it have to be a

>> >> >> >> >> deditcated server". You can please provide a little

>> >> >> >> >> more detail.

>> >> >> >> >>

>> >> >> >> >> --

>> >> >> >> >> This posting is provided "AS IS" with no

>> >> >> >> >> warranties, and confers no rights. "pete0085"

>> >> >> >> >> wrote in

>> >> >> >> >> message

>> >> >> >> >> news:1E25A8B3-6BF5-4A33-B8B1-9615384FDCCD@microsoft.

>> >> >> >> >> com ...

>> >> >> >> >> > Brief question about server requirement for a

>> >> >> >> >> > single terminal server.

>> >> >> >> >> >

>> >> >> >> >> > There would be a max of 12 users accessing the

>> >> >> >> >> > server at one time. With disk space not being an

>> >> >> >> >> > issue, what would be a recommendation for memory

>> >> >> >> >> > for such a server?

>> >> >> >> >> >

>> >> >> >> >> > Could it be an another application server or does

>> >> >> >> >> > it have to be a deditcated

>> >> >> >> >> > server?

>> >> >> >> >> >

>> >> >> >> >> > Can someone briefly explain why accessing

>> >> >> >> >> > resources through a terminal server doesn't take

>> >> >> >> >> > up as much bandwidth and is faster then accessing

>> >> >> >> >> > it over a Wan link?

 

 

 

Top


 

 

 

From: waynea@tek.com

To: none

Subject: Re: Roaming Profile Directories are not deleted

Date: 09/26/2007 18:05:04

 

 

Hi -

In the Quick Launch Bar, we usually just have the various Office

icons (Outlook, Word, Excel, PPT), IE, an explorer icon and the 'show

desktop' icon.

 

 

 

 

Top


 

 

 

From: Munindra Das [MSFT] <munind@online.microsoft.com>

To: none

Subject: Re: Remote desktop Web Connection

Date: 09/28/2007 13:33:01

 

 

Can the user open the TS Web client website (http://server_name/tsweb)? If

they cannot access the website itself, please check your IIS installation,

policies, firewall, etc. If they can get to the website, do they get the

prompt to install the ActiveX control? At what point do the connection

fails?

 

--

This posting is provided "AS IS" with no warranties, and confers no rights.

"Reboot" wrote in message

news:20C4437F-80DB-4626-8472-3E3FD7CD6BD0@microsoft.com...

>I am trying to setup the remote desktop web connection on our website so

>that

> users can connect to the terminal server, but unfortunately it doesn’t

> work,

> but whenever the user connect using the remote desktop connection they can

> connect. I am running terminal server on win 2003, IIS 6.0 and ASP is

> enabled

> but I don understand why it doesn't work please help.

> --

> Boot

 

 

 

Top


 

 

 

From: Reboot <Reboot@discussions.microsoft.com>

To: none

Subject: Re: Remote desktop Web Connection

Date: 09/28/2007 15:24:01

 

 

Hi Munindra,

 

The connection fails after the installation of the Activex control. I have

checked the firewall and IIS all is working fine. but remote desktop web

connection would not connect to the server.

--

Boot

 

 

"Munindra Das [MSFT]" wrote:

 

> Can the user open the TS Web client website (http://server_name/tsweb)? If

> they cannot access the website itself, please check your IIS installation,

> policies, firewall, etc. If they can get to the website, do they get the

> prompt to install the ActiveX control? At what point do the connection

> fails?

>

> --

> This posting is provided "AS IS" with no warranties, and confers no rights.

> "Reboot" wrote in message

> news:20C4437F-80DB-4626-8472-3E3FD7CD6BD0@microsoft.com...

> >I am trying to setup the remote desktop web connection on our website so

> >that

> > users can connect to the terminal server, but unfortunately it doesn’t

> > work,

> > but whenever the user connect using the remote desktop connection they can

> > connect. I am running terminal server on win 2003, IIS 6.0 and ASP is

> > enabled

> > but I don understand why it doesn't work please help.

> > --

> > Boot

>

>

 

 

 

Top


 

 

 

From: Vera Noest [MVP] <vera.noest@remove-this.hem.utfors.se>

To: none

Subject: Re: Remote desktop Web Connection

Date: 09/28/2007 15:41:56

 

 

Is port 3389 on your firewall pointing to the private IP number of

your Terminal Server?

The client will still need to communicate directly with the TS on

port 3389.

 

_________________________________________________________

Vera Noest

MCSE, CCEA, Microsoft MVP - Terminal Server

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

___ please respond in newsgroup, NOT by private email ___

 

=?Utf-8?B?UmVib290?= wrote on

28 sep 2007 in microsoft.public.windows.terminal_services:

 

> Hi Munindra,

>

> The connection fails after the installation of the Activex

> control. I have checked the firewall and IIS all is working

> fine. but remote desktop web connection would not connect to the

> server.

 

 

 

Top


 

 

 

From: DHL <DHL@discussions.microsoft.com>

To: none

Subject: RE: Remote Desktop Connection (Terminal Services Client 6.0)

Date: 09/29/2007 18:00:01

 

 

Vera, niether of these links are valid. Please advise.

 

"Vera Noest [MVP]" wrote:

 

> Check this:

>

> Vista Remote Desktop Connection Authentication FAQ

> http://blogs.msdn.com/ts/archive/2007/01/22/vista-remote-desktop-

> connection-authentication-faq.aspx

>

> and this:

>

> TS connection experience improvements based on RDP 6.0 client

> customer feedback

> http://blogs.msdn.com/ts/archive/2007/03/28/ts-connection-

> experience-improvements-based-on-rdp-6-0-client-customer-

> feedback.aspx

>

> _________________________________________________________

> Vera Noest

> MCSE, CCEA, Microsoft MVP - Terminal Server

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

> ___ please respond in newsgroup, NOT by private email ___

>

> =?Utf-8?B?REhM?= wrote on 02 sep

> 2007 in microsoft.public.windows.terminal_services:

>

> > I think I am having the same issue. When using the new RDP

> > client, when I type the host name or IP Address of the computer

> > I want to connect to, the computer host name or IP Address is

> > appended to the username when the "Enter Credientials" windows

> > is presented. Can someone help with this please. This is very

> > frustrating.

> >

> > "Q" wrote:

> >

> >> Is there a way to keep only the user name in the username field

> >> instead of servername\username?

> >>

> >> Thanks

>

 

 

 

Top


 

 

 

From: DHL <DHL@discussions.microsoft.com>

To: none

Subject: RE: Remote Desktop Connection (Terminal Services Client 6.0)

Date: 09/29/2007 18:00:02

 

 

Hi Vera, niethe rof these links are valid. Please advise.

 

"Vera Noest [MVP]" wrote:

 

> Check this:

>

> Vista Remote Desktop Connection Authentication FAQ

> http://blogs.msdn.com/ts/archive/2007/01/22/vista-remote-desktop-

> connection-authentication-faq.aspx

>

> and this:

>

> TS connection experience improvements based on RDP 6.0 client

> customer feedback

> http://blogs.msdn.com/ts/archive/2007/03/28/ts-connection-

> experience-improvements-based-on-rdp-6-0-client-customer-

> feedback.aspx

>

> _________________________________________________________

> Vera Noest

> MCSE, CCEA, Microsoft MVP - Terminal Server

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

> ___ please respond in newsgroup, NOT by private email ___

>

> =?Utf-8?B?REhM?= wrote on 02 sep

> 2007 in microsoft.public.windows.terminal_services:

>

> > I think I am having the same issue. When using the new RDP

> > client, when I type the host name or IP Address of the computer

> > I want to connect to, the computer host name or IP Address is

> > appended to the username when the "Enter Credientials" windows

> > is presented. Can someone help with this please. This is very

> > frustrating.

> >

> > "Q" wrote:

> >

> >> Is there a way to keep only the user name in the username field

> >> instead of servername\username?

> >>

> >> Thanks

>

 

 

 

Top


 

 

 

From: DHL <DHL@discussions.microsoft.com>

To: none

Subject: RE: Remote Desktop Connection (Terminal Services Client 6.0)

Date: 09/29/2007 18:30:00

 

 

Hi Vear, I was able to connect to the link

 

The explantion on the post is as follows:

How to remove invalid pre-populated domain names

Some users have noticed that an invalid pre-populated domain name is placed

in front of the user name in the credential dialog. Users are frustrated at

having to delete this bad domain on every connection. The sequence of steps

causing this behavior is as follows:

 

User wants to connect to a machine via IP address, say 127.0.0.1.

He enters the correct password and username “Administrator”. He successfully

logs on.

The next time he attempts to connect to 127.0.0.1, he sees in the “User

name” field of the credentials dialog “127.0.0.1\Administrator”. The user

deletes the text “127.0.0.1\” from the user name field and logs on. On

successive connections, he is forced to keep deleting this extraneous text.

Answer: When a domain is not presented for the username, Remote Desktop

assumes by default that a local server account will be used and the domain

name is pre-filled accordingly. In this case, the server name entered was

“127.0.0.1”, and as a result, the domain entered was the same. This was done

for various reasons in Vista that are too complicated (and irrelevant) to go

into detail here.

 

The best workaround for this behavior is to always enter a proper domain

into the credentials dialog. If you are connecting to machine “MyMachine”

using the “Administrator” account, do not just enter “Administrator” as the

username, enter “MyMachine\Administrator”. From there on out, the proper

domain and username will be prepopulated in the credentials dialog.

Alternatively, if the user account is an account named “DomainUser” in the

domain “MyDomain”, use “MyDomain\DomainUser” instead of just “DomainUser”.

 

PROBLEM: thsi is nor a solution. What if the computer I am connecting to is

not a server, hence no domain, or a workgroup server, not domain server. I

need to know how to disbale this function completely. If that is not

possible, than provide instructions for uninstalling so I can install RDP 5.

 

Doug

 

"Vera Noest [MVP]" wrote:

 

> Check this:

>

> Vista Remote Desktop Connection Authentication FAQ

> http://blogs.msdn.com/ts/archive/2007/01/22/vista-remote-desktop-

> connection-authentication-faq.aspx

>

> and this:

>

> TS connection experience improvements based on RDP 6.0 client

> customer feedback

> http://blogs.msdn.com/ts/archive/2007/03/28/ts-connection-

> experience-improvements-based-on-rdp-6-0-client-customer-

> feedback.aspx

>

> _________________________________________________________

> Vera Noest

> MCSE, CCEA, Microsoft MVP - Terminal Server

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

> ___ please respond in newsgroup, NOT by private email ___

>

> =?Utf-8?B?REhM?= wrote on 02 sep

> 2007 in microsoft.public.windows.terminal_services:

>

> > I think I am having the same issue. When using the new RDP

> > client, when I type the host name or IP Address of the computer

> > I want to connect to, the computer host name or IP Address is

> > appended to the username when the "Enter Credientials" windows

> > is presented. Can someone help with this please. This is very

> > frustrating.

> >

> > "Q" wrote:

> >

> >> Is there a way to keep only the user name in the username field

> >> instead of servername\username?

> >>

> >> Thanks

>

 

 

 

Top


 

 

 

From: TP <tperson.knowspamn@mailandnews.com>

To: none

Subject: Re: Remote Desktop Connection (Terminal Services Client 6.0)

Date: 09/29/2007 19:07:14

 

 

Hi Doug,

 

You can remove the new client through add/remove programs,

make sure Show updates is checked. The 6.0 client shows up

as KB925876 in the list.

 

-TP

 

DHL wrote:

> Hi Vear, I was able to connect to the link

>

> The explantion on the post is as follows:

> ...

>

> PROBLEM: thsi is nor a solution. What if the computer I am

> connecting to is not a server, hence no domain, or a workgroup

> server, not domain server. I need to know how to disbale this

> function completely. If that is not possible, than provide

> instructions for uninstalling so I can install RDP 5.

>

> Doug

 

 

 

Top


 

 

 

From: Vera Noest [MVP] <vera.noest@remove-this.hem.utfors.se>

To: none

Subject: Re: Remote Desktop (2003 Server) stops working, bounces initial connection attempt

Date: 09/25/2007 13:54:32

 

 

That's correct, you can't restart the terminal Services service.

I don't think that that's the problem either, since you can connect

and login.

 

Has this always been a problem with this server? If not, was

something changed directly before the start of the problem?

Which SP is the server running?

Any warnings or errors in the EventLog on the server when this

happens?

Similar problems are sometimes reported with certain video drivers

on the server. Updated yours lately?

_________________________________________________________

Vera Noest

MCSE, CCEA, Microsoft MVP - Terminal Server

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

___ please respond in newsgroup, NOT by private email ___

 

"Paul" wrote on 25 sep 2007 in

microsoft.public.windows.terminal_services:

 

> When I remote desktop into my Windows 2003 Server from Windows

> XP Pro, I enter my username and password into the local remote

> desktop dialog. The connection is established to the server.

> Screen goes black for a second like it's about to succeed, then

> bounces back out to the local username/password dialog. The

> only cure for this is to reboot the server. This doesn't happen

> often but it does seem to happen after a remote desktop

> connection over a poor/flaky/slow internet connection, like the

> server side remote desktop process gets confused by junk packets

> and never recovers.

>

> Is it possible to just restart "remote desktop service" without

> rebooting the whole server? I thought I read somewhere this

> isn't possible because "remote desktop" is integrated too deeply

> into the OS ?

>

> -- Paul

 

 

 

Top


 

 

 

From: Paul <paule@nospam-mindspring.com>

To: none

Subject: Re: Remote Desktop (2003 Server) stops working, bounces initial connection attempt

Date: 09/25/2007 19:33:44

 

 

It has always been a problem with this server ( Dell PowerEdge 1600SC )

when it ran Windows 2003 Ent. no SP, SP1, and now SP2. It has been a

problem with the previous version of mstsc.exe client (5.x) as well as the

current version (6.x) This problem is the main reason I installed a Dell

DRAC controller card in the server so I have the ability to reboot it when

the RDP console connection fails.

 

EventLog is mostly loaded with TermServDevices errors relating to missing

printer drivers when the client connects. I can't really see anything in

the log at the specific moment the client attempt to connect and fails.

 

The onboard video is ATI RAGE XL PCI with a driver version 5.10.2600.6014,

and according to Device Manager > Update Driver is the latest version

available.

 

-- Paul

 

 

 

"Vera Noest [MVP]" wrote in message

news:Xns99B6D4B2DC217veranoesthemutforsse@207.46.248.16...

> That's correct, you can't restart the terminal Services service.

> I don't think that that's the problem either, since you can connect

> and login.

>

> Has this always been a problem with this server? If not, was

> something changed directly before the start of the problem?

> Which SP is the server running?

> Any warnings or errors in the EventLog on the server when this

> happens?

> Similar problems are sometimes reported with certain video drivers

> on the server. Updated yours lately?

> _________________________________________________________

> Vera Noest

> MCSE, CCEA, Microsoft MVP - Terminal Server

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

> ___ please respond in newsgroup, NOT by private email ___

>

> "Paul" wrote on 25 sep 2007 in

> microsoft.public.windows.terminal_services:

>

>> When I remote desktop into my Windows 2003 Server from Windows

>> XP Pro, I enter my username and password into the local remote

>> desktop dialog. The connection is established to the server.

>> Screen goes black for a second like it's about to succeed, then

>> bounces back out to the local username/password dialog. The

>> only cure for this is to reboot the server. This doesn't happen

>> often but it does seem to happen after a remote desktop

>> connection over a poor/flaky/slow internet connection, like the

>> server side remote desktop process gets confused by junk packets

>> and never recovers.

>>

>> Is it possible to just restart "remote desktop service" without

>> rebooting the whole server? I thought I read somewhere this

>> isn't possible because "remote desktop" is integrated too deeply

>> into the OS ?

>>

>> -- Paul

>

 

 

 

Top


 

 

 

From: Vera Noest [MVP] <vera.noest@remove-this.hem.utfors.se>

To: none

Subject: Re: Remote Desktop (2003 Server) stops working, bounces initial connection attempt

Date: 09/26/2007 07:40:17

 

 

And when this happens, does the server still function normally in

all other respects?

Can you connect to a shared folder on the server?

Can you connect to the server by running TS Manager on another

computer? If you can, are there any sessions present on the server?

If so, in which state?

_________________________________________________________

Vera Noest

MCSE, CCEA, Microsoft MVP - Terminal Server

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

___ please respond in newsgroup, NOT by private email ___

 

"Paul" wrote on 26 sep 2007 in

microsoft.public.windows.terminal_services:

 

> It has always been a problem with this server ( Dell PowerEdge

> 1600SC ) when it ran Windows 2003 Ent. no SP, SP1, and now SP2.

> It has been a problem with the previous version of mstsc.exe

> client (5.x) as well as the current version (6.x) This problem

> is the main reason I installed a Dell DRAC controller card in

> the server so I have the ability to reboot it when the RDP

> console connection fails.

>

> EventLog is mostly loaded with TermServDevices errors relating

> to missing printer drivers when the client connects. I can't

> really see anything in the log at the specific moment the client

> attempt to connect and fails.

>

> The onboard video is ATI RAGE XL PCI with a driver version

> 5.10.2600.6014, and according to Device Manager > Update Driver

> is the latest version available.

>

> -- Paul

>

>

>

> "Vera Noest [MVP]" wrote

> in message

> news:Xns99B6D4B2DC217veranoesthemutforsse@207.46.248.16...

>> That's correct, you can't restart the terminal Services

>> service. I don't think that that's the problem either, since

>> you can connect and login.

>>

>> Has this always been a problem with this server? If not, was

>> something changed directly before the start of the problem?

>> Which SP is the server running?

>> Any warnings or errors in the EventLog on the server when this

>> happens?

>> Similar problems are sometimes reported with certain video

>> drivers on the server. Updated yours lately?

>> _________________________________________________________

>> Vera Noest

>> MCSE, CCEA, Microsoft MVP - Terminal Server

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

>> ___ please respond in newsgroup, NOT by private email ___

>>

>> "Paul" wrote on 25 sep 2007 in

>> microsoft.public.windows.terminal_services:

>>

>>> When I remote desktop into my Windows 2003 Server from Windows

>>> XP Pro, I enter my username and password into the local remote

>>> desktop dialog. The connection is established to the server.

>>> Screen goes black for a second like it's about to succeed,

>>> then bounces back out to the local username/password dialog.

>>> The only cure for this is to reboot the server. This doesn't

>>> happen often but it does seem to happen after a remote desktop

>>> connection over a poor/flaky/slow internet connection, like

>>> the server side remote desktop process gets confused by junk

>>> packets and never recovers.

>>>

>>> Is it possible to just restart "remote desktop service"

>>> without rebooting the whole server? I thought I read

>>> somewhere this isn't possible because "remote desktop" is

>>> integrated too deeply into the OS ?

>>>

>>> -- Paul

 

 

 

Top


 

 

 

From: Paul <paule@nospam-mindspring.com>

To: none

Subject: Re: Remote Desktop (2003 Server) stops working, bounces initial connection attempt

Date: 09/26/2007 12:00:22

 

 

I'll note your suggestions for the next time this occurs. It's hard to

reproduce. The server does seem to continue to operate normally in all

other respects (IIS, FTP, mail, etc.) Thanks.

 

-- Paul

 

 

"Vera Noest [MVP]" wrote in message

news:Xns99B7953F57DDveranoesthemutforsse@207.46.248.16...

> And when this happens, does the server still function normally in

> all other respects?

> Can you connect to a shared folder on the server?

> Can you connect to the server by running TS Manager on another

> computer? If you can, are there any sessions present on the server?

> If so, in which state?

> _________________________________________________________

> Vera Noest

> MCSE, CCEA, Microsoft MVP - Terminal Server

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

> ___ please respond in newsgroup, NOT by private email ___

>

> "Paul" wrote on 26 sep 2007 in

> microsoft.public.windows.terminal_services:

>

>> It has always been a problem with this server ( Dell PowerEdge

>> 1600SC ) when it ran Windows 2003 Ent. no SP, SP1, and now SP2.

>> It has been a problem with the previous version of mstsc.exe

>> client (5.x) as well as the current version (6.x) This problem

>> is the main reason I installed a Dell DRAC controller card in

>> the server so I have the ability to reboot it when the RDP

>> console connection fails.

>>

>> EventLog is mostly loaded with TermServDevices errors relating

>> to missing printer drivers when the client connects. I can't

>> really see anything in the log at the specific moment the client

>> attempt to connect and fails.

>>

>> The onboard video is ATI RAGE XL PCI with a driver version

>> 5.10.2600.6014, and according to Device Manager > Update Driver

>> is the latest version available.

>>

>> -- Paul

>>

>>

>>

>> "Vera Noest [MVP]" wrote

>> in message

>> news:Xns99B6D4B2DC217veranoesthemutforsse@207.46.248.16...

>>> That's correct, you can't restart the terminal Services

>>> service. I don't think that that's the problem either, since

>>> you can connect and login.

>>>

>>> Has this always been a problem with this server? If not, was

>>> something changed directly before the start of the problem?

>>> Which SP is the server running?

>>> Any warnings or errors in the EventLog on the server when this

>>> happens?

>>> Similar problems are sometimes reported with certain video

>>> drivers on the server. Updated yours lately?

>>> _________________________________________________________

>>> Vera Noest

>>> MCSE, CCEA, Microsoft MVP - Terminal Server

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

>>> ___ please respond in newsgroup, NOT by private email ___

>>>

>>> "Paul" wrote on 25 sep 2007 in

>>> microsoft.public.windows.terminal_services:

>>>

>>>> When I remote desktop into my Windows 2003 Server from Windows

>>>> XP Pro, I enter my username and password into the local remote

>>>> desktop dialog. The connection is established to the server.

>>>> Screen goes black for a second like it's about to succeed,

>>>> then bounces back out to the local username/password dialog.

>>>> The only cure for this is to reboot the server. This doesn't

>>>> happen often but it does seem to happen after a remote desktop

>>>> connection over a poor/flaky/slow internet connection, like

>>>> the server side remote desktop process gets confused by junk

>>>> packets and never recovers.

>>>>

>>>> Is it possible to just restart "remote desktop service"

>>>> without rebooting the whole server? I thought I read

>>>> somewhere this isn't possible because "remote desktop" is

>>>> integrated too deeply into the OS ?

>>>>

>>>> -- Paul

 

 

 

Top


 

 

 

From: Semir Hadzic <semir@gradpula.com>

To: none

Subject: Re: RDP shows blue screen for 2 to 5 minutes before icons come up.

Date: 09/28/2007 04:30:23

 

 

Do you have NOD32 installed, or something like that?

 

Semir.

 

"Vera Noest [MVP]" wrote in message

news:Xns99A8E39233B83veranoesthemutforsse@207.46.248.16...

> Have you checked the EventLog on the server?

> Sounds like it is the loading and unloading of the profile which

> takes so long.

> Have you checked the size of the user profile?

> If the user environment is misconfigured (f.e. with the home folder

> being part of the user profile), then profiles can become huge in

> size.

>

> Could be processing of Group Policies also.

>

> You can enable verbose logging of the user environment on the

> server to see how long the different phases of the logon process

> take.

>

> 221833 - How to enable user environment debug logging in retail

> builds of Windows

> http://support.microsoft.com/?kbid=221833

> _________________________________________________________

> Vera Noest

> MCSE, CCEA, Microsoft MVP - Terminal Server

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

> ___ please respond in newsgroup, NOT by private email ___

>

> =?Utf-8?B?bWhlaW5lbWFubg==?= wrote on

> 11 sep 2007 in microsoft.public.windows.terminal_services:

>

>> I have a Small Business Server 2003 and a Terminal server 2003

>> (two different boxes). This is a new customer so I do not know

>> how long it has been happening. When we DRP into the Terminal

>> Server box everything pops up great except between the login and

>> when the icons pop up. The time it takes after you type in the

>> password and when icons pop up is about 3 to 5 minutes. When

>> we try to get out of it the time is about the same - forever.

>>

>> I have tried to reduce all processes to nothing, no sharing of

>> hard drive, resolution to 16 bit, no printing, sound, nothing.

>>

>> Tried the command line trick and that did not work.

>>

>> Any help would be appreciated.

 

 

 

Top


 

 

 

From: Munindra Das [MSFT] <munind@online.microsoft.com>

To: none

Subject: Re: RDP local drives missing

Date: 09/29/2007 17:27:43

 

 

Does it happen only with the 6.0 client or with the older client (5.2) as

well?

 

--

This posting is provided "AS IS" with no warranties, and confers no rights.

"dvendt" wrote in message

news:3302BC1F-3319-47E7-A1BB-A04A2270F034@microsoft.com...

> Using RDP v6, connect to 2 different w2k3 servers, both domain controllers

> in

> the same domain. I am able to see my local drives as "drive_letter" on

> "local_computer_name" on one of the servers, but not the other. I have

> checked gpo settings, user profile environment settings, and RDP-TCP

> client

> settings, and they are all configured the same. Do you know what the

> problem

> could be.?

> Thanks

 

 

 

Top


 

 

 

From: dvendt <dvendt@discussions.microsoft.com>

To: none

Subject: Re: RDP local drives missing

Date: 10/01/2007 15:36:05

 

 

It happens on both vesions of the client.

 

"Munindra Das [MSFT]" wrote:

 

> Does it happen only with the 6.0 client or with the older client (5.2) as

> well?

>

> --

> This posting is provided "AS IS" with no warranties, and confers no rights.

> "dvendt" wrote in message

> news:3302BC1F-3319-47E7-A1BB-A04A2270F034@microsoft.com...

> > Using RDP v6, connect to 2 different w2k3 servers, both domain controllers

> > in

> > the same domain. I am able to see my local drives as "drive_letter" on

> > "local_computer_name" on one of the servers, but not the other. I have

> > checked gpo settings, user profile environment settings, and RDP-TCP

> > client

> > settings, and they are all configured the same. Do you know what the

> > problem

> > could be.?

> > Thanks

>

>

 

 

 

Top


 

 

 

From: Helge Klein <Helge.Klein@googlemail.com>

To: none

Subject: Re: RDP Compression

Date: 09/28/2007 08:06:19

 

 

I do not think that disabling RDP compression is possible.

 

Just out of curiosity: Why do you want to do that? To unload the CPU?

 

Helge

 

==================

Please visit my blog:

http://it-from-inside.blogspot.com

==================

 

On 28 Sep., 00:03, Julio wrote:

> Is it possible to completely disable RDP compression? If so, how? We are

> currently using RDP ver.5.2 ?

>

> Thanks.

>

> J

 

 

 

 

Top


 

 

 

From: Julio <Julio@discussions.microsoft.com>

To: none

Subject: Re: RDP Compression

Date: 09/28/2007 09:00:02

 

 

The reason I need to do that is because we are testing RDP traffic on our WAN

and are using a WAN optimization device that requires us to disable the

compression if possible.

 

"Helge Klein" wrote:

 

> I do not think that disabling RDP compression is possible.

>

> Just out of curiosity: Why do you want to do that? To unload the CPU?

>

> Helge

>

> ==================

> Please visit my blog:

> http://it-from-inside.blogspot.com

> ==================

>

> On 28 Sep., 00:03, Julio wrote:

> > Is it possible to completely disable RDP compression? If so, how? We are

> > currently using RDP ver.5.2 ?

> >

> > Thanks.

> >

> > J

>

>

>

 

 

 

Top


 

 

 

From: TP <tperson.knowspamn@mailandnews.com>

To: none

Subject: Re: RDP Compression

Date: 09/28/2007 11:56:44

 

 

Hi,

 

I would recommend you contact riverbed and ask them if

they *actually* claim to optimize RDP applications at a

deep level. For regular business apps RDP is already

highly optimized with intelligent caching and compression.

 

As you most likely already know, RDP benefits from any

device that smooths out the traffic flow, reduces latency,

gives priority to RDP traffic, guarantees minimum bandwidth

for each session, etc.

 

There are opportunities to optimize RDP traffic if they wanted

to. For example, in a case where large files are transferred

over RDP, or video/audio streaming, they could cache this on

their device and thus avoid transferring more than once.

Another potential would be to cache bitmaps so that these

would only be transferred over the WAN once, but then it

would need to take over the job of generating bitmap

hashes and instructing each client which cache cell to store it in.

 

Doing the above is complex and would require substantial

investment. They would need to license the protocol, program

their hardware to decrypt/decompress/compress/encrypt (unless

they developed a software piece that ran on the TS) the

stream, examine the traffic for file transfers, video playback,

bitmaps, etc. And if they accomplished the above the

product would likely only benefit a small subset of TS installs

which may or may not be enough to justify development costs.

 

If they have done even a portion of the optimizing techniques

for RDP I describe above I am certain they would be more than

happy to tell you about and rightly so.

 

-TP

 

Julio wrote:

> Is it possible to completely disable RDP compression? If so, how? We

> are currently using RDP ver.5.2 ?

>

> Thanks.

>

> J

 

 

 

Top


 

 

 

From: TP <tperson.knowspamn@mailandnews.com>

To: none

Subject: Re: RDP Compression

Date: 09/28/2007 12:16:39

 

 

I forgot to mention that in the past you could disable

compression in older versions of the client. The setting

for it is still in the .rdp file. Open it up in notepad and

change the 1 to a 0.

 

I am not sure if the compression setting is actually

honored or ignored in the latest clients.

 

-TP

 

Julio wrote:

> Is it possible to completely disable RDP compression? If so, how? We

> are currently using RDP ver.5.2 ?

>

> Thanks.

>

> J

 

 

 

Top


 

 

 

From: Julio <Julio@discussions.microsoft.com>

To: none

Subject: Re: RDP Compression

Date: 09/28/2007 12:39:01

 

 

Thanks for the great info "TP".

 

"TP" wrote:

 

> I forgot to mention that in the past you could disable

> compression in older versions of the client. The setting

> for it is still in the .rdp file. Open it up in notepad and

> change the 1 to a 0.

>

> I am not sure if the compression setting is actually

> honored or ignored in the latest clients.

>

> -TP

>

> Julio wrote:

> > Is it possible to completely disable RDP compression? If so, how? We

> > are currently using RDP ver.5.2 ?

> >

> > Thanks.

> >

> > J

>

 

 

 

Top


 

 

 

From: TP <tperson.knowspamn@mailandnews.com>

To: none

Subject: Re: RDP and Vista

Date: 09/20/2007 09:18:18

 

 

Hi,

 

Please read this document:

 

http://blogs.msdn.com/ts/archive/2007/01/22/vista-remote-desktop-connection-authentication-faq.aspx

 

If you want you can install and run the older Remote Desktop

Client on Vista. The install file for it is located on your 2003

server's drive here:

 

C:\WINDOWS\system32\clients\tsclient\win32\msrdpcli.msi

 

After it is installed make sure to launch it using the shortcut

under All Programs, not the shortcut under Accessories.

 

-TP

 

Chris wrote:

> This might sound like a stupid question but on my Vista box when I

> connect to a 2003 TS box with the RDP client it asks for Username and

> Password. Then, once it connects to the 2003 box it again asks for

> the information.

>

> Before it ever try's to connect it prompts me with a question that the

> "Remote Desktop cannot verify the identiy of the computer..." blah,

> blah however I figured out how to kill that messagebox with info from

> this page -

> "http://weblogs.asp.net/owscott/archive/2006/11/10/Vista_2700_s-Remote-Desktop-Prompt.aspx".

>

> RDP adds the IP address into the 'username' so it looks something like

> 66.7.243.91\Synergy. If I don't put any password in when I first

> click on the RDP connect button it doesn't string the IP into the

> 'username' field. However we like to keep the username ?

> the RDP except I cannot without the IP\Username begin populated. Is

> there a way around this?

 

 

 

Top


 

 

Post your questions, comments, feedbacks and suggestions