Architecture<\/span><\/h3>\nThe beauty of FSLogix Profile Containers and Office 365 Containers is the simplicity in approach that FSLogix has taken to solving the challenges of the end-user and administrator experiences.I like to refer to FSLogix\u2019s approach as no-architecture or architecture-less. What I mean by this is that there are no components, other than the FSLogix agent, to implement in your environment. In this approach, FSLogix solutions are flexible and deployed practically anywhere, whether on-premises or in a public cloud.The FSLogix Containers architecture consists of:<\/p>\n
\n- The FSLogix agent \u2013 a single agent that provides all functionality. The agent is either deployed to physical PCs, virtual desktops or in a master image<\/li>\n
- Group Policy \u2013 centralised configuration with existing infrastructure<\/li>\n
- Storage \u2013 host FSLogix Containers on standard SMB-based storage. Be sure to match SMB versions between clients and server for best performance. Shared folders could be hosted on Windows Server or natively by an existing storage array.<\/li>\n<\/ul>\n
That\u2019s it! No additional management layers, no back-end, no database, no web tier. Deployed using the services you already own.<\/p>\n
Storage<\/span><\/h3>\nThe most detailed considerations you may have will be for storage. Most partners and customers that I\u2019ve spoken to are using tiered storage or all-flash arrays, so storage performance should be excellent. You may need to give more consideration for storage performance to Profile Containers (rather than Office 365 Containers), given the nature of Windows Profiles; however, FSLogix Profile Containers will assist in optimising storage performance for profiles.<\/p>\n
Your storage layer should provide high availability, so disaster recovery will be something that to design for based on specific recovery requirements. In most cases, there\u2019s no need to replicate the Office 365 Containers because they contain only a cache of data stored in Office 365. Profile Containers will have a more significant impact on the user experience if unavailable, so consider replications to a secondary data centre.<\/p>\n
Preparing for Deployment<\/span><\/h3>\nTo prepare for deploying Profile Containers or Office 365 Containers, the primary process will be:<\/p>\n
\n- Create a secure shared folder to host the FSLogix Containers<\/li>\n
- Install the FSLogix agent into your master image<\/li>\n
- Create domain groups to allow targeting Containers to specific users<\/li>\n
- Create a Group Policy Object to configure the Profile Containers and Office 365 Containers Computer settings<\/li>\n<\/ul>\n
Finally, you can deploy your master image and link the GPO to the OU containing your computer accounts.<\/p>\n
A secure shared folder location for the FSLogix Containers is vital for ensuring least privilege. It\u2019s likely you\u2019re already doing this for home folders or user profiles.<\/p>\n
Microsoft has documented this approach in this article: How to dynamically create security-enhanced redirected folders or home folders<\/a><\/p>\nIf you want to take a shortcut, or are looking to automate the process, we have a script that you can use as a template, listed below. Use at your own risk, of course.<\/p>\n
That\u2019s it! No additional management layers, no back-end, no database, no web tier. Deployed using the services you already own.<\/p>\n
Storage<\/span><\/h3>\nThe most detailed considerations you may have will be for storage. Most partners and customers that I\u2019ve spoken to are using tiered storage or all-flash arrays, so storage performance should be excellent. You may need to give more consideration for storage performance to Profile Containers (rather than Office 365 Containers), given the nature of Windows Profiles; however, FSLogix Profile Containers will assist in optimising storage performance for profiles.<\/p>\n
Your storage layer should provide high availability, so disaster recovery will be something that to design for based on specific recovery requirements. In most cases, there\u2019s no need to replicate the Office 365 Containers because they contain only a cache of data stored in Office 365. Profile Containers will have a more significant impact on the user experience if unavailable, so consider replications to a secondary data centre.<\/p>\n
Preparing for Deployment<\/span><\/h3>\nTo prepare for deploying Profile Containers or Office 365 Containers, the primary process will be:<\/p>\n
\n- Create a secure shared folder to host the FSLogix Containers<\/li>\n
- Install the FSLogix agent into your master image<\/li>\n
- Create domain groups to allow targeting Containers to specific users<\/li>\n
- Create a Group Policy Object to configure the Profile Containers and Office 365 Containers Computer settings<\/li>\n<\/ul>\n
Finally, you can deploy your master image and link the GPO to the OU containing your computer accounts.<\/p>\n
A secure shared folder location for the FSLogix Containers is vital for ensuring least privilege. It\u2019s likely you\u2019re already doing this for home folders or user profiles.<\/p>\n
Microsoft has documented this approach in this article: How to dynamically create security-enhanced redirected folders or home folders<\/a><\/p>\nIf you want to take a shortcut, or are looking to automate the process, we have a script that you can use as a template, listed below. Use at your own risk, of course.<\/p>\n
To prepare for deploying Profile Containers or Office 365 Containers, the primary process will be:<\/p>\n
- \n
- Create a secure shared folder to host the FSLogix Containers<\/li>\n
- Install the FSLogix agent into your master image<\/li>\n
- Create domain groups to allow targeting Containers to specific users<\/li>\n
- Create a Group Policy Object to configure the Profile Containers and Office 365 Containers Computer settings<\/li>\n<\/ul>\n
Finally, you can deploy your master image and link the GPO to the OU containing your computer accounts.<\/p>\n
A secure shared folder location for the FSLogix Containers is vital for ensuring least privilege. It\u2019s likely you\u2019re already doing this for home folders or user profiles.<\/p>\n
Microsoft has documented this approach in this article: How to dynamically create security-enhanced redirected folders or home folders<\/a><\/p>\n
If you want to take a shortcut, or are looking to automate the process, we have a script that you can use as a template, listed below. Use at your own risk, of course.<\/p>\n
![\"\"](\"https:\/\/www.insentragroup.com\/wp-content\/uploads\/sites\/18\/2021\/02\/fslogix-install-step1-768x480.png\")
![\"\"](\"https:\/\/www.insentragroup.com\/wp-content\/uploads\/sites\/18\/2021\/02\/fslogix-localgroups.png\")
<\/p>\n![\"\"](\"https:\/\/www.insentragroup.com\/wp-content\/uploads\/sites\/18\/2021\/02\/fslogix-containersexplorer-aaron-1.png\")
<\/p>\n![\"\"](\"https:\/\/www.insentragroup.com\/wp-content\/uploads\/sites\/18\/2021\/02\/fslogix-containersexplorer-4.png\")
<\/p>\n