Terminal Server / Thin Client Implementation

[Guest D|an-0]

Environment (primary location)

 

System: Windows 2003 (Single Domain), XP Pro Clients, Exchange Server

2003, Outlook 2003 Clients, Terminal Server

 

WAN: T1

 

Users: 100 users. 30 Administration, 70 production

 

Hello,

 

I'd like the community's opinion on the following scenario.

 

We are planning to build a warehouse across the street from our primary

building. In the first phase, we expect to place 12 production users who

will need access to our production database. Eventually, we will have

all 70 production users in the warehouse. Since we have a terminal

server with only 10 users accessing it at our primary location, I am

thinking that we can purchase thin clients for the 12 users who will be

in the new warehouse. If I do this, the terminal server becomes a

mission critical machine, and I feel that we'd need to purchase a second

server to replicate the terminal server for failover purposes. To

assure reliable connectivity, I'm considering a dedicated peer to peer

T1 connection to link directly to our primary location.

 

What do you guys think of this implementation? Are there better solutions?

 

Thanks,

 

d|an-0

[Guest Scott]

RE: Terminal Server / Thin Client Implementation

 

We had the same situation and we connected the 2 networks with a Cisco 54g

WPA2 wireless solution. It was cheaper that 4 months T1 service and much

faster. We used directional antenna's from rooftop to rooftop.

 

"D|an-0" wrote:

> Environment (primary location)

>

> System: Windows 2003 (Single Domain), XP Pro Clients, Exchange Server

> 2003, Outlook 2003 Clients, Terminal Server

>

> WAN: T1

>

> Users: 100 users. 30 Administration, 70 production

>

> Hello,

>

> I'd like the community's opinion on the following scenario.

>

> We are planning to build a warehouse across the street from our primary

> building. In the first phase, we expect to place 12 production users who

> will need access to our production database. Eventually, we will have

> all 70 production users in the warehouse. Since we have a terminal

> server with only 10 users accessing it at our primary location, I am

> thinking that we can purchase thin clients for the 12 users who will be

> in the new warehouse. If I do this, the terminal server becomes a

> mission critical machine, and I feel that we'd need to purchase a second

> server to replicate the terminal server for failover purposes. To

> assure reliable connectivity, I'm considering a dedicated peer to peer

> T1 connection to link directly to our primary location.

>

> What do you guys think of this implementation? Are there better solutions?

>

> Thanks,

>

> d|an-0

>

[Guest George Yin]

RE: Terminal Server / Thin Client Implementation

 

Hello,

 

Thank you for posting in the partner newsgroups.

 

This question appears to be consulting in nature. Although this newsgroup

is here to provide break/fix resolution, we are happy to provide general

information and suggestions on it here and you may receive suggestions from

other partners on this topic both here and in the public newsgroup for this

product.

 

We would also like to introduce you to the Advisory Services team.

 

Advisory Services is a remotely delivered, hourly fee-based, consultative

support option that provides a comprehensive result beyond your break-fix

product maintenance needs. This support option includes working with the

same technician for assistance with issues like product migration, code

review, or new program development.

 

For more info in the US and Canada:

<http://support.microsoft.com/gp/advisoryservice>

 

Outside of the US/Canada:

<http://support.microsoft.com/common/international.aspx>

 

If you experience any specific break-fix issues, please feel free to open a

new thread in this newsgroup and we'll be very glad to work with you.

 

Sincerely,

George Yin

Microsoft Online Support

Microsoft Global Technical Support Center

 

Get Secure! - http://www.microsoft.com/security

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

When responding to posts, please "Reply to Group" via your newsreader so

that others may learn and benefit from your issue.

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

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

[Guest D|an-0]

Re: Terminal Server / Thin Client Implementation

 

Scott wrote:

> We had the same situation and we connected the 2 networks with a Cisco 54g

> WPA2 wireless solution. It was cheaper that 4 months T1 service and much

> faster. We used directional antenna's from rooftop to rooftop.

>

> "D|an-0" wrote:

>

>> Environment (primary location)

>>

>> System: Windows 2003 (Single Domain), XP Pro Clients, Exchange Server

>> 2003, Outlook 2003 Clients, Terminal Server

>>

>> WAN: T1

>>

>> Users: 100 users. 30 Administration, 70 production

>>

>> Hello,

>>

>> I'd like the community's opinion on the following scenario.

>>

>> We are planning to build a warehouse across the street from our primary

>> building. In the first phase, we expect to place 12 production users who

>> will need access to our production database. Eventually, we will have

>> all 70 production users in the warehouse. Since we have a terminal

>> server with only 10 users accessing it at our primary location, I am

>> thinking that we can purchase thin clients for the 12 users who will be

>> in the new warehouse. If I do this, the terminal server becomes a

>> mission critical machine, and I feel that we'd need to purchase a second

>> server to replicate the terminal server for failover purposes. To

>> assure reliable connectivity, I'm considering a dedicated peer to peer

>> T1 connection to link directly to our primary location.

>>

>> What do you guys think of this implementation? Are there better solutions?

>>

>> Thanks,

>>

>> d|an-0

>>

Scott, that sounds like a brilliant plan. How does the connection fair

in stormy weather conditions?

 

d|lan