How to Load Balance two Citrix Web Interface Servers

Citrix’s Web Interface (WI) is a popular way for users to connect to their ICA applications running on Citrix Presentation Servers. Unfortunately, if a Web Interface server fails then users lose access to their applications.

Citrix’s Web Interface (WI) is a popular way for users to connect to their ICA applications running on Citrix Presentation Servers. Unfortunately, if a Web Interface server fails then users lose access to their applications. Since WI also provides the back-end functionality for Citrix’s Program Neighborhood Agent (PNA) client, a WI server failure also means no PNA users would be able to run any applications.

Therefore, ensuring that your WI server is always available is very important. The easiest way to ensure availability is to build a second server for redundancy. (duh!) This is easy to do (just buy another server, install WI, and configure it like the first one).

The challenge is in the load balancing. How do you balance your users across the two servers? Or, more importantly, how do you ensure that users are only routed to a working server if one of your WI servers fails?

Fortunately there are several options when it comes to load-balancing your WI servers, and some of the options are easy to configure and free!

Load Balancing Basics

Before we look at the specific techniques you can use, let’s take a quick look at the basics of load balancing. All web servers are simply web sites running at specific IP addresses. In a load-balanced world, two (or more) web servers “share” an IP address. (This is called a virtual IP address.) By doing so, web clients request the virtual IP address, and the load-balancing system figures out which physical server should receive the request and the request is sent to the proper server.

Load-balancing solutions can be hardware-based or software based. When using hardware load-balancing solutions, you have an appliance that you configure for a load-balanced group of servers. For example, you might configure your hardware load-balancer as such:

  • Virtual IP address: 192.168.1.4
  • Real IP addresses of servers that will receive incoming requests: 192.168.1.2, 192.168.1.3

In this case the load-balancing hardware would listen on 192.168.1.4 for incoming HTTP requests. It would then act as a proxy or NAT and forward the request onto one of the backend servers (in this case 192.168.1.2 or 192.168.1.3). How does the load balancer know which server it should send incoming requests to? That depends on the load-balancer. Some have agents that run on each server and can balance based on perfmon counters. Others will use simply round-robin load balancing or they’ll make an HTTP request to each server to check its load.

The other key point to make about the hardware load balancers is that they’re smart enough to realize when a web server is not working, and they won’t direct any incoming client requests to non-working web servers. They also keep track of HTTP session cookies, so once a client establishes a connection with one of your web servers, the load balancer will ensure that that user is always routed to the same web server.

By the way, no one ever really calls these things “hardware load balancers.” Most vendors call them “application switches” or “Layer 7 switches” (or simply "L7 Switches") because they are like regular network switches except that they operate at the OSI Model Layer 7 (Application / HTTP) level instead of at the TCP/IP or MAC address level like regular network switches.

So how much do these things cost? A lot! The SMB version of Citrix’s NetScaler Application Switch is like $17,000! (And double that since you’ll want two for redundancy!) F5’s devices are in the same ballpark price-wise. They’re all pretty expensive except for a company called “Kemp Technologies” that has a two-server application switch for $2500. (Side note: This is what we use in front of the BrianMadden.com web servers.) While Kemp doesn't offer all the compression and caching features of the big boys, they offer great hardware-based application load balancing for a super price!

