MicrosoftHi,
I think these are great news. I am especially glad to be free of the HW hash. The issue of motherboard changes is very significant for us as it disrupts business processes, increases support overhead, necessitates contacting MS support more often, and creates logistical challenges for our clients. Removing this element will be beneficial for us.
As I understand, this issue can be avoided by uploading lists of device serial numbers, etc. (.csv). However, I have a question about the TPM chip evaluation through the ESP process: Does the new AutoPilotV2 still use TPM for AAD enrollment? We've had some issues there as well.
I suppose the Get-AutopilotDiagnostics script might need to be checked again. 🙂
We've been using self-deployed devices configured later with the SharedPC policy, and we've experienced issues with this method, particularly in relation to MDT.
I must say that I don’t fully understand the replacement of dynamic grouping with enrollment time grouping. I would appreciate more information on that.
From what I read, we still have the option to choose between AutoPilotV1 and AutoPilotV2, and it seems we can use a combination of both where appropriate.
I will be following this with great interest. 🙂
Best regards,
