What’s New for FlexApp One?
Version 6.8.7.9083 - Released November 20, 2024
What's New
- Proxy Support for OAuth: FlexApp One now supports proxy settings within Internet Options when using the OAuth feature, improving flexibility in environments where proxies are required for OAuth authentication.
- New FlexApp Filter Drivers: Both FlexApp Core and FlexApp One have been updated with new filter drivers. The FlexApp engine will prompt users to install the new driver during activation if a newer version is detected. Notably, both the old and new drivers can coexist, allowing older and newer FlexApp One packages to run side by side without needing to remove the older driver version.
- Shortcut Information via CLI: The FlexApp One Engine now includes a command-line interface (CLI) flag that enables users to print out package shortcut information.
- Custom Log Path via CLI: The FlexApp One Engine now supports a CLI flag to specify a custom log file path, giving administrators more flexibility in directing log output to the desired location for troubleshooting.
- AppStream support: AppStream support was added for publishing FlexApp One CTL shortcuts to AppStream Dynamic App API.
Component Versions
Component
|
6.8.7 |
VirtFS |
6.8.7.9083
|
FPC |
6.8.7.9083
|
Bundler |
6.8.7.9083
|
Engine |
6.8.7.9083
|
Installer |
6.8.7.9083
|
Issues Resolved
- Fixed an issue where FlexApp One was unable to create a mutex for a package with an error of Access is denied.
- Fixed an issue where FlexApp One deactivation scripts did not always run.
- Fixed an issue where the FlexApp One mutex was not being released in certain cases.
- Fixed an issue where FlexApp One package would cause disks to disappear before the CAP was unloaded.
- Fixed an issue where multi-session Windows and FlexApp One instances would remove prematurely, they now stay active.
Version 6.8.6.8805 R1- Released February 28, 2024
What's New
- Enhanced Security with OAuth Integration now supports multiuser operating systems.
- We are excited to introduce OAuth integration with Microsoft Entra ID (formerly Azure AD), bringing an additional layer of security to your FlexApp One experience. Before activating a FlexApp One package, users are required to authenticate, embracing a Zero-Trust approach for all your Win32 applications. This integration ensures that only authorized personnel have access to your applications, aligning with the industry's best practices for cybersecurity.
Component Versions
Component
|
6.8.6 R1 |
VirtFS |
6.8.6.8805 |
FPC |
6.8.6.8805 |
Bundler |
6.8.6.8805 |
Engine |
6.8.6.8805 |
Installer |
6.8.6.8805 |
Version 6.8.6.8711 - Released November 9, 2023
What's New
- Enhanced Security with OAuth Integration:
- We are excited to introduce OAuth integration with Microsoft Entra ID (formerly Azure AD), bringing an additional layer of security to your FlexApp One experience. Before activating a FlexApp One package, users are required to authenticate, embracing a Zero-Trust approach for all your Win32 applications. This integration ensures that only authorized personnel have access to your applications, aligning with the industry's best practices for cybersecurity.
- Session Isolation for Multi-User Support:
- FlexApp One now offers session isolation, a pivotal feature for environments with multiple users sharing the same system. This enhancement allows different users to access distinct applications simultaneously, fostering a collaborative and efficient workspace. Moreover, this feature extends to on-boot applications, ensuring they are only activated when the user has the necessary entitlements. This level of control and customization ensures a tailored user experience.
- Superior Performance with Memory Caching:
- We have leveraged memory caching to significantly boost the performance of your FlexApp One packaged applications. This optimization ensures quicker application launches and smoother operation, enhancing productivity and user satisfaction. Furthermore, administrators have the flexibility to adjust settings to optimize application performance based on specific needs.
- Support for Larger Applications:
- FlexApp One now proudly supports larger application packages, exceeding 4GB in size. For applications that expand beyond this size post-compression, FlexApp One intelligently creates a separate executable (.exe) and a FA1 file containing all necessary data. This development addresses a critical Windows limitation, ensuring seamless operation and compatibility regardless of application size.
- Simplified License Management:
- FlexApp One now supports machine-based FlexApp_One.lic files. This means that subscription customers do not need to re-bundle, or "migrate", existing package EXEs and can instead deploy their new FlexApp_One.lic file into C:\Program Files\ProfileUnity\FlexApp\ContainerService\x64\Licenses on endpoint machines. In addition, customers utilizing ProfileUnity Management Console and Client Tools for FlexApp One deployments will benefit from the license check being deferred to the existing ProfileUnity License Server implementation, bypassing the embedded license in the package EXEs.
Issues Resolved
- Fixed an issue where --Remove command was not removing the FlexApp One package in certain circumstances.
- Fixed an issue where --Stop command was not terminating all respective FlexApp One PIDs.
- Fixed an issue where FlexApp One PIDs created with --Sync command do not terminate after successful sync completion.
- Fixed an issue where possibility of profile corruption with FlexApp One packages that contain SYSTEM environment variables.
- Fixed an issue where FlexApp One packages occasionally fail to activate/playback when SentinelOne is installed and monitoring.
- Fixed an issue where CTL shortcuts were not created that exist in a subdirectory of the Start Menu 'Programs' folder.
- Fixed an issue where your unable to cleanup (--stop --clean) a FlexApp One package where the associated PID has already been terminated.
- Fixed an issue where FlexApp One packages activated by SYSTEM with --Ctl and/or -AddToStart do not create/remove shortcuts in respective PUBLIC and PROGRAMDATA locations.
- Fixed an issue where FlexApp One packages activated by SYSTEM with --Reg and/or --Startup do not create registry entries in respective HKLM keys.
- Fixed an issue where a broken logic flow of license detection when leveraging ProfileUnity to manage FlexApp One.
- Fixed an issue where the lwl_proc_info system driver is not removed during uninstallation.
Known Limitations:
- OAuth integration is limited to single-user desktops/sessions with package activation at logon. Mutli-user environments (RDSH, XenDesktop, etc.) and/or package activation at boot are not supported.
Component Versions
Component
|
6.8.6 |
VirtFS |
6.8.6.8711 |
FPC |
6.8.6.8711 |
Bundler |
6.8.6.8711 |
Engine |
6.8.6.8711 |
Installer |
6.8.6.8711 |
Version 6.8.5.8507 - Released April 19, 2023
What's New
- Updated build number to stay in sync with core FlexApp and ProfileUnity.
Component Versions
Component
|
6.8.5 R1 |
VirtFS |
6.8.5.8507 |
FPC |
6.8.5.8507 |
Bundler |
6.8.5.8507 |
Engine |
6.8.5.8507 |
Installer |
6.8.5.8507 |
Version 6.8.5.8490 - Released April 5, 2023
Issues Resolved
- Fixed an issue where packages could not be stopped if their PID had ended.
- Fixed an issue where FlexApp One applications failed to execute when run in the same millisecond.
- Fixed an issue where Click-To-Layer shortcuts failed to be created when they were in a Start Menu Programs sub-folder.
Component Versions
Component
|
6.8.5 R1 |
VirtFS |
6.8.5.8490 |
FPC |
6.8.5.8490 |
Bundler |
6.8.5.8490 |
Engine |
6.8.5.8490 |
Installer |
6.8.5.8490 |
Version 6.8.5.8454 - Released March 15, 2023
What's New
- Packages executed as SYSTEM automatically hide the tray app since system does not have a shell to load a tray app.
- When migrating a FlexApp One engine from one version of FlexApp One to another the existing package icon is migrated as well.
- FlexApp One logs now include the OS version, UAC status, elevation status and Version info with every log header.
- The FlexApp One command line argument --clean will now cleanup write VHDX files.
- FlexApp One now supports pre/post scripts. If you create and import a script called system_myscript.cmd or system_myscript.PS1 into the FlexApp Packaging Console, the script will run as system elevated. Any scripts that start with “system_” will run as system elevated. Any other script name will run as the user without elevation.
- The FlexApp One Installer and Engine now have optional reboot flags.
- engine: --upgrade --reboot, if anything was upgraded, it will reboot.
- installer: --install --reboot, if anything was upgraded, it will reboot. A fresh install will not reboot.
- FlexApp One now supports physical registry values being written to registry keys that are virtualized by FlexApp.
- The FlexApp One Bundler option –Migrate will now perform a test for a valid package file, license file, flexapp.zip and engine.exe before execution to ensure success.
- FlexApp One Engine --startup --index 999 will NOT automatically add --CTL to the HKCU\SOFTWARE\Microsoft\Windows\CurrentVersion\Run key.
- Using --startup --CTL --index 999 will still add CTL to the Run key.
- When FlexApp One is managed by ProfileUnity, no license file is needed. The license logic is handled by the ProfileUnity Client and the ProfileUnity Management Console.
- The FlexApp One standalone license checks at the packagename.exe level can be overridden by placing your FlexApp_One.lic in the following path “C:\Program Files\ProfileUnity\FlexApp\ContainerService\*\Licenses”.
Issues Resolved
- Fixed an issue where an expired perpetual license allowed applications to still be bundled.
- Fixed an issue where packages did not install or upgrade the engine.
- Fixed an issue where users were not able to modify files contained within a package activated as SYSTEM despite having permissions.
- Fixed an issue where addtostart and CTL shortcuts created as system using --system were not usable by regular users.
- Fixed an issue where the FlexApp One tray apps were mounted as system using –system. The FlexApp One tray can only stop one app.
- Fixed an issue where the container service still tried to load lwl_proc_info driver when it was unnecessary.
- Fixed an issue where packages started and stopped as SYSTEM failed to remove CTL shortcuts.
- Fixed an issue where running installer.exe --install created a literal folder called $TEMP.
- Fixed an issue where If you ran the same packagename.exe more than once then you ended up with the same number of tray icons showing.
- Fixed an issue where packages failed to parse the icon during execution and failed back to using the default Liquidware droplet icon.
- Fixed an issue where CTL shortcuts failed when the Desktop shell folder was redirected to a UNC path.
- Fixed an issue where call to home was not disabled when --calltohome false was specified.
- Fixed an issue where the Engine Start In shortcut field was ignored for CTL and index 0.
- Fixed an issue where long fully qualified mount point paths encountered the path length limit of 260 characters.
- Fixed an issue where micro isolation was occurring when a single FlexApp was played back.
- Fixed an issue where Flexapp One did not always start at startup.
- Fixed an issue where packagename.exe --uninstall and installer.exe --uninstall did not work.
- Fixed an issue where packagename.exe --uninstall did not uninstall while played back. Fixed an issue where Packages that fail to mount continue running.
- Fixed an issue where FlexApp One applications used ProgramData and the users public profile when running as SYSTEM account for shortcuts.
- Fixed an issue where command line arguments were case-sensitive.
- Fixed an issue where container service files failed to be removed during –uninstall.
Version 6.8.5.63276 - Released August 18, 2021
What's New
The first version of FlexApp One is released to market. FlexApp One makes offline distribution and consumption of applications possible.
Known Issues/Limitations
- Installing or uninstalling applications into the operating system that could be intermingled with active FlexApp One applications could present challenges. Note that FlexApp One applications might have to be stopped in order to install or uninstall other software on the end user device. Support for installing or uninstalling applications into the operating system with active FlexApp One applications is best effort on well-managed devices.
- FlexApp One applications are incompatible with the simultaneous use of ProfileUnity on an end user device. To get around this limitation, read the following knowledge base article, How to Use FlexApp One and ProfileUnity Version 6.8.4.