The “it just works” magic doesn’t apply in business environments

  • cm0002@lemmy.worldOP
    link
    fedilink
    arrow-up
    4
    arrow-down
    1
    ·
    4 days ago

    We are, but it’s not very helpful when the device can’t reach out to the MDM servers because it’s become disconnected from the WiFi for one reason or another

    Oh and apparently you can’t use an Ethernet USB dongle from the lock screen either, thanks Apple so wonderful and secure/s

    • Kit@lemmy.blahaj.zone
      link
      fedilink
      arrow-up
      3
      arrow-down
      2
      ·
      4 days ago

      You’re doing something wrong. If the devices are pre-enrolled in JAMF and you’ve configured PreStage Enrollment properly, they’ll automatically connect to corporate wifi on boot without needing a local user account or manual wifi connection.

      • cm0002@lemmy.worldOP
        link
        fedilink
        arrow-up
        9
        ·
        4 days ago

        Remote only company, there’s no “Corporate WiFi”, it does have a fallback WiFi profile where I have the employee start a hotspot on their phone with the matching info

        But it doesn’t always work on MacOS, almost like it stops trusting it if it’s not regularly connected to or something.

        Either way, no matter how you dice it, MacOS SUCKS on the business management side, Windows will let you do anything you want in any number of ways. MacOS is rigid and inflexible, the fact you need specific MDM platforms that focus on only MacOS/iOS to be any good should tell you that

        “Windows is an enterprise OS with consumer features, MacOS is a consumer OS with (half-assed) enterprise features” ~Me

        • Kit@lemmy.blahaj.zone
          link
          fedilink
          arrow-up
          7
          arrow-down
          1
          ·
          3 days ago

          I previously worked for a remote only company with similar roadblocks. The best option I found was to have the Macs shipped directly to a tech to be configured on their network (with their network profile configured in pre enrollment for ease of use) then ship it to the end user afterwards. The end users liked the “white glove” service.

          I worked for many years in endpoint management and actually like Macs. They’re not difficult to manage once you get the hang of it. In this oddly specific scenario, though, Windows would definitely be easier because the users could just login with their 365 account for provisioning.

          • cm0002@lemmy.worldOP
            link
            fedilink
            arrow-up
            3
            arrow-down
            1
            ·
            3 days ago

            Yup, that’s pretty much the flow I’ve had to put in place, I actually figured out how to pull off the MacBook box “seals” without ripping them and then reseal it when we’re done with so the employee feels like it’s brand new LMAO

            I worked for many years in endpoint management and actually like Macs. They’re not difficult to manage once you get the hang of it.

            Idk bro, seems like Apple considers all their business tooling and support as an after thought, perhaps it would be easier if we were all in on either/or but we have a 50/50 Windows/Mac/Android/iOS mixed environment and all the device management platforms seems to fall in to 2 categories: “Good with all devices except Apple” or “Good with Apple devices and sucky at everything else”

            Most in other mixed environments seem to settle into having 2 platforms, JAMF for Apple and something else for everything else. My funding request was denied for 2 though lol