6 thoughts on “FSLogix Office 365 Container Setup

  1. Hi Nishanth, I have recently configured FSLogix office container in citrix and upm is used for profile. Vhdx is getting attached for the first time and once the ost is created but the vhdx is not getting attached for the subsequent login. Log says “cannot open virtual disk. It is used by another process”. My vdi is non persistent win10 and FSLogix version is the latest. Any suggestion would be very much helpful.

    1. Hi Girish, I am assuming “Concurrent user access” and “VHD access type” are not configured?

      The scope of troubleshooting this problem can be very broad or very small depending on how you have configured Office Container. Can you send the logs to me at gupta.nishith@outlook.com?

  2. I have some users using the old .VHD format while caching “all” email and not currently containing any search or other Office 365 containers. If I move to .VHDX and enable more Office 365 containers, how much more space should I allocate? Some current drives are 18GB, but I am not sure how much more data to allocate for the maximum size threshold for FSLogix. Thanks!

    1. Hi Jeff,

      The default size of the VHD(x) is 30 GBs. You can change that according to your requirement with the help of “Size in MBs” setting (see point 15).

      Unfortunately, there is no single rule to determine the size of the VHDX. You should start small or start with baseline and observe the growth for some period of time.

      Another option is to use Dynamic VHD(X) allocation (see point 16). Dynamic disk automatically expands to the actual size of the content on the disk. I haven’t used it so I am not sure if it automatically shrinks or not.

      Do read https://stealthpuppy.com/fslogix-containers-capacity/

      Additionally, if you are using profile container then try reducing the size of the user profile by excluding specific files and folders from user’s profile with the help of redirections.xml. See https://docs.microsoft.com/en-us/fslogix/manage-profile-content-cncpt.

  3. Thanks Nishith for taking time to write so detailed article. It is excellent article. Google search never shows this article. Only duckduckgo. For me most confusing part is concurrent session. You had it very much clarified. I have one doubt when you said “The disadvantage of Per-session unique disk is that there is no fully merged VHD therefore the currently attached VHD takes extra time to fully synchronize.” So these VHDX merge or they do not merge. e.g. If user has session01 -VHD and Session02-diffVHD. When user from session01 logsout, how does that data is synced?

    1. Glad you liked it, Preetam.
      With “Per-session unique disk” there is no difference disk that’s why no merge.
      Not sure how synchronization works in the background. Probably, next time I will capture the sync operation using Procmon or some other tool.

Leave a Reply