The Exchange organisation was set up in a hybrid mode. All warmbody Mailboxes where located on the Exchange online and all coldbody mailboxes on the on-prem servers.<\/p>\n
This customer is using Skype for Business as a service from a third party provider. What means that I wasn\u2019t able to login directly to the Skype server.<\/p>\n
I will try to describe how the setup of this constellation was made in a later post on this page.<\/p>\n
Challenges<\/h4>\n
After all warmbody mailboxes where migrated to Exchange Online, I had to enable the UM Policy for all users.<\/p>\n
This is not really a big deal if you are doing it for one user. All you need is the Enable-UMMailbox cmdlet with the mailbox Id and the extension parameter. Of course there are more parameters you can set. For example the PIN or which UM policy to use.\u00a0 You can find more about the Enable-UMMailbox cmdlet here:<\/p>\n
https:\/\/technet.microsoft.com\/de-de\/library\/aa998033%28v=exchg.160%29.aspx?f=255&MSPPError=-2147217396<\/a><\/p>\n The challenge I had was to enable the UM role for more than 400 warmbody mailboxes. To do that you can follow different ways. The easiest way is to simply login to your Skype for Business server. But as I mentioned earlier in this post, the Skype for Business server is managed by a third party company. Thus, I was not able to do that.<\/p>\n Another way is to do it directly on the Exchange Online server through remote PowerShell.<\/p>\n But, here we have another challenge: The Enable-UMMailbox cmdlet is an Exchange command, but the extension I need is from the phone number, which is usually the Active Directory object field \u201cTelephones\u201d.<\/p>\n So how to do that now?<\/p>\n First thing I did was to search the web for some solutions for this challenge. After I wasn\u2019t able to find any solution which could help me, I started to write a script, which worked out perfectly for me!<\/p>\n I am now going to present you this script and how to use it in it\u00b4s current version (2.5).<\/p>\n The old Post was about the version 1.0. There you were only able to enable UM in Exchange Online and you had to modify parts of the script for the extension length.<\/p>\n Whats new in the current version (2.52)?<\/p>\n Well, this!<\/p>\n \u00a0<\/p>\n You can download the whole script from Microsoft Technet:\u00a0https:\/\/gallery.technet.microsoft.com\/Enable-UM-in-exchange-8a221ec1<\/a><\/p>\n \u00a0<\/p>\n Here now how to use the script:<\/p>\n .CHANGE LOG<\/p>\n V1.00, 2017\/11\/03 \u2013 Initial version \u2013 (Enable UM in exchange online) After starting the script in your Windows PowerShell console,\u00a0or through right-click \u2013> run with PowerShell (No need to start it over the Exchange Management Shell),<\/p>\n you will need to choose one of the two options you want go with. In this case we start with the Office 365 option [1].<\/p>\n The script now checks if\u00a0 the Azure Active Directory module is available on your machine, if not you will receive the following output:<\/p>\n If you receive this message, and you choose the option [Y], your browser will be opened and you will be redirected to the Microsoft download page.<\/p>\n Here you can see the content of the page:\u00a0http:\/\/connect.microsoft.com\/site1164\/Downloads\/DownloadDetails.aspx?DownloadID=59185<\/a><\/p>\n You just need to download the msi file from the web site, install it and then re-run the script again. You should close the current PowerShell console window and open a new one, as well.<\/p>\n If you have installed the Azure AD module, the script follows its procedure to the O365 credentials prompt.<\/p>\n Here, just enter the Microsoft Office365 credentials of an account that has administrative permissions in your O365 tenant and Exchange Online.<\/p>\n Usually this is your\u00a0ALIAS@contoso.onmicrosoft.com<\/a>\u00a0account, or in hybrid environments your on-premise e-mail, resp. UPN.<\/p>\n After entering your credentials, you will be asked for which Mailbox Type(s) you wanna enable the UM Role. (multiple are possible)<\/p>\n Now you will be asked to confirm your choose:<\/p>\n In the next step you will have to enter the length of your UM extension number. By this, you choose how many of the last digits of a users phone number which will be used as the extension number in Skype.<\/p>\n Now the script is connecting remotely to Exchange Online and AzureAD.<\/p>\n After the successful login, the script gets your existing UM policies and lists them for you in the form of a menu. Now you can easily choose the UM policy you want to enable for your mailboxes.<\/p>\n The script now searches all mail boxes which are not enabled for UM.<\/p>\n In a next step, UM will be enabled for any found mail box with the UM policy you picked and the extension number consisting of the last n digits of the users phone number.<\/p>\n After all mailboxes are processed, you will receive this message at the end, which shows you how many mailboxes where enabled for UM.<\/p>\n The script creates a log file in the path, where you saved and ran the script.<\/p>\n \u00a0<\/p>\n In this log file you can see every successful and failed try of enabling UM.<\/p>\n Running the Script on-premise is almost equal to the O365 mode. Of course there are some different steps which have to be done.<\/p>\n After starting the script in your Windows PowerShell console (No need to start it over the Exchange Management Shell),<\/p>\n you will need to choose one of the two options you want go with. In this case we start with the On-Premises option [2].<\/p>\n Now you need to enter your Exchange admin credentials for your on-premise environment:<\/p>\n After entering your credentials, you will be asked for which Mailbox Type(s) you wanna enable the UM Role. (multiple are possible)<\/p>\n Now you will be asked to confirm your choose:<\/p>\n In the next step you will have to enter the length of your UM extension number (same as in the O365 option):<\/p>\n After you have set the extension length, you will be asked to enter the name of an Exchange (CAS) server inside of your organization.<\/p>\n if your server name and Exchange credentials are correct, the script connects to your exchange server:<\/p>\n After the successful login, the script checks your existing UM Policies and list them for you in the form of a menu. Now you can easily choose the UM policy you want to enable for your mailboxes.<\/p>\n \u00a0<\/p>\n The script now searches all mail boxes which are not enabled for UM.<\/p>\n In a next step, UM will be enabled for any found mail box with the UM policy you picked and the extension number consisting of the last n digits of the users phone number.<\/p>\n \u00a0<\/p>\n After all mailboxes are processed, you will receive this message at the end, which shows you how many mailboxes where enabled for UM.<\/p>\n The script creates a log file in the path, where you saved and ran this script.<\/p>\n \u00a0<\/p>\n In this log file you can see every successful and failed try of enabling UM.<\/p>\n \u00a0<\/p>\n \u00a0<\/p>\n \u00a0<\/p>\n \u00a0<\/p>\n Photo by\u00a0Namroud Gorguis<\/a>\u00a0on\u00a0Unsplash<\/a><\/p>\n","protected":false},"excerpt":{"rendered":" Background Some time ago I was on a very interesting project about on-premise infrastructure, Exchange online and 3rd party player for Skype for Business. This constellation had a couple of challenges to cope with. The Exchange organisation was set up in a hybrid mode. All warmbody Mailboxes where located on the Exchange online and all […]<\/p>\n","protected":false},"author":1,"featured_media":3346,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_crdt_document":"","om_disable_all_campaigns":false,"_monsterinsights_skip_tracking":false,"_monsterinsights_sitenote_active":false,"_monsterinsights_sitenote_note":"","_monsterinsights_sitenote_category":0,"_uf_show_specific_survey":0,"_uf_disable_surveys":false,"footnotes":""},"categories":[1923,2,3],"tags":[],"class_list":["post-660","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-microsoft-365","category-exchange","category-powershell"],"post_mailing_queue_ids":[],"_links":{"self":[{"href":"https:\/\/www.msb365.blog\/index.php?rest_route=\/wp\/v2\/posts\/660","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.msb365.blog\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.msb365.blog\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.msb365.blog\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.msb365.blog\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=660"}],"version-history":[{"count":34,"href":"https:\/\/www.msb365.blog\/index.php?rest_route=\/wp\/v2\/posts\/660\/revisions"}],"predecessor-version":[{"id":5207,"href":"https:\/\/www.msb365.blog\/index.php?rest_route=\/wp\/v2\/posts\/660\/revisions\/5207"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.msb365.blog\/index.php?rest_route=\/wp\/v2\/media\/3346"}],"wp:attachment":[{"href":"https:\/\/www.msb365.blog\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=660"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.msb365.blog\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=660"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.msb365.blog\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=660"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}Solution<\/h4>\n
\n
Download<\/h4>\n
Enable UM in Exchange Online for multiple mailboxes<\/h5>\n
\nV2.00, 2017\/11\/14 \u2013 Added on-premise as a options | choose between Office365 and on-premise environment after starting Script to enable UM
\nV2.10, 2017\/11\/18 \u2013 Added the option to choose the Extension number length during the script execution, Added AzureAD module check (if O365 is selected)
\nV2.50, 2017\/11\/20 \u2013 Added support for MSonline module, added comments, added error count for summary<\/p>\nOPTION: Office 365<\/strong><\/h6>\n
![\"\"](\"https:\/\/msb365.abstergo.ch\/wp-content\/uploads\/2017\/11\/1-5.png\")
<\/p>\n![\"\"](\"https:\/\/msb365.abstergo.ch\/wp-content\/uploads\/2017\/11\/2.1-1.png\")
<\/p>\n![\"\"](\"https:\/\/msb365.abstergo.ch\/wp-content\/uploads\/2017\/11\/2.2-1.png\")
<\/p>\n![\"\"](\"https:\/\/msb365.abstergo.ch\/wp-content\/uploads\/2017\/11\/3-5.png\")
<\/p>\n![\"\"](\"https:\/\/msb365.abstergo.ch\/wp-content\/uploads\/2017\/11\/4-3.png\")
<\/p>\n![\"\"](\"https:\/\/msb365.abstergo.ch\/wp-content\/uploads\/2017\/11\/5-3.png\")
<\/p>\n![\"\"](\"https:\/\/msb365.abstergo.ch\/wp-content\/uploads\/2017\/11\/3-6.png\")
<\/p>\n![\"\"](\"https:\/\/msb365.abstergo.ch\/wp-content\/uploads\/2017\/11\/3-1.png\")
<\/p>\n![\"\"](\"https:\/\/msb365.abstergo.ch\/wp-content\/uploads\/2017\/11\/4.png\")
<\/p>\n![\"\"](\"https:\/\/msb365.abstergo.ch\/wp-content\/uploads\/2017\/11\/5.png\")
<\/p>\n![\"\"](\"https:\/\/msb365.abstergo.ch\/wp-content\/uploads\/2017\/11\/7.png\")
<\/p>\n![\"\"](\"https:\/\/msb365.abstergo.ch\/wp-content\/uploads\/2017\/11\/8.png\")
<\/p>\n![\"\"](\"https:\/\/msb365.abstergo.ch\/wp-content\/uploads\/2017\/11\/9-1024x741.png\")
<\/p>\n<\/h6>\n
OPTION: ON-PREMISE<\/strong><\/h6>\n
![\"\"](\"https:\/\/msb365.abstergo.ch\/wp-content\/uploads\/2017\/11\/1-6.png\")
<\/p>\n![\"\"](\"https:\/\/msb365.abstergo.ch\/wp-content\/uploads\/2017\/11\/2-3.png\")
<\/p>\n<\/p>\n<\/p>\n![\"\"](\"https:\/\/msb365.abstergo.ch\/wp-content\/uploads\/2017\/11\/3-7.png\")
<\/p>\n![\"\"](\"https:\/\/msb365.abstergo.ch\/wp-content\/uploads\/2017\/11\/4-2.png\")
<\/p>\n![\"\"](\"https:\/\/msb365.abstergo.ch\/wp-content\/uploads\/2017\/11\/5-2.png\")
<\/p>\n<\/p>\n<\/p>\n<\/p>\n<\/p>\n<\/p>\n