This guide helps you setting up the FSlogix Profiles Container. Just like the Office 365 Container this solution allows roaming the cache data on VDI/RDS of most Microsoft Office products. If you want to also improve login times, or have issues with other applications that require cache files for the user, which can't be roamed at the moment: Consider the Profile Container. This will offer the benefits of the Office 365 container including roaming the rest of the user profile. Login times of 2-3 seconds are a practical realisable option! Even with GB sized user profiles!

1. 1 | P a g e Prianto Benelux - Vasteland 78 - 3011BN - Rotterdam
www.prianto.nl - +31(0)103007878
FSlogix Profile Containers
Quick start guide for a successful trial
We are aware that deploying a new tool in a (test)environment can be a problem and
take too much effort. In the end this results in an installation that is either not performing
as it could be that the test completely fails as getting familiar with the product is too
hard. FSlogix is relative easy to deploy, and only a few configuration settings are needed.
We know FSlogix is a very technically oriented solution. Therefore, we advise to deploy in
a test environment to familiarize with the configuration needed in your infrastructure.
We want to explain our experiences at various other clients. This resulted in having some
best practices ensuring a low risk, well-documented and simple to reproduce results.
Prerequisites
We advise to first set-up the solution in a test environment, preferably configured
comparable to the target/production environment. This does not need to be on similar
high-performant (cost) hardware. But if your production is on a Windows Server RDS, do
not test on a Windows single user OS. Also (try to) use a comparable application
landscape, in particular Microsoft Office.
Additionally, FSlogix requires a network storage to hold the VHD(x) files. It is preferred
having a dedicated share on a separate disk. This allows simple resizing of the storage
afterwards (if initial sizing was misjudged).
Deployment of FSlogix
The deployment of FSlogix is pretty straight forward.
In conjunction with this document you received an email with a download link to the 30-
day trial version. This version can be installed and will offer the complete support of all
FSlogix features. For testing an administrator can install FSlogix manually, which should
be a simple ‘next-next-finish’ install.
For production a silent install feature is possible, allowing to deploy on large
infrastructures with the mechanism of your choice.
A reboot should not be required when installing 1st time on a system (but advised). Upon
an upgrade however a reboot is/will be needed to be able to replace the filter driver.
There are no server components that have to be installed. So please do NOT install
FSlogix on the fileserver!
Which FSlogix solution to use?
If you intend to roam cache data for Office applications (Outlook, OneDrive, OneNote, …)
you can use either FSlogix Profiles or Office 365 Containers.
In case you want to roam the user profile in total, FSlogix Profiles should be your tool.
If you (also) want to roam the Outlook search cache, you need to have the Office 365
containers. And if you want both, they work great side-by-side/extend each other…
What IS FSlogix ?
FSlogix offers the capability to solve very
specific IT issues with workspace deployment or
performance issues with 4 unique point-
solution tools. All tools are deployed using a
single, small installer.
The 4 solution areas are:
Application Masking
Hide applications, plugins, printers, … for
specific users or systems, allowing a single
image to be used, even in a diverse
environment.
This gives optimal integration with great
performance, as only required applications are
available for the user, natively installed.
Java management
Built upon masking this issue-specific solution
allows managing which Java versions are
available. This also allows assigning specific
versions to websites (even mix & match in a
single browser!) or local Java-applications.
User Profile (using VHD)
Comparable best to Microsoft UPD, but with
huge advantages in manageability and features.
Read twice: Roam a local user profile to various
systems (VDI/RDS/FLEX-Fat clients). Login near
instant, even with huge profiles.
Office 365 Containers (using VHD)
Point-solution based on the profile solution.
Are you happy with your current profile
solution, but want to migrate to Office365, and
can’t roam the Outlook Cache or Search
Index… even on RDS? Or want to roam
OneDrive?
One answer: Office365 Containers!
Author: Michael Baars
Document version: 1.0 (21-6-2018)
Verified with FSlogix version : 2.8.6686.44077

