New to Jamf Pro

Windows Server 2016 should be supported. Though, if you're doing it on-prem and not going with JAMF Cloud, Windows Server 2012 R2 might be less of a pain in the finances in terms of the per-core licensing structure they announced.

That said, I'd STRONGLY recommend installing your JAMF Pro server instance on either a Windows Server 2012 R2/2016 box or a Linux box and not a Mac server of any kind. It's not that the Mac couldn't do it. Just that Linux and Windows Server boxes are better geared for being, y'know, servers.

Welcome to JAMF!

Welcome...first advice is to feel free to come here and speak up with your questions. Most of us here like to help.

Second advice is to plan on working late on your jumpstart days. As you grasp each new item being taught, run with it and test on things you get. On things you don’t get, make your list and pepper your integrator until you do.

Third advice, in answer to your specific question...I second the advice above...you don’t have to host your jamf Pro server on a Mac. Use whatever platform you or your org is happy with. I cut my teeth on Macs growing up so at first I thought a Mac might be best, but it’s a total waste of a good Mac and it not always easy to get the software prerequisites right on a Mac these days without a little thought. If you work in a shop dominated by Windows admins, consider using Windows so they could help you out and bump a service if needed. If Ubuntu is your shop’s forte, then use that to host on. Jamf supports any host OS equally. For your Macs (as opposed to iOS devices) I would recommend also recommend a separate distribution point for your installer packages. Any well provisioned/provided SMB share should do. This way if you expand and grow, you can do so modularly.

One more point is to have your integrator teach you modern provisioning methods for Macs...old school imaging is on its way out given Apple’s recent developments .

Welcome and look forward to you posting
blackholemac

As said by @blackholemac, try and get yourself away from the imaging concept right from the start and have everything as enrol and then deployments or Self Service on top. It's just a better place to be and far less likely to fall foul of Apple's complete lack of a road mapping and penchant for springing "just one more thing" (that your going to hate as an admin because your completely unprepared for) surpises.

Thanks everyone, I decided to go with Windows Server 2016 and it's working fine so far. I'm getting myself acclimated with the dashboard and will add a few test machines just to see how everything looks.

Thanks again and I'll see you all in the threads!!!

Also you should join the macadmins slack

Sign-up here

We have a Mac Mini as a server and are switching to Linux. Just a heads up, Mac Minis aren't the best with SQL, good choice going with Windows

oh & Welcome tot he partyt~!