Option C would be my preferred method. If your LB can redirect to the correct LB at the site then you are good. The downside is that it adds an additional hop.
In your other scenarios, if the app volume agent tries to connect to a manager that isn't available you have to wait for the timeout. I personally would try to avoid this. I don't see any official wording but it seems the agent always checks the first one. You can adjust the timeout settings. The default for a connection is 10 seconds set by the ConnectTimeOutMs
I understand what you are saying.
So would I be right in thinking that, if you have multiple AppVol Mgrs configured in the registry, the agent will try to connect to the first one first. Then, if there is a timeout, it will try Manager2 and then Manager3 etc?
The issue here is that there will be a delay in connecting to the AppVol Mgr if the agent needs to cycle through all the "down" IPs first.
If that is correct then I understand your recommendation and I completely agree.
Also I believe that if you increase the timeout the the agent will just take longer while it tries to connect to the first Manager. If that manager is down then increasing the timeout will make the client experience even worse, right?
Based on Simon Longs explanation found at the link below, I think the assumption is correct that it checks it in order. I honestly haven't tested that theory. Maybe a dev can confirm.
Yes, the experience would be worse if you increase that time. The appvol service connects to the management server at computer startup and user login. What I don't know is if it caches the management server URL that it can connect to after computer startup or it just goes through the list again. It would be simple to figure that out by viewing the app volume service logs.
Thank you very much Techguy129.
Your answers have helped me understand the issue and even extend my understanding.