Automated Citrix Machine Registration Checks
Every hour, WebRun opens Citrix Cloud, reads the registration state of the machines in each catalog and delivery group, works out how much of each pool can actually take a session, sends an immediate Telegram alert when machines drop out, and posts the full breakdown to Microsoft Teams.
How do I catch Citrix machines that failed to register?
WebRun opens Citrix Cloud every hour and reads the registration state of the machines in each catalog and delivery group. When machines fail to register it sends an immediate Telegram alert with the share of the pool left and posts the full breakdown to Microsoft Teams, before the help desk starts taking calls.
- Unregistered machines are found before users hit them
- The available share of every pool is checked every hour
- Healthy hours stay quiet, so an alert always means action
Built for Citrix administrators · IT operations · VDI teams · infrastructure engineers
What does WebRun do on every run?
The exact actions WebRun takes, in order - in plain language, so you can adjust anything.
-
WebRun signs in and gets to work
Opens
citrix.cloud.comin a real browser with your saved login - no setup, no API keys. -
1
Citrix Cloud - read machine registration state
WebRun opens Citrix Cloud to read machine registration state. - Open Citrix Cloud and go to your machine catalogs and delivery groups
- Read the registration state of every machine in each catalog
- Count registered, unregistered, and unavailable machines per delivery group
- Note current session load against the machines that can still take a session
Done when Every delivery group has a registered count, an unregistered count, and its current load.
-
2
Telegram - alert on a shrinking pool
WebRun opens Telegram to alert on a shrinking pool. - Send an immediate internal alert when a delivery group has machines that failed to register
- Lead with the delivery group, the number of machines down, and the share of the pool left
- Escalate the message when the available pool falls below your threshold
- Stay silent on hours when every machine is registered
Done when An alert is out for every delivery group with unregistered machines, or all pools are healthy.
-
3
Microsoft Teams - post the full breakdown
WebRun opens Microsoft Teams to post the full breakdown. - Post the per-group breakdown to your infrastructure channel
- Name each unregistered machine and its catalog so someone can go straight to it
- Show how the counts changed since the previous hour
- Keep the message internal, never notify end users
Done when The infrastructure channel has this hour's registration breakdown.
How is each run configured?
Secure by default
Connect once, stays signed in
WebRun signs in once and keeps each session in a persistent environment, so every run picks up right where it left off.
Every action is checked against this policy before it runs.
Questions, answered
Will it restart or change any machines?
No. WebRun only reads registration state and session counts. It never restarts a machine, puts one into maintenance mode, or changes a delivery group, so nothing in your environment is altered.
Does it alert every hour?
Only when machines have failed to register or a pool has shrunk past your threshold. Healthy hours pass silently, so a Telegram message always means something needs attention.
Are end users told about the problem?
No. Both the Telegram alert and the Teams breakdown are internal to your infrastructure team. WebRun never messages users or posts anything a user would see.
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.