C.Imaging and JDS

[jwojda]

I have jamf working on this too, but wondering if y'all have run across this.

We just setup our JDS environment on 9.21 / 10.9 Servers and more or less everything has replicated. However, When I go into C.Imaging and override defaults to point to the JDS, C.Imaging errors out on mounting the JDS, adn the only error I can find is "there was a problem connecting to the server jds.server.com. Check the sever name or IP and try again.

I can ping it, I can do a cmd+k and map it (or at least get to the point where it prompts for credentials).

[denmoff]

The problem i had with Casper Admin connecting to the JDS was related to ping. I had enabled ping on the JDS, but my host was blocking ICMP. So, the ping wasn't coming back to C.Admin.

[stevewood]

I had a very similar problem, only the infrastructure is Ubuntu. The problem in my case was with the SSL cert for the JDS. The system that was running Casper Imaging didn't have that cert. So, open up Safari, navigate to the JDS URL (https://jds.yourdomain.com) and do Show Certificate and trust the cert. That should fix it.

[Josh_S]

The JDS servers use a certificate issued by the built-in CA. @stevewood is correct if your JSS is also using the built-in CA. You can also go to https://jss.yourcompany.com:8443/pki.html and click on "Download CA Certificate". Import/trust the certificate you download. You'll need to do this on any 10.9 system that connects directly to the JDS. Casper Admin/Imaging.

On a 10.8 system it would prompt you to connect to the share with an untrusted certificate. With 10.9 it appears that connections to shares with untrusted certificates that are not initiated directly by you, initiated in this case by Casper Admin/Imaging, fail outright rather than prompting to connect anyway.