However, even $5000 (cause you'll want two of them since this is all about redundancy) is too expensive for some people. Fortunately you can also use the Windows Network Load Balancing (NLB) capabilities that are built-in to Windows Server 2003 for a zero-cost software-based load-balancing solution that will probably be sufficient for 99% of the people reading this.

How does Windows NLB work?

At its most basic level, Windows NLB is a network service that runs on each of your web servers. Each server has its own IP address, and then the Windows NLB service uses an additional virtual IP address that is shared among all the servers that you’re load-balancing. (So you’ll need an “extra” IP address from your network guys.)

The Windows NLB service runs on each server that you want to load-balance, and each server’s NLB service communicates with each other server’s NLB service. Behind the scenes, NLB works by “multihoming” each network card in each server so that each server listens for its own IP address plus the shared “virtual” IP address. Then, when an incoming request comes in for the shared virtual IP address, all of the servers receive it. They do a quick check to see which server should handle the request, and then whichever server is chosen handles all additional IP communication for that TCP/IP session. The client still communicates with the virtual IP address—it’s just that only one server actually responds to that communication. The others simply ignore the traffic.

Windows NLB understands “stateful” connections which means that it’s smart enough to check the session cookies in the HTTP protocol stream to ensure that once a client’s browser establishes a session with a particular server, it stays with that server for the duration or the web session. That’s important when you’re using WI, because the web server maintains an encryption key for each user that connects to the server so that it can decrypt the user’s credentials as they launch applications.

Some people say that Windows NLB is crap, but those are usually people who have some other load balancing solution they want to sell to you. Let me be clear on this: Windows NLB is not fancy and has some limitations. (Maximum of 32 nodes in the load-balance group, all servers must be on the same subnet, and load algorithms based solely on network usage.) However, for the purposes of load-balancing a few WI servers, it works great and the price is right!

The main reason that people choose a hardware load-balancer over a Windows NLB is because NLB isn’t very “smart” when it comes to checking to see if a server is online. Of course NLB will not direct any incoming requests to servers that crash, but what if your WI application itself crashes? This might mean that WI is not working, but if NLB is just looking to see if a server is online, it will continue to send users to a broken WI server. The hardware load balancers are more advanced and can typically “test” a website to check for a certain response to ensure that the web application is really working before sending users to it.

Configuring NLB

I won’t go through all the details of configuring Windows NLB because there are plenty of places to find that online. Basically you just install the NLB Service (via Add/Remove Programs | Windows Components) and pick the IP address that you’ll virtualize between the two servers. You don’t even need to connect any special cables between the two servers. All of the “heartbeat” communication takes place over the standard network interface. (This means you can still team your NICs into a single virtual NIC.)

Once you have your NLB configuration set, make sure your users access your WI via the shared virtual IP address—not the individual IP address of one of the servers. It’s probably best to create a DNS alias for the shared IP address. Using the same IP addresses from above, you might create the following DNS entries:

192.168.1.4 access.mycompany.com <-- shared virtual IP address
192.168.1.2 access1.mycompany.com <-- WI Server 1
192.168.1.3 access2.mycompany.com <-- WI Server 2

All your users can use “access.mycompany.com” as their website which will be load-balanced, but as an administrator you can still connect to access1 or access2 if you need to check something out on a particular server.

Load Balancing WI for Program Neighborhood Agent

If you’re using the PN Agent, then there is nothing more to do other than to make sure that you configure your PN Agent clients to pull their configuration XML files from the virtual IP address. (Don’t forget to copy the XML config files to all your WI servers.) Also, when you’re making your configuration, specify the virtual shared IP address (or the DNS name associated with it) as the location for the WI server.

What about Web Interface version 4?

WI4 has a centralized configuration service which the instruction manual claims is used for configuring the WI servers in load-balanced environments. It’s important to note that WI4 does NOT have out-of-the-box load balancing. All this configuration service does is store the WI server configuration in the IMA data store instead of storing it locally on each WI server in the webinterface.conf file. Even if you use this centralized configuration service, you’re still on your own when it comes to the actual load-balancing of your WI servers, and you’ll still have to use Windows NLB or Kemp or F5 or Citrix NetScaler or whatever.

In reality, the WI4 configuration service is kind of a pain to use, and most people just configure one WI4 server to be how they want it and then copy the webinterface.conf file to the other servers.

Conclusion

Load balancing WI servers is really simple. So go ahead and use NLB, or get fancy and buy an application switch. The bottom line is that you have options and the configuration is pretty straightforward.

Join the conversation

55 comments

Send me notifications when other members comment.

By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy

Please create a username to comment.

This is a really good article.  I enjoyed it.
Cancel
Great article. I have gone through these solutions myself and implemented Microsoft NLB and had it working great for 2 weeks in production. Unfortunately we have both NLB servers in VMware and there are a few issues with Microsoft NLB and VMWare. The following article lists the issue because I have set them up in unicast mode:
http://www.vmware.com/support/esx25/doc/admin/esx25admin_cluster_loadbal_esx.html
http://www.vmware.com/support/kb/enduser/std_adp.php?p_sid=lHNXXgVh&p_lva=&p_faqid=1556
Basically I don't want to disable Net.Notify switch because it affects all machines but I am having issues getting our comms guys to certify multicasting within the environment and I am not sure of the potential issues.

The issue is only found when VMotioning a server. Any ideas on how to get NLB working well within VM's :)

Just when we thought it was easy we added another level of complexity

Thanks
Mick
Cancel
Nice article again Brian, but people should not forget that combining NIC's into a virtual NIC and then load balancing this virtual often creates much problems, because switches are becoming nuts of all those (virtual) MAC addresses.
 
Therefore i would advise to use a single NIC for MS NLB. Also you must remember that when using Unicast mode with a single (physical) IP address those server can not communicate with each other anymore. Adding an additional IP address (with another NIC) can solve this issue.
Cancel
Hi Brian,
 
You mention that the WI config will be stored in the Data Store when you choose the "centralized config" option. A 'centralized configuration service' is available to make this happen.
 
Is this true? When I check my WI server, there is no 'centralized configuration service' nor is there the IMA service which normally is necessary to talk to the Data Store. Also the WI admin guide does not mention a 'centralized configuration service' or that the config is stored in the Data Store. So please enlighten me in this piece of magic...
 
Great website by the way!
 
greetz,
 
Marcel
Cancel
This is for WI4 only. A DCOM service (not a windows service) that's the configuration service on the web server, and it communicates to the IMA data store via the Citrix XML service running on a backend Presentation Server.
Cancel
Cancel
what's your opinion on spellcheck?

Cancel
Agreed.  If you're balancing your servers, there's not a whole lot of point in virtualizing your NICs, and it can create some issues with NLB.  While NLB doesn't require a secondary NIC for a "heartbeat", it does make it easier for the balanced servers to find each other if they have a secondary NIC to talk over.
Cancel
so if i choose central configuration the wi server will register a central configuration service which talks to a backend citrix xml server is choose?
 
how does it know which server to contact if the information of the xml server list is in the datastore ?
 
greetz
Cancel
There is a bootstrap.conf file on the WI server that tells the server whether it will use local (via webinterface.conf) or central (via XML service to IMA Data Store) configuration.
 
Brian
Cancel
Is it necessary to have your redundant WI servers connecting to your network via hub, (instead of a switch) so the NLB can see all the packets coming to the shared IP.
Cancel
Nah.. works fine on every switch I've ever tried it on (which has been several).
 
Brian
Cancel
Hi guys,
 
load balancing WI/CSG seems to be pretty easy and cheap to setup (wont argue the ease of configuration), but in terms of redundancy this is abolutely overdone when you dont have your network (ISP) redundant as well, new bottleneck in terms of redundancy becomes the availability of your ISP's connection
 
can be solved easily and cheap, check out the killer product FatPipe @ http://www.fatpipeinc.com/
 
is anyone out there using this product already? and what is your experience with the product? now you can really tell if your ISP's live up to their SLA's...
 
subsequently, rad
Cancel
This is very useful. Thanks, Brian.
Cancel
So what setting do you have to set in Bootstrap.conf to tell it to use the WebInterface.conf file instead of the Data Store option?
Cancel
ain salah gaz progect
 
Cancel
Ive succesfully used the NLB for failover (balancing didnt work too great though).. But my main concern was STA (mayby a bit offtopic, but still linked..). Ive tried setting up 2 STA's with PS3 (http://support.citrix.com/forums/thread.jspa?forumID=75&threadID=63966) and i couldnt get it to work automaticly.. so if u want redundancy, thats the next step..  well. mayby its fixed in PS4 (does any1 know?), even though you need to upgrade the farm to use the full monty,..
Cancel
Web Interface NLB is great, does anyone know what happens when you are implementing WI NLC solution with Citrix Presentation Server installed?
Cancel
Here is a link to MS's website which goes over everything you ever wanted to know about MS NLB.
 
http://www.microsoft.com/technet/prodtechnol/windowsserver2003/technologies/nlb.mspx
 
 
Cancel
If you want the real cheap and easy method, just implement round-robin DNS. (I know, it's not really load-balancing at all, but in general, has the same effect! Half my WI users go to serverA; half go to serverB)
Cancel
I'm not sure if I get it right, but doing it with DNS round-robin will in a case of failure the 50% of the requests will still be forwarded to the failed server, which I find not realy setistificating.
ORIGINAL: Guest

If you want the real cheap and easy method, just implement round-robin DNS. (I know, it's not really load-balancing at all, but in general, has the same effect! Half my WI users go to serverA; half go to serverB)

Cancel
ORIGINAL: Guest

I'm not sure if I get it right, but doing it with DNS round-robin will in a case of failure the 50% of the requests will still be forwarded to the failed server, which I find not realy setistificating.
ORIGINAL: Guest

If you want the real cheap and easy method, just implement round-robin DNS. (I know, it's not really load-balancing at all, but in general, has the same effect! Half my WI users go to serverA; half go to serverB)



That is correct.  This is why people invest in hardware or software load balancers.

Shawn
Cancel
ORIGINAL: Brian Madden

There is a bootstrap.conf file on the WI server that tells the server whether it will use local (via webinterface.conf) or central (via XML service to IMA Data Store) configuration.

Brian

 
is it possible to specify more than one ConfigurationLocation in the bootstrap.ini?
as it is, with 4 metas, and 2 web servers running nlb i am redundant in the metas, and webs. BUT if the meta specified as the ConfigurationLocation in the bootstrp.ini goes down then it breaks wi4.
Cancel
I've been using WI4 and decided to try a hardware load balance situation with cisco hardware. The problem I keep running into is an inconsistent state on Internet Explorer. Testing suggests that this is because I have setup my hardware load balancer to read the cookies and Microsoft IIS doesn't put the servername in the cookie but rather the virtual name. This causes a problem on the hardware load balancer to switch between servers randomly and create the inconsistent state. Any idea on overcoming this issue or seen this before? I don't want to use Microsoft NLB.
Cancel
NOTE: PS4, WI4 and NLB are on ALL of the Servers A, B, C

NOTE: NLB is configured on Servers A, B, C:
       2 nics each server (different VLANS, x.x.x.number, y.y.y.number)
       Cluster operation mode    = Unicast
       Port Rules = only port TCP 80 open
                        identical load weight on each server

    The cluster/virtual address is x.x.x.150
    serverA = x.x.x.120
    serverB = x.x.x.121
    serverC = x.x.x.122

NOTE: WI is configure with local store and A, B, C I have each configure identically.
I have the virtual ip (NLB Cluster address) in each of the "Manage Server Farms" - Servers (in failover order).

I am very familier with the NLB and we have it in production for our native Terminal Server Farms with static (session independant web pages).

The problem I keep running into is an inconsistent state on Internet Explorer accessing the WI via the cluster/virtual address is (x.x.x.150)

Testing suggests that Microsoft IIS doesn't put the servername in the cookie but rather the virtual name. If I access each server's TCP/IP address in IE, the WI works 100 %, but when I access the WI via the cluster/virtual address, IE does not know what specific server I have a session with, so it flakes out.

Brian, or anyone have any ideas?

I really want to effectively load balance the WI accross all of the servers with the NLB, rather than just change the load weight to extreems so that in effect only one server is utalized and if it goes down, there would be a back (failover).

One thought, does the domain URL name under the Web Interface in the "MetaFrame Presentation Server Administration" snapin influence the IIS cookies or is it just a label in the WI?

Thank You
Dew
Cancel
Hi,

we have two cps 4.0 servers running on w2k3 sp1 -in single farm. Server X is running WI4.0 and both web client and PNAgent are working fine with this. We installed ACS + WI 4.0 on Server Y and Run Discovery + Created MetaFrame site with local configuration files as the source. From client when i access the site for server Y, it loads the login screen but once after i give the credential and click on Login it throws below error.

"ERROR: The supplied credentials could not be validated. Either they are incorrect, or there is a problem with the authentication system. Try again, or contact  your help desk or system administrator for help."

Could you please help me to fix this issue?

Thanks
Addagats

Cancel
 
I could trace the problem and it was with Server-Y and not with WI on Server-Y. I reconfigured the Sites on Server-Y through ACS to use Server-X and it was working fine. The problem is with Server-Y which is unable to communicate with WI. Found below errors in event viewer on Server-Y
 
Event Type: Error
Event Source: Web Interface at c:\inetpub\wwwroot\Citrix\MetaFrame
Event Category: None
Event ID: 0
Date:  8/30/2006
Time:  8:02:42 AM
User:  N/A
Computer: 
Description:
The Citrix XML Service object was not found: "404" "Not Found".  This message was reported from the XML Service at address "http://server:80".  This XML Service could not be contacted and will be temporarily removed from the list of active services.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
 
Event Type: Error
Event Source: Web Interface at c:\inetpub\wwwroot\Citrix\MetaFrame
Event Category: None
Event ID: 0
Date:  8/30/2006
Time:  8:01:43 AM
User:  N/A
Computer: CPSNYC2
Description:
All of the configured XML Services for farm "DESHAW" failed to respond to this XML transaction.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Does anyone know fix for this ??

Cancel
Hi,
 
I fixed it myself by following below steps.
 
1) Unregistred the xml service by running 'ctxxmlss /u'.
2) Re-registered xml service on port 8080 by using command 'ctxxmlss /R8080'
3) Modified Mgmt Console -> server properties -> metaframe settings -> XML port -> 8080
4) Modified ACS - > /Citrix/Metaframe -> Manager Server Farms -> changed the XML port to 8080
 
