Posted on 09-14-2015 10:00 AM
I now have a test JDS instance and a test JSS, everything is on CentOS 7.
Although the JDS works for imaging of MacBooks via a netboot server and an afp share on the JDS to pull down the packages for imaging, I don't think the JDS is communicating to the JSS at all. For instance some of the following fields are blank in the JSS web interface (Computer Management -> JDS Instances):
Root: Yes
Parent JDS Instance: None
Hostname:
Reported IP Address:
jamfds binary Version:
Operating System:
Operating System Version:
Total Memory:
Also, policies which need packages pulled down to the MacBook test machine are not being pulled down over https:
Executing Policy TestPolicy...
Downloading TestManageEngine.pkg...
Downloading https://sscvlqmljds001/CasperShare/TestManageEngine.pkg...
The network connection was interrupted while downloading the package from https://sscvlqmljds001/CasperShare/TestManageEngine.pkg. Attempting to reconnect...
Downloading TestManageEngine.pkg...
Downloading https://sscvlqmljds001/CasperShare/TestManageEngine.pkg...
Error: TestManageEngine.pkg is not available on the HTTP server.
Does anyone know how I can troubleshoot this and get the JDS communicating to the JSS? I am not sure how to set-up the http server, I thought this would have been done by running the JDS-Linux-Installer-9*.run package???
chmod +x JDS-Linux-Installer-.run
./JDS-Linux-Installer-9.run
When I did the above I was able to join it my JSS ("Installed and enrolled successfully") by putting in the URL and JSS username and password. But it's as if no http shares were set-up....
Thank you.
Posted on 09-15-2015 06:52 AM
I think I understand why it might not be communicating (see error below) but what is the way to fix an error like this if they see this? I think this is because I have migrated from our old JSS to a new JSS with a new hostname. Does anyone know how to generate a SSL cert self-signed but with the new hostname of the JSS?
[root@sscvlqmljds001 ~]# /usr/local/sbin/jamfds policy
error: (51) - SSL: certificate subject name 'skymac001.corp.xxxxxxxxxx.local' does not match target host name 'incvlnl1jss001.corp.xxxxxxxxx.local'
Posted on 09-17-2015 02:19 AM
I got this working by updating the JSS SSL Cert to match the new hostname by doing the following:
System Settings -> Apache Tomcat Settings -> Edit -> Change the SSL certificate for HTTPS
And now "/usr/local/sbin/jamfds policy" does not error.