Demo Desktop Access Patterns¶

Use this reference to standardize how guides tell users to access a demo desktop before the main walkthrough steps.

Use when: - The guide starts from Workspace ONE URL directly. - The guide requires launching TD-WINDOWS11, TD-RDS-Desktops, or TD-AVAoD from Workspace ONE.

Reusable steps: 1. Open a browser and sign in to Workspace ONE at https://testdrive.us0.wss.workspaceone.com/ using TestDrive credentials. 2. Go to Apps or Favorites. 3. Search for the required desktop pool name. 4. Open the actions menu on the tile and choose Launch from Browser or Launch from Client. 5. Continue once the Windows desktop session is visible.

Placeholders: - (examples: TD-WINDOWS11, TD-RDS-Desktops, TD-AVAoD) - (Launch from Browser or Launch from Client)

Validation checkpoint: - User sees the Windows desktop and can open desktop shortcuts used by the guide.

Mandatory screenshot requirements for Workspace ONE entry guides: - When Workspace ONE is the entry point, include a screenshot showing search results for the exact required desktop pool name. - For App Volumes demo guides, the search result must show TD-AVAoDv2. - Include a screenshot showing the star (favorite) action on the same desktop tile. - Place these screenshots in the guide's local assets/ folder and reference them in the Access section before launch steps. - Do not reuse screenshots that show a different desktop pool name.

App Volumes terminology rule: - Use Storages only when directly referencing the App Volumes UI label or navigation path (for example, Infrastructure > Storages). - In all prose outside direct UI references, use singular storage / storage location wording.

App Volumes language guardrails (current and future docs): - Do not use layer, layering, or AppStacks language in guide prose. - Use this goal statement when needed: Goal of this exercise is to show how the applications are separated from the operating system. We walk through where App Volumes application packages are stored on a file share and how they are delivered from that central location to assigned endpoints. - Prefer infrastructure platform, deployment model, or delivery architecture instead of layer terminology.

App Volumes delivery terminology guardrails: - Default language in guide prose should be application delivery, application package, assignment, set the application package version as Current, and delivered to assigned endpoints. - Use attach or attached only in these limited scenarios: - Direct references to explicit UI text that contains attachment wording (for example, Allow Multiple package attachment on multi-session RDS). - OS-level or validation statements about runtime behavior (for example, a VHD disk appears attached in Disk Management). - Outside those scenarios, replace attach/attached wording with deliver/delivered, assigned, available, or mounted (when describing technical storage behavior). - Do not use App Attach as a primary positioning term in new App Volumes guides. - When quoting UI text with attachment terminology, keep it exact and use surrounding prose that returns to delivery/package language.

Source examples: - ../TestDrive Knowledge Base/TestDrive KB Directory/Demo Guides/AppVolumes/Omnissa App Volumes - Applications and Packages.md - ../TestDrive Knowledge Base/TestDrive KB Directory/Demo Guides/AppVolumes/Omnissa App Volumes - Apps On Demand.md - ../TestDrive Knowledge Base/TestDrive KB Directory/Demo Guides/AppVolumes/Omnissa App Volumes - Published Apps On Demand.md - ../TestDrive Knowledge Base/TestDrive KB Directory/Demo Guides/AppVolumes/Omnissa App Volumes Writable Volumes User Installed Applications (UIA) Demo.md - ../TestDrive Knowledge Base/TestDrive KB Directory/Demo Guides/Dynamic Environment Manager/Omnissa Dynamic Environment Manager Walkthrough.md

Pattern 2: TestDrive Portal -> Workspace ONE Intelligent Hub -> launch Horizon desktop¶

Use when: - The guide begins in the TestDrive Portal and then transitions through the Workspace ONE Intelligent Hub tile. - You want to include DemoZone tile navigation and portal credential context.

Reusable steps: 1. Open https://testdrive.omnissa.com/ and sign in. 2. In DemoZone, find Workspace ONE Intelligent Hub and select View Details. 3. Record TestDrive credentials from the details pop-up. 4. Select Launch on the Workspace ONE Intelligent Hub tile. 5. In Workspace ONE, navigate to Apps -> Horizon category. 6. Find the target desktop pool and choose Launch from Browser (or Launch from Client if Horizon Client is installed).

