farscapesg1
2[H]4U
- Joined
- Aug 4, 2004
- Messages
- 2,648
Let me start by saying that our XenApp "guru" has left our company and our XenApp 7.6 environment has fallen into my lap to learn and support (yay on learning.. boo on supporting before I feel comfortable).
We have an application that was built under the 6.x version of XenApp that needs to be updated. With the newer version of XenApp we are using MCS with our VMWare infrastructure to create a "template" and then let MCS create replicas for scaleability. Unfortunately, this app requires Virtual IPs per session since it communicates back to the server and verifies the IP address before running. In the old version, the servers were configured with static IP pools (say 192.168.1.10 - 50 for Server A and 192.168.1.51 - 100 for Server B). I would prefer to use a DHCP scope so we can scale the replicas for performance (start with 2, increase to 3 if/when the app is used more).
Is this even remotely possible with MCS? Under the old way, we had to configure the registry with a static IP pool, add all the IP addresses to the NIC, and set the AdapterAddress for Remote Desktop IP Virtualization to the MAC on the server.
Or is this a use case where MCS can't really be used and we need to create each virtual server separately and not have it managed by MCS?
We have an application that was built under the 6.x version of XenApp that needs to be updated. With the newer version of XenApp we are using MCS with our VMWare infrastructure to create a "template" and then let MCS create replicas for scaleability. Unfortunately, this app requires Virtual IPs per session since it communicates back to the server and verifies the IP address before running. In the old version, the servers were configured with static IP pools (say 192.168.1.10 - 50 for Server A and 192.168.1.51 - 100 for Server B). I would prefer to use a DHCP scope so we can scale the replicas for performance (start with 2, increase to 3 if/when the app is used more).
Is this even remotely possible with MCS? Under the old way, we had to configure the registry with a static IP pool, add all the IP addresses to the NIC, and set the AdapterAddress for Remote Desktop IP Virtualization to the MAC on the server.
Or is this a use case where MCS can't really be used and we need to create each virtual server separately and not have it managed by MCS?