2. 2 | P a g e Prianto Benelux - Vasteland 78 - 3011BN - Rotterdam
www.prianto.nl - +31(0)103007878
FSlogix Profiles Container Configuration
The FSlogix Profile Container requires some configuration items:
- Registry settings (possible using policy)
The features of FSlogix Profiles are configured using registry settings in the machine hive.
- Assignment of users to in-/exclude groups
Using local groups (created during install of FSlogix) it is simple to assign what users will be able to use FSlogix Profiles. By
default all users will be included (which is not the desired production value!)
All these settings can also be deployed using GPO. This however is not required and, for speed, during testing not advised. By
editing the registry settings directly/locally, the often slow sync of the GPO’s can be skipped, speeding up the configuration
phase and resulting test cycle.
Group assignments
First we will make sure our Admin-users will not be hindered by potential configuration flaws. To do this please open the local
users & group management (in Computer management). You will find 2 groups:
- FSlogix Profiles Include
Please remove the ‘everyone’ assignment and replace this with either ‘Domain users’, a custom (domain) testgroup or a
specific account used for testing.
- FSlogix Profiles Exclude
By default this group is empty. Please add ‘Domain admins’ here, to prevent our admin account depends on FSlogix. Also
add any service accounts used. Local accounts should be excluded by only having domain accounts in the include group .
FSlogix Profiles activation
Now we add the configuration to enable ODFC. Please add the following values to the registry:
KEY: HKLMSoftwareFSlogixProfiles
- Enabled: 1 (DWORD)
This essentially enables FSlogix Profiles. For the less secure admins: add this setting last ☺
- VHDLocations: “servershare$path” (RegSZMulti)
Obvious this path needs to be adjusted to match your pre-created share on the fileserver. DFS is supported.
Even as multiple paths are allowed, please use only one (by default, see remark in tips on multi-site)
Permissions on the share should be: (Test with everyone/full control)
o Scope: This folder, Accounts: everyone or domain users
Permissions: Modify (needed to check folder existence & check permissions)
o Scope: Subfolders and files, Accounts: OWNER-CREATOR
Permissions: Modify (to create / use the VHD(x)).
- VolumeType: “VHDX” for Win8/Win10/WinServer 2012+, “VHD” for Win7/WinServer 2008 (RegSZ)
For maintenance features afterwards using VHDX is advised if supported…
Reference for more settings: https://docs.fslogix.com/display/20170529/Office+365+Configuration+Settings
Check the latest version of FSlogix is referenced. Please start with only the above settings!
Some things to keep in mind:
- Disable Mandatory Profiles, if applicable!
If you use mandatory profiles, make sure the system is excluded from this. It would be a shame to roam the profile using
FSlogix, to have it wiped on logon (that is wat a mandatory profile does). It is preferred to have a local profile…
- Delete existing local profile instances
By default FSlogix will not apply/activate the FSlogix profile for a user, if there is an existing local profile present. There is a
setting available (intended for production) to enforce a FSlogix profile: (Warning: Deletes local userprofile)
DeleteLocalProfileWhenVHDShouldApply: 1 (dword)

