New Jamf deployments will be as simple or complex as the needs of the environment.  My preferred way to explain Jamf is "who, what, when" - which users or devices are getting what software or settings, at the user's discretion or the admin's.

The initial setup would be an eight out of ten, but then they've got a service they call JumpStart, where they come and do the setup for you. The deployment took a few hours. Only one person was involved in the deployment process.

The initial setup was straightforward during Jump Start.

The setup is straightforward with help from Jamf to make sure you do not just install a server, but also tailor it to the needs of the (educational) organisation.

Its initial setup is complex. They can provide something in the beginning or they could have some kind of virtual thing that would help people prepare for it. I know it's a lot, and there's a lot they have to do, but if there was some kind of pre-starter package with the questions that people have asked while setting it up, it would be helpful. They can keep track of the questions that people ask and then put them in a knowledge base to give out before people come out to do the jump start.

I was partly involved in its deployment. I wasn't there the whole time when their person was here going over things. I was a part of it. They were asking a lot of questions about how we wanted it set up and how the structure is set up. We wanted it to mock our Active Directory environment, but the way it was set up, it was only two-tier, or we couldn't make it as nested as the way we wanted it, so we had to change things and group things in different ways. That threw us off a little bit. We had to organize departments in groups and we had to set them up. It took three to four days to deploy it from what I recall.

In terms of maintenance, we have to go in there and check on things. We also have to do software updates, which is expected because every software product that wants to stay current is going to have updates for it when the developer puts out new versions or updates to fix issues or add improvements to the product. It's just using the main apparatus and updating different modules. We're also in the RC program, so we get our releases a little bit early. We test their product a little bit ahead of time.

The setup is a breeze with the jump start program. A Jamf Pro rep will get you up and going right away. 

At my initial school district, it was pretty straight forward and we had a few days of training to make sure we were comfortable with the product.

I would rate the implementation process four out of five in terms of ease of deployment. It's not a new environment. Although it was new enrollment, we moved from MobileIron to Jamf. And the migration was smooth. The implementation was also smooth. 

First, we did the POC. Then, we implemented the same settings, et cetera, whatever we had in the MobileIron. We implemented those things in Jamf. After that, we just moved the users from the pilot phase and started the rollout for the business users.

In terms of the term that handles deployment and maintenance, initially during the implementation, as we have to manage both environments, MobileIron's and the Jamf's, the number of team members were around seven or eight. Now, we have dropped down to four.

It was set up as a POC and went into production a month after starting it.

The initial setup was straightforward as we had everything already prepared. However, it was also complex as there were a few differences between what I was used to and what Jamf is.

It was pretty straightforward once you're in the cloud. I see it from both ends. I was the one who could set up Jamf in the cloud for clients, and now, I'm on the other end having them doing it. I can just jump and set it up on my side. It takes about five minutes or less.

In terms of maintenance, if you have a good engineer, you don't really need a lot of support. I've supported over a thousand by myself.

The initial setup was quite complex. Once the initial setup was completed, I found it difficult to remember the steps. 

The installation process for iOS updates with Jamf Pro can be challenging. Upgrading from version 12 to 13, 13 to 14, and so on must be done in one go, taking hours and requiring a teacher's oversight to prevent issues. Pushing large updates increases the chance of errors, and iPads need to be at least 50% charged. Breaking updates into smaller chunks would be more practical for our over 800 iPads. Additionally, updating individual devices rather than the whole organization would offer more flexibility.

It was combination of being straightforward and complex. It took some time to set up the environment because we had to migrate the configurations and applications to Jamf. This took three months. 

The initial setup is quite simple. It is not at all complicated.

It is extremely simple for any user from an endpoint and an administrator's perspective.

If you're using a cloud-based deployment then it is straightforward and Jamf will spin that up for you. If you're on-premises then it's a $6,000 USD on-site visit. A technician will come on-site and spin up the on-premises solution for you. An on-premises version is primarily used by federal government agencies, more often than commercial agencies. Commercial agencies usually move to the cloud.

We used a kickstart consultant.

The initial setup was simple.

The initial setup was pretty straightforward, to be honest.

You needed to configure some prerequisites with Apple (ABM, APNS, VPP) but once everything was up and running, the rest was pretty seamless. The hardest part is taking a high-level look at your environment and determining how you want to manage the devices with the various scopes.

If you're new to Jamf Pro it may seem complex at first, but that's with anything new and different. Overall, I feel that the initial setup is straightforward.

The initial Jamf setup was straightforward, but we had to tweak things based on our requirements and existing environment. We had help from Jamf Professional Services and Support during the initial kickstart session.

