Anyone else having trouble with figuring out the best way to apply settings to endpoints with Unicon? Have to say the whole 'global' device management, OU device management, and the config rules/labels, and lack of proper inheritance seems like a pretty complex way to apply settings. Coming from Dell WMS and Igel, where inheritance just works, seems like a better strategy to me. Thoughts?

It can be messy creating OUs based on device configurations if you require a lot of different device configurations. I did put in a feature request to be allowed to disinherit certain sections within the device configuration, that way it is easier to do things like keeping the image the same across OUs but still being able to change other configurations. Hopefully other people request that as well so it gets some traction.

i've been letting our rep know as well....probably my biggest gripe at this point.

@Steve Noel What is your challenge? As a product specialist, I can hopefully clarify it.

in a nut shell, applying policies/settings/conifgurations. Organizing the OU structure, similar to how domain joined devices are organized. Id like to apply a top level policy/settings that contains global settings....and i get further down in the sub OU structure, i'd like to either override settings from an above OU, or apply a single setting for that specific subOU...

@Steve Noel We’ve got a basic setup with two main ways to go about it: Stick with the OU structure, break inheritance and tweak the changes. Try the new approach using Labels – create your configuration there and apply it across multiple levels with Label Rules. In fact, Labels can override OU settings, so you can use both together. If you’re new to this, I’d recommend Labels – they give you loads of flexibility and control.

@Mathias Törnbom - Labels/rules are working for us to break inheritance. Is there a way to check settings applied from which configuration? Like gpresult/rsop...

@Srinivasan Shanmugam, since labels are linked to a device, using inheritance and overriding them is a real superpower! In Scout Board 2607 and 2609 you can see exactly which rule applied to your device. There’s an RFE in for a modelling or RSOP-style tool – let’s hope the product managers push this into the queue.