{"id":1323,"date":"2020-04-08T15:12:55","date_gmt":"2020-04-08T13:12:55","guid":{"rendered":"https:\/\/itblogwildi.wordpress.com\/?p=780"},"modified":"2025-06-13T10:39:58","modified_gmt":"2025-06-13T08:39:58","slug":"migration-exchange-unified-messaging-von-exchange-2010-auf-exchange-2016-2","status":"publish","type":"post","link":"https:\/\/itblog.wildi.dk\/?p=1323","title":{"rendered":"Migration Exchange Unified Messaging von Exchange 2010 auf Exchange 2016"},"content":{"rendered":"\n

Ich musste obige Migration vornehmen. Exchange-seitig ja kein Problem. Aber UM war f\u00fcr mich Neuland.<\/p>\n\n\n\n

Falls das nicht auf Anhieb funktioniert, hier einige Anlaufstellen:<\/p>\n\n\n\n

  1. Eventlog (Anwendung) des alten Exchange-Server, Quelle = «MSExchange Unified Messaging»<\/li>
  2. Eventlog (Anwendung) des neuen Exchange-Server, Quelle = «MSExchange Unified Messaging»<\/li>
  3. Eventlog (\\Anwendungs- und Dienstprotokolle\\Lync Server) auf dem Skype for Business (SfB) Server, Quelle = «LS Exchange Unified Messaging Routing»<\/li><\/ol>\n\n\n\n

    Wir mussten in unserem Fall (nur 1 SfB Server), folgendes konfigurieren:<\/p>\n\n\n\n

    Exchange Admin Center > Server > neuen Server ausw\u00e4hlen > bearbeiten > Unified Messaging
    Bei «UM-Anrufrouter» und «UM-Dienst» jeweils Startmodus = «DUAL» und W\u00e4hlplan = den einzigen vorhandenen W\u00e4hlplan ausw\u00e4hlen.<\/p>\n\n\n\n

    Zuvor musste das Deutsche Sprachpaket noch auf dem neuen Exchange-Server installiert werden.<\/p>\n\n\n\n

    Als Zertifikat wurde das Server-Zertifikat (von der internen CA ausgestellt) verwendet.<\/p>\n\n\n\n

    Folgende Befehle sind in diesem Zusammenhang relevant:<\/p>\n\n\n\n

    Enable-ExchangeCertificate -Thumbprint [THUMBPRINT] -Services UM,UMCallRouter<\/pre>\n\n\n\n
    Restart-Service MSExchangeUM ; Restart-Service MSExchangeUMCR<\/pre>\n\n\n\n
    Wenn den UM-Diensten ein Wildcard Zertifikat zugewiesen wird, wird folgende Fehlermeldung protokolliert (dies ist n\u00e4mlich nicht supported):<\/p>\n\n\n\n
    Certificate subject name .domain.ch is not valid. UM local monitoring sip options probe will fail System.ArgumentException: The specified routing host name '<\/em>.realit.ch' isn't valid
    bei Microsoft.Exchange.Data.Transport.RoutingHost..ctor(String address)
    bei Microsoft.Exchange.UM.UMCore.SipPeerManager.GetSipPeerFromUMCertificateSubjectName()<\/pre>\n\n\n\n
    Falsche Konfiguration des Startmodus erzeugt folgende Fehler:<\/p>\n\n\n\n
    The Microsoft Exchange Unified Messaging Call Router service failed to exchange the required certificates with an IP gateway to enable Transport Layer Security (TLS). Please check that the gateway is configured to operate in the correct security mode. If the gateway is required to operate in TLS mode, check that the certificates being used are correct. More information: \"A TLS failure occurred because the remote server disconnected while TLS negotiation was in progress. The error code = 0x80131500 and the message = Unknown error (0x80131500).\". Remote certificate: (). Remote end point: [IP SfB]:60589. Local end point: [IP Exchange 2016]:5061.\n<\/pre>\n\n\n\n
    Diese Meldung wird beim Neustarten des Dienstes angezeigt:<\/p>\n\n\n\n
    The Client Access server isn't currently enabled and the Microsoft Exchange Unified Messaging call router can't listen on any TCP\/UDP ports. Any existing connections will be disconnected.<\/pre>\n","protected":false},"excerpt":{"rendered":"
    Ich musste obige Migration vornehmen. Exchange-seitig ja kein Problem. Aber UM war f\u00fcr mich Neuland. Falls das nicht auf Anhieb… Read more<\/a><\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[5],"tags":[57,58,60,114],"class_list":["post-1323","post","type-post","status-publish","format-standard","hentry","category-allgemein","tag-exchange","tag-exchange-2010","tag-exchange-2016","tag-skype-for-business-2"],"_links":{"self":[{"href":"https:\/\/itblog.wildi.dk\/index.php?rest_route=\/wp\/v2\/posts\/1323","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/itblog.wildi.dk\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/itblog.wildi.dk\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/itblog.wildi.dk\/index.php?rest_route=\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/itblog.wildi.dk\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=1323"}],"version-history":[{"count":1,"href":"https:\/\/itblog.wildi.dk\/index.php?rest_route=\/wp\/v2\/posts\/1323\/revisions"}],"predecessor-version":[{"id":1425,"href":"https:\/\/itblog.wildi.dk\/index.php?rest_route=\/wp\/v2\/posts\/1323\/revisions\/1425"}],"wp:attachment":[{"href":"https:\/\/itblog.wildi.dk\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=1323"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/itblog.wildi.dk\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=1323"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/itblog.wildi.dk\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=1323"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}