Installing Jamf is pretty easy once you understand how DEP works and how to enroll devices. Zero-touch because we were aiming for a zero-touch environment, and it's entirely in the cloud. I'm not an expert in Jamf yet— I'm still learning— but for me, it was a lot easier to understand than Workspace ONE. Navigation is straightforward. It's not hard to create policies and manage the device. It's a lot simpler to create smart groups, view inventory, and see what the estate looks like. Jamf makes it easier to create a roadmap by giving me that view of where we need to be.

The initial setup was straightforward. 

For someone who's familiar with device management and designing this type of environment, I wouldn't say it's hard to set up Jamf. It can take anywhere between two days and one month, but that depends on the type and size of the customer. 

Jamf require clients to have two to three days initial training known as 'Jumpstart'. A Jamf expert comes to your location and goes through everything you need to do to get it up and running. If you're simply managing Mac OS, it's two days. If you're managing iOS as well, as we are, it's three days. Jumpstart is a paid-for service.

The installation was complex. 

As far as I have heard, it was straightforward, and the switch to Cloud only took an hour. It was much shorter than the quoted time.

The initial setup was a little tricky, coming in with zero experience, but the support of Jamf and colleagues was there and we got it to a great place fairly quickly.

We haven't set up the solution just yet for this latest project. We're going to discuss implementing it soon. However, I need the budget for it first. I'm waiting for that. Right now, we're working on a demo.

We have done the initial setup for previous projects, and as I recall, it was not complex, it was quite straightforward.

I personally take care of any maintenance needed.

The engineer that came to help with setup adapted to my skill level. Parts that were complex were necessary based on the task at hand. Most of the setup was straightforward and easy to follow. We only had a development system during the initial setup, so when I was required to repeat the steps for our production, it went very smoothly. 

The solution's initial setup is very straightforward. They also provide a guide for you to come in, and they help you with everything from start. 

It was already in the current company I work with. It was already deployed in the previous one. We did it in a pilot project for about a month, and then we were able to move it into production pretty quickly. It all depends on your skill level. When you bring the vendor in with their sort of prep package; they do it in about four days with you.

We have a first-level service desk. We also have first-level desktop support, and then third-level would be me. I'm probably the only one with a lot of Macs or Apple experience, therefore, I'm probably the single person maintaining it other than like the basic day-to-day stuff, that the other people do.

The installation was very easy. It was done by the software company which I work with. The implementation took one day.

straight forward no complex at all.

The initial setup of this solution is really simple. You commit to something called a JumpStart, which is basically a consultancy and training session to ensure that your Jamf meets your organization's needs from day one.

The initial setup is easy to understand and is absolutely straightforward. 

The setup was complete before I arrived.

The initial setup was foreign as we were new to MDM systems, but support walked us through setup and provided training. 

The setup was as easy as contacting our Jamf team.

It was a simple setup. Jamf has a lot of manuals and the whole Jamf Nation is helpful.

The initial setup is simple, actually. We just need a Jamf URL and a basic connection. I'm just talking about for setting up a cloud instance. Since everything will be there in the cloud, you just need the URL, the Jamf cloud URL, and admin credentials. The APNs certificate is required. That allows them to enroll your device. After that, there are so many options; the configuration profile, et cetera, needs to be created. That's a different scenario. However, in general, the setup is fine. 

A Mac deployment usually will take three to four minutes. It's quite fast. However, it depends on how you're configuring it. If you have the URL and if you have the username and the password, you can do it immediately.

From the user's end, it will take some time in situations where a user is not familiar with the enrollment process. There'll be follow-ups with the documents. If you are an engineer, it's easy, it's minutes, and it's fast.

How many engineers you need for deployment depends on how big the project is. It depends on the devices. We do have a client where we have around 18,000 devices. For that, currently, we have four engineers and they're easily managing it.

The initial setup was straightforward. We didn't experience any gap there. It was good.

Jamf is easy to deploy. As soon as you have the instance up and running and the activation code, it's really easy. If you use Apple Business Manager then you don't need to do very much to bring clients into Jamf Pro.

The software itself is both complex and straightforward, meaning that you do have to understand what you're doing, but everything you need to get started is on the web interface.

The setup was a bit complex and had a learning curve to get past.

The JumpStart is extremely valuable, even if it's a bit pricy. 

The setup can be as complex as you want.

The initial setup of this solution was straightforward. Jamf offered a jumpstart that got us up in running in no time.

Deployment of this solution is super easy.

The initial setup was mind-boggling. However, I had not used DEP or VPP prior to this. Without having completed the CCT first, I was learning far too many things for the first time with very little time to process all of it.

With Jamf Start, everything was easy to set up and roll out to our team. 

You need to have Jamf certified people on board for the initial setup. It's much easier once it is applied and managed by the IT team. It's not very difficult for them. 

Deployment takes from 15 minutes to one hour, depending on if the profile is already created. It also depends on connectivity and other things.

The initial setup was straightforward.

This initial setup is a bit complex.