Howerver i think i screwed some of the settings while trying to fix this issue and now every application i lauch is prompting for username and password though i choose "Explicit" as my logon method.
 
Anys suggestions or fixes in this case are welcome :)
Cancel
I fixed it myself
 
I enabled the option "inherit client config" in Citrix Connection Configuration -> ICA-tcp Properties -> Advanced Connection Settings -> AutoLogon sections which was unchecked earlier
Cancel
NOTE : This fixed my issues but i still have problem configuring Server-Y to run XML on port 80. Not really sure if its problem with Citrix XML Service or IIS but i am going to leave this here as any how my servers will get rebuild soon.
 
if anyone has fix to make XML work with port 80 itself then please udpate this request.
Cancel
Actually it works perfect with HP NIC's since they have a very clever driver. Other vendors use the same chipset (Broadcom) but use Broadcom's own driver, which does not support NLB with virtual teamed NIC's. It's hard to find the documentation for this, but somewhere far into a release note on some obscure CD-ROM you'll find a passage that says that teamed NIC's and NLB is not supported in Broadcom's driver.
But as said: It works beautifully on HP NIC's.
Cancel
Nice article
 
I have tried this by myself.
 
Two PS4, WI, PNAgent Site (Teaming and NLB.)
ServerA 10.178.1.20
ServerB 10.178.1.21
Cluster IP 10.178.1.22
Four other PS4 Desktop Servers
NLB works fine. Load balanced/failover perfect
 
