![]() ![]() Intune can be thought of as Group Policy and some pieces of an RMM in the cloud. Intune works with all device flavors – Windows, iOS, MacOS, Android, etc. Intune is Mobile Device Management (MDM).This is the step we’re going to automate today in this post. These can be things like joining Azure AD, enrolling in Intune, skipping the setup screens, etc. The next time a machine goes through OOBE (either the first time or after a reset/reinstall of Windows) and is connected to the internet, will pick up the AutoPilot profile and follow the series of tasks you define. You can either preload your machine hardware IDs (or a CSV from your disty of choice) into AutoPilot or enroll them manually with a script. AutoPilot allows you to customize the Out-of-Box-Experience for the user when they power on a machine the first time.AutoPilot and Intune complement each other, but serve different purposes. Kind of, but not really, and this is a misconception that is very common in a lot of sysadmin circles. Aren’t AutoPilot and Intune two sides of the same coin? This is where most technical teams fall on their face – AutoPilot and Intune are complicated beasts with a lot of moving parts and many lack the foundational knowledge of things like Azure AD required to drive these solutions to completion. In this article we’re going to assume you’ve conquered implementing AutoPilot and Intune but need an intuitive way to get those existing machines enrolled in AutoPilot. I plan on writing a blog post in the near future laying out my case for why all MSPs should be aggressively aligning to AP/Intune and really explaining in depth all the reasons it’s a good idea. The present day incarnation of AutoPilot/Intune are production ready for almost all workloads. I would have considered the AutoPilot/Intune of January 2020 an incomplete product and not production ready for most workloads. While AutoPilot has been around for some time, it wasn’t really until COVID-19 that Microsoft started heavily improving both AutoPilot and Intune. Enter AutoPilot, Microsoft’s answer to controlling the OOBE. VPNs suck, SCCM sucks, going to the office in a pandemic to provision machines on the corporate LAN sucks, domain trust over VPN sucks…you get the idea. When the world as we knew it started to end in January 2020 many IT teams and MSPs found themselves in a tricky situation. Even before COVID-19 the landscape was changing and work from home was becoming more common. SCCM, Windows Deployment Toolkit, SmartDeploy – these are all products of a bygone era. Moving on!ĪutoPilot is one of the largest technological leaps forward Microsoft has made in machine provisioning. ![]() These aren’t the droids you’re looking for and everyone knows bad faith arguments like that belong in r/sysadmin. If you read this paragraph and said to yourself (or out loud to a coworker in your vicinity) “Well, this is why everyone just needs to use Linux/BSD/Windows3.1/HamSandwichOS!” then this is not the blog for you. Embrace the tools Microsoft is giving you to make your job easier instead of shunning the advancement of cloud management technologies. But for 90% of verticals and Windows shops, the future is now, old man. There’s a lot of perfectly valid reasons why AutoPilot and Intune might not be right for some of your clients – licensing requirements, etc. Most MSPs are failing to adopt technologies like AutoPilot and Intune. I’ll keep provisioning machines by hand, thanks!” ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |