Hi, Thank you so much for making this video. Can you please also make a video on how to automate the corp identifier upload using Azure Functions as well.
Great script! I want to check out that automation video because I only used it for Update Management a while back and never really got into more use from it. The one weird thing I am noticing about this process compared to V1 is that V1 was done during OOBE, this one is pushed to devices that have already been enrolled. So all of the benefits that we got with V1 (customizing OOBE), can't happen the first time around for the new method and new devices. We've got the cart before the horse now.
Great video, thanks. Great help for getting going with automation. Good points in the intro. There will be use cases for this, as you point out. But not my org. Not unless they come up something to manage the OOBE like V1 does, which feels unlikely given the design. There are valid reasons to be disappointed. It is hard to see why the new shiny ESP UI is exclusive to the V2 process. Same goes for the improved reporting and diagnostics. And the configuration UI in Intune is also better for V2. I'd like those things back ported, V1 needs some attention too, if it's not being abandoned. Then MS have said "We expect both environments to exist in parallel _for a while_ as we work to improve the experience and add more functionality." "For a while" is super vague, but it doesn't _feel_ like a long time. So that's going to press people's buttons when the new thing just can't ever do what the old thing does. The fact that it's also broken on launch just adds to the negative first impression. MS could've handled this a lot better, for sure.
Thanks. I can completely understand that perspective. My hope is they eventually take the improved pieces of V2 and retro fit them to V1 long before they decommission it. But time will tell.
![[UA] Team Vitality проти NAVI | IEM Cologne 2024](http://i.ytimg.com/vi/wttO1zVRTC0/mqdefault.jpg)
Hi,
Thank you so much for making this video.
Can you please also make a video on how to automate the corp identifier upload using Azure Functions as well.
Great script! I want to check out that automation video because I only used it for Update Management a while back and never really got into more use from it. The one weird thing I am noticing about this process compared to V1 is that V1 was done during OOBE, this one is pushed to devices that have already been enrolled. So all of the benefits that we got with V1 (customizing OOBE), can't happen the first time around for the new method and new devices. We've got the cart before the horse now.
Correct. This is going to be for a very different use case VS APV1
Our tenant is the same as your Rubix tenant (missing the CSV import part).
Great video, thanks. Great help for getting going with automation.
Good points in the intro. There will be use cases for this, as you point out. But not my org. Not unless they come up something to manage the OOBE like V1 does, which feels unlikely given the design.
There are valid reasons to be disappointed. It is hard to see why the new shiny ESP UI is exclusive to the V2 process. Same goes for the improved reporting and diagnostics. And the configuration UI in Intune is also better for V2. I'd like those things back ported, V1 needs some attention too, if it's not being abandoned. Then MS have said "We expect both environments to exist in parallel _for a while_ as we work to improve the experience and add more functionality." "For a while" is super vague, but it doesn't _feel_ like a long time. So that's going to press people's buttons when the new thing just can't ever do what the old thing does. The fact that it's also broken on launch just adds to the negative first impression. MS could've handled this a lot better, for sure.
Thanks. I can completely understand that perspective. My hope is they eventually take the improved pieces of V2 and retro fit them to V1 long before they decommission it. But time will tell.
Dude you are an inspiration.
I don’t even know what to say. Thanks!
Very helpful! Thank you
helpful! Thank you
Positivity is one thing... Releasing this as a "production ready" feature is a pi$$ take.
Fair enough :)