MSMQ 4.0 – what’s new in Computer Management?

I'm now the proud owner of a working Windows Server 2008 installation (I know, I know, I should have got into the beta but I've been busy..) so I thought I'd have a quick look at what's different in Computer Management. You'll be happy to know that little has been changed within MSMQ management except that there are now two places to do the same tasks (Computer Management and Server Manager).

MSMQ is now a "feature" of the operating system so is found under Features in Server Manager:

I can only suggest that you don't install all 35 features as otherwise finding Message Queuing amongst them may get to be a chore.

Only other change of note is on the "Server Security" tab of Message Queuing Propertries:

where there's an extra option for "Disable un-authenticated RPC calls". This option already exists in MSMQ 4.0 on Windows Vista.

The help explains:

"Specifies whether unauthenticated RPC calls are enabled. Unauthenticated RPC calls can be enabled to support workgroup clients."

Fiddling with this setting changes the AllowNonauthenticatedRPC registry value, a DWORD under HKEY_LOCAL_MACHINESOFTWAREMicrosoftMSMQParametersSecurity

I love undocumented registry values...

Comments (3)

  1. Kris says:

    I love undocumented registry values but I wish they are all documented somewhere not easily accessible 😉

  2. I have a client environment where messages stay in the outgoing queue on the source machine until I toggle this setting on the destination machine and restart msmq.  Any ideas what could be causing this?  I can see the setting stays in the unchecked state but for some reason the OS isn't respecting it.  I have to toggle it on, restart msmq, toggle it off, restart msmq and the messages go through.  Very strange and I can't figure out why.  Any ideas are very much appreciated.

  3. To be more clear this works fine for a while (i.e. a few days) and then I have to go through and toggle the setting again.  Then things start to work for a while again.  The setting is unchecked when I inspect it but it seems the OS isn't respecting the value after a few days.  I'm suspecting a domain group policy but don't know where to look.

Skip to main content