Forum Discussion

4 Replies

  • StuartK73​ 

    Hy,

    I am currently working on a project just for Windows Autopilot (Device Preparation).

    From my experience, even though MS says you can assign 10 APPs and scripts, I suggest keeping the APv2 profile as thin as possible.

    They optimize it every day and for example today I had a deployment that crashed on a script deployment in the enrollment monitor, but the user completed the enrollment without any problem.

    So in my opinion there is still room for optimization, but the enrollment process is very simple.

    If you need any advice on W11 enrollment, let me know.

    Good luck!

  • GriJ's avatar
    GriJ
    Brass Contributor

    Hi Stuart,

    we also implemented Enrollment Time Grouping. I used the instruction from Peter.
    https://petervanderwoude.nl/post/understanding-enrollment-time-grouping/

    The clear advantage is that the device hash no longer has to be imported. However, we use a hybrid environment and therefore cannot exploit the potential.

     

    We have already installed it for customers with our default settings and it works without any problems.

    The only hurdle during setup: 
    Service principal is called Intune Provisioning Client or Intune Autopilot ConfidentialClient.

    BR

     

    • Stuart_K_73's avatar
      Stuart_K_73
      Copper Contributor

      Thanks buddy.

       

      We have implemented ETG for Android Enterprise Dedicated and Fully Managed so far. 

       

      Will definitely look at the Autopilot stuff. Yeah, Peter is a great resource 😉 No hardware hash import sounds good 😉

       

      Stuart 

Resources