Today we’re very excited to announce the release of AOVPN DPC 4.0 with support for Windows 11!
AOVPN Dynamic Profile Configurator is now functional with both 21H2 and 22H2 versions of Windows 11.
Windows 11 has a number of known API bugs which prevented DPC from running properly. After extensive work on our side, we’re very happy to say DPC can now run on Windows 11!
Our development team has spent the last year rewriting the profile management engine in DPC to provide this functionality to our customers. So, as you can imagine, they’re very happy to have this work completed!
(Hey – if you’ve never heard of DPC, you can check out our previous posts on version 3.0 and our initial release to learn more…)
A lot has changed with DPC over the last few years – we’ve added Intune management, and a whole host of new features in the previous version. We’ve spent most of our energy on overcoming the bugs in Windows 11’s API, so this release just contains a few bug fixes.
Alongside Windows 11 support there are three bug fixes included in this release:
- Updated Event Logging to log more events by default
- Fixed issue where saving Profile Debug files happened before new profiles were added
- Improved Profile renaming behaviour
We continue to work hand in hand with Microsoft to improve the AOVPN experience for all users on Windows 11. As patches for Windows become available DPC will be updated to take advantage of this functionality where appropriate.
If you’ve made it this far, and want to know more, we’re running a webinar with AOVPN guru Richard Hicks to run through the changes and answer your AOVPN questions. Click here to find out more!
Please note that the first name provided as a device profile name is tattooed into the system and must be used for all future device profile imports. DPC works round this by tracking this initial profile name and always using it before renaming the profile after it has been imported.