All modern browsers are supported. However, if using Internet Explorer, please keep in mind that the ActiveX plug-in is not supported here. For dependent features like patching, it is necessary to either use the old UI with the ActiveX plug-in, or to use the new SVM Patch Publisher tool (separate from the web-based admin console).
What are some new features of the new UI?
Apart from looking better, when you select a menu item it will open a new tab making it easy to jump between views.
What limitations are associated with the new UI?
Patching and Software Suggestions are not planned as capabilities of the new admin console and will be handled via the SVM Patch Publisher going forward.
Specifically, the following features are not supported by the new web console. This is due to a reliance on ActiveX which we are moving away from by enhancing the SVM Patch Publisher to take on such needs. Patching will be addressed first, other features will follow, some capabilities (like Quick Scan) may be deprecated.
Patching – the creation of templates, patches, and the publishing of patches
Software Suggestions – the ability to suggest new software for assessment
Quick scan – the ability to initiate the scan of an endpoint from the browser
SCCM import – the ability to perform an assessment based on SCCM inventory data
We will be continuing to support this version of the user interface, at least until the functionality of the new SVM Patch Publisher reaches a stage where it can handle the features currently dependent on this version of the User Interface and its ActiveX plug-in.
Why would I want to use the old UI?
If you wish to leverage the existing functionality which depends upon our ActiveX plug-in, like patching, you may want to stick with the older user interface. The capabilities of the SVM Patch Publisher as an alternative to the older user interface will evolve over the months to come. Please continue to check in and monitor this progress as we work to reach a point where the use of the older UI is no longer necessary but displaced by a superior user experience with the SVM Patch Publisher.
What if I am using Single Sign-On for SVM?
SSO can only be configured for one of the two user interfaces, the new UI or the old one. Therefore, if you leverage SVM for patching and the SVM Patch Publisher does not meet your needs in its current form, you may wish to continue with the older user interface a bit longer. We will be making regular updates to the SVM Patch Publisher in an effort to reduce (and eventually eliminate) the need for the older UI in the months ahead.
Should I change my agent and patch daemon connections?
No. The agent and Patch Daemon (and SVM Patch Publisher) will continue to communicate using the older URL, so no change is necessary. If and when we do require changes to the Patch Daemon, SVM Patch Publisher, or agent communication, we will be sure to provide plenty of notice. Please watch product release notes and subscribe to our Release Blog to help ensure you don’t miss any such announcements.
Where can I share my feedback regarding the new UI?
What Should I Expect from Future Versions of the Patch Daemon (SVM Patch Publisher)?
We intend to continually improve and enhance the SVM Patch Publisher to provide a superior user experience as compared to the ActiveX plug-in of our older web-based admin console. As a priority, we will initially focus on handling all patching use cases in the SVM Patch Publisher. Other ActiveX-dependent features like Software Suggestions will also be addressed in future updates to eventually remove any need for our older UI with ActiveX. When the SVM Patch Publisher has evolved to such a state, we will communicate an end-of-life plan for the older user interface.
Our next release of the SVM Patch Publisher is planned for early December and will introduce the ability to assign patches to groups when publishing to Workspace ONE.
The ability to create and edit patches (and also to view Smart Group results) is currently planned for release in Q1 2022.