We had an issue when the search path for DNS did not include the domain. Once we added the domain to the search path Yosemite bound like previous OS's bound.

Update: It looks like the problem is that my machines' clock is not synchronized with my DC. I am running a script to accomplish this. But, it no longer seems to be working.

I was using this script in the past and it was working great:

/usr/sbin/systemsetup -setnetworktimeserve [Server IP Address]

After upgrading to 9.62, this stopped working.

I have switched to the following script I found on JAMFnation https://jamfnation.jamfsoftware.com/viewProductFile.html?fid=728
(hoping that would work better). But, the results were the same. My machines are still not synchronizing their clocks to my local DC and therefore I am unable to Bind them to AD.

Thanks!

We normally use the domain controller to set the time if a dedicated NTP server isn't available. You can even just use the domain itself:

http://www.amsys.co.uk/2015/blog/setting-network-time-server-command-line/#.VKrERCaQGJI

We've used Casper imaging to bind Yosemite Macs without issues (apart from the "crashing on startup when connected to an AD domain" problem lots are facing). The actual bind works fine.

Thanks @davidacland

Using the link you posted as a guide, I was able to just put my domain controller's FQDN and it worked.

Hi Markos, Hey I never got the email blast from the training, did you? Looking forward to talking with you. tom.harris@bhnetwork.com