Solution for slow link??

[Guest pete0085]

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.

[Guest Helge Klein]

Re: Solution for slow link??

 

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 <pete0...@discussions.microsoft.com>

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.

[Guest pete0085]

Re: Solution for slow link??

 

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 <pete0...@discussions.microsoft.com>

> 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.

>

>

>