Hi John,
When running MQ in MIQM mode on Windows, your machines would normally not be domain controllers, but just normal members of the domain.
There should be a domain group (called 'domain mqm') although you can give it a different name. Things are simpler to set up if you call the group 'domain mqm' though. This is documented in
https://www.ibm.com/docs/en/ibm-mq/9.2?topic=mq-creating-setting-up-windows-domain-accountsEach server that runs the MIQM queue manager then has a local mqm group, and 'domain mqm' is a member of the local 'mqm' group. The service account which runs the queue manager should be a domain account which is a member of the 'domain mqm' group.
Permissions get given to the local mqm group rather than the domain group when objects get created, but these don't really get used. They still need to exist though as far as I know.
These permissions are created automatically by the queue manager, and I would therefore consider them to be 'internals' and not to be trifled with.
Regards,
------------------------------
Neil Casey
Senior Consultant
Syntegrity Solutions
Melbourne, Victoria
IBM Champion (Cloud) 2019-21
------------------------------
Original Message:
Sent: Mon October 11, 2021 05:06 AM
From: John Hawkins
Subject: mqm group being used in Authrec in HA environment
Anyone ?
------------------------------
John Hawkins
Integration Consultant
Original Message:
Sent: Wed October 06, 2021 08:36 AM
From: John Hawkins
Subject: mqm group being used in Authrec in HA environment
Hi Folks,
I've got entries like
AUTHREC... GROUP('mqm@MachineName')...
this is a multi-instance environment so I don't want the specific machine name to be in Auth records at all. Ideally I want to remove the records that refer to the mqm group completely. I'm guessing that these entries are somehow created automagically by MQ but they're not needed are they? Doesn't mqm group have access to all mq objects by default? Therefore, I can just delete all authrecs that mention the mqm group?
thanks,
John.
------------------------------
John Hawkins
Integration Consultant
------------------------------