Way back in Jan 2014 grabbed a test iPhone & after charging I was greeted with the above.
After various exclamations along the lines of “Holy fishsticks, Batman!” we did get the iPhone enabled & this did not involve a time machine or me waiting the 23,053,554 minutes for the device.
Below is how & some guess work as to what happened.
Most of the Macs I support are mobile & it seems that around the with the release of the “Unibody MacBook Pro” Apple stopped shipping Macs with a battery that would keep the Macs time even when the Macs main battery had died.
This means that if a Macs battery dies during travelling to another office, they’d not be able to login once there as the time would be more than 5 minutes out. Also, we heavily use SSL to secure things like our Wireless & many websites (JSS distribution points included).
So the solution was for me to setup my own NTP, that would both sync with my domains NTP & be externally accessible for those mobile users on the road.
I’ve posted How To: Set a Macs Time Server, How To: Sync Time With NTP via Script & How To: Check Your Active Directory Domains Time. They all came about when 1st looking at this issue, this last post in the series with use all those posts.
A recent post showed how to forcibly update a Macs time against a given NTP server, i’ve since been asked how to set the Macs NTP server.
This post will try & show you how.
Time’s a blessing & a curse, but an absolute. When it comes to Active Directory & Kerberos, it’s very important.
The below script will try & sync the Macs time to the NTP server specified at $4 or hardcoded as a value for the NTPServer variable in the script.