AppSense and Remote Desktop Gateway Session Control
AppSense and Remote Desktop Gateway bring together endpoint configuration and controlled access to remote Windows desktops. AppSense can tailor the working environment and application experience on managed devices, while RD Gateway authenticates users and mediates connections to Remote Desktop Services. Session control integration links those responsibilities so remote access can follow organisational rules without duplicating local administration.
The approach is particularly useful for Australian organisations with staff working across offices, home locations and client sites. A support analyst in Brisbane may connect to the same managed desktop from an NBN connection that a colleague uses in a Sydney office. Session-aware AppSense behaviour, combined with gateway access policy, helps preserve configuration, licensing and security boundaries while giving remote users a consistent experience.
A reliable design treats the products as complementary rather than interchangeable. RD Gateway remains the access-control layer, and AppSense manages endpoint and user-workspace outcomes. Identity, deployment, session detection, exclusions and audit evidence should be planned together, then tested with the devices, users and network paths that will operate after go-live.
Establish the control boundary
Draw a clear boundary around each platform before changing production policy. RD Gateway should authenticate the connection, apply conditional access policy and control which resources a user may reach. AppSense should deliver the required desktop configuration and enforce session-specific application behaviour. It should not be relied upon to replace gateway authentication, network restrictions or Remote Desktop Services licensing controls.
A useful design separates four decisions: who may connect, which destination they may reach, what their endpoint can launch and which configuration follows them into the session. Conditional Access Policy, Active Directory groups and RD Gateway resource permissions answer the first two questions. AppSense policies, application delivery rules and user-workspace settings answer the remaining questions.
Account for the different roles of client devices and session hosts. A managed laptop may run the full AppSense client, while an RDS session host might need selected components for server-side Office, profile preparation or application integration. The gateway itself is an access service rather than the workstation being configured. Installing AppSense across every server role without a defined requirement can introduce unsupported combinations and unnecessary troubleshooting.
Deploy AppSense through MECM
Microsoft Endpoint Configuration Manager provides a repeatable path for installing the AppSense client, prerequisites and policy packages. The AppSense Exchange’s MECM deployment guide covers the deployment workflow and is a useful starting point for building a controlled pilot rather than relying on manual installation.
Create a dedicated deployment sequence with prerequisite checks, pilot membership, application deployment, reboot handling and success detection. Begin with a small collection representing corporate laptops, home devices and supported RDS clients. Expand in waves while comparing endpoint compliance, agent heartbeats and session-start success against the baseline. This also makes it easier to identify whether a problem comes from installation, policy processing or the remote connection itself.
Confirm where each AppSense component must run before packaging it. Client-side Outlook and Excel configuration has different requirements from settings applied inside an RDS session. The session host may need AppSense components even when the connecting device is managed, particularly where the design depends on Office add-ins, application settings or redirected user data. Validate supported operating systems and product versions, and document any components that should remain outside MECM deployment.
Allow time for AppSense to complete its first policy synchronisation before testing behaviour. A successful installation does not guarantee that settings have reached the user, especially after a long period offline or during a bandwidth-constrained connection. Check application deployment and policy status in MECM, then confirm the actual user experience in both local and gateway-backed sessions.
Connect identity to session policy
Use Active Directory as the common identity reference for gateway authorisation and AppSense policy targeting. Dedicated security groups can represent remote users, privileged administrators and staff requiring a distinct configuration. This keeps access decisions understandable and gives support teams a visible control point when a user changes role or leaves the organisation.
Create separate policies for local and remote sessions where the outcome genuinely differs. A remote user might receive a stricter application set, additional printing controls or a lighter configuration designed for intermittent connectivity. The same Active Directory group can feed the RD Gateway conditional access rules and AppSense criteria, but each platform must evaluate the policy independently. Allow for directory replication and AppSense policy refresh intervals so a new group membership does not produce different decisions at the gateway and endpoint.
Confirm how session state is detected in the deployed AppSense release. Session-control conditions vary by product version and licence, so the integration should rely on validated Windows session information rather than assumptions about the presence of an RD Gateway server name. The endpoint can identify an RDP session; that signal does not automatically prove that the connection passed through the approved gateway. Gateway logs and security telemetry must establish the access path.
Test the combined rule under realistic conditions. Compare a local sign-in, a direct RDP connection from an approved test network and a connection through RD Gateway. Direct external RDP should fail where the design requires gateway mediation. A gateway session should then produce the expected AppSense configuration without altering unrelated local settings. Record mismatches by policy name, session type and device profile so the cause can be isolated without weakening the overall rule set.
Protect gateway and registry settings
Exclusions are a normal part of AppSense administration, but broad exclusions can silently remove configuration that users and auditors expect to remain active. Review the AppSense Exchange’s exclusion list practices before changing package behaviour, and apply exclusions at the narrowest reliable scope.
Separate gateway, session-host and client exclusions. A process exclusion required on an RDS session host may be unnecessary on a managed laptop, while registry paths used by Remote Desktop components may need different treatment on the server and client. Maintain a reason, owner, affected package and removal condition for each exclusion. This prevents temporary pilot decisions from becoming undocumented permanent configuration.
Treat registry redirection as a deliberate data-flow design. It can move suitable per-user settings into an AppSense-managed workspace, but it should not capture server certificate stores, credential material, volatile connection state or security controls belonging to the local machine. Remote Desktop maintains session-specific registry data, so redirected paths must be tested across reconnects and across different gateway clients. A setting that appears correctly in a fresh session may still fail when the same user reconnects later.
Validate the exclusions against actual work. Test Outlook profiles, Excel add-ins, file associations, printer deployment, application licensing and any line-of-business tools managed through AppSense. Repeat those tests on both local and remote sessions, because a package can appear healthy while a narrow exclusion blocks only one application inside RDS. Store the test evidence with the deployment record so future upgrades can be compared against a known-good baseline.
Test, monitor and support the service
Pilot the design across representative Australian conditions rather than testing only from a corporate network. Include users in Sydney, Melbourne, Brisbane and Perth, remote workers on NBN services, and occasional staff connecting through mobile tethering. Check latency, packet loss, UDP behaviour and TCP fallback, as well as MFA prompts and gateway authentication. This exposes performance problems that may be hidden by a fast office connection.
Monitor the full session journey. RD Gateway and Remote Desktop Services events show whether access was authorised and the session was established; AppSense logs show whether policy arrived and configuration was applied; MECM reports show client health. Signalies provides product briefings that can help operators track changes in supported configurations and community experience. Correlate the sources through a service desk or incident identifier so gateway failures and endpoint failures are not treated as the same problem.
Run the service through normal operational changes. Maintain an owner for identity groups, gateway policy, AppSense packages, exclusions and certificate renewal. Review access rights when staff move between offices, begin annual leave or change roles. Australian teams often hand work over during the arvo, and daylight-saving transitions can complicate schedules for support staff in different states. Record escalation times in Australian Eastern Standard Time while displaying each participant’s local time to reduce confusion.
Audit the controls in line with the organisation’s risk obligations. The Australian Privacy Principles and the ASD Essential Eight provide useful context for access governance, logging and administrative accountability, although each organisation must determine its own requirements. Measure session establishment success, authentication failures, AppSense policy failures, unsupported exclusions and help-desk volume. A reduction in configuration incidents is often more valuable than a small change in raw gateway login count.
Start with one low-risk RDS workload, one managed client collection and one clearly defined remote-user group. Document the gateway permissions, AppSense conditions, deployment sequence, exclusions and rollback steps before broadening the rollout, then validate each layer in a real session.
Use the linked guidance to build the deployment package, and record the pilot results in the AppSense Exchange community. Publishing the tested configuration, known constraints and evidence from Australian network conditions will give other operators a dependable reference while turning the pilot into a repeatable service.