PolicyPak Cloud v26.9.4752 — Release Notes

:double_exclamation_mark: Warning: PolicyPak Cloud Client v26.9.4752 has been tentatively withdrawn from public use. Refer to this post for details. Until further notice, consider v26.7.4696 as the latest release.

This release adds a new editor to support the Secure Download Manager component, an improved search engine enabling metadata lookup across all your policies, as well as a batch of management-quality-of-life improvements for collections, duplicates, and computer group exports.

Want the full details? Click the link below!

What’s Changed in PolicyPak Cloud 26.9.4752

Secure Download Manager

PolicyPak Cloud adds a new editor to support a global policy type, Secure Download Manager, that blocks execution of files downloaded from the internet. As with other policy types, administrators can define exclusions for specific sites and file extensions. Supported browsers: Chrome, Edge, Opera, and Firefox.

New Search

Search across policies just got significantly more powerful. With the new improved engine, you get to have a look beyond mere policy names and into all associated metadata inside reports — comments, ADMX policy content, executable paths in Least Privilege Manager rules, and more. Results can be scoped with configurable options (word in the policy name, word anywhere in the raw XML, or restricted to a specific policy type), and the same improved search capabilities are now also, for the first time, available in the XML Data Files tab within Cloud Portal.

Safer Computer Duplicate Removal

The duplicate-removal workflow has been redesigned: you can now select individual duplicate rows to be removed instead of performing a batch removal of all duplicates—that option is now disabled. To further reinforce our dedication to as stress-free user experience as possible, a Yes/No prompt has been introduced to either confirm or deny your duplicate removal request. Moreover, three new pre-set filters will help you quickly mark duplicates for deletion: all duplicates allowed by the current filter, all duplicates except for the latest computer synced or all duplicates except the latest computer registered.

Bug Fixes and Miscellaneous Updates

New Features & Improvements

  • Cloud Client installer upgraded for .Net 10 support and minor visual modifications.
  • Added an Export as CSV button for computer groups, letting you export the computer list for one company group or all groups.
  • Added an option to send email notifications for when a computer is unexpectedly deleted.
  • Added Copy/Paste key support as an alternative to Drag-and-Drop in the Least Privilege Manager in-cloud editor.

Bug Fixes

  • Fixed an issue with scheduled Cloud Portal-created tasks not working as expected on an endpoint
  • Fixed a problem with the event time logged in Cloud Portal not matching exactly the time shown in an endpoint’s own event log.
  • Azure AD policies now no longer appear in the Computers Group list after being deleted.
  • Cloud Client Installers no longer return an internal server error for users without any customer certificates created.
  • “CompanyCertificateRevoke” event is now correctly logged upon a customer certificate getting revoked.

Need help with this update?

There are many different ways to get help with our products!

Situation Action
If you feel the product is broken and not working as intended… Contact Support
If you have a question you’d like to ask other experts… Create a discussion in the community: PolicyPak > Discussions & Questions
If you have a feature request… Let our product team know directly: PolicyPak > Ideas
If you have something cool to show… Show everyone what you built: PolicyPak > Show & Tell

What are your thoughts?

We are always happy to hear from our users on what you like, and what you hope to see in the future. Please, share your thoughts below!

1 Like

Thanks for the new release, the search functionality in particular sounds great.
Can you elaborate on the change to .NET?
Why are you making machine-wide changes to make all other apps use your bundled copy of .NET 10?I assume this change would mean we become reliant on PolicyPak version updates to receive .NET security updates that would otherwise come directly from Microsoft?
I appreciate .NET 8/9 are almost end of life but it’s not realistic to ensure every other application has already been updated to .NET 10, and it shouldn’t be something one app enforces for other apps?

Hi there, Luke! Thank you very much for sharing an honest opinion.

The .NET environmental variable being set to a PolicyPak directory is an approach that the team has been encouraged to reconsider. As a result, we have decided to publish a fix that will ensure the default path set into the .NET environmental variable during installation be the one assigned by Microsoft, that is C:\Program Files\dotnet\. A user will also be able to name a different path, if they so desire, but this will no longer be in any way unilaterally determined by PolicyPak. That should put the issue to rest.

We expect the fix to become available within the next couple of weeks, we’ll definitely communicate it when it happens. Please bear in mind that it is always good practice to run the installation with admin privileges.

Thank you once again, Luke, for showcasing just how critical it is for every great product to maintain an open channel with the user base leveraging platforms like Community. :slightly_smiling_face: Make sure to keep dropping by!

I really appreciate the prompt consideration you’ve given this; being able to retain the default .NET location is an enormous improvement. Thank you.

2 Likes