1 2 Previous Next 24 Replies Latest reply on Sep 23, 2019 7:54 AM by jmatz135

    Mandatory Profile Trumps UEM Start Menu persistence?

    robsisk1972 Enthusiast

      In the effort to make logons faster and the Win10 Start menu quicker to launch, I implemented a mandatory profile on Win10 1803.   After implementation, logons were a little faster and the start menu went from taking 30 seconds to launch to launching instantaneously.  Although I like the result of the instantaneous start menu, the user's changes to the start menu is no longer being saved.  If I disable the mandatory profile within AD for a user, the UEM brings back the user start menu changes.     My question is:   Is there a way I can use both the mandatory profile and the UEM and allow user changes to be saved in the start menu? 

       

      Thanks
      Rob

        • 1. Re: Mandatory Profile Trumps UEM Start Menu persistence?
          DEMdev Master
          VMware Employees

          Hi robsisk1972,

           

          That use case is definitely supported – mandatory profiles were the main reason to create UEM ten years ago, and although the Windows 10 start menu has proven to be a bit tricky to persist and restore, our latest templates should do the trick.

           

          Which version of UEM are you using, and how are you persisting the start menu? Also, how did you create the mandatory profile?

          • 2. Re: Mandatory Profile Trumps UEM Start Menu persistence?
            robsisk1972 Enthusiast

            n Response to:  Which version of UEM are you using, and how are you persisting the start menu? Also, how did you create the mandatory profile?

             

            UEM Version = 9.4.0.820

             

            Mandatory Profile creation method = Creating a mandatory profile on Windows 10 1803 – JAMES-RANKIN.COM

             

            Persisting Start Menu Config =

            • 3. Re: Mandatory Profile Trumps UEM Start Menu persistence?
              DEMdev Master
              VMware Employees

              Hi robsisk1972,

               

              Thank you for the additional info. Could you try recreating your "Start Menu" Flex config file based on the UEM 9.4 Windows Common Setting?

              That will capture a few more registry and file system locations than your current config file.

              • 4. Re: Mandatory Profile Trumps UEM Start Menu persistence?
                robsisk1972 Enthusiast

                Unfortunately, the template didn't work either.

                 

                I removed my custom  config and used the default as shown below:

                • 5. Re: Mandatory Profile Trumps UEM Start Menu persistence?
                  DEMdev Master
                  VMware Employees

                  Hi robsisk1972,

                   

                  Thanks for trying that. Just in case: did you remove the corresponding profile archive from the previous export before testing this?

                   

                  Paging Pim_van_de_Vis and ijdemes to see if they have any insights.

                  • 6. Re: Mandatory Profile Trumps UEM Start Menu persistence?
                    robsisk1972 Enthusiast

                    I deleted the entire profile for this user and attempted again but it appears that the Madatory profile takes precedence over the UEM.   I did not think that was supposed to happen.   I will attempt to upload the log file of this last test that includes deleting the user archive.

                    • 7. Re: Mandatory Profile Trumps UEM Start Menu persistence?
                      DEMdev Master
                      VMware Employees

                      Those [WARN ] ExportFiles::ExportFile: Sharing violation for file '<LocalAppData>\Microsoft\Windows\CloudStore\cloudstore.dat' log messages are not boding well...

                       

                      I hope Pim, Ivan, or someone else can shed some light on this...

                      • 8. Re: Mandatory Profile Trumps UEM Start Menu persistence?
                        robsisk1972 Enthusiast

                        I hope so too!  Any help I could get from Pim_van_de_Vis or ijdemes would be greatly appreciated.   This is one of my last issues before I take this POC in to production.   I have my new VXRails racked and stacked and I am ready to move on.   

                         

                        The warning message in the logs is definitely related to the mandatory profile.  If the mandatory profile is not set in AD, these files don't exist nor does the warn message appear in the log. 

                         

                        The only thing I can think of that may impact this is the way I created the Mandatory Profile.   I have to confess that I cheated a bit:   One of the steps before you copy out the profile to a network share is that one must completely patch the OS.   By nature, I'm lazy and this takes about 5 hours to accomplish so I did NOT patch the OS before exporting the profile.   I don't know if this factors in or not but I am currently in the process of creating a new ManProfil with a fully patched OS.   Is should be done in about 3 hours of pain staking waiting and will post the results back.   IF this works, I will have more questions regarding will my mandatory profile need to be rebuilt every time I patch my OS.   IF so, I will not be a fan of Mandatory Profiles.   I have even heard that MS may not even support them much longer.  Is there any truth to this?

                        • 9. Re: Mandatory Profile Trumps UEM Start Menu persistence?
                          robsisk1972 Enthusiast

                          Well...That proved to be a waste of time.   I completely patched the OS and ran through all parts of the mandatory profile build and I have the exact same problem.  When I shutdown the machine after making changes to the start menu, I see this in the log file and all of my start menu changes have vanished.

                           

                          2018-07-25 12:17:50.386 [INFO ] Exporting file information

                          2018-07-25 12:17:50.386 [DEBUG] ExportFiles: Recursively processing folder '<LocalAppData>\Microsoft\Windows\Caches'

                          2018-07-25 12:17:50.407 [DEBUG] ExportFiles: Recursively processing folder '<LocalAppData>\Microsoft\Windows\CloudStore'

                          2018-07-25 12:17:50.407 [WARN ] ExportFiles::ExportFile: Sharing violation for file '<LocalAppData>\Microsoft\Windows\CloudStore\cloudstore.dat'

                          2018-07-25 12:17:50.409 [WARN ] ExportFiles::ExportFile: Sharing violation for file '<LocalAppData>\Microsoft\Windows\CloudStore\cloudstore.dat.LOG1'

                          2018-07-25 12:17:50.409 [WARN ] ExportFiles::ExportFile: Sharing violation for file '<LocalAppData>\Microsoft\Windows\CloudStore\cloudstore.dat.LOG2'

                          2018-07-25 12:17:50.411 [DEBUG] ExportFiles: Recursively processing folder '<LocalAppData>\Microsoft\Windows\Explorer'

                          2018-07-25 12:17:50.907 [INFO ] Exported file information successfully

                           

                          I'm at a loss!

                          • 10. Re: Mandatory Profile Trumps UEM Start Menu persistence?
                            Pim_van_de_Vis Expert
                            VMware EmployeesvExpert

                            I suspect the mandatory profile is the issue here.

                            Could you give this guide a try?

                            Creating an Optimized Windows Image for a VMware Horizon Virtual Desktop | VMware

                             

                            Just been published and I've heard good results with creating a mandatory profile when following these steps.

                            Please let me know the results.

                            1 person found this helpful
                            • 11. Re: Mandatory Profile Trumps UEM Start Menu persistence?
                              robsisk1972 Enthusiast

                              So it's not really the mandatory profile as much as it is 1803 and UEM.  After getting my VMWare ticket escalated, I was finally able to work with a tech and we figured out that it's a bug right now and is documented in the UEM 9.4 release notes.    So now I am building a new Master image and moving down to 1709 until it's fixed.   The major issues is that some files in %Localappdata% are in use and locked therefore can not be copied back to the network share.  

                               

                              VMware User Environment Manager Release Notes 9.4.0

                              Known Issues

                               

                              • Updated - Folder redirection of Roaming AppData does not function on Windows 10 Version 1803When configuring folder redirection to the AppData folder, the redirection fails for users on Windows 10 Version 1803 systems with the following error message in the log file: [ERROR] Error 0x80070057 redirecting 'AppData' folder to '\\server\share\...'Workaround: Upgrade Windows 10 Version 1803 to Build 17134.137 or later.
                              • You might encounter limitations with the Windows 10 Start Menu Windows Common SettingConfiguration settings for the Start menu itself, such as Show most used apps and Use Start full screen, are not saved.Workaround: No workaround exists for this issue.
                              • 12. Re: Mandatory Profile Trumps UEM Start Menu persistence?
                                DEMdev Master
                                VMware Employees

                                Hi robsisk1972,

                                 

                                That known issue is just about a few aspects of the start menu (like the ones mentioned there); the start menu tiles themselves roam correctly.

                                Note also that that issue is not specific for a particular Windows 10 version.

                                 

                                I don't have anything constructive to add, I'm afraid, but just wanted to warn that moving down to Version 1709 isn't necessarily going to make this work, until we figure out what exactly is happening in your setup.

                                • 13. Re: Mandatory Profile Trumps UEM Start Menu persistence?
                                  robsisk1972 Enthusiast

                                  How can you say that it is not specific to a version of windows 10 when it clearly states 1803 and was just added to the release notes 2 days ago?  Unless you have a better idea, I am proceeding.

                                  • 14. Re: Mandatory Profile Trumps UEM Start Menu persistence?
                                    DEMdev Master
                                    VMware Employees

                                    These are two separate issues (maybe more clearly visible on the original release notes page.)

                                     

                                    The update from a few days ago only applies to the folder redirection item. That is indeed specifically an issue on Version 1803, but Microsoft fixed that in a later build, hence the update.

                                    1 2 Previous Next