If you have ever managed an Apple device, you know this story all too well. In my experience, this ‘keep it simple’ approach is fine for most small organizations, however sooner or later we are all faced with a need to push the limits of what turn-key offerings can provide and look closely at the gears under the hood in order to move forward. With no on-prem infrastructure to build and maintain, we often learn just enough to make services like Intune do what we want and move on without a second thought to why or how. With the advent of MDM in the cloud, very little has changed in this regard except the exposure we receive to the inner workings of the platform. No matter if you used ConfigMan, DesktopCentral, Smart Deploy, or even good ol’ fashioned MDT the underlying premise has always been the same: Distribute a payload and run it. Always approach information you find outside (or inside for that matter) official documentation with skepticism and follow the golden rule: Never test in production.įor many Administrators, MDM for Windows has historically been a smattering of scripts, agents, group policy, and registry changes. As the name suggests, these accounts are based on experiences I’ve had in my own lab. Disclaimer: This blog is not intended to be advice on how to manage your environment.
0 Comments
Leave a Reply. |