3. 3 | P a g e Prianto Benelux - Vasteland 78 - 3011BN - Rotterdam
www.prianto.nl - +31(0)103007878
Testing
It is advised to restart the machine after applying (new) configuration settings. This way it is ensured the correct settings are
active. Now logon with a test-user, preferably a non-admin user. This user should be member of the ‘Include’-group!
What you should see:
- VHD(x) created
In the share a folder with the user-SID and name should be created. In this folder a VHD(x) called “Profile-<username>”
should be created. This VHD(x) should be about 200MB in size. FSlogix pre-initialises the VHD with 200MB to prevent
having to resize the disk on 1st real use (resulting in potential extreme fragmentation).
The user should be the owner of the folder (and VHD(x))
- The VHD(x) should be loaded
In Disk Management (Computer Management component) you should see the VHD for the user is loaded, but no drive
letter is assigned. This is correct!
- There should be 2 folders in the user-root: <username> and “local-<username>”
The “local-<username>” folder will hold files that should/must be on local storage. For example the credential store MUST
be local (will be synced to the VHD on login/logoff). On the other hand TEMP-folders (including internet cache) should not
be roamed, so will not be included as well, but deleted after logoff.
- In the log there should be ‘success’ messages
Check the logs in the following folder: “%PROGRAMDATA%FSlogixLogsProfiles”. There should be a log file with the
current date, containing as last section the logging for the test-user. This log should be easy interpretable containing
‘success’ messages.
Note: Please consider auto-starting the systemtray tool (frxtray.exe) as it is a quick way to access the logging. For FSlogix
Profiles a green light indicates all ok, giving you a quick indication if all is working fine..
If any of the above is not the case:
- Re-check if you did not miss a configuration item
- Do you have Microsoft UPD active, check the corresponding appendix too!
- Any obvious error message in the logs?
If you can fix it, patch the configuration to match it with your environment.
- Call in the help-lines (see corresponding appendix)
You got this far without issues? Give yourselves some shoulder-pads ☺ Well done!
Now we can verify that all works fine:
Start some applications and change some settings, which should be roamed in the user profile. Some simple examples could be
desktop background, change the screen zooming (100%-150%) or the font to be used in NotePad. Also cookies and favorites in
internet explorer are good test candidates. Or any application you deploy to your users (you know best what settings should be
roaming: The ones the users complain about whenever an user profile is reset.
The settings should roam with the user whenever you logon on a FSlogix enabled system. After log-off the VHD should be
released (check using Disk Management) and the user profile should be removed (including the ‘local-<username>’-folder.
Even made it to this point? You are great!
It is time to call your colleagues and show-off ☺

4. 4 | P a g e Prianto Benelux - Vasteland 78 - 3011BN - Rotterdam
www.prianto.nl - +31(0)103007878
Move to production
Now that everything is working in your test environment it is time to think about deploying it in your production environment.
Before we move to production some additional actions have to be prepared:
- License
Even as your trial might still be valid for some days, the last thing you would want to happen is that you deploy in
production and next the ‘real’ license is received late. Blame it on slow signing of the order, low speed internet making the
delivery of the digital email take ages or a mailman delivering the mail to the wrong address.
If end-users are used to the new features and suddenly all fails due to an expired license results in having a busy support-
line…
- Make the configuration ‘production-ready’
Put all the configuration items, optionally upgraded with some other features found in the options-list, in a GPO. Advised is
to also add the group membership assignment in the same GPO.
If you have other settings (like those for FSlogix Office365 Containers), just add the registry settings directly. You can add
the Profile settings as registry as well (using the ADMX is not required).
- VHD(x) share checkup
Check-out the share. Make a best-effort sizing and check the permissions - again…
Re-test!
Even with the best preparations there always is a small risk of production disturbance. In particular, if this is a RDS/XenApp
environment this could quickly impact multiple users and could require a system reboot. Either do this off-hour or exclude a
system from the production pool. Apply the test here, just in a ‘managed’ way (using deployment tools, GPO, …) and TEST!
If all seems to work fine, ask someone to be your guinea pig.
Sorry, but someone needs to do real-life production work to verify all works as before (or better ☺).
Success? Go Large and accept all the ‘well-done’ compliments.
This was a showcase deployment…
GPO remarks
If you want to configure the location using a GPO, and want it to include an environment variable (like %USERNAME%). This
should variable not be evaluated when applying the policy (computer startup), but when using the value set (in our case: user
logon). If you just add the following to the value to a GPO:
- %PROGRAMDATA%UserDataOutlook-%USERNAME%
The following will be added to the registry when applying the GPO:
- C:ProgramDataUserDataOutlook-LocalSystem << Orange are the variable-evaluations
So both variables are resolved when applying GPO, which is fine for ProgramData, but not for username.
LocalSystem is the account used when the system starts. The username should be resolved when logging on!
Use the following instead:
- %PROGRAMDATA%UserDataOutlook-%<USERNAME>%
This will leave the username intact till the logon-moment (the ‘<>’s are removed when applying the GPO)

5. 5 | P a g e Prianto Benelux - Vasteland 78 - 3011BN - Rotterdam
www.prianto.nl - +31(0)103007878
Trouble shooting guide
If it did not all work out…
First thing: Don’t Panic! The answer is most likely 42, or is a missed configuration setting.
‘It does not work’ checklist
- I can’t install FSlogix…
There are some prerequisites (required hotfixes for Windows for example). The setup will notify if these are missing, but
check them manually: https://docs.fslogix.com/display/20170529/FSLogix+Apps+Agent+Installation
- Redirections
Strongly advised… Especially redirecting the document folders (pictures, …) to a network location should be best practice.
If you suspect issues, please temporary disable the redirects (if possible)…
- Deploy the FSlogix Tray tool
This little tool shows a stoplight-indicator. Green means ‘all OK’. Orange and red indicate load failed or an error. It also
gives fast access to the logging…
- If a user logs off, and immediately logs on again… Loading the profile fails
After a user logs off it takes a few seconds (appx. 30 seconds) until the user profile is unloaded and released by Windows.
If a user tries to logon within this time, the VHD will be in use. Include the LockedRetryCount-setting (advice: 10) to give
some slack on the login. In combi with the 5 seconds interval it gives users a 1 minute before login fails.
- Mixed targets
If you have an environment with various targets, try to prevent mixing various versions for the same users. If you switch a
lot with OS (for example from a RDS on Server 2017 to Win7 VDI) expect that certain settings are not accepted on the
other OS, or even get corrupted. There is a reason Microsoft’s Roaming Profiles have a version number…
Either split the platforms and give incompatible environments separate VHD(x)’s
- After changing configuration settings, now things have errors
We noticed, in particular during first tests that ‘fixing’ a configuration issue might still raise an error if the data in the
VHD(x) is corrupted. The simplest way to fix this and have a clean situation is to log-off and delete the VHD(x). FSlogix will
re-create it upon logon.
- Multi-logon (Silo, …)
In some situations it could be possible a user is logged on multiple times. This can be due to having silo’s, but also errors in
the connection broker (new session, even as an existing session exists).
FSlogix does have a feature that allows multi-connection. This involves having differencing disks, merging settings and
other hard to explain situations to keep in mind. This is beyond this quick guide and please get in touch with experienced
support to help you in this case, and prevent undesired behavior..
- Search not working
o FSlogix Office 365 container license required
This feature requires a ODFC license, even as the search can be stored in the FSlogix Profile VHD.
o Wrong configuration of the search mode (RoamSearch)
Do you have the proper configuration applied? 1 (RDP: 2), also in the FSlogix APPS key?
Please check the Office Container documentation as well…
o RDP on Server 2008R2?
Search Roaming on Windows Server requires Server 2012R2 (or later), so it will not work on 2008R2
- Microsoft OneDrive roaming
Microsoft is pushing OneDrive at the moment, for example to replace users’ home drive. This also is one of the ‘more
frequently updated’ applications. Be aware that updates might break cache functionality of FSlogix.
o Support for OneDrive for Business, not the ‘personal’ version
Please deploy the production version of OneDrive – this is the only version of OneDrive supported by FSlogix:
https://support.office.com/en-us/article/New-OneDrive-sync-client-release-notes-845dcf18-f921-435e-bf28-4e24b95e5fc0#windows
o If you are deploying to Windows 10 – 1709 image
In this Windows 10 release Microsoft officially introduced placeholders (download files on demand). This feature
is not supported now, and OneDrive will fall back to full download of all synced data.

6. 6 | P a g e Prianto Benelux - Vasteland 78 - 3011BN - Rotterdam
www.prianto.nl - +31(0)103007878
This item is in investigation. Other solutions to roam user settings (UPD, …) do not support placeholders
either…
o Additional caching solutions (profile management)
Make sure that your current profile solution is not trying to save/roam anything about OneDrive. FSLogix handles
all of that.
If this checklist did not help
Sorry about that.
Please contact your support line… If there is local support available (should be communicated with your trial), feel free to
contact them. If you have an implementation partner (consultancy), they should be able to support you as well.
In case you get stuck or can’t reach either, file a support case at the FSlogix website. You will need to have/create a login
account to be able to access the support area. When creating an issue, you will see some suggestions. Please check these first.
With your support request, you will need to supply a log dump. There is a tool that collects all configuration and logging
information. In case you ‘forget’ this, be aware that the first response will be to run the tool and deliver the information. So,
save you the delay and include it on forehand…
Also: If you are in trial and get stuck, please don’t raise an ‘urgent/critical’ support case.
Thanks, in advance…
Version history
V1.0 Updated folder permissions
v0.99 First Pre-release (after review)