What was a pretty easy task in Exchange 2010, seems to have become more difficult in the new Exchange 2013 Control Panel (ECP). When deleting a UM Dial Plan you need to remove all of its associations first, these are:
UM Mailbox Policies and UM Auto Attendants
Remove any Mailbox Policies or Auto Attendants from the Dial Plan
![]()
UM Server
Remove the Dial Plans association to the UM Call Router and UM Service
![]()
UM IP gateways/UM Hunt Groups
Remove the Dial Plans association to a UM IP Gateway by deleting the UM Hunt Group bound to the Dial Plan. This is where it gets interesting - The below screen shot shows the UM Hunt Group configuration section in the Dial Plan. The troubles is when you create a SIP URI Dial Plan type which is required for Lync, you cannot see this section. I'm not sure if this is a bug, or by design.
![]()
![]()
Your command should look something like this:
If you get the syntax wrong you'll probably see one of the following 2 error messages:
PowerShell
Below is a rough example of how PowerShell could make this task a little easier:
UM Mailbox Policies and UM Auto Attendants
Remove any Mailbox Policies or Auto Attendants from the Dial Plan
UM Server
Remove the Dial Plans association to the UM Call Router and UM Service
UM IP gateways/UM Hunt Groups
Remove the Dial Plans association to a UM IP Gateway by deleting the UM Hunt Group bound to the Dial Plan. This is where it gets interesting - The below screen shot shows the UM Hunt Group configuration section in the Dial Plan. The troubles is when you create a SIP URI Dial Plan type which is required for Lync, you cannot see this section. I'm not sure if this is a bug, or by design.
To get around this issue you can use PowerShell, but this leads me to the next issue. The Technet documentation gives the following syntax "Remove-UMHuntGroup -Identity MyUMHuntGroup", however this is not 100% correct. The identity should actually be in the form <Gateway Identity>\<Hunt Group Name>.
- Gateway Identity is found in the "Name" column returned from Get-UMIPGateway
- Hunt Group is found in the "Name" column returned from Get-UMHuntGroup
Your command should look something like this:
If you get the syntax wrong you'll probably see one of the following 2 error messages:
>>Cannot process argument transformation on parameter 'Identity'. Cannot convert value "NLNZ Offices:NL NZ Offices Dial
Plan" to type "Microsoft.Exchange.Configuration.Tasks.UMHuntGroupIdParameter". Error: "'NLNZ Offices:NL NZ Offices
Dial Plan' isn't a valid UM hunt group identity. Specify an identity in the form "<gateway identity>\<hunt group
name>"."
+ CategoryInfo : InvalidData: (:) [Remove-UMHuntGroup], ParameterBindin...mationException
+ FullyQualifiedErrorId : ParameterArgumentTransformationError,Remove-UMHuntGroup
+ PSComputerName : lxlhlyncexch01.lhl.local
>>The operation couldn't be performed because object '<UM Server>\NLNZ Offices' couldn't be found on
'<UM Server>'.
+ CategoryInfo : NotSpecified: (:) [Remove-UMHuntGroup], ManagementObjectNotFoundException
+ FullyQualifiedErrorId : FAC401B1,Microsoft.Exchange.Management.Tasks.UM.RemoveUMHuntGroup
+ PSComputerName : <UM Server>
PowerShell
Below is a rough example of how PowerShell could make this task a little easier: