Tracking down MSMQ registry documentation

MSMQ is a protocol that can benefit from the odd tweak to the registry. Unfortunately it is not always obvious what you can change to improve performance so I've tried to pull together the various sources of documentation.

The first place to look is the Resource Kit Registry Reference which is pretty comprehensive.

The Windows 2003 version is here but is dated "March 28, 2003" so doesn't include any new registry values introduced through hotfixes. Also, not every registry value is included for whatever reason but here's a start to the list. I'll update it as I come across published references. I'll also see if I can get some unpublished information included (although those registry values can be unpublished for a good reason).

• AlwaysWithoutDS (from KB article 839929)

• BindInterfaceIP (from KB article 895867)

• CleanupInterval (from KB article 251294 and Windows 2000 registry reference)

• CloseSessionOnNonLocal  (from KB article 833512)

• DenyOldRemoteRead (MSMQ FAQ)

• DepClientContextCleanup (from KB article 304395)

• DepClientCleanupInterval (from KB article 304395)

• DomainBinding (from KB article 842513)

• DSListRefreshErrorRetryInterval (only found in MS-Internal documentation)

• DSNextEnterpriseListRefreshTime (from KB article 303421)

• DSNextSiteListRefreshTime (from KB article 303421)

• EnableLocalUser (from KB article 840146)

• EnablePingService (MSMQ 4.0, from article Security Enhancements that Affect the Default Behavior of Message Queuing) 

• FastDisconnect (only found in MS-Internal documentation; waiting on KB article 928380)

• ForceNameResolutionDirect (from KB article 833512)

• HttpPipeLine (from Technet article HTTP/HTTPS messages)

• HttpsPipeLine (from Technet article HTTP/HTTPS messages)

• HttpResponseTimeout (from KB article 883474)

• IgnoreOSNameValidation  (from KB article 899611)

• IgnoreSiteLinks (from KB article 817076)

• InSeqCleanupInterval (mentioned in text for InSeqCheckInterval registry value)

• Keepcurrentdomain (from KB article 815643)

• (only found in MS-Internal documentation)

• MachineDeadletterQuota (MSMQ 4.0, from article Security Enhancements that Affect the Default Behavior of Message Queuing)

• MaxAdminCommandsPerSecond (MSMQ 4.0, from article Security Enhancements that Affect the Default Behavior of Message Queuing)

• MaxInSessions (from KB article 870985)

• MaxRRThreads (from KB article 901279)

• MaxWaitResourceDown (from KB article 824375)

• MaxWaitTimeToService (from KB article 842511)

• MulticastBindIP (from Technet article IP multicasting)

• MulticastRateKBitsPerSec (MSMQ FAQ)

• MulticastReceiversCleanupTimeout (from KB article 936267)

• NetNameForPerfCounters(from KB article 884975)

• NewRemoteReadServerAllowNoneSecurityClient (from article Message Queuing security overview)

• NewRemoteReadServerDenyWorkgroupClient (from article Message Queuing security overview)

• PermitAnonEveryoneSend (MSMQ 4.0, from article Security Enhancements that Affect the Default Behavior of Message Queuing)

• PermitInsecureNacks (MSMQ 4.0, from article Security Enhancements that Affect the Default Behavior of Message Queuing)

• PurgeInconsistentQueues (from KB article 827493)

• RestrictAdminAPI (only found in MS-Internal documentation)

• RoundTripDelay (from KB article 303293)

• SendEnhRC2With40 (MSMQ FAQ)

• SendWindowInBytes (only found in MS-Internal documentation)

• SkipRevocationCheck (from KB article 889859)

• StaticAddrRes (from KB article 311827)

• StatusGenFrequency (Triggers) (from KB article 330090)

• TryConnectInterval (from KB article 899470)

• UseServerAuthWithParentDS (only found in MS-Internal documentation)

• WaitMaxInSessions (from KB article 870985)

• WaitTime (from KB article 909401)

• Workgroup (only found in MS-Internal documentation)

 Stay tuned.

Comments

• Anonymous
  February 14, 2007
  Thanks for sharing this. I always felt that MSMQ is so underutilized technology especially in an enterprise scenario. People are willing to spend a lot of money on MQ Series when a lot of the problems can be solved by MSMQ (as long as you are on Windows n/w) which is available with Win2K3 for free!

• Anonymous
  February 15, 2007
  The comment has been removed