• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 180
  • Last Modified:

I have 25 users that connect to a Windows 2003 Standard Server, over RDP (Terminal Services). Is Microsft Clustering my only option to provide high availability?

In the event the server dies, what options do I have for high availability?   Clusterting under 2003 Enterprise version?  

I'd like a low cost solution if possible.
Thank you.
  • 2
2 Solutions
Henrik JohanssonSystems engineerCommented:
Don't use failover clustering for a TS.
Use NLB for load balancing between two (or more) servers. To keep down costs, NLB is available in Standard Edition
jvutechncAuthor Commented:
NLB sounds good.   What should I do to get the two servers identical in data then?  
Henrik JohanssonSystems engineerCommented:
If you mean profile data, configure users to have roaming TS profiles stored on common file server share.
Installation of applications like Office etc nead to be done on each node.

Re-connection to disconnected sessions on same node can't be guaranteed when not joining the nodes to Session Directory available for nodes running Enterprise Edition. If upgrading the TS-nodes to Windows Server 2008, the sequel replacement of Session Directory (Session Broker in 2008, Connection Broker in 2008R2) will be available for nodes running Standard Edition.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Free Tool: Subnet Calculator

The subnet calculator helps you design networks by taking an IP address and network mask and returning information such as network, broadcast address, and host range.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now