We’re really excited to be releasing the next version of Cloudpaging Studio. The primary focus for this release is simplifying and streamlining the packaging process based on feedback we’ve received from existing customers. For new and existing customers alike, this release provides a lot of upgrades to be excited about, from packaging workflow processes to enhanced automation capabilities.
This blog will provide insights into the latest release and what it means for your day-to-day.
Windows 11 and Windows Server 2022 Support
Last year we released support for Windows 11 and Windows Server 2022 with the launch of Cloudpaging Player 9.3 Player. This ensured you could deploy all your virtualized applications to the latest Windows environments.
With the release of Cloudpaging Studio 9.3, we’ve further expanded support for the latest Microsoft technologies. Studio 9.3 ensures modern applications designed for Windows 11 and Windows Server 2022 can be efficiently packaged and provisioned using Cloudpaging.
Enhanced Security Access Controls for Windows Services
Cloudpaging Studio 9.3 allows users to specify which Windows services to allow/deny access to virtualized applications, effectively limiting Windows functionality allowed into your Cloudpaging containers. These new security overrides provide fine-grained access controls that can be applied to virtualized applications, allowing specific Windows services to have disposition access control. In other words, you can now perform security overrides by service name, in addition to process names.
Refined Capture Filters
As many of you know, most applications can be packaged simply by clicking through the capture and cloudification Wizard, without making manual changes thanks to the Cloudpaging Studio filter. We’ve refined filters for this release to address niche use cases, enabling higher packaging success rates into Cloudpaging containers without modifications.
Additionally, we have established more fine-grained controls at the file-path level.
Automatic Print Driver Detection
We’ve significantly expanded driver detection capabilities to make packaging even simpler. By default, Cloudpaging Studio will automatically detect and enable printer drivers when packaging applications without the need for manual configurations.
Expanded Search Functions
You can now search for items within projects by disposition layer. You can search for items that belong to specific layers (e.g., layer 1, layer 2, etc.) or any combination of layers (e.g., layer 1 and 2, layer 2 and 3, etc.). Moreover, we’ve expanded the search functionality to not only find assets within the container, but to cut and paste the results for changes made.
Support PowerShell Configurable Application Events (CAEs)
Cloudpaging Studio 9.3 provides native support for PowerShell configurable application events (CAEs), making it far more convenient to automate tasks and implement DevOps capabilities within Cloudpaging Studio. While we have supported PowerShell for a long time, it is now more straightforward to use in this version to accommodate its increase in popularity as a DevOps tool.
Consolidated Packaging Outputs
Based on user consumption preferences, we have consolidated Pre-cache and Multi-Source outputs into one Cloudification option, streamlining the Cloudpaging Studio packaging experience. You simply have to designate the source, enabling you to use your Cloudpaging packages for either our Pre-Cache or Multi-Source functionality (or both).
For legacy appsets that utilize the other less common options associated with Multi-Source, you can still edit these options in Cloudpaging Studio by editing the container.
Removed the Requirement to Save Before Capture
Previously, it was a requirement to save projects prior to capturing. For larger projects, this meant a few minutes of waiting for saves to effectively execute. We have removed the requirement to save before capturing to mitigate dead time. As you go through the capture process, the project will be saved in the background.
Container Export Logs and Analysis Tools
To simplify troubleshooting and analytics, Cloudpaging Studio now enables you to scan packaged applications to report on potential issues.
As you may know, AIB Analyzer is a tool on the Player side. On the Studio side, we have an AIB Export function. In 9.3, we have expanded upon the export options available to the Studio CLI, which were previously available only on the Studio UI.
This enhances the support for scripting and automation with Studio. For example, the user can now export the AIB to a text file and then scan the text file for information that can be acted on.
Container Metadata XML for Tracking and Automation
Improvements to log formatting makes it easier to analyze packaged applications and automate related tasks. The latest XML enhancements enable you to generate the following information on any given appset:
- Application IDs
- When it was packaged
- How long it is valid for
Legacy Feature Deprecation
We have removed deprecated features from Cloudpaging Studio. Instead, these legacy features can be controlled on either Cloudpager Server or directly on desktops. For example, you can leverage third-party UEM tools to allow settings to be roamed without adding settings to the container. Now that these features no longer reside in Cloudpaging Studio, you can seamlessly reuse application containers, drastically reducing redundant work.
High Contrast Accessibility
Cloudpager Studio 9.3 accessibility tooling allows High Contract modes in Windows, enabling more IT professionals to use the solution.
For additional information on the improvements included as part of the release, see the release notes included with the installer. Customers can download the current release here download.numecent.com.
Interested in learning more about our Cloudpaging technology? We’d love to discuss how our product portfolio can help simplify the mobilization and management of your Windows applications across modern desktop and multi-cloud environments.