aamirahmad
asked on
citrix xenapp server 6 assign specific user to a server in a farm
Hi
We have 3 servers in one citrix farm. How do I create a policy to assign specific users to a specific server in a farm when the users logon?
We have 3 servers in one citrix farm. How do I create a policy to assign specific users to a specific server in a farm when the users logon?
edjakeman
You could have three sets of published applications, with each having different servers and users specified?
create and assign Load Evaluators
ASKER
we currently have a published desktop. how do you create and assign load eveluators? through citrix delivery console?
Hi,
You go to the Delivery Console and click on Load Evaluators, right click new. It also depends on what you want to load balance. You assign load evaluators to resources like CPU, memory, disk I/O number of users logged on.
Hope this helps,
You go to the Delivery Console and click on Load Evaluators, right click new. It also depends on what you want to load balance. You assign load evaluators to resources like CPU, memory, disk I/O number of users logged on.
Hope this helps,
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
@Mutawadi you can very simply use the IP adress of that user (or range), make a dhcp reservation and it will always work fine. (we use this for years to test a specific server)
There are several ways to configure a published app/desktop to specific users. As mentioned above, you can publish it three times to different groups with slightly different names, you can use a Load Balancing Policy (XA6 and above) to direct users to specific servers, you can specify by source IP with a few different mechanics etc.
The real question becomes why would you want to do this? The whole point of a well designed XA infrastructure is that the individual server you are on simply does not matter to the end user. They (in theory) should all look & feel the same. With a distributed environment, they can in theory travel to any location and get the same basic look & feel. By limiting them to 1 server, you are removing any HA for them and creating single points of failure where there doesn't need to be any.
Coralon
The real question becomes why would you want to do this? The whole point of a well designed XA infrastructure is that the individual server you are on simply does not matter to the end user. They (in theory) should all look & feel the same. With a distributed environment, they can in theory travel to any location and get the same basic look & feel. By limiting them to 1 server, you are removing any HA for them and creating single points of failure where there doesn't need to be any.
Coralon
@Warddhooghe. Now I see what you mean - you are actually associating the machine on which the user is logging on by using the IP address, not the user account itself.
This scenario would be valid in normal work circumstances. It wouldn't be valid in cases where a user is rotated with other coworkers on different machines or in cases for example a user goes to a disaster recovery site where a specific seat is not associated for that user only.
This scenario would be valid in normal work circumstances. It wouldn't be valid in cases where a user is rotated with other coworkers on different machines or in cases for example a user goes to a disaster recovery site where a specific seat is not associated for that user only.
Then you will definitely want to use a Load Balancing Policy. You can direct a user or group of users to specific servers.
Coralon
Coralon