Hi, I have set up Azure Virtual Desktop and I am testing before rolling out to users. We are using Azure AD DS.
I want to use FSlogix to enable roaming profiles and remote storage for user documents and outlook files. I followed the instructions here:
All went OK until the assign users step where it says "Run Windows PowerShell as an administrator, then run the following cmdlet to sign in to Azure Virtual Desktop with PowerShell:". The given PowerShell cmdlet Add-RdsAccount -DeploymentUrl $brokerurl fails. I had a look and it seems this may only apply to the classic WVD and not AVD with ARM? I hunted for more information about the TenantCreator role and cannot see how to apply in our setup.
Nevertheless fslogix is installed on our session host. However I discovered it was not configured for a user logging in because the user does not appear in the local users and groups. I manually added the user to the FSlogix include group and deleted the local profile, now an FSLogix profile is created. But that does not seem the right way to do this?
What steps can I take so that users automatically get FSLogix profiles and what are the consequences of not being able to follow the steps for "Assign users to the session host"?
I can quite easily add the group I am using for AVD users to the local user group manually if that is the right approach but want to observe best practice.