I really like the forward movement on the WebUI front! Patch policies is something we could greatly benefit from, but the current structure is not feasible for us at this point due to overwhelming confusion with the way applicable patches show within Patch Policies as well as the timing schedule format.
- Targeting/Patch Relevance Confusion: When you target a device or group of devices then look at the patches tab it’s not showing what is actually applicable to those targeted devices. Per conversations with IBM and WebUI Engineers it seems this is expected. What occurs is you see the relevant content for the user you are logged into and since you can only create patch policies with a MO account that is all endpoints so it’s very confusing. The same applies for the timing of an action and how this is displayed from the highlevel view of patch policies once set. For example, you may set the targeted policy for a group a servers that are all in CST, but the next run time view shows it 10+ hours ahead of schedule due to it accounting for all timezones for all endpoints the MO sees.
All in all, it makes it appear that the targeting of endpoints is not meaningful since I would only want to see what is relevant or set for items in that target and not for everything outside of the target. One thing I will note is that the policy runs as scheduled for those endpoints, but is very confusing if you are not aware of all of the above.