Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
FSLogix operates based on specific registry settings that define how it operates. These registry settings are applied on a per-machine level. For information on each registry setting and the expected behavior, see Configuration settings reference.
There are several ways to apply registry settings depending on the scenario and scale of your environment:
Manual registry entries: The manual method implies adding registry entries directly through one of these types of processes:
- Registry Editor
- Registration Files
- Console Registry Tool for Windows
- PowerShell
- Desired State Configuration
Note
Using a manual method is perfect for single machines in a test or development environment. With the right expertise, this method could scale and work within an automated orchestration framework (for example, Azure DevOps, Jenkins, Chef, or Puppet).
Local Group Policy (ADMX): You can use the Local Group Policy editor to configure FSLogix through the ADMX files when they're stored locally on the virtual machine. Unlike the manual methods, this method doesn't scale and is used only as part of a test or development environment.
Group Policy Objects (ADMX): Group Policy Objects are an ideal method for large-scale configuration, especially where there isn't any existing automation.
Intune (settings catalog): An Intune policy can target Windows 10 or Windows 11 multisession operating systems. You can find the FSLogix settings in the settings catalog.