RUNNING JSS on WINDOWS SERVERS

I would say that one benefit of not using Mac OS X server is that Apple hardware really does not play nice in a server room environment and are definitely not enterprise-class machines (despite what Apple claims). Before I get criticized for writing that, please allow me to say I'm not trying to flame Apple here. As folks know, you can only legally run OSX (whatever version) on Apple hardware. So that limits the ability to run OSX. If you use Windows or Linux, you have a bunch of options. Both of those operating systems play nice in a variety of VM environments like Hyper-V or VMWare. You could also run each OS on standalone server hardware, like Dell PowerEdges. Since I brought up true server class hardware (not limited to just Dell, fyi), there would be considerable advantages like sophisticated hardware redundancies for up-time, many clustering options, storage solutions, management solutions, and so on. In my environment (a large university), I have the option of having a dedicated team of staff to manage the back-end infrastructure for me. They take care of all the headaches about maintaining both a VSphere environment and physical hardware. I am responsible for the service that runs on the hardware or server OS instance (like a JSS). I could not use any of the advantages I've described if I had to use OSX server based on limitations that come from Apple, both in terms of their hardware and OSX itself.

However, if you're smaller or medium sized shop, what I've written is probably all theoretical. If you can get away with, or are limited to, running Casper on a desktop class machine in a back-office room, then I'd say it boils down to personal preference. If you're familiar with OSX server, then in this case go purchase a Mini or Mac Pro and set up your JSS. The same idea applies to Linux or Windows, go purchase a solid PC machine (like a Dell Optiplex or Precision) and run Windows or Linux.

I would say having a Mac in the datacenter can be a tough sell for many places. A mac mini might have the muscle to run a small operation but it would depend on your architecture / how things are laid out. You could run a mix of operating systems (MySQL running on Windows, Tomcat on Linux and AFP distribution / Netboot available from a Mac Server). I like Linux much better than Windows as it is closer to the Mac OS, there is no need to RDP to a server and it runs a lot smoother. It really depends on what you are comfortable with and what your organization wants to support.

If you're in enterprise and have a datacenter team, the biggest benefit is you never have to worry about the server again. Whether physical or virtual, it's off your plate. You own the application (MySQL, Java and Tomcat), but "they" (the datacenter team) own the rest. They ensure the server is always up, they ensure services are always running, they back it up, they restore if there's a need. What's not to like?

I would echo the above, or at least the main two points for me:

1. Play nice in the DataCenter; the admins who keep this stuff up and running are generally all too happy to keep another Win2008R2 box/vm patched and backed up, whereas if you try to put an OS X server in there, you're on your own. Not to mention the hardware limitations: you've got aging Xserves that you can only get second hand, or desktop models that aren't really fit for managing the types of environments what call for something like the Casper Suite.

2. You only worry about the App; per the above, if they're keeping the server running and maintained, you just worry about Casper.

Now, I'll add the caveat that if you're a) a competent and diligent server admin, and b) your datacenter team is not, or c) you don't really have such a thing, what it boils down to is that you should manage what you're comfortable with. I would still steer you away from OS X because of the hardware limitations, and toward the easy route (Windows) or the Puts Hair On Your Chest route (grab the war and spin up a Unix server). Warning: if you're asking for advice, I doubt the latter is your particular mug of beer.

+1 to Don and JP.

If you're in a company large enough that has a server team of some sort, be their customer. You don't want to be in the server business as you'll have plenty else to keep you busy. Obviously, Windows will be supported. There's things to learn to get a good running JSS on that. Same can be said for Linux, however. People will have their preferences, but I'd say go with what your server team officially supports and "learn up" to that.

+1 to most of the comments, just that installation and distribution point sync are not "easy"/bulletproof on Windows, now or in the future.

Thanks Guys!!!!

How do you boot to the JSS for imaging on a windows server? We too are considering migrating to a VM on a standard intel server. For us, we are windows so we would use windows.

Thanks for any input

You cannot boot to a JSS running on Windows. If you can do that now, then it's a simple matter that your JSS is on a Mac server where you've enabled the Netboot service.

Going forward if you move JSS to a Windows box, you either keep and OS X server around with Netboot configured or you install NetSUS as either an appliance or on a full Linux server.

https://jamfnation.jamfsoftware.com/viewProduct.html?id=180&view=info

Just noticed @RobertHammen wrote:

+1 to most of the comments, just that installation and distribution point sync are not "easy"/bulletproof on Windows, now or in the future.

Our datacenter teams were nice to us, they installed rsync on our virtual Windows servers. Syncing distribution points wasn't hard, and much easier and more reliable than trying to use robocopy.

Our datacenter teams were nice to us, they installed rsync on our virtual Windows servers. Syncing distribution points wasn't hard, and much easier and more reliable than trying to use robocopy.

@donmontalvo What troubles did you encounter syncing DPs' with Robocopy?

I'm getting ready to execute on project plans to migrate JSS from Xserve to WinVM and migrate a dozen DP's from Xserve's to Win shares. I fully expect our server teams will want to default to Robocopy for DP replication.

@dpertschi Now that JSS 9 does flat files only, you probably won't run into any problems. The issues we had were from bundle PKG/MPKG's getting whacked.

We have to Mac Minis sitting in our Data Center for a clustered JSS. I'm totally fine with self-managing the server so it's great for me. Every once in a while it causes headaches, like after running an OS update and rebooting one of the Minis wouldn't boot up and someone had to go hard reboot it for me and I had to wait a few days for that to happen… but we still have the database team maintaining/backing up the DB and I run updates to the Minis themselves and so far it's been pretty pleasant. I've also learned a lot about the upkeep, which is a nice bonus.