FSLogix S2E1 Configuring FSLogix Profiles and Office Containers for the enterprise
HTML-код
- Опубликовано: 17 сен 2024
- The most applicable configuration settings common to both Profiles and Office products
Enabled 0:52
VHDLocations 1:19
SizeInMBs 5:01
FlipFlopProfileDirectoryName 13:58
SIDDirNameMatch 15:52
SIDDirNamePattern 15:52
Recorded with Camtasia Studio
www.techsmith....
one of the best videos about this topic
Thank you Jim. Now looking at FSLogix for roaming profiles and this was easy yet detailed to get it working for our purposes.
Really thorough and well explained video, thank you very much.
Hi Jim.
The profile gets locked on servers on logoff sometimes and becomes impossible to find in which machine. Any ways around it or to find which Multisession the user got locked this on?
First thing to do is make sure you're on the latest version of FSLogix as there have been fixes implemented for this. If you still have an issue there are some community PowerShell scripts to help.
@@JimMoyle thanks Jim!
More please !!
I also accidently deleted your other comment/question sorry! Which was to ask why I chose VHD over VHDX, I'm just showing how to modify default behaviour, if compatibility allows vhdx should always be first choice.
Hyper-v role for the tools is really bad. I had to use diskpart to shrink as hyper v role could not be installed. Really bad, because it makes it less sufficient.
This was fantastic...would you be able to do one on the different ProfileType options? Also, do you recommend using both Profile Containers and Office Containers together?
As soon as I get time I will do this yep.
Great video - I have a quick question. Currently have a whole company running on just fslogix profiles, as I haven't enabled Office Containers. If I now go ahead and enable this, what will happen with the existing profiles? Does fslogix pull the Office related data out and move it to the Office Containers? Will there be any impact on the users? Thanks again for the video
No, the stale data will stay in the containers and new will be pulled down from Azure into the O365 containers. There are some scripts around to clean them up.
@@JimMoyle OK thanks - so it should be transparent to the user. Thanks again.
Hi Jim, excellent explanation. Could you please help me to figure out below errors in my environment (WS2016 + Profile container only)
Errors
1. Creating new user profile disk (user's registry hive was missing) (The system cannot find the file specified.)
2. Error removing profile key (The system cannot find the file specified.)
3. Export registry failure (Incorrect function.)
The above three error I am getting for some users. Please help me to resolve the matter.
Many thanks.
SM
I'm afraid you'll need to raise a support case for this. One hint, make sure you don't have competing profile solutions in place.
Why not use the gpo?