Use the multi-user client on multi-user machines such as terminal servers.
Typically, when users run desktop or published applications on multi-user machines such as Citrix XenDesktop or Windows Terminal Server, an internal firewall must allow access from the terminal server to the trusted network for all applications and users. When users with different roles share the same operating system, such as Windows Terminal Server, network-layer segmentation is not possible.

AppGate ZTNA can still capture each individual user's network traffic because each user signs in to their own AppGate ZTNA client within the Citrix XenApp or Windows Terminal Server session.
When the first user signs in, the shared multi-tunnel virtual network adapter starts. It first intercepts all routed traffic for destinations that the user's Sites and entitlements define, including traffic from the system, all applications, and all other users. It then attempts a source network address translation (SNAT) operation on the intercepted traffic, substituting the appropriate user's tunnel IP address. Because the adapter intercepts all routed traffic, it drops any traffic from a source without a matching tunnel IP address. This means the behavior of the multi-user host system may change when the first user signs in: the adapter intercepts all traffic destined for a host behind AppGate ZTNA and may drop it.
Examples of the effect this can have:
Example 1: The first user signs in to AppGate ZTNA on a multi-user host such as a Citrix server and receives an entitlement for the same DNS server IPs assigned to the host operating system. AppGate ZTNA has a higher route priority than the system, so the multi-tunnel virtual network adapter intercepts DNS server requests and drops all traffic except traffic from the signed-in user. The host operating system can no longer resolve DNS queries.
Example 2: A user signs in to AppGate ZTNA on a multi-user host such as a Citrix server and receives an entitlement for
webserverA1at10.10.10.100. Non-AppGate ZTNA users on the same multi-user system lose the ability to send traffic towebserverA1.
The system then routes traffic to that specific user's tunnel, just as in the single-user case. The client establishes these tunnels when the user signs in to their AppGate ZTNA client, one to an available Gateway on each allowed Site.
The client routes each user's application traffic through their specific encrypted tunnel to the Gateway, where the system dynamically applies firewall and application rule sets unique to the user. This makes network-layer segmentation possible even when users with different roles share the same operating system. This helps customers who require PCI DSS certification for certain user roles.
Because operation is essentially the same as the single-user case, you do not need additional configuration beyond installing with the multi-user option. The isMultiUser device claim (true/false) lets you adjust configuration as needed. For example, you can use this claim to remove the user's DNS entitlement, since the multi-user client uses the operating system's DNS settings.
System limitations
The Windows multi-user client has the following limitations:
The multi-user client does not apply identity provider (IdP) DNS settings, including Block Local DNS Requests, on the host device. DNS resolution always uses the device's OS DNS settings. DNS resolution always uses the DNS settings of the device’s operating system.
The client drops system traffic that the adapter captures, such as ICMP (ping) or SMB (file shares), because the traffic is not associated with a specific user's tunnel IP. This is a Windows limitation.
The Route all traffic through tunnel is not recommended for the multi-user client. This effectively prevents the multi-user host operating system from sending traffic to any network destination except AppGate ZTNA appliances, which the system automatically excludes from tunnel traffic.
AppGate ZTNA requires access to a full desktop. Because the application is interactive and users may need to enter a one-time password (OTP) at any time, it does not work correctly if the user has access to only one published application.
Standard executables
The Windows multi-user client uses the following standard executables:
Kernel Filter. Added to tag different users’ traffic. Runs as SYSTEM.
After installation, the client looks and behaves exactly like the normal full client.
Installing the Windows multi-user client
NOTE
You cannot install the filter driver on systems with Secure Boot enabled. If your system uses Secure Boot, disable it, reinstall the client, then re-enable Secure Boot.
Downloading the installer from the command line
To download the installer, follow the steps in Downloading the installer from the command line.
Installing from the command line
To install the client as a service, run the installer with the /M switch. The /S (silent installation) switch is also recommended. Run CMD or PowerShell as an administrator. See Windows clients for a full explanation of all installation switch options.
To install the Windows multi-user client in silent mode, run CMD or PowerShell as an administrator and ensure the installer is in your C:\tmp folder. Then run one of the following commands using the full client profile URL (from Identity > Client Profiles) and replacing x.y.z with the correct version number:
CMD
start "" /WAIT "AppGate-SDP-x.y.z-Installer.exe" /M /S /P="<full profile URL>"PowerShell
Start-Process "Appgate-SDP-x.y.z-Installer.exe" -ArgumentList ' /M /S /P="<full profile URL>" 'Uninstalling the Windows multi-user client
You can uninstall the client in the following ways:
Run the uninstaller from the Start menu shortcut.
Use Add or Remove Programs in Windows.
NOTE
Uninstalling the client removes only the client binaries—client configurations are not removed.