Placeholders: - (example: TD-WINDOWS11)

Validation checkpoint: - User reaches the Horizon desktop session and can proceed with in-desktop tasks.

Source examples: - ../TestDrive Knowledge Base/TestDrive KB Directory/Demo Guides/Horizon/Launching Horizon Virtual Desktops from Workspace ONE.md - ../TestDrive Knowledge Base/TestDrive KB Directory/Demo Guides/Horizon/Launching Horizon Remote Apps from Workspace ONE.md

Pattern 3: TestDrive Portal -> Horizon tile -> HTML Access (browser-only)¶

Use when: - The guide should stay browser-based. - You want Horizon Web Access entry instead of native client.

Reusable steps: 1. Open https://testdrive.omnissa.com/ and sign in. 2. In DemoZone, select Launch on the Horizon tile. 3. In Launch links, select Launch Horizon Web Access -> America Region - Standard and vGPU Demo. 4. Sign in with TestDrive credentials shown in the tile credentials section. 5. Launch the required desktop or published app resource from the HTML Access page.

Placeholders: - (example: TD-WINDOWS11 or RDSH-paint.net)

Validation checkpoint: - User can interact with the launched desktop/app in browser.

Source examples: - ../TestDrive Knowledge Base/TestDrive KB Directory/Demo Guides/Horizon/Launching Horizon Resources using HTML Access.md

Pattern 4: TestDrive Portal -> Horizon tile -> Native Horizon Client¶

Use when: - Native Horizon Client behavior is required. - You want users to pick pools from the native client selector.

Reusable steps: 1. Confirm Horizon Client is installed locally. 2. Open https://testdrive.omnissa.com/ and sign in. 3. In DemoZone, select Launch on the Horizon tile. 4. In Launch links, choose Launch Horizon Native Client -> America Region - Standard and vGPU Demo. 5. Sign in with TestDrive credentials. 6. Double-click the target pool to start the desktop session.

Placeholders: - (examples: TD-WINDOWS11, TD-RDS-Desktops)

Validation checkpoint: - Desktop opens in native Horizon Client window.

Source examples: - ../TestDrive Knowledge Base/TestDrive KB Directory/Demo Guides/Horizon/Launching Virtual Desktops from Horizon Client.md

Pattern 5: Prerequisite desktop session (guide starts after desktop is already open)¶

Use when: - The guide's main task starts inside an already running desktop session. - You want to avoid duplicating full launch steps in every guide.

Reusable prerequisite block: - Before starting this walkthrough, launch a TestDrive desktop session (TD-WINDOWS11 or TD-RDS-Desktops) using one of the standard access guides: - Launching Horizon Virtual Desktops from Workspace ONE - Launching Virtual Desktops from Horizon Client - Launching Horizon Resources using HTML Access

Validation checkpoint: - User confirms an active desktop session before Step 1 of the walkthrough.

Source examples: - ../TestDrive Knowledge Base/TestDrive KB Directory/Demo Guides/Horizon/Accessing the Horizon Console.md - ../TestDrive Knowledge Base/TestDrive KB Directory/Demo Guides/Horizon/Horizon Session Collaboration.md - ../TestDrive Knowledge Base/TestDrive KB Directory/Demo Guides/Horizon/Horizon Help Desk Tool.md

Recommended standard section to paste into new guides¶

Access the demo desktop¶

Use one of the approved paths below to start the required desktop session for this guide.

Workspace ONE direct login path: sign in at https://testdrive.us0.wss.workspaceone.com/, search for , then choose .
TestDrive Portal -> Workspace ONE path: sign in at https://testdrive.omnissa.com/, launch Workspace ONE Intelligent Hub from DemoZone, then open from the Horizon app category.
TestDrive Portal -> Horizon HTML Access path: sign in at https://testdrive.omnissa.com/, open Horizon Launch links, choose Launch Horizon Web Access, then launch .
TestDrive Portal -> Horizon Native Client path: sign in at https://testdrive.omnissa.com/, open Horizon Launch links, choose Launch Horizon Native Client, then open .

Proceed when your desktop session is visible and responsive.