Jump to content

Recommended Posts

  • Replies 8
  • Created
  • Last Reply

Top Posters In This Topic

  • Employee
Posted

It's a while since I did this for Access on-prem using the Avi load balancer. Here are some screenshots showing the main settings for the virtual service and the pool from that environment.

image.thumb.png.c50ba9089e08d6f4fa1f36f04331af11.png

image.thumb.png.1d31aec7c45b4fdb5bf2be39126d1201.png

image.thumb.png.ef09c8610502f030aa44fedd59f924b3.png

Posted

thanks @Graeme Gordon . I solved it by check the rewrite host header to server name.

but actually my problem now is when I integrate it with UEM , so when I start the enrollment and ad group ID, it redirect me to the ws1 access and I when I add the AD, it give me an error that invalid and forword me to the normal AIRWATCH login not that for ws1 access as below 

 

image.png.196bacc28d48c68b288eed1b16991ac9.png

  • 2 weeks later...
  • Employee
Posted
2 hours ago, Asma Alfayyad said:

@Jack M actually, its work correctly before I added to AVI lb 

Then it's gotta be your AVI config. Do you have session persistence setup so it's not bouncing between appliances for a single user?

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...