Easy bug reporting with Connect

Just logged my first bug for the Host Integration Server 2009 beta (in fact the first public bug!) and it was a piece of cake. The Connect website is pretty minimalist for providing bug reports or – more accurately – feedback. Just sign in with a Passport account and start reporting anything broken or unexpected.

0

Host Integration Server 2009 in public beta

[[24th March, 2009 – Updated to reflect NO 64-bit support for the MSMQ-MQseries Bridge]] Beta news  Last weekend (November 22nd) Microsoft posted the beta of Host Integration Server 2009. Microsoft Host Integration Server 2009 offers key enabling technologies that allow enterprise organizations to integrate their mission-critical host applications and data with new solutions developed using…

0

MSMQ 4.0 Management Pack for Operations Manager 2005

Sometimes products just appear out on the wild without any publicity. Prime example is this management pack for MSMQ 4.0 which came out a few months ago. Please download and deploy: Windows Server 2008 Message Queuing Management Pack for Microsoft OpsMgr 2005 And just for reference: MSMQ 3.0 Management Pack MSMQ 2.0 Management Pack  

3

What features will be in the next BizTalk MSMQ Adapter?

At the moment BizTalk Server 2006 (the current release) is not supported on Windows Server 2008 which means it cannot make use of the new features in MSMQ 4.0. The version that will run on the latest server operating system was announced back in September and will be called BizTalk Server 2009 (see the roadmap for…

0

How to replace an MSMQ server without bringing down the AD roof

The scenario is that you have a migration plan to move all your existing Windows 2000 servers in your domain to a newer Windows operating system. Or just moving to new hardware – the problems are the same. If you make use of MSMQ in Active Directory Integration mode then there will be a few…

2

So, what is an Outgoing Queue and what does MSMQ do with it it?

[[I touched on Outgoing Queues last week so thought I would add some more detail. This post has been in my draft folder for a while so may have some duplicate information to last time.]] MSMQ has a dilemma – what to expose of its inner works and what to hide.For example, back in MSMQ…

0

Routing Support in MSMQ requires Enterprise Administrator privileges

One down-side of enabling Routing Support for MSMQ is that you need to be an Enterprise Administrator to install it, as can be seen from this Technet article: Installation permissions   Message Queuing computer Permission level required Message Queuing server on a domain controller domain administrative permissions (or member of the Domain Admins group) Message Queuing…

0

Oil and water – MSMQ transactional messages and load balancing

A really common request is to load-balance MSMQ, either to “scale out” (adding more machines, as opposed to “scale up” by enhancing the existing server) or for high availability. For load-balancing to work, the traffic must be stateless as there is no guarantee that a sending machine will be using the same balancer each time. For…

2

Today’s favourite command line (#2 in a series)

For years without end I’ve been typing NET STOP MSMQ {{twiddle thumbs}} NET START MSMQ without realising there has always been a way to get rid of the wasted time in the middle – you can concatenate the commands! NET STOP MSMQ && NET START MSMQ Every day there is an opportunity to learn something…

2

Make sure to set the clocks for MSMQ

If you are using public queues and addressing them with path names then you need to ensure the system clock on the sending machine is in synch with that on the domain controllers. This is because kerberos authentication will fail if you let enough gap exist between the clocks (45 seconds, in fact). Without that you cannot…

0