fslogix O365 container bug

Update 25.07.2019:
Finally Microsoft/fslogix fixed the issue. The development team found this is a problem with a value that OneDrive uses to open files that are cached by the FSLogix frxdrvvt driver. It’s timing out the fslogix cache entry too quickly. To fix it, create these two registry values and reboot the system:

I’m so happy that this issue is now fixed (and my customers as well). I don’t know yet if this issue will be addressed in a next fslogix version, but I hope so.

Original post:
As you probably know, fslogix has been acquired by Microsoft and beginning July 1 2019, the fslogix product is now finally available for many Microsoft customers. You can read more about here: https://www.microsoft.com/en-us/microsoft-365/blog/2019/07/01/improving-office-app-experience-virtual-environments/.

When you follow all the social media channels, you will see many thumbs up for the fslogix products. I agree, fslogix solved a problem many of us working in the EUC field, have had until fslogix was there. Using apps like Onedrive in a virtual non-persistent user environment was challenging and that was one of the reasons why Microsoft decided to acquire fslogix. It’s a needed puzzle piece in order to have Office 365 ProPlus with Teams, Onedrive etc. working properly on Windows Virtual Desktop. That sounds all good, right? Yes, indeed, but….there is still a known issue when you use fslogix O365 containers. If you use Windows 10 1709 or 1803 (I didn’t test newer version, but assume it will be the same) with Onedrive and the files on-demand feature enabled, you will get into troubles when you want to save existing Office documents located on Onedrive. Usually it works the first time with a new document (or a document that hasn’t been downloaded yet). If you open an existing Office document that has already been downloaded modify and save it, you will get the following error message:

You won’t be able to save Office documents any longer. Means you cannot use fslogix O365 containers in production if your users need to modify Office documents on Onedrive when the files on-demand feature is enabled. Note that other files like .txt files aren’t affected. A possible workaround (if I’m allowed to say that this is a workaround) is to disable the files on-demand feature by Group Policy. Then everything works as expected. The result will be huge vhd files because most of the users will sync their complete Onedrive folder (default max size is 30 GB per user vhd file).

I do have an open fslogix support for that particular issue for 10 months and it’s very challenging to make any progress as I guess the integration of fslogix into the Microsoft organization takes much higher priority for them and is of course also very time consuming. At least fslogix confirmed this is a bug that either the fslogix dev team, Onedrive dev team or both have to fix. So it won’t be as easy as it looks like to fix it. I was hoping it will be fixed with the first “Microsoft release”, fslogix 1907, but unfortunately it’s not. But the behavior seems to be a little different. With fslogix 1907 when you try to save a document a few times in a row, it will save the document after a few tries (still Autosave doesn’t work). That’s better than before, but still not ready for production. I’m really wondering how many people use fslogix O365 profile containers in production in the mentioned environment. I guess not many, otherwise much more customers would have reported the issue. I believe most of the customers is fslogix O365 containers on Server 2016 and because the files on-demand feature isn’t supported, the issue won’t be seen here.

Conclusion: fslogix developed a fantastic product, but unfortunately O365 container won’t work properly on Win 10 with Onedrive files on-demand feature enabled (yet). Due to the official Microsoft announcement of the new fslogix 1907 version and a clear communication about the fslogix use rights, there will be a lot more customers going to implement fslogix O365 containers. Please be aware of the mentioned bug that isn’t fixed yet so that you won’t get in trouble when you start to use in production.

I will update that post as soon as I do have some news. Stay tuned.

Error: “Cannot Complete Your Request” When Using Custom Portal Theme on AAA or Gateway VServer

In case you see this error, that shows up right when you open the aaa or gateway vserver (before logging in), this is the solution: https://support.citrix.com/article/CTX244520

When the “Integrated caching” feature isn’t licensed, you will just need to execute the following command:

set aaa parameter -enableStaticPageCaching NO

I tested it on Netscaler ADC 12.1 51.19 and it worked perfectly.

Storefront 3.9 – default Website not working

Recently I upgraded to Storefront 3.9. Setting the default Website no longer works in that verion:

Disable the setting and enable it again won’t make any difference. That setting configures the web.config file in the root folder of IIS (c:\intetpub\wwwroot\web.config). As a workaround you can configure it in the web.config by yourself. Just add the following config:

<?xml version=”1.0″ encoding=”UTF-8″?>
<httpRedirect enabled=”true” destination=”https://FQDN/Citrix/StoreWeb” childOnly=”true” />

Replace the destination value with your Website of the store and you’re done.

Adobe solved the z@ tmp files issue

Back in 2014 I posted about these z@ tmp files that are sometimes created by Adobe Acrobat (or Reader) in the temp Folder and cannot be deleted anymore afterwards because they are still in use (see post here).

Adobe finally solved the issue in Adobe Reader 11.0.14, released in January 2016. See the release notes here: http://www.adobe.com/devnet-docs/acrobatetk/tools/ReleaseNotes/11/11.0.14.html

How to bring back the customized Delivery Group icons with Storefront 3.0

When you migrate to Storefront 3.0, you probably will see that the customized delivery Group Icons are gone. There’s an Powershell command that brings those icons back, just run it on the Storefront Server:

& ‘C:\Program Files\Citrix\Receiver StoreFront\Scripts\ImportModules.ps1’

Disable-DSStoreSubstituteDesktopImage -SiteId 1 -VirtualPath /Citrix/Store


Note that you might have to Change the paths according to your Installation.

Reserve your free upgrade to Windows 10…

…yes, that’s the message I got after clicking on the Windows symbol that appeared in my system tray:


That confirms the statement of a free upgrade, although it’s time limited (I believe 1 year). Today I read that Win 10 would be delayed and will be released for public end of August. Let’s see….

Update 8.6.15: Windows 10 will be available end of July….

App-V 5.0 SP3 Sequencer issue

There is a bug with the App-V 5.0 SP3 Sequencer that has just been release some days ago. When you try to install the MSI of a created App-V package created by the SP3 Sequencer, the installation only works when you run the MSI installation in an elevated cmd (start cmd.exe with “Run as Administrator”). If you deploy your apps with SCCM, you’re usually not affected when you run the installation by the system account.

The following error messages are shown when you install the msi without elevated cmd:

error1 error2

I created an mst that fixes the issue. Do the following steps to apply the fix :

  1. Download the mst that fixes the issue: http://www.notmyfault.ch/downloads/AppV5_SP3Fix.zip
  2. Extract the mst file and copy it into the same folder as your msi file
  3. Run the following command:
    msiexec /i YourAppvPackage.msi TRANSFORMS=AppV5_SP3Fix.mst

If you want to run it unattended, add /qb as parameter. Make sure your current directory is the one that contains the msi/mst or just add the full path to your msi and mst. Don’t rename your msi, use the original name that has been created by the sequencer.

You can also permanently apply the transform (mst) to the msi with Orca.

The root cause of the issue is a changed setting in the MSI. The custom actions responsible to publish and remove the App-V package won’t run under the local system account with full privileges (no impersonation)


The mst I created changes that configuration back so that these custom actions run under the local system account with full privileges (no impersonation) as it was prior to SP3. This change is done by changing the above marked type values from 1025 to 3073.