After the pandemic, my customers prefer the deployment of Jamf Connect on the cloud. However, for distributions, we prefer that the point should be local depending on the site and the number of devices we manage. Everything is on the cloud, but distribution points could be local. To be very honest, my experience has been that initially, it was a bit challenging for us as well, but after one integration, we understood everything, and after that, it is seamless for us. However, sometimes clients have different expectations, perhaps based on information they have found on the internet or from someone else. They are seeking that kind of option in Jamf Connect, but if it is not available, we cannot do anything. We explain to them politely that this is not a part of Jamf Connect. We cannot embed it because it is not developed by the vendor's team. We can work on the expectations they have, looking for free or open-source tools or priced ones, where our sales team comes into the picture. Depending on the environment and client requirements, things vary. A potential challenge for new users of Jamf Connect during the deployment stage, as I have seen, is that initially they face many problems. After our first implementation, we created common questionnaires and steps and, with each version change of Jamf Connect, we prepare documents to float to new users. We inform them about upcoming changes they will notice on their devices, such as the screens they will see, their login credentials, and how often their passwords will change or sync. If their password is mismatched, they will encounter similar screens. After that, they generally understand well. We also provide that document and other technical materials to the service desk teams, so if one hundred users come from a pool of ten thousand, they know what to explain. In rare cases, they need to do troubleshooting because if it is a new configuration, issues are somewhat rare, but in the technical world, they can arise. We explain to the service desk team what they need to do in those scenarios. We have already implemented Jamf Connect in seven different clients without issues reaching us; our service desk team has fixed those issues.
Senior Endpoint Engineer (macOS/Jamf) at PVH Corp.
Real User
Top 5
Dec 3, 2024
I would recommend Jamf Connect depending on the specific needs of the organization, particularly for those not reliant on user-level configuration profiles. I rate the solution six out of ten.
I would recommend Jamf Connect to companies who do not want to bind their devices to Active Directory due to compatibility issues with Apple devices. Active Directory works, but there are many complications with password syncing and keychains. I'd rate the solution nine out of ten.
Solution Lead Engineer at a tech vendor with 10,001+ employees
Real User
Top 5
Jun 21, 2024
It is easy to integrate into any existing IT workflow. I would give the tool itself a ten, but because of the support issues, I would rate it a nine out of ten.
A Jamf-certified technical guy with experience is needed to manage this tool. Customers who are completely based on the Apple ecosystem should use Jamf Connect. Someone who understands the tool and has had some hands-on experience will be able to manage it. Overall, I rate Jamf Connect ten out of ten.
Jamf Administrator at a financial services firm with 10,001+ employees
Real User
Jul 20, 2023
I rate Jamf Connect ten out of ten. We have 500 users and require two people for the maintenance of the solution. There is nothing on the market as good as Jamf Connect for Apple devices, including Microsoft Intune.
It's a good and stable tool, so you should use it if you have a need. It's not complicated. It simply needs to authenticate the user, and it does its job. Overall, I rate the solution a nine out of ten because it functions as it should. There are practically no issues with it.
Information Technology System Administrator at General Assembly
Real User
Jun 8, 2023
I'll give it a ten. It's a great product. I can't imagine how we could go back to life before we had it in our environment. It simplifies managing our devices, simplifies the user login experience, and improves the quality of service. Users don't have to log in to each and every website individually with their credentials.
Wandera Threat Defense helps businesses ensure a productive workforce, by defending both managed and unmanaged devices against the full spectrum of mobile threats. The solution includes security protections on the device and in the network, allowing for effective and targeted policy actions against even the most sophisticated attacks. Wandera Threat Defense is powered by MI:RIAM, a leading threat intelligence engine that learns in real-time through signals from 425 million sensors around the...
After the pandemic, my customers prefer the deployment of Jamf Connect on the cloud. However, for distributions, we prefer that the point should be local depending on the site and the number of devices we manage. Everything is on the cloud, but distribution points could be local. To be very honest, my experience has been that initially, it was a bit challenging for us as well, but after one integration, we understood everything, and after that, it is seamless for us. However, sometimes clients have different expectations, perhaps based on information they have found on the internet or from someone else. They are seeking that kind of option in Jamf Connect, but if it is not available, we cannot do anything. We explain to them politely that this is not a part of Jamf Connect. We cannot embed it because it is not developed by the vendor's team. We can work on the expectations they have, looking for free or open-source tools or priced ones, where our sales team comes into the picture. Depending on the environment and client requirements, things vary. A potential challenge for new users of Jamf Connect during the deployment stage, as I have seen, is that initially they face many problems. After our first implementation, we created common questionnaires and steps and, with each version change of Jamf Connect, we prepare documents to float to new users. We inform them about upcoming changes they will notice on their devices, such as the screens they will see, their login credentials, and how often their passwords will change or sync. If their password is mismatched, they will encounter similar screens. After that, they generally understand well. We also provide that document and other technical materials to the service desk teams, so if one hundred users come from a pool of ten thousand, they know what to explain. In rare cases, they need to do troubleshooting because if it is a new configuration, issues are somewhat rare, but in the technical world, they can arise. We explain to the service desk team what they need to do in those scenarios. We have already implemented Jamf Connect in seven different clients without issues reaching us; our service desk team has fixed those issues.
I would recommend Jamf Connect depending on the specific needs of the organization, particularly for those not reliant on user-level configuration profiles. I rate the solution six out of ten.
I would recommend Jamf Connect to companies who do not want to bind their devices to Active Directory due to compatibility issues with Apple devices. Active Directory works, but there are many complications with password syncing and keychains. I'd rate the solution nine out of ten.
It is easy to integrate into any existing IT workflow. I would give the tool itself a ten, but because of the support issues, I would rate it a nine out of ten.
A Jamf-certified technical guy with experience is needed to manage this tool. Customers who are completely based on the Apple ecosystem should use Jamf Connect. Someone who understands the tool and has had some hands-on experience will be able to manage it. Overall, I rate Jamf Connect ten out of ten.
I rate Jamf Connect ten out of ten. We have 500 users and require two people for the maintenance of the solution. There is nothing on the market as good as Jamf Connect for Apple devices, including Microsoft Intune.
It's a good and stable tool, so you should use it if you have a need. It's not complicated. It simply needs to authenticate the user, and it does its job. Overall, I rate the solution a nine out of ten because it functions as it should. There are practically no issues with it.
I'll give it a ten. It's a great product. I can't imagine how we could go back to life before we had it in our environment. It simplifies managing our devices, simplifies the user login experience, and improves the quality of service. Users don't have to log in to each and every website individually with their credentials.
I rate Jamf Connect eight out of 10. I like it better than any other MDM I've used for Apple devices.