Skip to main content
Question

New MacMini unable to connect to JSS

  • May 12, 2015
  • 2 replies
  • 48 views
P
Forum|alt.badge.img+4

We have a number of different Macs from 'old' Mac Pro's (Early 2008), through a range of MacBooks to iMacs etc. all of which we can neboot and image, I also have a USB external boot drive configured with Casper imaging which also works with our Macs.

However, we have one MacMini (Mac mini (Late 2014), 3 GHz Intel Core i7, 16 GB 1600 MHz DDR3, Intel Iris 1536 MB), that will not netboot, will not boot from the external USB but will boot to either Maverick or Yosemite Installer on a USB drive.

Once installed with either Maverick or Yosemite, I can bind it to our network, configure proxy etc. so the idea was to Casper Remote to it and install the apps.

But for some reason, it cannot 'see' the jss. I can ping the server and run nslookup to confirm that the server name resolves correctly .

I can run two terminal windows up ping the server and run nslookup etc to the server, whilst running either 'JAMF enroll -prompt or JAMF recon and /usr/sbin/jamf checkJSSConnection in the other and it errors out with the message below.

'' Error enrolling computer: Unable to establish trust with the JSS - Connection failure: "There was a problem communicating with the secure web proxy server (HTTPS)."

Any ideas or suggestions? While I Google around for any insights.

Cheers
Phil

    2 replies

    G
    Forum|alt.badge.img+9
    • GaToRAiD
    • Contributor
    • May 12, 2015

    Phil,

    Try this command

    sudo jamf createconf -url http://yourserver -insecure

    I'm pretty sure its -insecure, maybe not. May want to ask your tam what the flag is for insecure setting.

    P
    Forum|alt.badge.img+4
    • Phil11
    • Author
    • Contributor
    • May 12, 2015

    OK, I have no idea why this should work.

    I set the proxy to auto discover, which should not really have worked.

    But we have been experiencing some issues with our proxy, we no longer have a single Mac proxy config under Maverick and Yosemite.

    Under Lion and Mountain Lion we simply pointed at the PAC file, or entered absolute values and port numbers.

    Under Maverick and Yosemite the PAC file failed to work so we had to push out a script to remove the PAC file and use absolute values.

    As said under Yosemite on this MacMini, I have deleted all proxy settings and simply selected auto and I can now run Recon and Remote on it.

    Thanks for your time, maybe this will help someone else.

    Cheers
    Phil

    Terms & ConditionsCookie settingsAccessibility statement