Hello, thanks for this tool.
I've been going through a few deployments and noticed the article below suggests the following FSLogix configuration. The tool does 1/3 non-default suggestions already.
The default size is default so not sure why they mention it
The the flipflop profile key is already part of the tool.
The VolumeType and DeleteLocalProfile are new. I was surprised the volumetype doesn't default to VHDx!
| Setting |
Value |
Reason |
| DeleteLocalProfileWhenVHDShouldApply |
1 |
This setting avoids errors while logging in with an existing local profile. It removes the profile first, if any already exists. |
| SizeInMBs |
30000 |
Specifies the size of newly created VHD(X) in number of MB. Default value is 30000 MB or 30 GB. |
| VolumeType |
VHDx |
More capabilities for PowerShell and maintenance. |
| FlipFlopProfileDirectoryName |
1 |
Makes it easier to search for the specific profile container user folder on the network share. |
https://docs.microsoft.com/en-us/azure/architecture/example-scenario/wvd/windows-virtual-desktop-fslogix#best-practice-settings-for-enterprises
Hello, thanks for this tool.
I've been going through a few deployments and noticed the article below suggests the following FSLogix configuration. The tool does 1/3 non-default suggestions already.
The default size is default so not sure why they mention it
The the flipflop profile key is already part of the tool.
The VolumeType and DeleteLocalProfile are new. I was surprised the volumetype doesn't default to VHDx!
https://docs.microsoft.com/en-us/azure/architecture/example-scenario/wvd/windows-virtual-desktop-fslogix#best-practice-settings-for-enterprises