- WINDOWS 10 START MENU FOLDER MODIFICATIONS LICENSE
- WINDOWS 10 START MENU FOLDER MODIFICATIONS WINDOWS
I've set it up to run evey night on my profile directory and it cleans up very nice (the profile of 11GB was reduced to 3GB). I did find a solution for this also! Look at ShrinkFSL. I even had a user which had a 11GB profile VHDX which contained only 3GB of data. After using it for about 3 months now on a group of 30 test people I noticed the VHDX files are becoming quite large compared to the data that is actually in it. Although I must admit I was also worried about the profile bloat. We are also very happy with this solution. Here is a very succinct article that got me started.
WINDOWS 10 START MENU FOLDER MODIFICATIONS LICENSE
FSlogix is free with certain Microsoft agreements, including RDS cals, but I read in a recent release they stopped license checking. So I do not have an answer for traditional Microsoft roaming profiles and 1909. If profile growth becomes an issue we will revisit the exclusions.
I cannot yet say exactly which folder was responsible for breaking the menu, but it sure is obscure. Due to time constraints I removed every appdata - Microsoft exclusion, and the start menu started working again. I started removing every exclusion that seemed could affect the start menu, with no luck. With concerns about profile bloat, I started using exclusions from "app-data." I started with an example redirect.xml file I found. I was also able to continue to use our redirected folders so nobody loses data, no data has to be migrated. The initial setup was rather easy, and had my first test in a couple hours. Previous to this I didn't even know Microsoft had bought the technology, so thank you. I was finally able to determine that our school has an agreement that covers FSlogix. Then it is fine until you recompose or login from a different pool. The issue is definitely something in the profile, because to fix the issue you delete the user profile and allow it to be recreated at next logon. We do not have Enterprise so UDE or whatever the latest and greatest is, is not an option.
WINDOWS 10 START MENU FOLDER MODIFICATIONS WINDOWS
So Windows Roaming Profiles and redirected folders have been working rock solid for us. We are using Windows roaming profiles, because back when we set this all up on 7.5.1 Persona had serious known issues, one that it wouldn't roam the start menu settings. This behavior did not happen previously with Win 1803.We have not changed any GPO or any other settings. Login from the second pool and the start menu breaks. Login from the first pool, and everything is good. In addition, we have two pools from the same image, the only difference being one pool is vGPU enabled.
If the user profile is deleted, and recreated in a subsequent logon, then the start menu is great again. But a subsequent recompose for even the smallest change and the start menu breaks, both the apps and the tiles. The first time I recomposed the VM was great, everything fine. The master looks great and I created and imported a custom start layout for the tiles. Does anyone know if or how the underpinnings of the Start Menu have changed from 1803 to 1909? We recently upgraded from 7.5.1 to 7.11, and created a new Image.
0 kommentar(er)
