Hello Oliver,
Thank you very much for the project, it has significantly simplified our Autopilot deployments. What worked best for us was Approval mode and a bunch of group tags (to distinguish Employee vs Shared machine pretty much). I also went ahead and modified the client app a little bit so it automatically reboots the system once everything is assigned. That way, our end users only need to run the app once and don't touch the device at all, until a company branded sign-in screen is shown. I can submit a PR to an AutopilotManagerClient repo if you are okay with this.
One feature request if I may -- would be awesome to have an option to set a device name during approval.
The Device Name is definitely something that can be sent to Autopilot during enrollment - WindowsAutopilotInfo script has a separate command line switch for this. That would help me set the hostname that corresponds to our internal inventory without the need to rename all devices post-deployment.
Thanks
Vlad
Hello Oliver,
Thank you very much for the project, it has significantly simplified our Autopilot deployments. What worked best for us was Approval mode and a bunch of group tags (to distinguish Employee vs Shared machine pretty much). I also went ahead and modified the client app a little bit so it automatically reboots the system once everything is assigned. That way, our end users only need to run the app once and don't touch the device at all, until a company branded sign-in screen is shown. I can submit a PR to an AutopilotManagerClient repo if you are okay with this.
One feature request if I may -- would be awesome to have an option to set a device name during approval.
The Device Name is definitely something that can be sent to Autopilot during enrollment - WindowsAutopilotInfo script has a separate command line switch for this. That would help me set the hostname that corresponds to our internal inventory without the need to rename all devices post-deployment.
Thanks
Vlad