But citrix seems not to handle this configuration.
If you run command query farm, the two servers above (NLB) is listed with two ip addresses, the own + the cluster address.
If i log in to wi and start an application (published to ServerA), and have a look at the actual ica file, the address to the server is 50/50% of the times 10.178.1.22/10.178.1.20. The times the is 10.178.1.22 i don´t works. How do i get rid of the cluster address to the farm, i only want to use it for load balancing wi/PNAgent Sites not for citrix XML communication ro what ever.
Cancel
You just need to set Affinity=Single in the NLB configuration and then set the weight for each member to 33%
Cancel
Wow, aren't we anal today...
Cancel

CTX108812 states :

Environments that have Web Interface and Citrix Presentation Server on the same server with Network Load Balancing configured are not supported.

So i think it's not possible or adviced.

I also had this configuration and had the same issue. 

Cancel

Greetings!

 I followed the CTX article to a "T" for setting up NLB (CTX108812) but now when I attempt to connect via the PNAgent, I get an "Unable to refresh the application list" error on the client. I tried using the cluster hostname (created a DNS "A" record) and also the IP, both to no avail. Any suggestions?

Cancel
Looking solution for Loadbalancer
Cancel
Try www.Xrio.com im sure one of the guys there could sort you out? theyre pretty good tho a bit hard to get hold of sometimes.
Cancel
I read a post that the Kemp LoadMaster 1500 load balancer when it is in front of 2 WI servers, that it sometimes ask for the user credentials again.  Does anyone know how to fix this?
Cancel

