Skip to content

Instantly share code, notes, and snippets.

@1RedOne
Created January 25, 2021 17:39
Show Gist options
  • Save 1RedOne/7109bd1377a168ff622c48ba839239d9 to your computer and use it in GitHub Desktop.
Save 1RedOne/7109bd1377a168ff622c48ba839239d9 to your computer and use it in GitHub Desktop.
Why ARC Matters

Ancient History

The world's most popular platform to manage giant ass windows envrionments is made by microsoft, it's called System Center Configuration Manager.  Now called MEMCM, Microsoft Endpoint. 

Before I became a dev I was a consultant setting up ConfigMgr for big companies for years.

This was good but was mostly built for managing devices the company owns, it didn't really support managing devices the user brought in, like a personal cell phone or personal laptop scenario.

So Microsoft made a new product that can handle that scenario, like how we joined Azure AD on our laptops to set them up. that's called MDM management. It uses a different channel to configure devices than SCCM did.

Now companies had both products and had two places to manage them. It sucked because to specify the same setting for both Intune managed and ConfigMgr managed devices meant finding the setting in two different apps, and something there wouldn't be feature parity.

That other product was called Intune, btw, for managing personal phones and laptops, etc.

Microsoft spent years merging them and now in big companies they can see user's machines and laptops and phones in the same place they manage servers and company owned laptops. Single pane of glass, one place to manage them.

ARC is doing the same thing, letting Azure tools like Azure Automations, Azure Resource Group Policies, ARM Templates and extensions all work on Company Owned Physical Computers and Servers.

Single pane of glass for customer's actual real computers and their Azure Stuff.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment