Pooled hosts and profiles sticking

[getbeyond]

Been POCing the WVD solution and have a funny issue (at least in my head). I've setup 2 hosts that should be using pooled desktops. As I understand pooled means non-persistent (I'm a VMware guy not hyperv/ms so my terminology may be lacking). So the hosts are actually keeping the profiles on the systems instead of wiping at logoff. Is that supposed to happen? I thought the FSLogix manager was supposed to keep the profiles and they would be scrubbed from the host. Is that not how it works? I'd assume personal keeps the profiles/pooled kills em. What am I missing?

[#2 · Accepted solution]

@getbeyond you are correct that FSLogix manages profiles for non-persistent environments.  The language of your question suggests that your expectation may be that using FSLogix is the default state when selecting pooled desktops during the host pool creation.  Because there are configuration decisions that must be made related to FSLogix, it is installed and configured after the host pool is created.

For instructions on a minimal install of FSLogix to get started in WVD please see this article:  https://docs.microsoft.com/azure/virtual-desktop/create-host-pools-user-profile?

Additional documentation may be found at https://docs.microsoft.com/fslogix/overview.

[#3]

I was about to post the exact same observation. I understand FSLogix is not enabled by default when creating a host with pooled desktops.

However as per @getbeyond I'm noticing that profile data and even application installation is persisted when users log on/off to a pooled host. That can't be intentional...can it?

Thanks.

[#4]

@Ian_CC In a pooled environment the user will be attached to the same resource if possible, this would result in the behavior that you observe.  This is not guaranteed in a pooled environment.  For instance, if the resource is not available, say it is stopped for some reason, or if the resource is saturated in certain scaling schemes.  In these cases, the user would be routed to a different host in the host pool, and their information would not be available.  This could be perceived, by users, as data loss.  This would also result in non-consistent user profiles scattered across any host that the user has logged into.