Microsoft RDS Virtualized Applications and Desktops: Goliath Ensures Availability Before End Users Experience Issues

The Goliath Availability Monitor for Microsoft RDS (Remote Desktop Services, formerly Terminal Services) can confirm that any Microsoft RDS delivered virtualized applications or desktops will launch when an end user attempts to logon.

Not to be confused with a “logon script” or “logon simulation” tool, the Goliath System user exercises the Microsoft Remote Desktop Web Access and Remote Desktop Connection Broker from the endpoint, just as your end users do.

This means: if there is an issue, we’ll spot it, and IT can hear about it before the end user. This gives them time to troubleshoot and prevent delivery issues going forward using in-depth metrics captured by our integrated Goliath Performance Monitor.

Slideshow: A Walkthrough of the Microsoft RDS Application Availability Monitor.

 

How the Microsoft RDS Application Availability Monitor Works

Our Application Availability Monitor for Microsoft can alert and help you pinpoint root cause of Microsoft RDS application and desktop delivery failure (or, in some cases, logon slowness overall).

We can accomplish this no matter the location of the Microsoft RDS servers, the applications themselves, or the users (as explained in our functionality walkthrough). We can do the same with desktops, making it a ubiquitous application launch performance monitoring tool that’s completely unique in the RDS performance monitoring space.

We provide visibility into all applications and desktops being launched, with reports and drilldown analytics detailing root cause if users do run into issues. This makes Microsoft RDS troubleshooting for login issues a lot easier. Moreover, we detect this before users realize there’s an issue. In each case, we provide visual proof of the success or failure of each stage of the logon process.

With our built-in alerting, IT administrators get real-time alerts via our Microsoft RDS via our logon performance monitoring software the moment a problem occurs, triggered by the Goliath system user’s scheduled attempt. This can – and has – given our customers a sufficient amount of time to get ahead of users, accompanied by the right, correlated metrics to diagnose root cause and practice towards future prevention.

If a failure does occur with Microsoft RDS application or desktop delivery, our ability to monitor, report, and alert in detail on the following common issue root cause areas provides a complete look at your virtual infrastructure for troubleshooting Microsoft RDS:

  • Connectivity (i.e. network speeds, latency)
  • Application/desktop availability
  • Configuration or availability problems with the delivery infrastructure, including: the remote desktop gateway, web access interface, the connection broker, active directory, licensing servers, SQL databases, and much more
  • Licensing issues
  • Client-side errors (i.e. a message box error presented at the endpoint level — these are easily captured by our screenshotting tool)

 

 

Features

Benefits

Better than real-time advanced warning of Microsoft RDS login issues re: failures or slowness By having the Goliath system user attempt Microsoft RDS logons – modeled after one of your actual users in terms of site/profile – we provide actual data on what will happen when your Microsoft RDS end user tries to access his/her Microsoft RDS application or desktop. Microsoft RDS logon issues reduce as you gain time and detailed metrics to proactively troubleshoot and practice towards future prevention.
Live dashboards showing end user experience session logon metrics You gain the ability to monitor Microsoft RDS end user logon experience in real time with the Application Availability Monitor. Giving you immediate access to the right information allows you to mitigate logon issues quickly to eliminate end user pain.
Broad and deep integration & metrics capturing for issue root cause analysis With application monitoring and real-time reporting of all layers of the Microsoft RDS delivery infrastructure in one location, you can see – at a high level – what’s going on across all your Microsoft RDS environments with visibility into the end user session level if needed
Historical reports of Microsoft RDS logon success and/or failure We provide the historical data and insights required to perform trend analysis, metric correlation, and site/user-specific drilldowns over any time you choose. These can provide empirical evidence for demonstrating Microsoft RDS application or desktop launch problem resolution and/or user logon experience enhancements. We also do not impose retention limits.

 

Microsoft RDS Application Availability Monitor: Functionality Walkthrough

Screenshot Analysis

With each phase of the Microsoft RDS logon process the Application Availability Monitor attempts, a screenshot is taken to provide visual evidence and objective proof of logon success or logon failure. This is allows you to see the potential impact that typically elusive items like disclaimers, secondary authentication, and multiple launch sequences may have on the results of the Microsoft RDS logon process.

