Ennbee

What happens when a stranger on the Internet asks you to look at something they’ve got a problem with? Here we are, looking at how to deploy Microsoft Teams Backgrounds to macOS devices.

Installing the Configuration Manager client on Hybrid Azure AD Joined Autopilot devices should be an easy process right?

No one, and I mean no one, really wants to manually and individually assign Mobile Apps to Users or Devices in Intune in their 100’s, so we should find a solution for this bulk assignment approach.

Apple devices shouldn’t be exempt from Operating System compliance policies, and these policies should share the same fate as Windows ones, and be updated monthly in line with update release cycles.

Migrating iOS/iPadOS device to Microsoft Intune shouldn’t be a headache, and assignment of Automated Device Enrolment profiles with Apple Business Manager integration isn’t the exception.

Nothing has really changed in the Hybrid Join Autopilot space when it comes to device names, and we’re still stuck with useless naming conventions for these devices; sometimes a prefix and random characters just isn’t a good enough identification method for Windows devices.

Have you ever had the pleasure of migrating Configuration Manager clients from one domain to another, or maybe between Configuration Manager environments? Tired of manually reinstalling the client from the Console? Wanting a quick and easy way to keep on top of migrated devices? You’re in luck.

What if you want to ensure that all of your Microsoft Teams Rooms System accounts, and any future accounts can enrol using Android Device Administrator in Microsoft Intune?

With the impending retirement of the Azure AD Graph API and ADAL authentication methods, and by impending, I mean the end of 2022, we should probably look at how we move away from the existing authentication methods.