We all know the fact that window servers are not configured out-of-the-box to work like charm for BizTalk. When you install a BizTalk environment you need to tell the server that it is not going to act like a normal server. It’s going to be hammered!
So what is ment by that? First of all BizTalk as we know sends, receives and process a lot of data, there are a lot of connection towards different servers, protocols and partners. Some environment have massive loads on their environment and the machine may not work as expected.
Like, turning of the anti-virus. I often explain this to people so they understand “When you download a file on your win 8 machine, when the file is done downloading the anti-virus program scans the file for viruses, the size of the file gives you a slight idea if it’s going to take a while of go fast”. Now, imagine if this would happen to all files going in and out of BizTalk, that would make a massive delay.
There are plenty of other settings to, I did a blog post about a checklist when configuring and installing BizTalk 2010 (a lot of this is the same for BizTalk 2013, so feel free to use it there as well) I talk about some registry settings, you have two options, run in and change them through “regedit.exe” or script them, with PowerShell or with a registry file. Since some clients have limitations on PowerShell and who’s allowed to run it I ended up with a registry file that updates all the values and add the values that are not there. And as always I’d love to share it. If you have some other settings you’d like to add go ahead, I often change this to tailor it more towards the client if I know that they need some specific settings set. You can run this script in a running environment, but be aware that these settings will not take effect until the server has been rebooted.