Skip to content

Home > Demo Guides > AppVolumes

Omnissa App Volumes - Notepad++ Application Lifecycle (Operator)

In this operator walkthrough, you demonstrate how App Volumes lifecycle management changes the active Notepad++ package version centrally by setting the application package version as Current, while assignments remain unchanged.

Internal Use Notice

This guide is for trusted operators in shared TestDrive environments. Do not publish publicly.

Overview

This flow validates the full operator lifecycle story:

  1. Users initially receive the Notepad++ package version set as Current.
  2. The operator sets a different application package version as Current.
  3. Users log out and log back in.
  4. The new version is delivered automatically.
  5. No base image changes, reinstalls, or user-side actions are required.

Packaging and capture are out of scope for this demo and are already completed before the walkthrough begins.

Access the Demo Desktop (Operator Start)

Follow the same opening access language and desktop launch pattern used in the Adobe operator guide:

  1. Open a browser and sign in to Workspace ONE at https://testdrive.us0.wss.workspaceone.com/.
  2. Go to Apps or Favorites.
  3. Search for TD-AVAoDv2, then click the star on that tile to add it to Favorites for faster future access.

4. Launch the desktop from the tile actions menu. 5. Continue when the Windows desktop is fully visible and responsive.

Desktop Pool

Operators launch desktops from:

  • TD-AVAoDv2

Operator Walkthrough Steps

Step 1: Confirm Current Lifecycle State

In App Volumes, open the Applications view and locate Notepad++. Confirm that version 8.9.1 is set as Current, enabled, and delivered via VHD.

Flow context: This establishes the initial lifecycle state and confirms which version is active before users log in.

Step 2: Validate Package Health and Eligibility

Open the Notepad++ package details and verify version metadata, format (VHD), delivery method (Classic), OS compatibility, and capture/agent information.

Flow context: This validates that the package is healthy, eligible, and ready for delivery before the demo change.

Step 3: Confirm Assignments Stay Constant

Open Assignments and confirm Notepad++ is assigned to the TDAV desktop group with the Current version selected.

Flow context: This proves no assignment edits are required during a version switch. Only the package version set as Current changes.

Step 4: Validate User Baseline Session

Log in to a TDAV desktop and confirm the Notepad++ icon is visible and available alongside other delivered applications.

Flow context: This is the participant baseline state before the version switch.

Step 5: Prove VHD Delivery at OS Level

In the same session, open Windows Disk Management and confirm the CVApps disk is attached, healthy, and read-only.

Flow context: This provides technical proof that delivery is dynamic through App Volumes and not installed into the base image.

Step 6: Confirm Application Usability

Launch Notepad++ and confirm normal operation in the user session.

Flow context: This confirms successful delivery and usability from the participant perspective.

Step 7: Set the Application Package Version as Current

Back in App Volumes, select the alternate Notepad++ package version and set the application package version as Current.

Flow context: This is the core operator lifecycle action showing centralized version control without assignment changes.

Validation Sequence After Step 7

  1. Have users log out and log back in.
  2. Re-open Notepad++ and confirm the new version is now delivered.
  3. Confirm assignments still point to the same group policy and were not edited.

Guardrails

  • Execute only pre-approved package state changes in shared environments.
  • Do not combine lifecycle version flips with unrelated troubleshooting changes.
  • Capture before and after evidence for all Current version transitions.
  • Confirm rollback target before ending the operator session.

Screenshot Map (Final)

  1. 01_appvol_notepadpp_package_current.png
  2. 02_appvol_notepadpp_package_details.png
  3. 03_appvol_notepadpp_assignments.png
  4. 04_desktop_notepadpp_icon_visible.png
  5. 05_diskmgmt_cvapps_attached.png
  6. 06_notepadpp_running.png
  7. 07_appvol_notepadpp_set_current.png

Summary

This operator walkthrough demonstrates App Volumes lifecycle management for Notepad++ by setting the application package version as Current centrally, validating that user assignments remain unchanged, and proving that updated application delivery occurs automatically at next login without base image modifications.