XP SP2 Terminal Server Printing

Posted by support | Terminal Server | Thursday 22 March 2007 4:58 pm

This Microsoft fix allows your computer to print. It only needs to be run one time.
(Security settings in recent updates disable printing ports by default.)

  • You must be LOGGED OUT of the connection to do this.
  • Click to RDP Printer Script.
  • Please click “run” or “open”, which will open a DOS window.
  • Reboot your machine.
    • Permanent link to this post (58 words, 0 images, estimated 14 secs reading time)

    Microsoft Vista Terminal Server Security Settings

    Posted by support | Terminal Server, Vista | Thursday 22 March 2007 4:49 pm

    This Microsoft fix allows your Vista computer to connect to Terminal Servers. It only needs to be run one time.
    (Security settings in Vista are not compatible. Disabled RDP ports by default.)

  • You must be LOGGED OUT of the connection to do this.
  • Click to Vista RDP Script
  • Please click “Save” to Desktop.
  • Right Click on the Batch file and click on Run as Administrator
  • Reboot your machine.
    • Permanent link to this post (69 words, 0 images, estimated 17 secs reading time)

    NLB Load Balance Terminal Server Farm

    Posted by support | Terminal Server | Wednesday 28 February 2007 10:13 am

    NLB (Network Load Balance) can be used to direct one name to multiply servers.  They are of course pros and cons to this type of load balance.1) Does not use resource load2) Does not work with some Vista Clients all the time (home edition)

    3) If Cluster IP and backend servers are on the same subnet, network is clogged

    4) NLB has to use Public IP addresses only. (I called Microsoft and Firewall (Boardware) and got them to agree what I should do for this type of environment.

    5) NLB can only use 31 Servers in a farm.
    This is a preview of NLB Load Balance Terminal Server Farm. Read the full post (207 words, 0 images, estimated 50 secs reading time)

    Enterprise TS Cluster OR Citrix

    Posted by support | Citrix, Terminal Server | Sunday 26 November 2006 8:52 pm

    Overview:
    Enterprise 2003 Server cluster can be a less costly way to have load balancing on Terminal Servers. However, if not network correctly it can cause all sorts of issues. These issues range from server load to the NLB heartbeat. Citrix has a solution, but the cost is a heavy factor. The “bottom line” comes to cost. The question an ASP has to ask: “What will the users pay?”

    To Know:
    The cluster must have public IP addresses in order for session directory to work correctly. If a user gets disconnected the TS servers must have a public IP in order for the user to get back to their session that is already open. Microsoft has confirmed this in their white papers. Session Directory PDF

    This is a preview of Enterprise TS Cluster OR Citrix. Read the full post (300 words, 0 images, estimated 1:12 mins reading time)