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

AppSense and Windows 11: Known Issues and Upgrade Considerations

Moving managed desktops to Windows 11 is rarely a simple operating system refresh. AppSense policies, user profiles, application controls, shortcuts, shell settings and endpoint services all operate within the Windows client environment, so a change to the underlying platform can expose compatibility gaps that were invisible on Windows 10.

For Australian organisations, the transition often happens across a mixed estate. A head office in Sydney or Melbourne may have modern laptops and fast corporate links, while regional staff, branch offices and remote workers depend on variable NBN performance or older hardware. A careful upgrade process needs to account for those differences rather than treating every device as the same.

The AppSense brand is now commonly associated with Ivanti User Workspace Manager products, including Environment Manager, Application Control and Performance Manager. Product names, agent builds and support policies can vary, so teams should confirm the exact release combination before deployment. Community experience on AppSense Exchange can help fill in practical details that formal documentation does not always cover.

Confirm the Product and Support Baseline

The first task is to identify which AppSense components are installed and how they interact with Windows 11. Environment Manager may be responsible for policy processing and personalisation, Application Control may govern executable trust, and Performance Manager may apply application or process rules. Each agent can have its own compatibility requirements.

Do not assume that an agent that runs on Windows 10 will be fully supported on Windows 11. Confirm the supported operating system editions, Windows 11 release, AppSense or Ivanti version, architecture and required hotfixes. Windows 11 feature updates can introduce behavioural changes even when the organisation remains within the same broad operating system family.

A useful baseline includes the current agent version, console version, policy package, management server version and profile storage location. Record whether endpoints are physical, virtual or Azure Virtual Desktop machines. A clean inventory makes it easier to distinguish an AppSense defect from a driver problem, a profile issue or a Windows servicing change.

Application Control deserves particular attention. Windows 11 security features, Smart App Control, reputation checks, driver protections and updated Microsoft Defender behaviour can affect how applications are identified or permitted. Review trusted vendors, publishers, paths and certificates before the pilot begins, especially where line-of-business software uses unsigned helper processes.

Expect Profile and Personalisation Differences

Windows 11 changes parts of the shell, Settings application, Start menu, taskbar and default application experience. Policies designed around older registry values, shell locations or Windows 10 shortcuts may still apply technically while producing an inconsistent user experience. A setting that appears harmless in a lab can become frustrating when it affects every sign-in.

Profile personalisation can also behave differently after an in-place upgrade. Cached user data, redirected folders, OneDrive policies, temporary profile handling and permissions all influence whether a user receives the expected desktop. Before migration, capture representative profiles and test sign-in, sign-out, reconnect and first logon after the upgrade.

Teams working with roaming or non-persistent desktops should pay close attention to what is captured and restored. The user profile roaming guide offers a useful reference point for reviewing personalisation across sessions. It can help administrators separate genuine Windows 11 changes from an existing profile design issue.

Common checks include Start menu behaviour, taskbar pins, default browser associations, mapped drives, printer connections, Office settings and application preferences. Test both a clean Windows 11 profile and a migrated Windows 10 profile. The two scenarios may expose different problems, particularly where legacy registry settings or old shell customisations remain in the user store.

Investigate Agent Stability and Policy Processing

An AppSense agent issue may appear as a slow logon, delayed desktop, missing policy, application launch failure or repeated service restart. Users may describe the result simply as “Windows being a bit average”, but event logs usually provide a more useful direction. Correlate AppSense logs with Windows Event Viewer, Application Control events, Defender records and profile service messages.

Agent crashes can be caused by unsupported builds, conflicts with endpoint security software, damaged local data, incompatible drivers or policy actions that create an unexpected loop. Avoid making broad exclusions immediately. First identify the affected agent, process, policy and Windows build, then reproduce the behaviour on a small test group.

The community resource on common agent crashes can support that investigation by helping administrators interpret familiar errors and collect the right evidence. When raising a case with a vendor or Australian managed service provider, include timestamps, agent logs, policy exports, operating system build and a precise reproduction sequence.

Performance Manager rules should be reviewed after an upgrade because process names, service behaviour and application packaging may change. A rule intended to reduce resource use can interfere with a Windows 11 component or a modern application framework. Check CPU, memory, disk and sign-in duration before and after policy changes instead of relying on user reports alone.