This allows Microsoft RDS administrators or the IT help desk to quickly gain context to go along with full text logon sequencing results. As such, it’s much easier for IT to understand the intricacies of a particular logon issue without needing to: a) attempt to reproduce the problem manually, or b) wait for it to happen again (effectively, forcing your team to act as manual application performance monitors).

Scheduling and Automation

The Application Availability Monitor can be scheduled to run automatically and continuously, based on your preference, measuring the Microsoft RDS logon success or failure across different locations and/or different types of users as needed. For example, it can run throughout the day so your Microsoft RDS team can know immediately if/where there is a problem and at which stage of the process the problem occurs.

Microsoft RDS application/desktop launches can be scheduled to execute, for example, every 10-15 minutes so that IT can be alerted to problems before Microsoft RDS end users feel the impact of an application/desktop load failure. Many of our customers strategically have the Application Availability Monitor attempt logons overnight to get ahead of Microsoft RDS logon and application launch issues, with alerts reaching IT before end users reach their facilities in the morning.

Alerting

Alert notifications of Microsoft RDS logon failure or logon slowness can be sent immediately if a scheduled logon attempt fails at any time. These can be sent via email, SNMP, SYSLOG, or directly to your ticketing or enterprise monitoring solution.

Deployment

Our Application Availability Monitor can be deployed however it’s needed. You can deploy it on-premises or in the cloud to identify individual, site, or geographic application availability issues.

Because the Microsoft RDS logon attempts can be scheduled and remotely deployed, it can be strategically positioned at the location Microsoft RDS users sign in from to provide objective evidence regarding logon success, logon failure, or logon slowness from the user’s unique access location.

This way, you can diagnose whether Microsoft RDS login issues are location-specific or global in nature, providing the help desk with relevant data regarding availability and application performance if users need support.

Remediation

We integrated a remediation engine directly into the Goliath Application Availability Monitor. The remediation engine is customizable; however, it comes with a large number of prebuilt rules aimed towards quick, automated resolution and prevention of further issues or complications.

For example, a Microsoft RDS server could be set into maintenance mode to prevent any further failed logon attempts. Or, a Microsoft RDS server could be checked to validate if it should be unavailable to mitigate false positives.

Ease of use

Unlike other technologies, the Goliath Application Availability Monitor has built-in logon scheduling functionality. We provide an easy to use, templated approach to configuring launch sequences. This gets you scheduled in minutes – not hours – without the need for custom scripting or recording sequences.

Integration with Goliath Performance Monitoring

The Goliath Application Availability Monitor is fully integrated into the Goliath Performance Monitor. As a result of the inclusion of our RDS monitoring on the performance end, IT not only can identify application availability issues but also the root cause of the issue. Other technologies called “logon simulators” may be able to simply ‘identify’ a logon failure, but without full integration into an enterprise monitoring product, there is no way of identifying why the failure or slowness occurred. Therefore, these products can’t help you proactively troubleshoot an issue or prevent it in the future.

Comprehensive Exercising of the RDS Delivery Sequence

Since our Goliath system user attempts the logon process exactly as one of your end users would, our product truly exercises the entire application and/or desktop delivery infrastructure. To achieve high quality end user experiences, multiple elements of this infrastructure must successfully work in concert.

One of the core problems of other applications is that they are monitored disparately. If they are gauged separately, they may look fine. It is only when executing the fully integrated launch process by multiple users – including remote access, Microsoft RDS application/desktop availability, and the Microsoft RDS delivery workflow – that you not only trigger issues but see contextual, objective evidence of where the root cause of your Microsoft RDS login issues is sourced.

Want to see a personalized demo or access a 30-day free trial of the Goliath Application Availability Monitor? Contact us today!

techinfo@goliathtechnologies.com

(855) 465-4284

  • INFORMATION
  • Press Releases
  • Privacy Policy
  • Reports
  • Dashboards
  • Sitemap
  • FOLLOW GOLIATH
Goliath on LinkedIn Goliath on facebook Goliath on Twitter