Most of the authors at BizTalkAdminsBlogging.com also contribute at TechNet. Besides editing existing Wiki articles and helping users at the TechNet Forums, they also write new Wiki articles and add new scripts to the TechNet Galleries. This article provides a small overview of the contributions made by our authors.

"More" Can Be Dangerous - There is a Better Alternative

When you pipe output to more.com, the output is displayed page by page.

You will not get any results for a long time, and your CPU load increases.

Windows Server 2008 R2 comes with the GroupPolicy PowerShell module.

You might have to install that feature first before you can use it – run these lines with full Administrator privileges:

Import-Module ServerManager

Add-WindowsFeature GPMC

Once installed, the GroupPolicy module provides you with a lot of new cmdlets to manage group policy objects.

When launching a PowerShell script from outside PowerShell, it is a good idea to return an Exit Code to the caller so the caller will know if the script ran successfully.

You can send back an Exit Code by using the statement:

     exit XX 

XX would be a numeric value

The folowing is an example:

    param($code=99)

    exit $code

One of my clients asked for an easier way to stop and start BizTalk applications. I created a PowerShell script with a Windows forms GUI. You can use it to stop or start all host instances and or IIS on a server in a BizTalk group.

Depending on whether your BizTalk environment is multiple-server or stand-alone environment, you can use domain users or local users. If you have a multiple-server configuration, then you must use domain groups and domain accounts. BizTalk Server supports local groups and user accounts only in single-server (standalone) configuration. In this example I will talk about a multiple computer configuration. For more information about which groups are necessary in BizTalk and how to create them, follow this link: http://msdn.microsoft.com/en-us/library/aa577661.aspx

When it comes to performance analysis you can get overloaded with performance data. Manually analyzing it takes a lot of time. Analyzing it can be difficult. Most admins know that an average cpu load of over 80% is seen as problematic. But at which value does Memory Pages/sec or Process Private Bytes starts to be problematic?