Posted on 11-03-2017 04:33 AM
I seem to have this process running on all of my machines, some of them clean installs and enrolled, and it's the only thing I can think of.
Posted on 11-03-2017 05:55 AM
@Backoffice That's not happening on my systems enrolled with the Jamf binary. What version of macOS are you using? And when you say clean install, do you mean a fresh install of an image you've built or just running the Apple macOS installer on a wiped drive?
Posted on 11-03-2017 05:36 PM
The only Apache process Jamf runs is Apache Tomcat on your Jamf Pro server.
On the clients, Jamf uses the native macOS features for scheduling processes, running policies, etc. It doesn't install any new processes.
Posted on 11-09-2017 11:25 PM
Thanks for the reply guys.
I just created a build from a brand new install of Sierra, with createuserpkg added, and then used it to build via TMI.
However there is now out of date version of Apache running on most of these machines, and I can't think why, so thought it may have been this...
Posted on 11-10-2017 12:39 AM
@backoffice The mere existence of Apache shouldn’t be troublesome since it’s included in the OS by Apple but it shouldn’t be running by default on a clean install.
What the name of the process in Activity Monitor are you seeing?