Round robin DNS is the way to go!

program neighborhood pn agent and Internet explorer will all try the second or third address for round robin if the first doesn't respond. haven't tested any other browsers. although ping will only ever try the first address.

Cancel

 To setup NLB , your servers have to be in same network, right ?

So,  what if we want to loadbalance over a wan connection ? Any ideas here ?

Cancel

Hello everyone.  After several weeks of working in a test environment and the help of Jonathan Braunhut @ Kemp Technologies, I have the (single) Kemp LoadMaster 1500 working in a 1 arm config with 2 Citrix Web Interfaces with the Secure Gateway loaded on the same box.  Here is what I had to do.

Initially, the Kemp support rep (not Jonathan) told me that I had to run in 2 arm config, but then Jonathan told me that you could do this in a one arm config.  The one arm config doesn't give you as much network speed since the inbound and outbound traffic are going over the same wire.  No worries for me since I only have a 3Mbps Internet connection and running at 100Mbps is WAY fast enough.  Also since Citrix only passes keyboard and mouse strokes through the wire, then there isn't much speed need.  This was a very simple installation with no extra rewiring.  In fact, when checking the stats on the Kemp my utilization on the Eth0 interface is only about 0.3 - 0.4% with 60 users connected at the same time.

I am using 2 Web Interfaces on 2 separate servers running VM Ware Server.  This works great by the way, because the Web Interface doesn't really take up that much usage on the server.  I did a test and my CPU and disk utilization averaged about 2% each for a full day.  This is on a HP DL380 G3 server with a total of 4 VMs on each server with about 20 - 60 users connected through the Web Interface.

