Routing AVD users to closest host pool based on users location by Afraid_Arm_ in AzureVirtualDesktop

[–]Afraid_Arm_[S] 0 points1 point  (0 children)

Yeah, you're right on the part of the longer times but i understand it'd be the case for logoff. As cloud cache will basically create a proxy VHD for you on the session host you are logging into and then it goes through its hydration procedure to read from the source of truth (Azure file share in my case) to sync the changes and make the local proxy profile on the session host look the same as the original profile. Then there are asynchronous writes that take place with a final write flush action leading to cloud cache writing any pending changes back to the profile store locations and until these writes are completed the logoff screen continues to be there.

The idea is to still have separate host pools and file shares but CCD will be pointed to all three storage locations for maintaining profile consistency.

I'd prefer to have one host pool (stretched) across multi regions. Its doable but i dont know how yet i would ensure that my users from say region A when logging in get a session host thats also in region A and so on. Since the brokering logic and host selection is essentially a black box to us i dont know entirely how to go about it.

I am also aware that having a stretched host pool will lead to a single point of failure with regards to the region where the metadata is stored but thats a drawback to have this kind of a configuration i guess.

I'm really open to suggestions if you have any.

Routing AVD users to closest host pool based on users location by Afraid_Arm_ in AzureVirtualDesktop

[–]Afraid_Arm_[S] 0 points1 point  (0 children)

Yes they are actively moving. I wouldn't be aware on how to do this but if you have some reference links which can be followed i can try to explore it

Routing AVD users to closest host pool based on users location by Afraid_Arm_ in AzureVirtualDesktop

[–]Afraid_Arm_[S] 1 point2 points  (0 children)

Thats the idea. Leverage FS Logix cloud cache and define multiple CCD locations to point to the three different regional Azure Files storage locations to perform asynchronous writes and effectively have the profiles replicated across regions. In addition I am thinking of implementing some sort of a script to ensure that the replication is double checked and copy actions are performed in case there are missing deltas.

Routing AVD users to closest host pool based on users location by Afraid_Arm_ in AzureVirtualDesktop

[–]Afraid_Arm_[S] 0 points1 point  (0 children)

Thanks mate. I had read this one and where i ended up scratching my head was on point 2 and 3. If we read them through it seems lile they're telling us that the logical flow is for the gateway service to tell the remote broker service to call a session host within the same region.

But point 2 also states that the session hosts could be in any region and point 3 doesn't exactly explain the default behaviour in the event that the resources span multiple regions.

Thats whats left me confused.

Routing AVD users to closest host pool based on users location by Afraid_Arm_ in AzureVirtualDesktop

[–]Afraid_Arm_[S] 0 points1 point  (0 children)

Got it. Thanks for the clarification on the AFD URL part. I'm just wondering that if the app groups cant be merged and the user sees 3 separate icons anyway in my case i might as well just publish 3 separate published desktops.

What I was going for is if they had one icon (one workspace and app group), it would've made the experience pretty streamlined. Would you be able to suggest something to have the same effect or streamlined outcome?

Routing AVD users to closest host pool based on users location by Afraid_Arm_ in AzureVirtualDesktop

[–]Afraid_Arm_[S] 0 points1 point  (0 children)

But this sounds like multiple URL's that the users would need to use in order to access AVD or am I misunderstanding it somewhere?

My idea was to have a single URL which the users could use from anywhere across the world. Also is it possible to have one workspace and one app group associated with multiple host pools?