Consistency in OS Selection, Alert Messaging, and Scheduling
Currently, there are several variations on common components in the K1000 admin interface that cause confusion & force workarounds. Some implementations of the OS selection force you to go in and revise all Custom Inventory Rules every time a OS update is released. Some instances of scheduling force the creation of multiple items (alerts & Wake on LAN events, for example) because they are needed multiple times in 1 week to match a patch schedule. These are the different implementations I have seen:
1) OS Selection-
Software Inventory: (also used for custom inventory rules) forces admins to select supported OS versions to the specific point update or Service Pack;
Scripting: Allows for individual OS selection like above, but allows selection of "All Windows" or "All OS X", or even "Leave blank to deploy to ALL operating systems";
Patching: Allows for the same options as Scripting, but with a different layout/selection list.
Patching: Alerts are restricted to 255 characters, and will not allow additional characters to be saved in the message box;
Managed Install: I believe Alert length is limited, but you can save an alert message with a seemingly unlimited length. It will just not be displayed in full;
Standalone: Alerts are limited (somewhere between 400-500, if I am correct) but again, the UI does not warn you if you put in too long of a message, it just clips it when displaying on the client/agent.
Wake on LAN: Allows only "Run Every...(day)" or "Run on the...(1st)" options;
Scripting: Allows "Run every ... minutes", "Run every ...(day)", Run on the ...(1st)", or "Run custom";
Patching: Allows "Run every ... hours", "Run every ...(day)", Run on the ...(1st)", or "Run custom";
Scheduled Reports: Allows only "Run every ... hours", "Run every ...(day)", or Run on the ...(1st)";
Alerts: Allows ONLY "Run every ...(day)";
Email Alerts: ONLY “Frequency (15 min/30 min/Hourly/Daily/Weekly/Monthly);
MI/FS: Uses only a ‘live’ deployment window (cannot specify a future date).
I would like to see these three aspects of the UI be more consistent across the various functions. It is frustrating to schedule multiple things to be in conjunction with each other, but then have to create multiple scheduled WOL events to match one patch deployment (for example) only because of the scheduling syntax.
For the three options, I would recommend the following models:
1) OS Selection: Model all instances after the Scripting implementation.
3) Scheduling: Model all instances after the Patching/Scripting implementations, but allow for switching between minutes/hours on the first option.
We are investigating some changes to the UI that will ensure a more consistent experience across the K1 for each of these areas.
Considering there are three different areas listed in this idea, we may look to implement these separately to focus on the most urgent needs. Based on the comments, the biggest issue here appears to be related to the OS selection for software inventory not allowing the ability to select all OS versions for Mac or Windows.
These are all valid ideas that would improve consistency so these have all been added to the backlog but they are not currently planned for our next release. Please continue to vote if you’d like to see this prioritized for a future release.
Any news on this? We want this feature.....!
Dean: Your response, dated September 12, **2012** states that "We are going to invest some time in making each of these aspects common across the K1 rather than variances of each other."
This is obviously not a priority if you guys haven't made any progress 3.5 years later. Let me tell you, though, it is a MAJOR inconvenience to your customers. Especially if they utilize Custom Inventory Rules. Every time Apple releases a new build of any OS, or Microsoft releases a different version or service pack or preview of Windows, I have to go in to each of my ~30 Custom Inventory Rules and re-select.
PLEASE make this OS Selection issue a higher priority.
Troy V. Barkmeier commented
K1000 admins who support Macs need this functionality, and we need it yesterday. The fact that this has been sitting at “Planned” with no updates (or discernible progress) for three and a half years is borderline criminal. Thus far, in six years of using the K1000 to deploy to Macs, we have encountered a grand total of ZERO (0) Mac apps that have a dependency on a particular build version of a X.x.x revision of OS X; this “feature” literally serves no purpose but to waste the time of K1000 Mac admins.
Here’s a thought exercise for those of you who are using the K1000 for Windows exclusively: what if, immediately after roughly every other Microsoft Patch Tuesday, you had to go back into the Software Detail for every single custom inventory rule and every single piece of software that you are advertising in the User Console and command-click to add new patch levels for Windows 7, Windows 8.x and Windows 10 under Supported Operating Systems. How many hundreds of Software Detail pages is that for you? How many hours would you lose to this process every 60 days?
Here's what my Supported Operating Systems box looks like right now:
Mac OS X 10.10 (x86_64) (Build 14A389)
Mac OS X 10.10.1 (x86_64) (Build 14B25)
Mac OS X 10.10.2 (x86_64) (Build 14C109)
Mac OS X 10.10.2 (x86_64) (Build 14C1510)
Mac OS X 10.10.2 (x86_64) (Build 14C1514)
Mac OS X 10.10.3 (x86_64) (Build 14D131)
Mac OS X 10.10.3 (x86_64) (Build 14D136)
Mac OS X 10.10.3 (x86_64) (Build 14D2134)
Mac OS X 10.10.4 (x86_64) (Build 14E46)
Mac OS X 10.10.4 (x86_64) (Build 14E7f)
Mac OS X 10.10.5 (x86_64) (Build 14F1021)
Mac OS X 10.10.5 (x86_64) (Build 14F1505)
Mac OS X 10.10.5 (x86_64) (Build 14F1509)
Mac OS X 10.10.5 (x86_64) (Build 14F1605)
Mac OS X 10.10.5 (x86_64) (Build 14F27)
Mac OS X 10.11.1 (x86_64) (Build 15B42)
Mac OS X 10.11.2 (x86_64) (Build 15C50)
Mac OS X 10.11.3 (x86_64) (Build 15D21)
Mac OS X 10.11.4 (x86_64) (Build 15E27e)
Mac OS X 10.6.8 (i386) (Build 10K540)
Mac OS X 10.6.8 (i386) (Build 10K549)
Mac OS X 10.6.8 (x86_64) (Build 10K524)
Mac OS X 10.6.8 (x86_64) (Build 10K540)
Mac OS X 10.6.8 (x86_64) (Build 10K549)
Mac OS X 10.7.4 (x86_64) (Build 11E53)
Mac OS X 10.7.5 (x86_64) (Build 11G56)
Mac OS X 10.7.5 (x86_64) (Build 11G63)
Mac OS X 10.7.5 (x86_64) (Build 11G63b)
Mac OS X 10.8.3 (x86_64) (Build 12D78)
Mac OS X 10.8.4 (x86_64) (Build 12E55)
Mac OS X 10.8.5 (x86_64) (Build 12F2501)
Mac OS X 10.8.5 (x86_64) (Build 12F2518)
Mac OS X 10.8.5 (x86_64) (Build 12F2542)
Mac OS X 10.8.5 (x86_64) (Build 12F2560)
Mac OS X 10.8.5 (x86_64) (Build 12F37)
Mac OS X 10.8.5 (x86_64) (Build 12F45)
Mac OS X 10.9 (x86_64) (Build 13A603)
Mac OS X 10.9.1 (x86_64) (Build 13B42)
Mac OS X 10.9.3 (x86_64) (Build 13D65)
Mac OS X 10.9.4 (x86_64) (Build 13E28)
Mac OS X 10.9.5 (x86) (Build 13F34)
Mac OS X 10.9.5 (x86_64) (Build 13F1066)
Mac OS X 10.9.5 (x86_64) (Build 13F1077)
Mac OS X 10.9.5 (x86_64) (Build 13F1096)
Mac OS X 10.9.5 (x86_64) (Build 13F1112)
Mac OS X 10.9.5 (x86_64) (Build 13F1134)
Mac OS X 10.9.5 (x86_64) (Build 13F1507)
Mac OS X 10.9.5 (x86_64) (Build 13F1603)
Mac OS X 10.9.5 (x86_64) (Build 13F34)
Microsoft Windows 10 Enterprise x64
Microsoft Windows 10 Pro x64
Microsoft Windows 7 Enterprise
Microsoft Windows 7 Enterprise SP1
Microsoft Windows 7 Enterprise x64 SP1
Microsoft Windows 7 Professional SP1
Microsoft Windows 7 Professional x64 SP1
Microsoft Windows 8.1 Enterprise
Microsoft Windows 8.1 Enterprise x64
Microsoft Windows 8.1 Pro x64
Microsoft Windows Server 2012 R2 Standard x64
Every new OS X build listed above represents one entire morning or afternoon of productive work lost to updating custom inventory rules. Based on my rough calculations, Dell/KACE owes my employer at least a month’s worth of my salary; feel free to deduct it from our currently due maintenance fees.
Please, please fix this ASAP.
Hi we have to put a lot of man hours in specifying the seperate OS versions when there is an update. We just want to use "All Windows" or "All Mac OSX" especially for software titles!
Brandon Padgett (Gerane) commented
It has been 3 years, any updates on this? I have a very, large number of Custom Inventory Objects among other things. It is a major time investment to go and correct these constantly.
Troy V. Barkmeier commented
The OS selection issue is becoming increasingly brutal for Mac OS X. Apple is releasing new build versions every few weeks, which means that I get to spend two hours revising all software packages and custom inventory rules. The last couple OS X updates aren't even different x.x.x versions. PLEASE bump the priority of this fix ASAP.
Matthew Krohn commented
I'd really like to see this for Software and custom inventory rules, I have many command line custom inventory fields I want to run on ALL Mac OSes.