Forum Discussion

Eddie_Ortega_27's avatar
Eddie_Ortega_27
Icon for Nimbostratus rankNimbostratus
Mar 18, 2013
Solved

VMView Horizon view HTML Feature pack

Has anybody able to manually configure the Big-ip to allow HTML connections from the outside with the vmware view 5.2 and the new HTML access feature?

 

 

The IAPP doesn't seem to support it as it goes thru port 8443.

 

cloud
vmware
  • JustHall_48130's avatar
    JustHall_48130
    Apr 23, 2013
    I created a new pool (View_blast_pool) where the members are my security servers, port 8443. I used the "View_tcp_monitor" that came with the iApp for the monitor on this pool and set the load balancing method to "Least Connections (node)" because that's what the PCoIP pool uses (which was set by the iApp).

     

     

    I then made a new virtual server (View_blast) on port 8443 and assigned my new pool as the default pool. I also chose "View_source_address_persistence_profile" (came with the iApp) for the default persistence profile. Everything else is blank/default (except SNAT Pool which is Auto Map, but that may be specific to my environment).

     

     

    P.S.

     

    I also ran into another issue with View 5.2 where the Receive String in the View_https_monitor was no longer valid because of VMware's decision to rebrand the product from VMware View to VMware Horizon View. To fix, disable Strict Updates on your Application Service for View and then go modify the View_https_monitor receive string to say "VMware.*Horizon View" (without quotes, of course). You may have already run into this before tackling the Feature Pack/HTML Access issue, but thought I'd throw it out there just in case.

1 Reply

Sort By
  • JustHall_48130's avatar
    JustHall_48130
    Icon for Nimbostratus rankNimbostratus
    Apr 23, 2013
    I created a new pool (View_blast_pool) where the members are my security servers, port 8443. I used the "View_tcp_monitor" that came with the iApp for the monitor on this pool and set the load balancing method to "Least Connections (node)" because that's what the PCoIP pool uses (which was set by the iApp).

     

     

    I then made a new virtual server (View_blast) on port 8443 and assigned my new pool as the default pool. I also chose "View_source_address_persistence_profile" (came with the iApp) for the default persistence profile. Everything else is blank/default (except SNAT Pool which is Auto Map, but that may be specific to my environment).

     

     

    P.S.

     

    I also ran into another issue with View 5.2 where the Receive String in the View_https_monitor was no longer valid because of VMware's decision to rebrand the product from VMware View to VMware Horizon View. To fix, disable Strict Updates on your Application Service for View and then go modify the View_https_monitor receive string to say "VMware.*Horizon View" (without quotes, of course). You may have already run into this before tackling the Feature Pack/HTML Access issue, but thought I'd throw it out there just in case.