While performing a change CA (Certificate Authority) or a Remint CA operation, you can now provide the certificate validity for MDM and non-MDM servers, separately. This feature is helpful in ensuring a 2 year validity for MDM servers, which is a requirement for iOS devices. For more information, see Configuring the Certificate Authority in the ZENworks SSL Management Reference.
From ZENworks 2020 Update 1 onwards, by default, the new Remote Management viewer will be used while remote controlling devices. You also have the option to use the legacy Remote Management Viewer, if required. The new viewer includes a lot of performance improvements and bug fixes. For more information, see ZENworks Remote Management Reference.
Remote Control sessions are now even more secure using TLS 1.3. This enhanced security is available only when both the Remote Viewer and Managed Device are running 2020 Update 1 components on Windows devices.
Mobile Management includes the following new features and enhancements:
Support for iPadOS platform: ZENworks now supports the iPadOS platform that are iPad devices with iOS version 13 or later installed. All policies and bundles that are applicable for iOS devices are now extended to include iPadOS devices as well. This feature is by default in a disabled state and needs to be enabled after migrating to the ZENworks 2020 Update 1 release version. For more information, see Support for the iPadOS platform in the ZENworks Mobile Management Reference.
Also, new settings have been introduced for iOS and iPadOS devices in the Mobile Device Control Policy and the Apple Device Enrollment Program (general and skip item settings). For more information, see Securing a Device in the ZENworks Mobile Management Reference.
Distribute Provisioning Profile for iOS/iPadOS: You can now renew a provisioning profile that is required to run enterprise and developer apps. As a provisioning profile expires within a year, you can use the existing iOS/iPadOS Profile bundle to renew the profile without the user having to re-install the associated app manually on the device. For more information, see Distributing an iOS Profile in the ZENworks Mobile Management Reference.
Deploy Web App shortcuts: Using the existing bundles feature, ZENworks now lets you deploy a web app shortcut to iOS, iPadOS, and Android devices. These shortcuts will allow users to have quick access to web pages that they use frequently. For more information, see Distributing Web App Shortcuts in the ZENworks Mobile Management Reference
Auto-update bundles when updates are available for VPP apps: In previous ZENworks releases, when there was an update for a VPP app, it was not automatically deployed on the assigned devices and the end user had to manually update the app. From this release onwards, when an update for a VPP app is available, you can instruct ZENworks to automatically create a Sandbox version or a Published version of the associated bundle and deploy it on devices. This can be set at the Subscription level or for specific apps in the Apps Catalog page. For more information, see Distributing VPP Apps in the ZENworks Mobile Management Reference
Change in bundle status in the Device Relationship page: In the Device Relationship page, the bundle status is now displayed at a granular level based on the action sets that are Distribution, Install and Launch. This will enable you to identify the exact stage at which the bundle failed to apply on the device.
Display block status for user assigned bundles: The deployment dashlets now reflects the correct status of a user assigned bundle when it is blocked. For more information, see Accessing the Bundle Dashboard in the . ZENworks Software Distribution Reference
Addition of new value type and string type in Registry Key Value in System Requirements: A new value type “version” has been added in the Registry Key Value filter condition as a part of the Bundle and Policy system requirements. The ‘contains’ operator has also been added in the same filter condition. For more information, see Managing System Requirements in the ZENworks Software Distribution Reference
Display exact reason of assignment failure for a bundle: If an assignment is not effective on the device, then the bundle assignment status dashlet will display the exact reason for the failure. To view these details, you need to click the hyperlink displayed in the Not Effective Reason column in the dashlet. For more information, see Accessing the Bundle Dashboard in the ZENworks Software Distribution Reference.
Display device assignments for a disabled bundle: The Relationships tab of a bundle, now displays all the effective and non-effective device assignments of a bundle. This is particularly useful if you want to identify all the device assignments made for a disabled bundle. For more information, see Bundle Tasks in the ZENworks Software Distribution Reference.
ZENworks has always supported execution of PowerShell scripts on Windows devices. While creating a bundle, and choosing a script to run, now it is possible to select PowerShell from the drop-down and ZENworks will automatically populate the execution parameters, thus making it easier to execute PowerShell scripts on Windows devices. For more information, see Action - Run Script in the ZENworks Software Distribution Reference
Display pending records within Data Sync Status panel in the Diagnostics page: The Data Sync Status section in the Diagnostics page that displays the status of the data sync process between the RDBMS and Vertica, also displays the number of pending records that are yet to be migrated from each Kafka connector to Vertica. For more information, see Data Sync Status in the Vertica Reference Guide.
Re-create Kafka connectors: When you migrate from one RDBMS to another, and if you have Vertica installed in your zone, then you need to re-create the Kafka connectors to enable syncing of data from the new RDBMS to Vertica. A new zman command has been introduced to re-create Kafka connectors after database migration. For more information, see Maintaining the Kafka Cluster in the Vertica Reference Guide
Removal of the maximum cluster size parameter from the ZooKeeper update command: The requirement to update the maximum cluster size, if more than 3 ZooKeeper nodes are to be installed, is now removed.
By default, content is now transfered from Primary Servers, in an encrypted form, to other Primary Servers, Satellite Servers and managed devices through a secure connection (HTTPS port 443). However, content between Satellite Servers and Managed Devices will continue to be transfered over port 80.
Since the Relationships page for Devices was earlier taking a lot of time to load as it included information related to device groups along with bundle and policy assignment details, this information has now been split into the following pages to improve readability and performance:
Memberships: Includes information about groups and dynamic groups.
Assignments: Includes information about Bundle and Policy assignments.