Normalize Identifying Corporate Devices in Your Software
1–10 of 62 posts
Re: Normalize Identifying Corporate Devices in Your Software
#2Normalizing this would start a game of cat & mouse, no?
Re: Normalize Identifying Corporate Devices in Your Software
#3Normalizing this would start a game of cat & mouse, no?
That, and a lot of false positives.
People that run an AD domain for their home lab, people that use apple configurator to create profiles for their own devices (can enable some settings/features that are otherwise gated behind using an MDM profile - like shared iPads), etc.
On the flip side, you are also missing all of the solopreneurs using your software for commercial use but obviously aren't spinning up a whole endpoint IT infrastructure to manage their own single device. Or contractors doing BYOD without MDM enrollment. Or small businesses/startups that are mostly BYOD, or don't do any kind of endpoint/device management...
So who are you going to catch, really?
Re: Normalize Identifying Corporate Devices in Your Software
#4Oh no they'll find out my company is i.manage.microsoft.com/DeviceGatewayProxy/ioshandler.ashx?Platform=MacMDM
Re: Normalize Identifying Corporate Devices in Your Software
#5Normalizing this would start a game of cat & mouse, no?
That, and a lot of false positives. People that run an AD domain for their home lab, people that use apple configurator to create profiles for their own devices (can enable some settings/features that are otherwise gated behind using an MDM profile - like shared iPads), etc. On the flip side, you are also missing all of the solopreneurs using your software for commercial use but obviously aren't spinning up a whole e…
A lot of people use MDM for managing their kids devices (pinning DNS for filtering etc.)
Re: Normalize Identifying Corporate Devices in Your Software
#6I heard folks here used MDM to give themselves more control over Apple security features that they otherwise don’t. This code example and scenario penalizes them by side effect
Re: Normalize Identifying Corporate Devices in Your Software
#7I heard folks here used MDM to give themselves more control over Apple security features that they otherwise don’t. This code example and scenario penalizes them by side effect
This happens in a lot of software in the Windows world, too. As soon as you run it on a non-Home SKU you’re suddenly The Enterprise, even as a home-gamer.
Re: Normalize Identifying Corporate Devices in Your Software
#8Normalizing this would start a game of cat & mouse, no?
How so? You think big corps would pressure corporate device management providers into making their services stealthier in order to avoid paying appropriate license fees for software that does this detection?
I'd always assume the worst of corporations but I think it's a little far fetched, probably doesn't affect their bottom line to just pay for the software.
Re: Normalize Identifying Corporate Devices in Your Software
#9Normalizing this would start a game of cat & mouse, no?
That, and a lot of false positives. People that run an AD domain for their home lab, people that use apple configurator to create profiles for their own devices (can enable some settings/features that are otherwise gated behind using an MDM profile - like shared iPads), etc. On the flip side, you are also missing all of the solopreneurs using your software for commercial use but obviously aren't spinning up a whole e…
> People that run an AD domain for their home lab, people that use apple configurator to create profiles for their own devices (can enable some settings/features that are otherwise gated behind using an MDM profile - like shared iPads), etc.
That's a tiny minority of your user base. You'll live. They'll live.
> So who are you going to catch, really?
Enterprises that are big enough to manage their fleet, but small enough to not enforce rules. Which is a good chunk of money.
Re: Normalize Identifying Corporate Devices in Your Software
#10As with every similar heavy-handed approach to enforcement you are making life difficult for the 99% of regular, honest users while the remaining 1% can trivially bypass it.