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

Using AppSense to deliver per-machine vs per-user application settings

A sound AppSense design for per-machine and per-user application settings starts with deciding who should own each configuration value. A toggle suited to a shared reception terminal may be wrong for a designer’s laptop, while a personal language choice should not be pushed to every device. Application owners, endpoint administrators, service-desk analysts and users all need predictable behaviour when someone joins, changes role, moves site or replaces a machine.

Per-machine settings belong to the endpoint and normally affect every account that uses it. Per-user settings follow the identity and may vary by group, role or individual. The distinction is more than a convenient delivery choice: registry location, profile behaviour, package dependencies and application licensing can make one scope the only valid option. Scope also affects support, because a shared default may need administrator repair while a personal value may need to survive a device replacement.

AppSense supports this work through configuration and software delivery, conditional targeting, scripts and repair actions. Packages can enforce prerequisites, apply values during installation and correct drift later, although available functions vary by AppSense release. Community examples therefore need validation against the version and application in use. The AppSense Exchange is a practical place to compare scripts, uncover edge cases and learn how other organisations have handled comparable deployments.

Australian environments add complications that are easy to underestimate. Many workplaces in Sydney, Melbourne and Brisbane now combine corporate desktops, hot desks, laptops used at home and Citrix virtual sessions. Regional offices and field staff may have intermittent connectivity, making remote remediation harder than initial deployment. The local market includes government, education, healthcare, retail and professional-services fleets, where one application may support both office and operational users. Where settings affect identity, access or monitoring, the Privacy Act 1988, Australian Privacy Principles and Notifiable Data Breaches scheme make governance relevant, even when AppSense itself is not the system holding the regulated information.

Start with ownership and intent

Begin with a catalogue of the settings that matter to the application rather than a catalogue of every registry value. For each entry, record its business purpose, technical location, owner, intended audience, trigger and removal behaviour. “Required for operation”, “controlled by IT”, “preferred by the user” and “temporary for a task” are different intents, and each calls for a different scope and service model.

Define a default before adding exceptions. A machine baseline can carry shared values that every supported device needs, while approved per-user overrides can cover role-based or personal choices. Exceptions should name their source, expiry and approver. Otherwise, a support workaround can become an undocumented standard and drift away from the packaged configuration.

Make application owners accountable for intent and the AppSense team accountable for implementation. A useful review checks whether a proposed rule changes the supported configuration, user experience, security boundary or upgrade path. This prevents a small deployment script from becoming permanent operational logic with no owner.

Separate deployment from personal preference

Per-machine control is the natural choice for artefacts and behaviour shared by an endpoint: installation paths, application binaries, machine-wide services, shared plug-in locations, licensing components and integrations expected to exist once per device. Many shared values live in the machine-wide registry hive, outside the roaming user profile. A package can establish them during installation, repeat them when needed and help reconstruct a device that has been repaired or rebuilt.

Use the machine scope for controls that protect the device or establish a consistent managed environment. Examples include disabling an unwanted start-up path, registering a required component, setting a managed proxy address or locking a shared configuration file. The exact method depends on the application, but the test is whether the value should follow the device regardless of who signs in. If it changes with a person’s job, a user-scoped mechanism may be safer.

Manage these settings as controlled configuration, not as incidental deployment residue. Version the packages that change machine state, record which package owns each setting and avoid altering the same value through several tools. Scheduled changes should align with testing, maintenance windows and the application release cycle. Otherwise, AppSense may repeatedly repair a value that another platform policy also changes, leaving administrators to diagnose a conflict they did not create.

Build conditional rules without scope confusion

Per-user delivery suits preferences that should remain with a person: interface language, theme, selected workspace, notification behaviour or an application feature that varies by job. Many personal values live under the user registry hive or in application data within the user profile, and they may roam depending on the operating system and profile design. AppSense can target a package or configuration according to account, group and other conditions, allowing personalisation without changing the common endpoint baseline.

Test the timing, not just the target. Some application settings are read only when the profile is created, while others are read at every launch or overwritten when the application starts. Delivering a value during a Citrix session may therefore behave differently from delivering it to a managed laptop. Use a test account that reflects the real logon path, then check the outcome after profile refresh, sign-out and reconnect.

Keep secrets and regulated data out of personal configuration packages. Prefer the application’s supported authentication path, such as single sign-on, or an approved enterprise credential method. A setting that stores a token or password in a roaming profile can expose it beyond the intended device. Document which values may roam, which must remain local and which are cleared at logoff. This prevents personalisation from weakening the organisation’s security controls.

Reconcile profiles, devices and virtual desktops

A hybrid estate can apply the same AppSense package in several contexts, including a physical desktop, a personal Windows device and a non-persistent Citrix workspace. Each context may have a different profile source and different available registry locations. Establish a clear precedence: organisation baseline, application package, platform policy and approved user preference. Without one, the last writer can win and support may see inconsistent results even though every individual package succeeded.

For Citrix deployments, profile management and AppSense delivery need deliberate coexistence rather than accidental overlap. This resource on Citrix coexistence strategies is useful when assessing profile refresh timing, registry redirection and where machine-scoped changes should occur. Test both persistent and non-persistent sessions, and verify that a setting moved between scopes still reaches the application at the expected point in its startup sequence.

Pilot with representative users and devices before extending a rule across the fleet. Include office staff who hot-desk in Melbourne, a team working from a regional Queensland office, and staff who use the same application from home. Compare physical and virtual sessions, standard and privileged accounts, and devices managed under different configurations. Record results by device type and role so that the final policy reflects actual working conditions rather than assumptions from a lab.

Operate the model with confidence

Before a broad rollout, protect the AppSense database and configuration history as carefully as the application settings themselves. Package versions, scripts, assignments and audit records can determine whether a device can be restored to a known state. This database backup guidance provides a practical starting point for schedules, retention and recovery testing. A backup is useful only when a restore has been attempted and the resulting packages can still be parsed and deployed.

Privacy and security controls should shape targeting and logging as well as application behaviour. Australian Privacy Principle 8 requires reasonable security and control measures for covered personal information, while the Notifiable Data Breaches scheme may apply to eligible incidents involving compromised data. The ASD Essential Eight is guidance rather than legislation, but many Australian organisations use it as a baseline for identity, patching, backups and privileged access. AppSense changes should fit those wider controls and be included in security reviews.

These controls create a practical operating standard:

Choose one business-critical application and map every important setting to its owner, scope and target condition before changing delivery. Use the AppSense Exchange forums to compare that design with similar deployments, publish tested scripts and record what changed in your own environment. A small, visible pilot will produce better decisions than a large rollout based on untested assumptions, and the resulting standard can then be applied consistently to the next application.