Posts

Users cannot manage distribution groups that they are owners of in Exchange 2013

If you have recently ran across an issue where users are unable to manage a distribution group in Outlook or Exchange even though you have made them owners of this group it is by design.  By default users in Exchange 2013 are assigned to the “Default Role Assignment Policy”.  This role does not have the permissions to edit group ownership even if they are owner’s of the distribution group.  In order to fix this you must login to the ECP by going to https://servername/ecp  Once here go into the permissions on the left hand side.
distribution groups i own
Click on admin roles in my instance I just assigned my user Recipient Management rights since they are an administrator level employee.  This resolves the issue.
permissions
If all of the following hold true then you can also just download and run this Powershell script.

  • I want my users to be able to manage distribution groups they own.
  • I don’t want them to be able to create distribution groups.
  • I don’t want them to be able to remove distribution groups even if they do own them.

# Script for creating a Role that can manage distributions groups but can’t create new ones
#
#################################################################################
#
# The sample scripts are not supported under any Microsoft standard support
# program or service. The sample scripts are provided AS IS without warranty
# of any kind. Microsoft further disclaims all implied warranties including, without
# limitation, any implied warranties of merchantability or of fitness for a particular
# purpose. The entire risk arising out of the use or performance of the sample scripts
# and documentation remains with you. In no event shall Microsoft, its authors, or
# anyone else involved in the creation, production, or delivery of the scripts be liable
# for any damages whatsoever (including, without limitation, damages for loss of business
# profits, business interruption, loss of business information, or other pecuniary loss)
# arising out of the use of or inability to use the sample scripts or documentation,
# even if Microsoft has been advised of the possibility of such damages
#
#################################################################################
#
# Written by Matthew Byrd
# Matbyrd@microsoft.com
# Last Updated 10.15.09

# Parameter to get a different name than default for the new Role
Param([string]$name=”MyDistributionGroupsManagement”,[string]$policy=”Default Role Assignment Policy”,[switch]$creategroup,[switch]$removegroup)
# Help Function
Function Show-Help {

This script is will create or manage a management role designed to allow users to modify groups that they already own
but not create or remove any new distribution groups.
Switches:
-name           Name of the managment role you want to create or modify
Defaults to: `”MyDistributionGroupsManagmenet`”
-policy         Name of the Role Policy you want to assign the role to
Defaults to: `”Default Role Assignement Policy`”
-creategroup    Adds or Removes the ability of the Role to Create DLs
-removegroup    Adds or Removes the ability of the Role to Remove DLs
Examples:
——————————————–
This will Use the default names and Policy and will create a role that cannot
Create or remove groups but can still modify them.  If the role already exists
It will modify it by removing or adding the abiltity to create and remove groups
based on the current state.
Manage-GroupManagementRole -CreateGroup -RemoveGroup

}
# Function to modify a role by removing or adding Role Entries
# If no action is passed we assume remove
# $roleentry should be in the form RoleRoleentry e.g. MyRoleNew-DistributionGroup
Function ModifyRole {
Param($roleenty,$action)
Switch ($action){
Add {Add-ManagementRoleEntry $roleenty -confirm:$false}
Remove {Remove-ManagementRoleEntry $roleenty -confirm:$false}
Default {Remove-ManagementRoleEntry $roleenty -confirm:$false}
}
}
If (($creategroup -eq $false) -and ($removegroup -eq $false)){
Show-Help
exit
}
# Test if we have a role that already has that name
If (([bool](Get-Managementrole $name -erroraction Silentlycontinue)) -eq $true){
Write-Warning “Found a Role with Name: $name”
Write-Warning “Trying to Modify Existing Role”
}
Else {
# Create the new Management Role
Write-Host “Creating Managmenet Role $name”
New-ManagementRole -name $name -parent MyDistributionGroups
}
# Determine if we have the New and Remove Role Entries on the Role Already
$create = [bool](Get-managementroleentry $nameNew-DistributionGroup -erroraction Silentlycontinue)
$remove = [bool](Get-managementroleentry $nameRemove-DistributionGroup -erroraction Silentlycontinue)
# If we have the switch CreateGroup add or remove the RoleEntry for New-DistributionGroup
If ($creategroup -eq $true){
If ($create -eq $true){ModifyRole $nameNew-DistributionGroup Remove;Write-Host “Removing ability to create distribution Groups from $name”}
elseif ($create -eq $false) {ModifyRole $nameNew-DistributionGroup Add;Write-Host “Adding ability to create distribution Groups to $name”}
}
# If we have the switch RemoveGroup add or remove the RoleEntry for New-DistributionGroup
If ($removegroup -eq $true){
If ($remove -eq $true){ModifyRole $nameRemove-DistributionGroup Remove;Write-Host “Removing ability to create distribution Groups from $name”}
elseif ($remove -eq $false) {ModifyRole $nameRemove-DistributionGroup Add;Write-Host “Adding ability to create distribution Groups to $name”}
}
# Test if we have the assignment for the Role and Policy
# If we do … write a warning
# If not create a new assignment
If (([bool](get-managementroleassignment $name-$policy -erroraction SilentlyContinue)) -eq $true){
Write-Warning “Found Existing Role Assignment: $name-$policy”
Write-Warning “Making no modifications to Role Assignments”
}
Else {
# Assign the Role to the Role Policy
Write-Host “Creating Managmenet Role Assignment $name-$policy”
New-ManagementRoleAssignment -name ($name + “-” + $policy) -role $name -policy $policy
}
 

If you just installed Exchange 2013 and you have an Exchange 2010 mailbox you cannot access EAC you get the old ECP management

If you just installed Exchange 2013 and you try to go to http://ServerName/ecp you’ll notice that you get the old Exchange 2010 interface and cannot manage your Exchange 2013 server.  There is a simple fix for this just simply use the following url syntax.
https://ServerName/ecp?ExchClientVer=15
 

While installing Exchange 2013 it reports there are Exchange 2003 servers in the network when there are not

One or more servers in the existing organization are running Exchange 2000
Server or Exchange Server 2003.

Installation can’t proceed until all
Exchange 2000 or Exchange 2003 servers are removed.

If you previously upgraded from Exchange 2003 to a version before 2013 then you may not have removed Exchange 2003 or 2000 server properly.  If this is the case you can run adsiedit.msc and find the following location.
Load Configuration
services>Microsoft exchange>first organization>administrative groups>  In here find your administrative group.  Then you will see a “servers” container.  Go in there and delete any name references to your old servers that are no longer in your network.

While trying to install Exchange 2013 you receive the error message "A reboot from a previous installation is pending. Please restart the system and rerun setup.

error
If you receive this error it is a relatively easy fix.  Just go to regedit and find the following key and delete it.
HKLMSYSTEMCurrentControlSetControlSession ManagerPendingFileRenameOperations
Hit the retry button in setup and it will work.