Enterprise Voice

Error When Installing UM Role on Exchange 2010 SP1

11/12/2010 12:31:24.0997] [2] Active Directory session settings for ‘install-umservice’ are: View Entire Forest: ‘True’, Configuration Domain Controller: domaincontrollerfqdn, Preferred Global Catalog: “domaincontrollerfqdn”, Preferred Domain Controllers: ‘{ domaincontrollerfqdn }’
[11/12/2010 12:31:24.0997] [2] Beginning processing install-UMService
[11/12/2010 12:31:26.0012] [2] [WARNING] An unexpected error has occurred and a Watson dump is being generated: There are no more endpoints available from the endpoint mapper. (Exception from HRESULT: 0x800706D9)
[11/12/2010 12:31:26.0012] [2] [ERROR] There are no more endpoints available from the endpoint mapper. (Exception from HRESULT: 0x800706D9)
[11/12/2010 12:31:27.0668] [1] The following 1 error(s) occurred during task execution:
[11/12/2010 12:31:27.0668] [1] 0.  ErrorRecord: There are no more endpoints available from the endpoint mapper. (Exception from HRESULT: 0x800706D9)
[11/12/2010 12:31:27.0668] [1] 0.  ErrorRecord: System.Runtime.InteropServices.COMException (0x800706D9): There are no more endpoints available from the endpoint mapper. (Exception from HRESULT: 0x800706D9)
   at Interop.NetFw.INetFwRules.Add(NetFwRule rule)
   at Microsoft.Exchange.Security.WindowsFirewall.ExchangeFirewallRule.Add()
   at Microsoft.Exchange.Configuration.Tasks.ManageService.Install()
   at Microsoft.Exchange.Management.Tasks.UM.InstallUMService.InternalProcessRecord()
   at Microsoft.Exchange.Configuration.Tasks.Task.ProcessRecord()
   at System.Management.Automation.CommandProcessor.ProcessRecord()

 

When running the wizard to add the UM role to your Exchange 2010 Sp1 server, you may have this error appear in the install wizard:

ErrorRecord: System.Runtime.InteropServices.COMException (0x800706D9): There are no more endpoints available from the endpoint mapper. (Exception from HRESULT: 0x800706D9)

If you take a look at the Exchange setup log, it is trying to add firewall rules, and fails, and kills the install. If your windows firewall service is not running, you must start it.  Re run the installation with windows firewall running, and all is fine Smile

(145)

Posted on by Randy Wintle in Enterprise Voice, Exchange 2010, Exchange UM, Lync, Microsoft, OCS 2007 R2, Server 2008 R2, Unified Communications 5 Comments

Powershell Script to create new user, enable for Exchange, UM and Lync Server

I created this powershell for our internal onboarding process, figured I would share it with the masses.

I think there are a couple good takeways from this script, it remotes into Exchange 2010 and Lync Server 2010 Powershell sessions, so nothing except Powershell 2.0 is required on the client side, which is standard with Windows 7. It also shows how you can simultaneously use Exchange and Lync powershell commands in the same script to get things done.

A couple of disclaimers:

I am in no way advanced at powershell scripting, so nothing fancy here.

This was developed specifically for my internal needs, you will probably have to add/remove variables and requirements.

http://cid-389bd51b03b1f8f9.office.live.com/embedicon.aspx/Public/UserSetupScriptGeneric.ps1

 

Script is above, any freedback is appreciated, if you improve on this at all, I would love to see it as well.

(773)

Posted on by Randy Wintle in Enterprise Voice, Exchange 2007, Exchange 2010, Exchange UM, Lync, Lync RC, Microsoft, OCS, OCS 2007 R2, Unified Communications 12 Comments

Exchange UM Auto Attendant Key Mappings Not Transferring Calls After SP1

After upgrading my Exchange 2010 environment to SP1 we ran into an issue where our Auto Attendant would not transfer calls to our OCS Response Groups and users. If you dialed by name or number, it would transfer, but if a key mapping was set to transfer to an extension, it would fail.

Example:

Primary AA

Key Mapping of 1 set to extension 1000

Extension 1000 is an OCS Response Group Workflow

Key Mapping 4 is set to a separate auto attendant that is speech enabled and intended for use with saying a persons name or extension to reach them.

When a caller pressed the 1 key, the attendant would say “The call could not be transferred”

When pressing 4, and then entering the same extension, 1000, the call would dial properly.

I setup a new AA to run some tests and tried everything imaginable to get this working. No matter what I did, the key mappings would not transfer to an extension, or a full DID of a user off of the auto attendant. All other dial by name or extension functionality worked.

Running traces on the OCS front end and mediation showed no sign of a refer happening, which would appear when the call transfer was attempted.

I finally broke down and opened a PSS case, they had me set a dialing restrictions rule on the Dial Plan and Auto Attendant to allow all numbers.

image

 

Now, normally ,this was only used to dial outbound, so if a user setup dialing rules on their mailbox, or the auto attendant or dial plan had to call a number outside of the organization. I had previously no rules that allowed for any internal number patters, only 10 digit external number patterns.

This is just a normal allow all rule:

image

By setting a rule to allow all dialing and applying it to the dial plan and auto attendant, the issue was resolved.

I will update as soon as I find out if this is a bug, or if it is how it is going to be going forward.

(1787)

Posted on by Randy Wintle in Exchange 2010, Exchange UM, OCS 2007 R2, Unified Communications 6 Comments

Exchange UM Auto Attendant Key Mappings Not Transferring Calls After SP1

After upgrading my Exchange 2010 environment to SP1 we ran into an issue where our Auto Attendant would not transfer calls to our OCS Response Groups and users. If you dialed by name or number, it would transfer, but if a key mapping was set to transfer to an extension, it would fail.

Example:

Primary AA

Key Mapping of 1 set to extension 1000

Extension 1000 is an OCS Response Group Workflow

Key Mapping 4 is set to a separate auto attendant that is speech enabled and intended for use with saying a persons name or extension to reach them.

When a caller pressed the 1 key, the attendant would say “The call could not be transferred”

When pressing 4, and then entering the same extension, 1000, the call would dial properly.

I setup a new AA to run some tests and tried everything imaginable to get this working. No matter what I did, the key mappings would not transfer to an extension, or a full DID of a user off of the auto attendant. All other dial by name or extension functionality worked.

Running traces on the OCS front end and mediation showed no sign of a refer happening, which would appear when the call transfer was attempted.

I finally broke down and opened a PSS case, they had me set a dialing restrictions rule on the Dial Plan and Auto Attendant to allow all numbers.

image

 

Now, normally ,this was only used to dial outbound, so if a user setup dialing rules on their mailbox, or the auto attendant or dial plan had to call a number outside of the organization. I had previously no rules that allowed for any internal number patters, only 10 digit external number patterns.

This is just a normal allow all rule:

image

By setting a rule to allow all dialing and applying it to the dial plan and auto attendant, the issue was resolved.

I will update as soon as I find out if this is a bug, or if it is how it is going to be going forward.

(79)

Posted on by Randy Wintle in Exchange 2010, Exchange UM, OCS 2007 R2, Unified Communications 6 Comments

Little Improvements on Exchange 2010 SP1 UM Voicemail

So, I heard about a few improvements with Exchange 2010 SP1 being released. (Full List Here)

One cool thing I just saw, was presence inside the transcription on my voicemail. This may have been there in 2010 RTM and I just didn’t notice it, but this seems new to me.

vm1

As you can see, it detected my name, and put presence next to it, It also added presence to the phone number I left in the voicemail, allowing me to call directly out of the transcription text. This is just another one of the examples as to why the Microsoft Unified Communications package is truly amazing.

image

 

The  translation still isn’t perfect, but its getting better and better Smile

(18)

Posted on by Randy Wintle in Exchange 2010, Exchange UM, Unified Communications Leave a comment