Skip to main content

Hi all,



I just finished moving from a JSS 8.72 on an old Xserve to a new 9.25 Ubuntu JSS install.



I followed the directions here:
https://jamfnation.jamfsoftware.com/article.html?id=122



Everything went very smoothly up until I started testing.



Any existing devices, enrolled in the old JSS, are not getting any of the push commands.



Newly enrolled devices work fine.



I put a CNAME record in our internal DNS for the old JSS server pointing to the new JSS A record. Same for our external DNS. Deleted the old JSS A record. I did regenerate a new, self-signed, SSL cert too. The Self-Service apps also works fine for devices; Self-Service is pointing to the new server.



I feel I'm missing one piece??



Thanks,
Patrick

Thanks to help from JAMF Support I got it working.



We were moving from one server to a new one, hoping to still use the old one as a Netboot/Deploy Studio server.



Doing my research beforehand I was told we could just put a CNAME in DNS resolving the 'old' JSS servername to the new JSS servername. We did that, however, our 1650+ iPads were not getting any push commands to work.



What I had to do was change the JSS URL (in Global Management>JSS URL) on the new server to be the same name as the 'old' JSS URL. Then, I had to reissue a new self-signed cert in JSS (System Settings>Apache Tomcat Settings) so it had the 'old' JSS name as the issuer.



So what I have is a new, physical server with a new hostname and IP address, running what is essentially an upgraded JSS under the 'old' servername URL. Still resolving the 'old' JSS URL to the new IP/hostname in DNS.



Unless I wanted to re-enroll all those iPads so they got the new Cert with the new servername, I had to keep the 'old' JSS URL and Cert alive.



It actually turned out fine. On the old server I just changed the hostname, DNS A record, uninstalled JSS, reinstalled Deploy Studio and rebooted.

Terms & ConditionsCookie settings