On the Web Interface Servers you MUST put the Kemp LoadMaster IP address as the  Default Gateway address for these servers.   This allows the source IP address to be passed to the Web Interface servers.

In order to do RDP into the Web Interface servers, Jonathan also had me disable the SNAT on the Kemp LoadMaster by going to  System Configuration > Miscellaneous Options > SNAT Control and turn off the SNAT.

We also changed the L7 Transparency, by going into the same Miscellaneous Options under L7 Configuration and changing it to Non Transparent.  For some reason, the Web Interface was going very slow in presenting the list of applications after signing on, so we also changed the L7 Connection Timeout to 660.  This made the speed of displaying the applications much faster.

I also have the Secure Gateway loaded on the same box as the Web Interface, which Citrix doesn't suggest to do anymore.  They want you to purchase the CAG (Citrix Access Gateway) at $2,500 just to house the certs and do the SSL VPN.  For the amount of users that we have (40-60), I didn't think that this deserved spending this kind of money.  You have to setup the Web Interface on port 444 since the Secure Gateway is on the same box and wants to have port 443.

Now on the Kemp LoadMaster 1500 I setup the Virtual Server at a VIP (virtual IP) that wasn't used on my network.  You can then setup a redirect on the LoadMaster so that anyone who doesn't type the "https" before the URL, will then automatically get redirected to https (port 443).  This works great!

