After my blog post about the server diagnostics lifecycle, PerfMon and PAL, many of you asked me how the report automation could be set up. In this post, I’ll therefore outline a couple of ideas and provide you with some guidelines on how automation of PerfMon and PAL could be configured and scheduled in practice. In this post, you will find information on how to configure PerfMon and how to execute PAL from PowerShell to create fully automated diagnostics reports on a regular basis.
Microsoft official software requirements for BizTalk server 2013 (R2) support no other versions but .NET Framework 4.5.x. On a couple of our environments, we noticed that the .NET 4.6.1 update has been pushed automatically because of the Windows updates mechanism. This could cause different issues in our production environment in all kinds of software packages that have never been tested with this version. Due to its sensitive nature, no answer from Microsoft could be found online on how to rollback from .NET 4.6 to 4.5.2.
Many IT divisions and administrators of companies struggle answering questions such as: Is your current infrastructure still capable to handle the load from years ago and deliver the same performance? What is the maximum amount of capacity your severs can handle? Where do you feel bottlenecks or pain points today in system’s or application’s performance? What is the long-term growth and usage of your applications servers? If you cannot answer half of the questions based on data provided by a monitoring system, it would be a good idea to consider and set up fine-tuned diagnostics tools for your system administrators. This will improve your capacity planning and help you identify bottlenecks, including disk latencies, IIS web call performance, and SQL deadlocks.