FSLogix profile configurations for App virtualization only scenario


Hi everyone, need some advice here 


We understand that the FSLogix can be used for profile management and profiles can be stored externally on some storage e.g. Azure Files. 


In theory, this tells us that we would need to worry about managing user profiles and configure FSLogix on base image only when end users are going to sign-in and consume complete desktop as a  service. (i.e. when users are assigned to Desktop application group). Is it correct understanding?


If above understanding is correct then, does this mean that if RDS hosts are only going offer virtual apps and not full desktop as a service (i.e. all users assigned to Remote application group and not to Desktop application group) then we wont need to configure FSLogix on the base image at all?


Can someone please clarify this?

Thanks in advance! 


4 Replies
you still need FSLogix for RemoteApp.

@Soo Kuan Teo curious to know the specific reason around why it would still be needed for remote app only scenario. 

@bhushangawale, I may be mistaken in this, however it's preferable to have the UPD/FSLogix containers stored in a central location, as opposed to locally on each host's C drive.  If you're deploying RemoteApps via WVD then I can see no reason not to take advantage of the benefits of the more streamlined FXLogix containers instead of the more usual UPD storage on a network accessible drive.  Also I'm not aware of how to configure that location under the WVD way of doing things.  Likely FSLogix is your only real method of configuring where they will reside.  It's also Microsoft best practice at this point for WVD deployments, even if the user profiles are goign to be small due to only being RemoteApp deployments. 

The apps you published may also have user data that needs to be stored in user profile, for example Outlook.