Build an Australian-Friendly Pilot

A staged pilot is more reliable than a broad upgrade pushed overnight. Include devices from different hardware generations, office locations, network conditions and user roles. A Melbourne finance user, a Brisbane contact-centre worker, a Perth field employee and a regional home user may exercise very different parts of the environment.

Australian organisations should also consider time zones and support coverage. A central IT team in Sydney may complete a change while Western Australia offices are still operating, leaving less time for local validation. Schedule pilot waves with enough overlap for service desk staff and regional partners to investigate issues during their normal working hours.

Connectivity matters for profile and application delivery. A Windows 11 device that signs in quickly on a corporate LAN may struggle over a congested home connection if large profile data, scripts or application packages are processed at logon. Measure logon duration over realistic links, including remote access, Wi-Fi and branch connectivity, rather than testing only from the main office.

A sensible pilot should include a rollback path. Confirm that devices can return to the previous operating system or be reimaged, and verify that user data is protected before the change. Keep a record of policy revisions so a failed test can be reversed without guesswork. “No worries” is a useful attitude during testing, but it should not replace a documented recovery process.

Upgrade Checks Worth Recording

Before the first production wave, capture these baseline details:

During the pilot, compare these operational measures:

Review Security, Applications and Hardware

Windows 11 introduces security expectations that can affect older AppSense deployments. Secure Boot, TPM requirements, virtualisation-based security, memory integrity and updated Defender capabilities may change the way drivers and protected processes behave. Hardware that technically starts Windows 11 may still perform poorly when security features are enabled.

Application Control policies should be tested against modern installers, packaged applications, Microsoft Store components, browser updates and applications that launch child processes. Pay attention to certificate changes and automatic updater behaviour. A rule that permits an old publisher certificate may fail after the vendor changes its signing process.

Hardware compatibility is equally important. Older laptops may have limited storage, insufficient memory or firmware that requires updating before Windows 11 is stable. Docking stations, smart-card readers, VPN clients, print drivers and accessibility tools should form part of the test matrix. In Australian workplaces, this is especially relevant for mobile staff who use a mixture of corporate and personally sourced peripherals.

Endpoint security products can amplify compatibility problems. Test AppSense agents alongside the actual security stack used in production, including application isolation, web filtering, EDR and VPN software. A clean lab with fewer controls may provide a false sense of security. If a temporary exclusion is required, document its scope and remove it after the root cause is understood.

Broader security governance should remain separate from AppSense troubleshooting, but related operational material can still be useful when documenting the change. A general security operations reference may provide supporting context for endpoint controls, asset records or risk ownership. It should complement, not replace, the product-specific compatibility review.

Use Community Evidence Without Losing Change Control

AppSense Exchange is valuable because administrators often share working configurations, diagnostic methods and lessons from real deployments. Search by product, version, Windows release and error code, and check when a resource was published. A configuration that solved a Windows 10 issue may be unsuitable for a current Windows 11 build.

Treat downloaded tools and policy examples as test material. Review scripts before execution, inspect registry changes, confirm required permissions and compare settings with your organisation’s standards. Preserve the original policy package and export a known-good version before importing community content into a test environment.

Discussion forums can also improve the quality of troubleshooting. A useful post describes the operating system build, AppSense version, deployment type, symptoms, logs and changes already attempted. Vague reports such as “Windows 11 breaks AppSense” are difficult to validate, while a clear timeline can reveal whether the failure began after an update, policy revision or security product change.

For remote teams, evidence collection should respect privacy and business controls. Remove usernames, customer data, internal hostnames and sensitive policy details before uploading logs or screenshots. If support sessions are needed, use approved corporate tools and record who accessed the device. General remote communication resources, including a video support guide, may help explain session setup, but they should not replace your organisation’s approved support process.

The most dependable upgrade programme combines vendor documentation, controlled pilots, community knowledge and local operational feedback. Track each finding in a change record with an owner, severity, affected build, workaround and permanent resolution. That record becomes especially useful when the next Windows 11 feature update arrives or when an acquired business brings a different AppSense estate into the environment.

Use AppSense Exchange to validate your component versions, search for matching Windows 11 symptoms and share tested fixes with the wider community. Run the upgrade in measured waves, keep rollback available, and promote only after profiles, policies, applications, security controls and regional users have passed the same practical checks they will face in production.