UPDATE: We've since updated to JSS 9.3 & we no longer have this issue.
We recently updated our JSS from 8.73 > 9.22 & on the whole it’s been a non-event.
However, we started to find that some Self Service policies were erroring with the below message post the upgrade.
Even though we’re using a HTTP/S distribution point, that should allow for resumable downloads we sometimes see the below error;
Within our Casper environment all our distribution points are HTTPS. On occasions we’ll get the emails from our JAMF Software Server containing the below:
As mentioned in my previous post, we have a simple cluster setup for our JSS.
The “cloud” accessible version of our JSS we disable the web app, so if you navigate to it you’ll be presented with the below:
This weekend our firewalls were replaced with us moving from one vendor to another. This took a little longer than required due to some issues with rules & inside outside definitions, but my colleague was more than up to the challenge.
This change required our VPN config profile to be re-pushed, it seemed to work. But further testing revealed we had an issue.
We have a simple cluster for our JSS with one server “cloud” accessible in the DMZ & another on our WAN that is our master JSS, post firewall change I checked:
Subject’s a mouthful eh? Basically, I needed for my 10.7 Macs to authenticate to our RADIUS wireless network using PEAP authentication & the Mac’s Certficate from our domain.
UPDATE: Since 8.61+ User information can be submitted following the method outlined here.
For couple of years now i’ve ran various flavours of the below script via a login policy on my Mac clients.
The purpose of this script is to first check if the user is a network user, & if so then perform a lookup of their account against AD grabbing information that can then be submitted to the JSS in the relevant fields as per the below, (click to enlarge).
NOTE: This script needs to be customised for YOUR environment for it to work, some fields of data may well be the same.. but it depends on dumb luck & your AD being relatively “standard.”
When trying to setup a clustered DMZ server as a computer only JSS I get the
Could not write to /Library/JSS/Tomcat/webapps/ROOT/WEB-INF/web.xml
Recently we setup a 10.7 Mac Server in our DMZ & clustered this with our main JSS to enable external clients connectivity to our JSS & for them to be able to use Self Service & ASUS when off the network.
However we’ve had some issues getting the distribution point to work over HTTPS, however HTTP & AFP worked fine.
UPDATE: Updated to now work with Lion
This Extension Attribute checks to see if Mac has either an Airport or Wireless & returns “Yes” is the Mac has one & “No” if it doesn’t. Continue reading