You are not logged in.

Announcement

[2017.09.08] DeployStudio build v1.7.8 (checksum, release note).
[2016.08.26] DeployStudio build v1.6.19 (release note).
[2013.02.23] DeployStudio last universal build v1.5.17 (release note).

#1 2013-12-19 12:06:57

jelockwood
Member
Registered: 2009-11-11

BUG - Setting Date/Time/NTP etc.

DeployStudio has a workflow option called Time which allows setting the computers NTP (Network Time Protocol) server and the time zone. Like the Date & Time option in System Preferences it has a pre-defined list of NTP server which contains the same three Apple server entries for America, Europe and Asia and like the Date & Time preference you can enter a custom entry as well.

The NTP server choice would then get written to the /etc/ntp.conf file which is used by the ntpd software on the Mac.

The problem is that while the ntpd software and the /etc/ntp.conf file and in fact Apple's Date & Time system preference allow entering multiple servers this does not work via the DeployStudio workflow item. In Apple's Date & Time you could enter two servers by typing any of the following formats

ntp1.example.com, ntp2.example.com     <--- (separated by a comma followed by a space)
ntp1.example.com,ntp2.example.com      <--- (separated by a comma only)
ntp1.example.com ntp2.example.com      <--- (separated by a space only)

All three versions result in /etc/ntp.conf containing the same (correct) results as follows

server ntp1.example.com
server ntp2.example.com

If in DeployStudio you use either of the following formats the item fails completely and the Mac ends up with no file at /etc/ntp.conf and therefore ends up using time.apple.com (i.e. America) and also ends up being shoved in to a Los Angeles location/timezone regardless of what you specified.

ntp1.example.com, ntp2.example.com     <--- (separated by a comma followed by a space)
ntp1.example.com ntp2.example.com      <--- (separated by a space only)

If in DeployStudio you use the following format

ntp1.example.com,ntp2.example.com      <--- (separated by a comma only)

Then the item runs but the content of /etc/ntp.conf ends up looking like

server ntp1.example.com,ntp2.example.com

In other words, both host names have been combined in to one with a comma in the middle. This is of course an illegal host name and as a result the Mac fails to sync its time.

It could be argued that DeployStudio does not support multiple values and therefore this is not a bug. If that is the case then I would say this needs to be considered as an enhancement request to add support for multiple values as multiple values is a official part of the ntpd software and is supported by Apple.

Offline

#2 2013-12-23 17:50:34

admin
Administrator
Registered: 2007-03-29
Website

Re: BUG - Setting Date/Time/NTP etc.

Thanks for the feedback, it's an enhancement request.

Offline

#3 2013-12-24 09:02:17

homerdjw
Member
From: London, England
Registered: 2013-01-24
Website

Re: BUG - Setting Date/Time/NTP etc.

Hi jelockwood,

A work around is, if you have a 'currently' configured DNS structure (in fairness I'm unsure of the specific requirements) you can point the NTP to the domain and it will contact the nearest working NTP server. For example, use 'example.com' instead of "ntp1.example.com, npt2.example.com". I've used it a few times on other clients AD networks and it works, just test first!

Hope that helps,

Darren

Happy Holidays

Offline

Board footer

Powered by FluxBB