Community-shared tools & configurations for AppSense Environment Manager, Application Manager and Performance Manager

AppSense and VMware Horizon: advanced UEM integration

AppSense and VMware Horizon create a powerful foundation for managing virtual desktops, but their value depends on treating them as one operating model rather than two disconnected tools. AppSense supplies user experience management (UEM), application delivery and end-user support, while VMware Horizon provisions and connects hosted desktops and published applications. The control plane must understand whether a request came from a physical endpoint, a pooled session host or a persistent virtual machine.

For teams evaluating this pairing, advanced UEM integration best practices begin with the user journey, not the console. A successful login may depend on virtualised applications, redirected printers, mapped drives, Outlook profiles, language packs and line-of-business tools that behave differently in a multi-session image. Defining those dependencies early helps administrators prevent duplicated installations, inconsistent settings and performance faults that appear only after a user reaches the corporate network.

This guide covers architecture, policy design, Environment Manager, testing and operations. It also treats Australia’s distributed workplaces and strict support expectations as design inputs. The aim is a repeatable integration that can be supported by internal IT teams, local partners and the wider AppSense community without relying on undocumented workarounds or a single specialist’s memory.

Map the architecture and ownership

Start with a component map that covers identity, management and session delivery. On the AppSense side, document the management server, policy services, AppSense client and Environment Manager components. On the VMware side, record the Horizon Connection Server, broker, agent, entitlement services, customisation server, image management process and every session-host pool. Include supporting services such as Active Directory, DNS, certificate authorities, application sources and ticketing or monitoring platforms.

Decide which system is authoritative for each outcome. Horizon should remain the source for entitlement and session assignment; AppSense should enforce approved application experiences and user settings. Avoid asking both products to perform the same installation or profile task in the same logon phase. Where Group Policy, Configuration Manager or a third-party tool already owns a control, record the overlap and define precedence so troubleshooting can begin from known facts.

Define failure behaviour as carefully as the successful path. If the AppSense service is temporarily unavailable, decide whether Horizon sessions should start, whether policy enforcement should fail open and how users receive a clear support message. Test service-account expiry, certificate renewal, storage thresholds and backup restoration. For Environment Manager, retain a known-good payload and verify that Horizon agent, AppSense client and operating-system updates can be rolled back as one controlled image.

Test communication paths from the session host and from a supported administration location. Confirm DNS resolution, HTTPS access, certificate trust, service accounts, agent heartbeats, policy retrieval and Event Log access. Sequence software changes in a golden image, including operating-system updates, Horizon client deployment, AppSense installation, Environment Manager payload updates and profile preparation. Keep a documented rollback image and record the supported versions of every component before production rollout.

Build session-aware AppSense policies

Create policies around delivery groups, pool type, image version and named session rather than applying broad workstation rules to every Windows device. A useful condition can combine Horizon delivery-group attributes, operating-system build, AppSense client version and image identifier. For organisations using shared session hosts, the practical challenge is separating machine-wide state from per-user state. Community guidance on concurrent user settings offers a useful reference for reviewing settings that may conflict when several virtual users share one host.

Treat machine configuration as immutable unless a controlled change process owns it. Install shared applications and HKLM components during image construction, then use user-scoped actions for preferences, certificates, mapped resources and application data. For Office and Outlook, test whether cached data is acceptable, what is synchronised through OneDrive and how temporary files are removed. In named persistent desktops, include the virtual-machine identifier so that a personal desktop can receive a different policy from a pooled host.

Guard against logon recursion and policy loops. A condition should not launch an app whose installation depends on the same policy, and AppSense actions should tolerate a missing profile, unavailable application source or interrupted network connection. Apply least privilege to the account used by the client, avoid storing domain credentials in scripts and give every action a timeout with observable failure logging. Publish policies in stages so administrators can compare the intended state with the state reported by the session.

Configure Environment Manager for cloud applications

Environment Manager extends AppSense by executing controlled processes before or after managed applications. It is well suited to restoring registry values, preparing application files, configuring Outlook, setting per-user registry entries and cleaning temporary artefacts. Define each task as an idempotent operation that can run again without damaging a working profile. The expected result, maximum runtime, retry count and dependency order belong in the task metadata, not only in the script comments.

Office applications need particular care because Microsoft 365 is a dominant corporate suite in Australia and combines local Click-to-Run components with cloud-backed data and per-user profiles. Use the Office 365 deployment guide to structure Environment Manager tasks around application launch, add-in registration, cache locations and exit behaviour. Test Outlook first, because mailbox creation, add-ins and profile paths differ from file-based applications. Teams, OneDrive and SharePoint also have process models that can trigger repeated actions if the match criteria are too broad.

Keep tenant-specific values outside the package. Store environment references, URLs and credentials in an approved secrets mechanism, and sign or checksum scripts so agents can distinguish trusted content from altered files. Review privileges against the Australian Signals Directorate’s Essential Eight where the organisation applies it, and ensure diagnostics capture enough context for an incident without recording mailbox content or authentication secrets. Version the package alongside the golden image and test it against patched Horizon agents and current AppSense releases.

Test safely across Australian operating contexts

Build a representative test matrix before touching production. Australian organisations commonly span Sydney, Melbourne and Brisbane, with remote users connecting from Perth, Adelaide or regional homes; each location can expose a different WAN path, broadband latency and power-reliability pattern. Include pooled and persistent desktops, VMware Blast and any legacy PCoIP estate, common office applications, peak logon periods and deliberately degraded network conditions. Use Horizon performance data and AppSense action logs to locate delays rather than treating a slow desktop as a single product fault.

Local date, time and governance details can invalidate tests written for another market. Scripts should accept unambiguous ISO 8601 values, while interfaces that display Australian dates should use DD/MM/YYYY and Monday as the first day of the week. Test eastern and western Australian time zones through daylight-saving transitions, including sites that observe it and Western Australia, which does not. Under the Privacy Act 1988 and Australian Privacy Principles, confirm where AppSense telemetry and Microsoft 365 tenant data are hosted; do not assume a global service configuration satisfies state health, finance or customer contractual requirements.

Plan release waves around Australian public holidays, school holiday periods and end-of-financial-year workload rather than relying on a generic midnight change window. Keep a small representative user group, a business owner and an escalation contact available during the first wave. Monitor session start time, login failures, AppSense policy deployment, application launch errors and Horizon broker events. If support is needed, evaluate local implementation depth through Amrella support resources alongside the relevant vendor support agreement, internal runbook and AppSense Exchange discussions.

Operate, measure and improve the integration

Treat observability and ownership as part of the integration. Assign named owners for the AppSense server, Environment Manager packages, Horizon infrastructure, Windows images, applications and identity services. Maintain a service catalogue that links each policy and task to its business purpose, owner, last test date and retirement date. Remove rules that merely duplicate another tool, and place uncommon exceptions in a controlled policy with an expiry date so they do not become invisible permanent configuration.

Measure trends rather than individual alerts. Useful indicators include policy download failures, unsupported client versions, Horizon session-start latency, application launch duration, Environment Manager task failures and the number of session hosts missing required agents. Compare those measures by office, delivery group and image version. A rising failure rate after an update often identifies a compatibility fault more clearly than a support queue full of unrelated symptoms, while task-duration trends can expose slow network paths or inefficient scripts.

Browse AppSense Exchange, search by the exact AppSense, Environment Manager and Horizon versions in use, and read the matching community reviews before changing production. Compare a candidate package with the published configuration examples, validate it in a disposable session host and publish it with a rollback procedure. Start with one delivery group, expand through an Australian pilot office, then schedule the next image review with evidence from the previous wave.