A clue -
This involves preparing the system for Ghosting. We sell alerting systems with a Dell desktop as the Admin station in the system. Takes a long time to set one up out of the box so I recently looked into how to create a base system, then run Microsoft's sysprep utility which strips out all the ID stuff from it, then do a Ghost image of this base state, and then create Admin stations from the Ghost image and fill in the customer-specific stuff each time. Very valuable, from my point of view as the guy who has been tasked with the setup chore.
Well, this is the first time I've tried it and it's been a learning curve.
Anyway, it seemed to work, except for this problem - Message Queuing won't start on the new-born system loaded from the image. I think that sysprep stripped out something needed. I did find that not only certain ID things had to be created anew, but there's a 3rd NIC card that we install, and I had done that and configured it - well, Windows immediately told me it found new hardware.
The other 2 NICs, that I had configured as I always do, with specific IP's for the little private LAN that our system runs in, well those also had been stripped of their IP's.
So since networking seems to get stripped, maybe the Reliable Multicast Protocol Driver thing was stripped, too.
If the driver, RMCast.sys is there in System32\DRIVERS where it's supposed to be, is there some way to "reinstall" it or reconnect it to Message Queuing or whatever is involved? I tried uninstalling MessageQueuing from Windows Components and reinstalling it but that did not work.