Skip to main content

FlexAppOne Shortcut Issue when assigning an updated application with a different name but same shortcut name and Preservation Mode Enabled

Kamil Posluszny
  • Created:
  • Updated:

Problem:

When using FlexAppOne with Preservation Mode enabled, users may experience the following issues when the FlexApp one name changes but the shortcut being used remains the same:

  1. Orphaned shortcuts remain in Start Menu after unassigning a FlexAppOne package
  2. Error messages about missing shortcuts when assigning a new FlexAppOne with the same shortcut name but different package name
  3. Pinned taskbar shortcuts break after logoff/logon due to full path targeting

Environment Details

  • Affected Systems: Windows 10/11 Enterprise
  • ProfileUnity Version: 6.8.7.9145 and potentially other versions
  • Configuration: FlexAppOne with Preservation Mode = ON

Root Cause

This behavior is by design when Preservation Mode is enabled in FlexAppOne. The preservation mechanism conflicts with dynamic package naming conventions, causing shortcut management issues when package names change between versions but the shortcut name remains the same.

 

Solution(s)

Potential Approach:

  • Use consistent base package names without version suffixes
  • Utilize the Version field in the package properties in FPC to differentiate between versions
    • Avoid changing package names between different versions of the same application

Example:

❌ Incorrect Naming:
- Package Name: "Notepad++-8.7"
- Package Name: "Notepad++-8.8"

✅ Correct Naming:
- Package Name: "Notepad++"
- Version: "8.7"
- Version: "8.8"

Alternative Considerations

If you must maintain version-specific package names:

  • Consider disabling Preservation Mode.
  • Implement manual cleanup procedures for orphaned shortcuts

Troubleshooting Steps

Step 1: Verify Current Configuration

  1. Check if Preservation Mode is enabled in FlexAppOne settings
  2. Review current package naming convention
  3. Document affected applications and shortcuts

Step 2: Implement Solution

  1. For new packages: Adopt the standardized naming convention
  2. For existing packages:
    • Create  or clone existing packages with correct naming
    • Use version field in FPC for packages
    • Gradually migrate users to new packages
    • Clean up old package assignments

Step 3: Test and Validate

  1. Test shortcut behavior with new naming convention
  2. Verify shortcuts are properly removed when unassigned
  3. Confirm pinned taskbar shortcuts remain functional after logoff/logon

Product: ProfileUnity-FlexApp

Product Version: Any

 

 

Related articles