3 Replies Latest reply on Nov 15, 2019 4:02 AM by lucasitteam

    Win10-1803 losing time after every reboot

    lucasitteam Enthusiast

      I have tried everything possible. Probably someone can give another thought.

       

      I have built a Windows 10 (1803) image (without customizatIOn or customization) does not matter.

      Every time I reboot the VM, the time goes fast forward by 5 minutes. After the system boots, the time resets to domain time within 1 minute.

       

      Any idea why this is happening? This is production setup. I have windows 7 machines running on it and working perfectly fine.

       

      Below is what i see every time user logs. GPupdate solves the problem. I guess time sync issue is causing this problem.

       

        • 1. Re: Win10-1803 losing time after every reboot
          lucasitteam Enthusiast

          Just to update. it is not the timing issue.

          I tried the same Image on other setup and time is completely in sync. No lapses.

          Something else is causing this issue.

          Hope it helps someone.

          • 2. Re: Win10-1803 losing time after every reboot
            lucasitteam Enthusiast

            To keep everyone update

            1. Finally came to know why this is happening. By the way I'm not using UEM or Persona. I'm only using stupid/simple roaming profile.

            Every time I enable this roaming profile I face above problem. It is unclear why this is happening yet. I hope it will help someone. if I get a solution I will share here.

            • 3. Re: Win10-1803 losing time after every reboot
              lucasitteam Enthusiast

              .........Update........

              we were unable to find the root cause for this but what I found is every time I remove roaming profile setting from the group policy, it worked. We cannot use UEM as we have standard version of Horizon and it made no sense upgrade as the same setup works with Windows 7.

              So finally decided to go against using roaming profile. Instead I used FSLogix as we became entitled to it automatically after MS bought out this company. This also solved our O365 problem with Activation and Persistent desk. FSLogix simply works.

               

              I hope this thread helps someone. There is a interesting discussion here on FSLogix

               

              ---------------------------------------------------------------------------------------------------------

              Was it helpful? Let us know by completing this short survey here.