Category Archives: Exchange

Exchange UM Voice Auto-Attendant custom greeting and those pesky system prompts

Microsoft Exchange Unified Messaging is a very cool tool to put into your corporate telephony arsenal.  You get a very nice, voice activated auto-attendant with some very nice features.
One feature the Exchange UM team didn’t get fully right is customization of the initial greeting.

Out of the box, your voice enabled AA (auto-attendant) will say:

Thank you for calling [your company name] To reach a specific person, just tell me their name

If you are like ArmgaSys, you will want to customize your greeting via the ECP (Exchange Admin Center).  You hire voice talent and record a really nice greeting along the lines of “Thank you for calling my company, if you know your parties extension, you may dial it now or simply tell me their name”.  You then upload your greeting in the UM and are shocked to hear the following:

Thank you for calling my company, if you know your parties extension, you may dial it now or simply tell me their name. To reach a specific person, just tell me their name.

You just discovered a UM system prompt, specifically the Voice AA prompt which says (in a female voice) “To reach a specific person, just tell me their name”

At this point, you have only one option:  You must replace the system prompt with a audio file containing silence.*  Fortunately, this is very easy to do!

The solution:

  1. On your Exchange UM server, navigate to
    C:\Program Files\Microsoft\Exchange Server\V[#]\UnifiedMessaging\prompts\en\
  2. Delete the file vuiAADsearch_Yes_Custom_No_main.1.wav
  3. Make a copy of Silence-250ms.wav
    (This .wav file is also located in the prompts\en directory)
  4. Rename your copy of the silence file to vuiAADsearch_Yes_Custom_No_main.1.wav

That is it!

Warning! Warning! Warning!
Installing cumulative updates (CU) and service packs will revert this file back to its original state.  You will need to repeat these steps after each CU and Service Pack!


*Some of you will be asking “Why not just delete the file”.  Well, it is a system prompt which means Exchange UM pretty much requires the file to be there.  Deleting the file can (and will) cause your UM service to fail.

Exchange Unified Messaging Doesn’t Start (No Certificate Found)

So, you have updated your SSL certificates in Exchange 2010 to comply with (insert corporate policy here).  All seems well until you receive a frantic call: “Voice Mail is down!”.

A quick search of the event viewer turns up:

The Microsoft Exchange Unified Messaging service was unable to start. More information: “Microsoft.Exchange.UM.UMService.UMServiceException: No certificate was found using the thumbprint ” specified in the UMCertificateThumbprint property of the UMServer object.
   at Microsoft.Exchange. UM.UMService.UMConnectionManagerHelper.TLSConnectionManager.Initialize()
   at Microsoft.Exchange.UM.UMService.UMService.InitializeConnectionManager()
   at Microsoft.Exchange.UM.UMService.UMService.StartService()
   at Microsoft.Exchange.UM.UMService.UMService.OnStartInternal(String[] args)”


You cradle your head in your hands and begin to weep softly.

Fear not!

The Solution

  1. Launch Exchange Management Console from the server hosting the Unified Messaging Role
    Important: Remember to launch with UAC elevated permissions!
  2. Expand and click on Server Configuration
  3. From the server list in the center pane, select the server hosting the Unified Messaging Role
  4. In the lower center pane, you’ll very likely notice the new SSL certificate is not assigned to any services
  5. Right click on the certificate and select Assign Services to Certificate
  6. In the wizard, check the Unified Messaging (UM) service
  7. Finish the wizard and dry your tears!

SharePoint Alerts, External Users, and Exchange Relay


One of SharePoint’s nicer features is a rich alert system which supports change driven e-mail based alerts.  Configuring SharePoint and Exchange Server 2007 to e-mail alerts is relatively straight forward for internal e-mail clients (I.E. those e-mail clients which are actually hosted by your Exchange Server).  Configuration becomes much more difficult if you are attempting to alert SharePoint users at e-mail addresses which are NOT hosted on your Exchange Server.  To accomplish this feat, you must relay the e-mail.

This is where the fun begins!

The Scenario
Your e-mail address is  Your SharePoint install at is setup to alert you of any changes to your document libraries.  All is well in the world!

A new user is introduced to your SharePoint user list with an e-mail address of  This new user reports he is not receiving any alerts from SharePoint.

A quick review of the logs reveals the following error:

#160009: The e-mail address ‘’ is unknown.

Root Problem
Your exchange server is setup to disallow relaying.  Under the hood, SharePoint is receiving the following error from Exchange:

550 5.7.1 Unable to relay

Enable relaying for your SharePoint server.  Easy huh? Well… sort of.

Open Exchange Management Console and navigate to Server Configuration –> Hub Transport.  Find the Receive Connectors tab.  You should see something similar to the image below:


Open the Receive connector and note all of the settings on each screen.  Take good notes as you will need the settings later.
They will look similar to the images below:

SCREEN#1              SCREEN#2              SCREEN#3               SCREEN#4

Remove the receive connector by right clicking on the connector and selecting Remove.
Why do we do this?  Because Exchange Server 2007 appears to process the receive connectors in the order they were created.  In the standard install, the default Receive Connector is configured to receive e-mail from ALL IP addresses.  If you add the Relay Receive Connector AFTER the default connector, it will never be processed.  You want your Relay to process first.

Create the relay connector

  1. Click New Receive Connector on the Action Bar located at the right of the Exchange Management Console.
  2. Name the connector, click Next.
  3. On the Local Network settings screen, modify as necessary.
    NOTE: These will normally be the same as SCREEN#2 in STEP#2 above
    Click Next
  4. On the Remote Network settings screen, remove the default settings by click the red “X”.
  5. Add in the IP address of your internal SharePoint sever.
    NOTE: If your SharePoint server is hosted on the same physical box as the Exchange Server, be sure to enter in the loop back IP address (IPv4, IPv6 ::1) as well as the actual IP address of the server.�
    Click Next
  6. Click New to create the Receive Connector, then click FinishBut wait, you are not done just yet!
  7. Right click on the newly created Received Connector and click Properties to edit the Receive Connector
  8. Select the Permission Groups tab
  9. Check the Exchange Server check box
  10. Select the Authentication tab
  11. Check the Externally Secured check box
    Make sure all other check boxes are NOT checked.
  12. Click apply to save your changes

Your new relay connector should look similar to the screenshots below
(Double click to enlarge)

SCREEN#5                  SCREEN#6               SCREEN#7                SCREEN#8

Recreate the original Receive Connector using the settings noted in Step#2
Your receive connector list should now look like the following:


Validate functionality

  1. Verify you can still send e-mail.
  2. Verify you can still receive e-mail.
  3. Verify SharePoint is now sending alerts to the external e-mail.
  4. Verify you have no open relays.  This can be completed via any of the available open relay tests on the internet.