Jump to content
Welcome to our new Citrix community!
  • 0

FSLogix - Not creating profile containers but is creating Office 365 containers


Tom Swift

Question

6 answers to this question

Recommended Posts

  • 0

Just looking at the log made the error very clear.  It was giving an error 3 that there was a local profile detected.  Updated the GPO to delete the profile and use FSLogix instead.

 

 

1.  Add additional 500gb to FS01 server in VMware

2.  Format partition using ReFS

3.  Create folder named D:\Users and share with Everyone R/W

4.  Properties, Security, Add Creator Owner, Apply, Advanced, Edit Creator Owner (Full Control - Subfolders and files only), Everyone (Read & execute, List folder contents, Read, Write — Unchecked Full Control & Modify)

5.  On RDSH Servers: Download FSLogix, Open Zip file, x64, Release and install FSLogixAppsSetup, Restart

6.  Domain Controller \\domain.local\sysvol\domain.local\Policies\PolicyDefinitions - Copy FSLOGIX ADMX & ADML files from FSLogix installation media

7.  Domain Controller create GPO in Group Policy Objects named FSLogix and link to Servers / RDSH OU

     Computer Configuration, Policies, Administrative Templates, FSLogix, Office 365 Containers:

            Enabled = Enabled

            Include OneDrive data in container = Enabled

            Include OneNote data in container = Enabled

            Include Outlook data in container = Enabled

            Include Skype data in container = Enabled

            Set Outlook cached mode on successful container attach = Enabled

            Size in MBs = Enabled (50000 = 50gb)

            Store search database in Office 365 container = Enabled

            VHD location = Enabled (\\fs01\users)

            Virtual disk type = Enabled (VHDX) *All FSLogix VHD & VHDX files are thin provisioned / VHDX better for 2016 / 2019 Server

            Allow concurrent user sessions = Not Configured (optionally turn this on if users will be on multiple session hosts at the same time which for this environment should not be happening unless there is an issue with Microsoft session broker)

     Computer Configuration, Policies, Administrative Templates, FSLogix,  Profile Containers

            Delete local profile when FSLogix Profile should apply = Enabled

            Enabled = Enabled

            Size in MBs = Enabled (50000 = 50gb)

            VHD location = Enabled (\\fs01\users)

     Computer Configuration, Policies, Administrative Templates, FSLogix,  Profile Containers, Container and Directory Naming

            Virtual disk type = Enabled (VHDX) *All FSLogix VHD & VHDX files are thin provisioned / VHDX better for 2016 / 2019 Server

     Computer Configuration, Preferences, Control Panel Settings, Local Users and Groups

            Add, Name = FSLogix ODFC Include List, Order = 1, Action = Update, Delete all member users = Checked, Delete all member groups = Checked, Members = DOMAIN\Office365_Containers

            Add, Name = FSLogix Profile Include List, Order = 2, Action = Update, Delete all member users = Checked, Delete all member groups = Checked, Members = DOMAIN\Profile_Containers

8.  Create AD groups named Office365_Containers and Profile_Containers - Add accounts from that should use FSLogix (recommendation is to not add administrators)

9.  Confirm GPO is applied using RSOP on RDSH servers after having performed GPUPDATE /FORCE on Domain Controller and RDSH Servers

10.  Confirm registry has correct settings for FSLogix

            HKCU, SOFTWARE, FSLogix, ODFC, Session = Important values are ErrorCode = 0 and Status = 0

            HKCU, SOFTWARE, FSLogix, Profiles, Session = Important values are ErrorCode = 0 and Status = 0

11.  Confirm from command prompt DISKMGMT that an additional drive is attached which is used for O365 and FXLogix Profiles

12.  Confirm C:\Program Files\FSLogix\Apps\frxtray.exe (launches in System Tray) is Active

13.  FXLogix Logs are in C:\ProgramData\FSLogix\Logs\ODFC and C:\ProgramData\FSLogix\Logs\Profile

Link to comment
  • 0

Hi,
Stumbled upon this while looking for something else, bu tI think I have the answers.
Might not be exactly the same for Citrix, but for FSLogix, when you configure settings through Group Policy, there is a long standing bug.

Weirdly, when using a GPO for the Profile location only and not for the ODFC (office 365) profile path the registry key that get created is a REG_DWORD.
And, as profiles can be located in more than one location, the  Value should be a Multi String value  for VHDLocations

Located under  HKEY_LOCAL_MACHINE\SOFTWARE\FSLogix\Profiles
You can see this is you run the configuration manually running the C:\Program Files\FSLogix\Apps\ConfigurationTool.exe
and that's what we do. Everything, but this setting is configured in the GPO and this setting only is configured using the configuration tool.

And make sure you have you permissions just right on the share and top level ACLs. FSlogix uses these (and not the name) to determine which folder belongs to who.
And lastly, the option for not having a folder for each user seems to make sense, but complicates things or it did for me.

Link to comment
  • 0

Hi, 

just stumbled over this.

In my case I configured "VHD name pattern string" via GPO and set it to "Profile-%username" (which is actually the default configuration).

This breaks Profile container completely ;)

 

Error Code is 

[13:00:20.765][tid:000012e4.000016dc][WARN: 00000000]   User session for [SID] has an unexpected status. STATUS = 1

 

just if someone has the same problem.

 

Remove the values in registry or disable the two policies makes it work again.

 

 

Link to comment

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...