You try to remove or make a change to a distribution group by using the Exchange admin center in Microsoft Exchange Online for Microsoft Office 365 or in on-premises Microsoft Exchange Server. In this situation, you receive the following error message: You don't have sufficient permissions. This operation can only be performed by a manager of the group.
This is because your user account lacks sufficient privileges to make hardware changes. As such, you cannot install equipment and add it to your company's network unless your user account receives. From the Kaspersky Internet Security 2014 Knowledge Base, you will learn how to install, activate, and update the application and how to download virus removal utilities. 'You do not have sufficient privileges to run the Sophos Endpoint Security and Control main application. You are not a member of any of the Sophos groups. Please contact your administrator.' I am the administrator!!! And I'm deffinately a member of the SophosAdministrator group.
Cause
This issue occurs if you're not a manager of the group. In this situation, you're not listed in the ManagedBy attribute.
Solution
Use one of the following methods.
Method 1: Use Exchange Online PowerShell or the Exchange Management ShellImportantYou have to be an Exchange Online admin, an Exchange admin, or a member of the 'Security Group Creation and Membership' role in the Exchange admin center to perform this procedure.
Take one of the following actions, as appropriate for your situation:
Connect to Exchange Online by using remote PowerShell. For more information about how to do this, see Connect to Exchange Online using Remote PowerShell.
On Exchange Server in your on-premises environment, open the Exchange Management Shell.
Make the change that you want to the distribution group by using the appropriate Windows PowerShell cmdlet.
For example, to remove the distribution group, use the Remove-DistributionGroupcmdlet together with the BypassSecurityGroupManagerCheck parameter. Here's an example:Remove-DistributionGroup -BypassSecurityGroupManagerCheck Note In this cmdlet and in other cmdlets in the 'Examples' section, the distribution group is represented by the placeholder .
Examples
Here are some more examples of other Windows PowerShell cmdlets that you can use to manage distribution groups:
To assign ownership of a group, use the Set-DistributionGroupcmdlet, as in the following example:
To add a user to a group, use the Add-DistributionGroupcmdlet, as in the following example:
To remove a user from a group, use the Remove-DistributionGroup cmdlet, as in the following example:
To check the members list for a group, use the Get-DistributionGroupMember cmdlet, as in the following example:
Method 2: Add yourself to the 'ManagedBy' attributeTo add yourself to the ManagedBy attribute, follow these steps:
Take one of the following actions, as appropriate for your situation:
Connect to Exchange Online by using remote PowerShell. For more information about how to do this, see Connect to Exchange Online using Remote PowerShell.
On Exchange Server in your on-premises environment, open the Exchange Management Shell.
Run the following command:
For example, if you're an Exchange Online admin or an Exchange admin who isn't listed in the ManagedBy attribute and you want to make changes to a distribution group that's named Accounting, run the following command to add yourself to the ManagedBy attribute:
After you do this, you'll be able to change the distribution group.
For more information about the Set-DistributionGroup cmdlet, see Set-DistributionGroup.
References
To learn about managing distribution groups that are synced to Office 365 from the on-premises environment, see the following Microsoft Knowledge Base article:
2417592 Owners of an on-premises distribution group that's synced to Office 365 can't manage the distribution group in Exchange Online
Still need help? Go to Microsoft Community or the Exchange TechNet Forums.
Active5 years, 5 months ago
I have in hands a third party msi installer that requires to be executed by an administrator. Im trying to change that so it could be installed by a regular user.
I managed to open it with installshield and changed some obvious settings like:
But in your perspective is that even possible? I´m having a hard time changing settings and configurations and until now i´m not having any success.
Im working with InstallShield 2013 Professional and if it is possible, in wich settings do you think i should be focusing?
For instance, running as regular user im now having a 1925 error.
And i feel if i correct the error, others will appear.
It's highly unlikely you can do this because it depends on too many things in the MSI package that can change the system. Any files going to restricted locations (program files, common files etc) or changes to HKLM registry keys will require elevation. MSI installs don't violate security - they don't allow a limited user to change areas of the system that are restricted.
If the environment has group policy/Active Directory you can arrange for the MSI to be deployed from a central location via Group Policy, that's the way people get around this. Otherwise on UAC systems the MSI may offer an elevation prompt that allows admin credentials to be entered.
Otherwise the vendor needs to create an install that can be used by limited users.
Well, Yes i need administrative privileges to write to locations that are shared by multiple users. In the filesystem, this means folders like WINDOWS or Program Files. In the registry, this means all of the hives which aren't per-user. That´s ok, i don´t need any of this.
Therefore, i thought it could be possible to change the filesystem to something like [userprofile] and rewrite the program to only use the HKEY_CURRENT_USER.
But i suspect it could be more to it than only this.
You Do Not Have Sufficient Security Privileges To Install Hardware Security
Andre GarciaAndre Garcia
You Do Not Have Sufficient Security Privileges To Install Hardware Windows 10
Not the answer you're looking for? Browse other questions tagged windows-installerinstallshieldmsiexec or ask your own question.