Apologies for the late post this week, readers! We’re engaged in some server moves & updating. I don’t have a whole lot of time available. But the blog must go on!
We’re continuing our “Examining Lync’s Connection Tools” series this week with OCSUMUtil.exe.
What Does OCSUMUtil Mean?
It stands for ‘OCS Unified Messaging Utility’, which I believe is its original name. However its official name – at least according to TechNet – is “Exchange UM Integration Utility”.
Many people refer to it as just ‘OCSUMUtil’, so we’ll do that here.
What Does OCSUMUtil Do?
Its primary purpose, as you might guess, is aiding in Lync/Exchange Unified Messaging integration. It does this in two ways:
- Creating Active Directory contact objects for Auto Attendant and Subscriber Access numbers used in Enterprise Voice.
- Verifying that each Enterprise Voice dial plan matches its corresponding Unified Messaging dial plan. (According to TechNet, this is only necessary if you’re using an Exchange Server earlier than Exchange 2010 SP1.)
This has been its purpose since OCS 2007 days. In fact, I think it’s the longest-used connection tool in our series.
(If I’m wrong, please comment and set us all straight!)
How Do You Use OCSUMUtil?
Instructions for its use in a Lync Server 2013 deployment: http://technet.microsoft.com/en-us/library/gg398193.aspx
When you implement Unified Messaging, you’re essentially connecting Lync Server and Exchange Server together. They will coordinate communications data like voicemail, Auto Attendant activity, etc. The PluralSight blog has a good listing of the features involved in Unified Messaging. I’ll give more detail on this topic later.
By using the OCSUmUtil tool, you’re facilitating the creation of connections between Lync Server and Exchange Server. It’s not the central component of integration, but it’s very important to Subscriber Access (which allows people to access their voicemails) and Auto Attendant (which answers & redirects certain calls for you).
You’ll run OCSUMUtil from the /Support/ subfolder on the computer where you installed Lync Server. When the tool is open, you’ll click ‘Load Data’ to find your Exchange forest.
See Blog.Schertz.name for the full image.
- In the SIP Dial Plans list, select the UM dial plan for which you want to create contact objects. Click Add.
- In the Contact box, either use the default organizational unit, or click Browse to search for another one with the OU Picker. I’ll presume you want to use the default, since most admins will.
- In the Name box, either accept the default dial plan name or enter a new one. (For example, if you’re creating the Subscriber Access contact object, name it “Subscriber Access”.)
- Enter a new SIP address for the contact object in the SIP Address box (or accept the default).
- In the server list, select the server where you want to place the contact object (either Standard Edition or Enterprise Edition’s Front End pool).
- In the Phone Number list, select “Enter phone number” and enter a standardized phone number.
- Select the type of object you want in the Contact Type list.
- Click OK to finish creating the object. Repeat these steps for any more contact objects you need to make.
For another perspective, see the Lync and Exchange UM Integration post by Jeff Schertz. As is his usual, he talks in good step-by-step detail about using OCSUmUtil in the course of a Lync Server 2010/Exchange Server 2010 integration.
Potential for Error
While you can encounter an error just about anywhere, I noted in my research that OCSUMUtil has a higher-than-average potential for error. If either Lync or Exchange UM are not properly configured prior to using OCSUMUtil, it will give an error. Also, if you configure OCSUMUtil incorrectly, it will error out.
Handy for troubleshooting, but it does mean you have to go back & fix things. I haven’t personally encountered an OCSUMUtil error, but searches have told me of a couple types:
- If you select the Director (or the Director is selected by default) in Step 5 above. It must be a front end server.
- If there is no number (or an incorrectly-created number) in Exchange for Auto Attendant or Subscriber Access.
Next time, I’ll blog either about our last connection tool, Online Directory Synchronization…or some hands-on updating work. Check back here next week to find out!
Have you encountered an error while using OCSUmUtil? Or did it go smoothly? Either way, share the experience with us!