primaryliner.blogg.se

DEFINE HOBO HOW TO
DEFINE HOBO INSTALL

Select your Subscription and Resource group (or create a new one). Open the Storage accounts blade and click the + Add button to add a new storage account. Login to the Microsoft Azure Portal to perform the steps below. Step 1 : Create a Storage account with a Private endpoint Standard storage account general-purpose file shares are good for dev/test environments with up to 200 concurrent active users. Premium storage account have more IOPS, but file share size is provisioned (Standard HHD is Pay-as-you-Go), so in general you pay more for your storage, at least in the beginning.

For the local domain you need to have the rights to create groups, users, add ADMX files to the Policy repository and create and edit GPO objectsĭuring the creation of the storage account you get the option to select Standard (HHD) with account type GPv2 or Premium (SSD) with account type FileStorage.

Owner permissions on the Azure subscription.

Up and running Windows Virtual Desktop environment ( click here for guide).

Up and running Azure tenant, including configured with Azure AD Connect.

The following prerequisites must be in place:

Configure FSLogix Profile Container via GPO.

DEFINE HOBO INSTALL

Install FSLogix Profile Container in your WVD Host pool.Configure NTFS rights on the Azure File Share.Configure Storage account Access control (IAM).Enable Active Directory authentication on the Storage account.Create a Storage account with a Private endpoint.This blog is divided into the following steps:

DEFINE HOBO HOW TO

In this blog I will show you step-by-step how to deploy FSLogix Profile container user Azure Files and Active Directory authentication for Windows Virtual Desktop. Azure Files is an Azure service that is scalable on-demand and which is not dependent on a VM that needs to be running 24/7. There are several options for the storage location like an existing (or new) Windows File server, but since Azure Files with Active Directory authentication is GA, I personally prefer this option. It will optimize the sign-in time for the end user because the user profiles are stored in VHD(X) file that is mounted to the concerning Session host VM every time the user signs in and therefor nothing has to be downloaded first. With FSLogix Profile container you can maintain user context (for example application settings) in non-persistent environments like within a Pooled Windows Virtual Desktop Host pool.