Hi guys,

I am doing some research into deploying and managing Macs on our network and I am pleased to see the latest update for the K1000 has support for deploying Profiles for OS X to El Capitan clients.

What's not clear to me is whether or not its necessary to bind Mac clients to an OS X Server's OD. From what I can ascertain OS X Server is only needed to create custom payloads that are then deployed via the K1000 rather than OS X Server. The K1000 can do all of the patching and management of OS X clients rather than OS X Server if I am understanding things correctly?

Can anyone please confirm or provide some advice?

Thanks in advance.


2 Comments   [ - ] Hide Comments


  • We run a very small group of Mac clients on our network and I have tried the Golden Triangle method but did not have much success, Lots of moving parts. I have since moved to just setting up the Mac devices as one offs and use KACE to push apps/files to them. I have not used profiles.
  • Thanks for your reply smalls. How small is "a very small group" exactly?
    And specific issues did you have I have been using the Golden Triangle successfully for a small test network of 2 clients and an OS X server reasonably successfully. But I have read reports that it doesn't scale very well hence why i'm looking to Kace to do it.

    I'm anticipating growing to approximately 10-20 Mac clients in the short term with more to come in the medium term. I want to have a robust solution in place before we deploy any more Mac clients than we already have.

Please log in to comment

Answer this question or Comment on this question for clarity


You do not need to bind to a Mac OS Server in order to deploy profiles. While you can use the server app to create payloads I don't find that method intuitive. Instead I tend to use Tim Sutton's MCXtoProfile script found here:

There is a bug with the current profiles support on the K1000 that limits the size of mobileconfig files that can be uploaded. Hopefully that will be resolved soon. One gotcha with using MCXtoProfile is that it assigns a profile name that may not be completely descriptive. For instance if you create a profile based on the com.apple.dock.plist it sets the PayloadDisplayName key to MCXtoProfile: com.apple.dock. I recommend changing that value manually because once you upload the mobileconfig file to the K1000 you can't modify it and if you manage the same preference differently depending on location that will get confusing.

We use our K1000 for application and patch deployment for our MacOS environment of close to 1,000 computers. We don't tend to push out the large MacOS updates via KACE due to their size but other updates work fairly well. It isn't perfect but the flexibility of managed installs plus scripting can fill in many of the gaps.
Answered 01/06/2016 by: chucksteel
Red Belt

Please log in to comment