Hey guys!
I would like to thank you guys for all the hard work I know you are doing to make this product great! I have a client that will be upgrading their old ZCM infrastructure from 11.2.4 to ZENworks 2017 at some point in the future. Please do not ignore this input and any work to get the following features available would be amazing.
I spun up a Server 2016 VM and installed ZENworks 2017. Nice job so far! Chrome support, Better Dynamic Workstation Group Options, Preboot options for PE and MS Deployment Toolkit. etc.
I am struggling to figure out though, why are as administrators we are so limited with the Bundle/ Policy / Dynamic Workstation Filters.
If the ZCM Agent collects inventory and writes that information to the database, why can’t we create Dynamic Workstation Groups based on that detailed information? If I need to make a specific dynamic workstation group for not just Windows 10 workstations, but Windows 10 Workstations that are a particular build is one such use case.
OSVersion is 10.0.10586.% or OSVersion is 10.0.14393.%
Feature Request # 1
Ability to apply policies, patches, bundle filters, or bundle step filters based on detailed information collected from inventory. Software, Hardware, MSI Product Codes, etc.
MSI Product Installed: {4334343-343434-3333-333434663} = YES/TRUE or NO/FALSE
Feature Request # 2: Inventory Variable Access
When running the “Run Script” Action under specify script, we should be able to access inventory variables and inject them into the script at runtime.
Example: ${NIC0_IPADDRESS} or ${RAM_DIMM1_SIZE}, etc…
Feature Request 3: More data collection from Inventory.
The ability to specify WMI classes, Registry Keys, etc so that more data can be collected from devices.
Functions like these need to be exposed to Administrators so we can make our environments more dynamic and other products out there can already do this. There are specific reasons however, why I think ZCM is better! But these things need to be in ZENworks 2017 to warrant an upgrade and to compete in the market.
Doing it this way will keep CPU cycles down but increase the product functionality a great deal.
Right now, all we can do to achieve stuff like this is write a script, export that data to a registry value and have ZCM read that value. That is tremendously pain staking.
by: Alphaeus M. | over a year ago | ZENworks Control Center
Comments
There is also not feature parity on filters on mac and Linux.
On a mac, you can not create a filter like if OS > 10.11.
I have to spell out each OS separately.