The current Jamf provisioning on most Dartmouth computers consists of a small number of profiles and policies that allow us to meet the requirements set by the ITC InfoSec team and help us configure customization to meet the institutional standards.
- These areas include and cover:
- Disk Encryption (FileVault)
- Firewall
- Crowdstrike endpoint security
- VPN (Global Protect)
- Splashtop (preference settings supporting official remote support tool)
- Dartmouth specific fonts
- Privacy preferences
- Core Dartmouth software installation
- Dartmouth Software Center (App store curated by ITC)
- Updated core software and optional applications
- Automation tasks for various audiences
- Printer Drivers
Common Questions / Concerns
I am concerned that having my machine managed will cause performance issues, is this true?
The agent on a client checks in with the JSS (Jamf Software Server) at computer start up and every 15 minutes thereafter, consuming 2KB of network traffic, 4MB of memory, and 0.10% CPU. In addition, computer inventory is uploaded to the JSS once a day, causing less than 200KB of network traffic, 8MB of memory, and 3.74% CPU. On average the inventory process takes 30 seconds to complete.
To date we have not seen or encountered performance issues caused by Jamf. If you feel you are experiencing performance issues related to Jamf please feel free to contact our team by heading over to our ITC Service Portal and opening a ticket. We'd be happy to discuss this with you.
I work from the Unix command line and need Root access to get my work done. It is my understanding that you block this.
While most users do not need this sort of low level access, we understand that there is a contingent of specialized areas that do. Jamf profiles and policies do not prevent you from enabling this capability on MacOS.