D81 Posted October 9 Share Posted October 9 Hi After successfuly created a load balance for App volumes instance (two app vol servers), I have tried to add the load balance to the dashboard of the Connection servers. So if I add each App vol server FQDN then they will be added witout problem. However in case I want to add the load balance FQDN then I get this error ( I cant find more info about it): By the way refreshing the browser didnt help... Notice that both App volumes servers and the load balancer are sharing the same certificate and it works fine with HTTPS (I have still not tested a package but I assume it is fine too). So any help will be appreciated. Thanks Quote Link to comment Share on other sites More sharing options...
vmguru Posted October 11 Share Posted October 11 I think this is not possible! maybe someone knows better Br Quote Link to comment Share on other sites More sharing options...
D81 Posted October 11 Author Share Posted October 11 21 minutes ago, vmguru said: I think this is not possible! maybe someone knows better Hi, thanks for answering! I've check the Omnissa doc and it sais it is possible: "Depending on your environment and setup, add all App Volumes Managers that you want to be associated with Connection Server and used with published apps on demand. You can add individual App Volumes Managers, which would be multiple records if you have different App Volumes Managers that you want to use for published apps on demand, or add a load balancer which would only have one record." https://docs.omnissa.com/es-ES/bundle/Desktops-and-Applications-in-HorizonV2406/page/AddaAppVolumesManager.html Anyway I think in this case the issue is related with the load balancer config, I will check it later and I will post the results... Quote Link to comment Share on other sites More sharing options...
Robin Harmsen Posted October 11 Share Posted October 11 If I interprete that text correclty you should only add the load balancer address or the specific managers.. not the seperate managers and the load balancer at once. 1 Quote Senior Engineer (SDDC, EUC, DBA, Applications) at the Netherlands Cancer Institute - Antoni van Leeuwenhoek Hospital (NKI-AVL) Link to comment Share on other sites More sharing options...
hans straat Posted October 11 Share Posted October 11 (edited) Robin is right, Our environment consists of 4 appvolume manager servers to spread the load and only the FQDN of the load ballancing address is where we manage our environment through the webinterface. Right i misread your post and checked our Horizon console. Also there is the load ballancing address instead of individual servers. Edited October 11 by hans straat 1 Quote Senior technical specialst at Leiden University Medical Center (lumc) Link to comment Share on other sites More sharing options...
D81 Posted Wednesday at 08:44 AM Author Share Posted Wednesday at 08:44 AM (edited) Thanks for the clarifications! I have tried to add the load balancer FQDN for the app volumes but it always gives me the error message. So I ended by adding the app volumes by separate. Anyway I assume adding them on the horizon console is not a mandatory request... isnt it? As far as I understand this is only useful for providing packages to the applications farm in case you have one and you want to attach the packages to the RDS servers or VDI servers that will provide the applications to the users. Please correct me if Im wrong... EDIT: I still have load balance issues. I have created an empty golden image, I have installed the app volumes agent on it and I have set the load balance FQDN to it. However after rebooting the golden image I have a time out when loading app volumes services... And when it loads the Windows session it shows this: I have tried to reinstall the agent without the "validate certificate" option to check if the issue was related with the SSL certificates but I got the same results The customer has configured F5 load balancer wih this guide: https://www.f5.com/pdf/solution-center/f5-big-ip-vmware-app-volumes-integration-guide.pdf Notice that I can access to the App volumes manager console url from the Golden image by using the load balanced FQDN url. https://appvolumes.mydoman.local So I assume that the load balance works at least partialy.... Edited Wednesday at 11:16 AM by D81 Quote Link to comment Share on other sites More sharing options...
D81 Posted yesterday at 06:59 AM Author Share Posted yesterday at 06:59 AM More feedback here... As mentioned before, when pointing App volumes through the URL on a browser the load balance works fine. However when the agent points to the load balance FQDN it doesnt work. The customer is using SNI, so he thinks thats the problem... Any idea? Quote Link to comment Share on other sites More sharing options...
Robin Harmsen Posted yesterday at 12:41 PM Share Posted yesterday at 12:41 PM Perhaps try without SNI Quote Senior Engineer (SDDC, EUC, DBA, Applications) at the Netherlands Cancer Institute - Antoni van Leeuwenhoek Hospital (NKI-AVL) Link to comment Share on other sites More sharing options...
D81 Posted yesterday at 02:40 PM Author Share Posted yesterday at 02:40 PM He told me that's the way they have configuered the appliance and they can't change it. I have Zero idea regarding F5 appliances so I dont know if there is a way to avoid SNI just for a specific load balancing service and let the rest of the services with SNI. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.