Earlier in the week I posted a blog about Monitoring vs. Diagnostics; where I noted the skills, tools, and ultimately the visibility required to proactively monitor an environment versus re-actively diagnose, are very different. I’m sure those of you who have lived this challenge would agree. For those who have not lived to tell the tale, I’ll share this example from the field.
Please note I am not attempting to call out or embarrass anyone. The nuance and balance between monitoring and diagnostics is lost on all but the most seasoned end user computing professionals. It’s quite common that desktop workload-focused IT teams are ill prepared to solve a diagnostics problem with a monitoring solution. In this case, our example organization was experiencing crippling performance of its most important tier one application: the electronic health record (EHR) solution from Epic Systems.
Not Sized for Growth or Spikes
Our story begins at a large health care organization that recently completed a 20,000-user desktop transformation from physical PCs to virtual desktop infrastructure (VDI). The multi-year project went well; and until recently, everyone was happy. Management was realizing significant operational benefits. User expectations were being met, and the IT team has been proactively monitoring the environment.
Windows 10 migrations for the home market have largely been successful for most users because of a few things:
You must be logged in to post a comment.