The redirect must use the Layer 7 (L7), but the actual virtual service to the Web Interface only uses Layer4 (L4).  

Here are the settings on the Kemp LoadMaster that I setup for the virtual server for the Web Interface.

Service Type:  HTTP/HTTPS

Force L7:  <not enabled> 

Persistence Options:  Source IP Address, 2 hours

Scheduling method:  least connection  (I had initially set it for round robin, but it wasn't balancing the users on each server.  After I changed it to "least connection" everything worked great.)

SSL Acceleration:  <not enabled>  Citrix Secure Gateway forces you to put the certificate on the Web Interface server.  You can't load it on the Kem

Cancel

Healthcheck URL:  <nothing>  (Using the HEAD option should be enough to monitor the Web Interface) 

HTTP Healthcheck method:  HEAD.  (This is the L7 checking of the website to make sure that it is up.

Real Servers:  The real servers must be set for port 443 forwarding. 

That was it.  The Kemp LoadMaster is working beautifully right now.  It has been up for about one week without any problems.

Cancel

Nifty little loadbalancer http://siag.nu/pen/

Also comes ready in a virtual appliance for your fav vmware platform as hercules http://www.vmware.com/appliances/directory/300

Don't always make Wintendo your first choice :)

Cancel
Cancel

Below is a document from Microsoft that says not to use Windows NLB in a production environment. Read the section "A Note About NLB" on page 2.

Document is titled: Live Communications Server 2005 Document: Enterprise Pools and Windows 2003 Network Load Balancing

http://www.microsoft.com/downloads/details.aspx?FamilyID=649ee26c-0a3c-4fb0-81c6-42afc3cb08e4&DisplayLang=en

Cancel
HI, I have a for the most part complete PS 4.5 environment, but the only thing left is the WI running on 4.0 which also has apps on it which i am moving off.  (ie conf. mgr.) I want to set up WI (latest) on another server and run them both in an NLB setup then create a second WI (latest) also NLB as well so I can take the 4.0 WI out of the picture.  What would be the best way to do this? Will they run together in this situation if at all?  Trying to create as little down time as possible while still moving from the old WI to the new and implement the redundancy.  Any help or input would be greatly appreciated... Thx...
Cancel
I am trying to move from using the 4.0 console which is published (on that same WI machine) to my helpdesk and "field" users to monitor sessions right now to the new console but it is not working nearly the same as far as what they see and what they can do.  ie... limitting access and giving shadow rights.  ANY suggestions on this would be GREATLY apprecieated as  well.  I can only seem to give shadowing to people in the admin group that have "full access".
Cancel

I've set the affinity to single, and I still get the error..... Now what do I do?


Cancel

Can we have IP source persistence for 5 minutes for a load balanced WI through a device like Big IP.  How will it affect the WI.


Cancel

is there any method for pinging the gateway directy from my sytem with system working on cotrix presentation server


Cancel

Generally Gateway servers are located in the DMZ zone so you may have to open ICMP which is a security risk in order to ping the server from either ways.


Cancel

I have NLB working but I'm unsure how to force both WI servers to point to the new DNS name.  Can someone help please?


Thanks


Cancel

Sorry, I wasn't specific enough.  I am trying to get PN Agent working through the NLB DNS name.  Where do I need to make changes?


Cancel

Citrix know how to make an application switch, and even real load balancing. Isn't that part of what Citrix are promoting?  Why not put it into the WI? It is not possible? Then why not put it in the client? Citrix; use your imagination. You can do it!  Citrix need to add more real value to their main product.


Cancel

-ADS BY GOOGLE

SearchVirtualDesktop

SearchEnterpriseDesktop

SearchServerVirtualization

SearchVMware

Close