CitraTest APM location-based monitoring for Citrix, Microsoft RDS, AVD, and every Windows application - run one on-the-glass business transaction from headquarters and from each remote office, compare the same timed step by location, and alert on the office that falls behind.
Direct answer: A monitor that runs next to the datacenter tells you how the application feels next to the datacenter. Users in remote offices reach the same Citrix, RDS, or AVD front door over a different path, and the published app can feel very different on their screens. CitraTest APM® lets you build monitoring scenarios based on physical locations - headquarters, a city office, remote offices - so the same synthetic business transaction runs from each one. WaitForImage confirms each screen, StartTimer/StopTimer time it, and the results line up by location so you can identify response-time geo-discrepancies and get alerted at the first sign of trouble. No CitraTest APM elements are installed on any server.
The ticket usually reads the same way: "The app is slow here." Headquarters says it is fine. The broker is green, the hosts have headroom, and the monitor in the server room passed its last run. Everyone is telling the truth - from where they sit. The question nobody can answer from a central dashboard is what the same transaction looks like from that office, right now.
That is the branch problem: one green check from one location is not a user SLA for every location.
By Jay Labadini, Tevron
Why one monitoring location is not enough
Citrix and RDS stack many layers - broker, gateway, profile, image, application, and network. A remote office adds its own piece of that path between the user and the session. When the monitor shares a building with the farm, it measures everything except the part branch users feel first. The session host renders the same pixels for everyone; what differs is how quickly those pixels become a usable screen on the glass at each location.
Control-plane and host telemetry stay essential. They answer whether the platform is healthy. They do not answer whether the order screen appeared in time for the people in a particular office. Related: Director Watches Brokers. APM Watches the Screen.
One scenario, run from every location
The CitraTest APM product page describes three ways to build custom monitoring scenarios: by physical location (Headquarters, NYC, remote offices), by functionality (SAP, Salesforce, a website), or by a series of steps. The branch method combines them: one series of steps, one definition of success, run from each location you care about.
| Keep identical across locations | Why it matters |
| The transaction | The same script - log on, launch the published app or desktop, open a record, save - so a difference points at the location, not the test. |
| Moments of truth | The same StartTimer/StopTimer pairs, each closed by WaitForImage on the screen the user is waiting for. |
| Display contract | The same resolution, color depth, theme, and font smoothing on each monitoring client, so baseline images match everywhere and an image miss means a real delay or failure. |
| SLA thresholds | Measured the same way at every location - in absolute values, percentages, or statistical deviations, as the product supports. |
Each monitor drives the real client path the way a user in that office would: real mouse and keyboard, visual checks of the desktop, timings taken along the way. Synthetics run from outside production, and no application code is modified.
One measurement contract: see, wait, act, measure
- Scripts encode the business transaction on a Windows desktop.
- Playback sees the UI with bitmap images (and OCR when text is dynamic).
- Playback acts with real mouse and keyboard.
- WaitForImage synchronizes and verifies expected screen state before the next step.
- StartTimer / StopTimer capture on-screen response: StartTimer immediately after the initiating action; StopTimer immediately after WaitForImage confirms completion.
Prefer small, unique, static bitmaps for sync cues. Reserve OCR for values that are unknown ahead of time; OCR is not a wait/sync.

Illustrative method diagram - not customer results. The same pipeline scores the transaction at headquarters and at each office.
Read the results by location, then by step
Line the timers up per step and per location. The pattern points to where to look next:
- Every location slows on the same step - the shared parts of the path are the first suspects: the session host, profile, image, or the application behind the published app.
- One location slows and the others hold - look at what is unique to that office's path before touching the farm.
- One location fails a step outright - the failure screenshot shows exactly what that office's screen displayed instead of the expected state.
- Logon is fine but a business screen lags at one office - time the heavy screens, not only logon, so the transaction users complain about is the one you watch.
That is what "identify response time geo-discrepancies" and "rapidly isolate slow components and root cause" look like in practice: the same timed step, compared across locations, with screenshots taken when problems are detected.

Illustrative method diagram - not customer results. Location bars are example scenario shapes, not Tevron benchmarks.
Alert on the office, not just the platform
An alert that says "the app is slow" starts a hunt. An alert that says "the order screen missed its threshold from one remote office, here is the screenshot" starts a fix. Set thresholds per location scenario, route alerts through the enterprise management frameworks you already own - CitraTest APM integrates with them - and hand the operations team on-glass proof for the location that breached. For the scenario and SLA lifecycle itself, see Publish → Scenario → SLA.
One CitraTest APM license covers Citrix, Microsoft RDS, AVD, Epic, Cerner, SAP, Salesforce, Java, .NET, and every Windows application, so the same location scenarios can watch a published Citrix app and a locally installed thick client side by side.
How this sits next to related posts (brief)
Closing: one transaction, many screens
Same Transaction, Every Office is not a new product mode. It is CitraTest APM pointed at the gap between headquarters and everyone else: build scenarios by physical location, run the same business transaction from each one, confirm every screen with WaitForImage, time it with StartTimer/StopTimer, compare by location and by step, and alert on the office that falls behind - with a screenshot of what its users saw. A green check from the server room is still useful. It is not the experience in every office.
FAQ
What is location-based monitoring in CitraTest APM?
It is building CitraTest APM monitoring scenarios by physical location - headquarters, a city office, remote offices - so the same synthetic business transaction runs from each one and its on-screen response times can be compared and alerted on per location.
Why isn't a monitor in the datacenter enough for remote offices?
It measures the application from next to the farm. Remote-office users reach the same front door over a different path, so a published app can pass at headquarters and still be slow or failing on a branch screen. Running the same transaction from each location shows the difference.
How does CitraTest APM help find which office has the problem?
The same timed steps are compared across locations. If every location slows on the same step, look at the shared path; if one location slows alone, look at what is unique to it. Screenshots are taken when problems are detected to help analyze root cause.
Does location-based monitoring require agents on Citrix or RDS servers?
No. No elements of CitraTest APM are installed on any server and no application code is modified. Synthetics run from outside production, like real users connecting with the client.
Can OCR be used as the wait in a location scenario?
No. Confirm readiness with image functions such as WaitForImage first, preferring static bitmaps. Use OCR afterward to read or verify dynamic text. OCR is not a wait/sync.
Contact Tevron
Tevron LLC
402 Amherst Street, Nashua, NH 03060
Phone: 866.788.3650
Email: sales@tevron.com
Web: www.tevron.com
Product: CitraTest APM | What is CitraTest APM? | CitraTest VU
Charts labeled illustrative are method diagrams, not customer benchmarks. Citrix, Citrix Virtual Apps and Desktops, Citrix DaaS, Director, Microsoft, Remote Desktop Services, Azure Virtual Desktop, Epic, Cerner, SAP, Salesforce, Java, .NET, and related marks are trademarks of their respective owners. Tevron is not affiliated with Citrix or Microsoft. Names are used for identification only. CitraTest®, CitraTest VU®, and CitraTest APM® are Tevron products.