We are using 9.0.835 client on OS X Yosemite and it seems to work just fine even though it is not officially supported. We have over 400 Yosemite clients in our environment right now.
Anything greater than version 9 should work on Yosemite just fine. It can take IBM quite a long time to list a new version of OS X as officially supported due to being conservative about it, but we always test machines running the beta builds of OS X with not the newest client and we don’t see issues often. We typically have about 50 machines running the latest OS X within weeks of the release date running whatever version of BigFix we happen to be using at the time.
We do have one issue with Yosemite that we are aware of, but it affects a very small minority of Yosemite endpoints, and we are not entirely certain if it is a BES Client issue or something else. See that post here: OS X Yosemite (10.10) 13FileItemError
This isn’t an official announcement and I don’t know if any official announcement has been made but I would suggest using a 9.2.1 version of the client at a minimum for Yosemite.
There are some minor issues reported actually through the forum which we are looking at as jgstew mentions. The main workings of the Mac agent from the OS side haven’t changed much since 8.2.1322 but of course if you have a newer deployment you need to use a newer agent for the functionality (and bug fixes)
Apple also changed their signing requirements for binaries but not installers with the introduction of 10.10 and with recent patches to 10.9 and 10.8 so we are also looking at how to address those. The client is not affected but the accessory programs are affected by your Gatekeeper settings. This is part of the question I posted to the forum recently about the accessory DMG.
A few Macs with Yosemite and 9.2 show in triplicate, or more, in my console. Pushes to the wrong one just sit there… Pushes to the correct machine (the one with the most recent report time) work fine… Not just VMs, also real machines… But not all. Weird.
Speaking of IEM support on OS X, I just discovered that the “build number” inspector is broken in the IEM 9.2.1.48 client. It returns the Z of the X.Y.Z version, i.e. “2” of “10.10.2”.
In 8.2.1409 it returns the build number, e.g. 13F1066 from 10.9.5. This is the desired behavior.