Andy M

Have an issue you can't solve? I offer consulting engagements and can be reached here: consulting[а 𝐭 ]amorales[․]org This is an extension of my FSLogix Office 365 container guide . All of the steps in that guide should be followed before continuing onto this one. Overview FSLogix profile containers allow you to easily roam user files and settings across multiple machines. A VHDX file will be created and it will store all user settings. This is similar to roaming profiles, but you do not have to deal with any login delays while files copy. Instead, the VHDX file is attached to the RDS server and the user's profile loads immediately. FSL Profiles vs UPDs Windows has a native solution called User Profile Disks, but it has some big limitations. With UPDs some applications will detect that data is being stored in a UNC path and malfunction. The best example of this is the inability to install Google Chrome extensions on UPDs. FSLogix drivers trick the OS into thinking that t...

One of the hurdles of UPDs and FSLogix is that they cause issues if they run out of space, and they don't alert users when they are out of space. In some cases you will waste time troubleshooting when you could have resolved it in a minute by just cleaning up the disk. I created the script below to address this issue. You can run it against your RDS servers and gateway, and you will not need to modify anything beyond the SMTP settings, thresholds, and exclusions. The script will do the following: Exit if it is not run on a server (you can comment this out if you use UPDs on Desktops) Query all collections on the RDG and scan all UPD paths *Must be run on the Gateway for this to work Query FSL Profile and ODFC paths *Must be run on computers with FSL enabled If low space disks are found the script will send you an email with a table of all the paths If nothing is found the script will exit. Known limitations: The script might report false positives/negatives if...

Have an issue you can't solve? I offer consulting engagements and can be reached here: consulting[а 𝐭 ]amorales[․]org Updated 2020-04-27 This search portion of this guide does not apply to Server 2019 since it  should roam the Windows search out of the box . However, you can still configure FSLogix to store Office 365 data.  In my experience it is best to avoid mixing FSLogix and UPDs. My recommendation is to go with FSLogix Profiles and FSLogix ODFC. If you have dealt with User Profile Disks and Office 365 then you might know about the issues with search indexing. Every time a user signs out of the RDS their index is cleared and it has to be rebuilt the next time they sign in. The index will never fully rebuild once you have 5+ users on the server since it throttles itself. Recently I discovered FSLogix which resolves this issue with minimal configuration. FSLogix creates its own UPD that it uses to store Outlook, OneDrive, and search index data. It then tricks Windo...

Have an issue you can't solve? I offer consulting engagements and can be reached here: consulting[а 𝐭 ]amorales[․]org Last Updated 2020-01-03 After months of testing I recommend deploying FSLogix Profile Containers instead of User Profile Disks. You can find my guide here . Some of the items below apply to FSL Profile Containers.  User Profile Disks (UPDs) are great for load balanced RDS farms since it allows users to seamlessly roam from server to server. The goal of this article will be to configure the RDS and file servers in a way that maximizes performance and reduces the likelihood of UPD disconnects. I'll keep this updated any time I find new improvements. Use FSLogix Before you even consider deploying UPDs you need to be aware of  this limitation . On Server 2012 and 2016 (Server 2019 does not have this issue,  but it doesn't support Office ) the Windows Search index is machine wide. This means that when a UPD is disconnected the user's index data is d...