Recently Sandro added a new article to the series of articles about monitoring your BizTalk environment by using PowerShell:
This post adds to that series. It will show you how to monitor your BizTalk environment for ‘old’ dehydrated instances by using the provided PowerShell script. Microsoft defines a dehydrated instance as following:
Welcome back to this series of articles about Monitor your BizTalk environment using PowerShell that already have three previous editions wrote by me and Jeroen:
Today we will talk about how you can monitoring Windows Updates and Pending Restarts on the servers by using PowerShell scripts.
As the official documentation specify, in addition to the high availability aspects of the host instance configuration, you should separate sending, receiving, processing, and tracking functionality into multiple hosts. This provides flexibility when configuring the workload in your BizTalk group and is the primary means of distributing processing across a BizTalk group.
This also will allows you to stop one host without affecting other hosts. For example, you may want to stop sending messages to let them queue up in the MessageBox database, while still allowing the inbound receiving of messages to occur.
The last couple of months this blog received large numbers of spam-comments. Unfortunately captcha’s etc. did not do their work. To prevent this large numbers of spam comments we made the decision to only allow bloggers to write comments.
If you ever want to comment on something, have a question or a remark please use the contact us to stay in contact with us: http://www.biztalkadminsblogging.com/index.php/contact-us