Shape the future of IBM!

We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:

Post your ideas

Start by posting ideas and requests to enhance a product or service. Take a look at ideas others have posted and upvote them if they matter to you,

  1. Post an idea

  2. Upvote ideas that matter most to you

  3. Get feedback from the IBM team to refine your idea

Help IBM prioritize your ideas and requests

The IBM team may need your help to refine the ideas so they may ask for more information or feedback. The offering manager team will then decide if they can begin working on your idea. If they can start during the next development cycle, they will put the idea on the priority list. Each team at IBM works on a different schedule, where some ideas can be implemented right away, others may be placed on a different schedule.

Receive a notification on the decision

Some ideas can be implemented at IBM, while others may not fit within the development plans for the product. In either case, the team will let you know as soon as possible. In some cases, we may be able to find alternatives for ideas which cannot be implemented in a reasonable time.

If you encounter any issues accessing the Ideas portal, please send email describing the issue to for resolution. For more information about IBM's Ideas program visit

Status Not under consideration
Created by Guest
Created on Oct 13, 2021

Be able to restrict the Windows local Administrators group for having MQ rights equal to mqm

By default an IBM MQ installation on Windows grants the mqm AND the local Administrators group a maximum set of rights on MQ. Just like on Linux/Unix the root rights are seperated from mqm rights and vice versa (So root can't administer mqm, and mqm can't administer the platform).

Idea priority High
Why is it useful?

In lots of organizations the local Administration group contains too many members. The MQ admin team is member of mqm, but the Windows administration group and maybe some others have local administrator rights as well, and therefore can potentially do anything with MQ! During audits this might be an extra security risk.

Who would benefit from this idea? Every company in the world that runs MQ on Windows servers
  • Guest
    Nov 2, 2021

    Hi Mark, I understand what you mention because of for example migration issues. My idea is that nothing will differ by default because of that. But it should be an option in by example qm.ini. If I adjust autorizations as MQ administrator I want to be in control of that. Too many people now have high priviledged access to MQ by default. This is a finding by our audit team.

  • Admin
    Mark Taylor
    Nov 2, 2021

    It is not likely that we will change the current Windows security model. Generally, an OS administrator can do anything either directly or indirectl and the model on Windows reflects that. Changing the approach would lead to compatibility and migration issues.

    On Unix, while the 'root' id is not automatically considered able to adminsiter MQ, there is no real added security there as it is trivial for root to switch to the mqm id.