Deployment on RDS/Citrix Environment

Kabeen agent deployment guide for RDS and Citrix virtualization environments

The Kabeen agent is compatible with application virtualization environments such as Microsoft Remote Desktop Services (RDS) and Citrix Virtual Apps.

Prerequisites

  • Administrator access to RDS/Citrix servers
  • Server base image (Gold Image)
  • Kabeen API key

Virtualized Environment Specifics

In RDS and Citrix environments, multiple users share the same server. The Kabeen agent adapts to this architecture by:

  • Running in each user session context
  • Isolating each user's data
  • Optimizing shared resource consumption

Installation on Gold Image

Step 1: Prepare the Server

  1. Put the server in maintenance mode
  2. Disable user connections
  3. Open an administrator session

Step 2: Install the Agent

  1. Download the MSI package from the Kabeen platform
  2. Run the silent installation:
msiexec /i kabeen-agent.msi /qn APIKEY="YOUR_API_KEY"
  1. Verify that the Kabeen service is installed and configured

Step 3: Configure for Multi-session

The agent automatically detects the multi-session environment. No additional configuration is required.

Step 4: Finalize the Image

  1. Run image preparation tools (Sysprep, etc.)
  2. Create an image snapshot
  3. Publish the image to your infrastructure

Team Configuration

For environments with user pools from different teams:

  1. Configure the team UUID via GPO or login script
  2. The parameter will be applied at user session startup
reg add "HKCU\SOFTWARE\Kabeen" /v TeamUUID /t REG_SZ /d "TEAM_UUID" /f

Performance Considerations

  • CPU: Minimal impact (~1% per session)
  • RAM: ~50 MB per user session
  • Network: Data sent every 5 minutes (a few KB)

Troubleshooting

Agent doesn't start in session

Verify that:

  • The Kabeen service is configured to start automatically
  • Registry permissions allow user access
  • No group policy blocks execution

Data not reported

Verify that:

  • HTTPS connection to api.kabeen.io is allowed
  • The API key is valid
  • The firewall doesn't block port 443