{"id":2198,"date":"2021-01-23T10:37:17","date_gmt":"2021-01-23T10:37:17","guid":{"rendered":"https:\/\/modern-workplace.uk\/?p=2198"},"modified":"2021-01-24T05:03:34","modified_gmt":"2021-01-24T05:03:34","slug":"teams-virtual-sbc-closing-azure-network-ports-warnings-for-azureloadbalancer-and-virtualnetwork-2-2-2","status":"publish","type":"post","link":"https:\/\/modern-workplace.uk\/?p=2198","title":{"rendered":"Teams &#8211; Removing (Decommissioning) Skype for Business Server after Microsoft Teams migration"},"content":{"rendered":"\n<p style=\"font-size:18px\">As a starting point when removing Skype for Business (SfB) from an on-premises domain, there must be a decision about removing JUST the SfB topology from the on-premises deployment or if you want to remove also the Active Directory schema preparation that was required to install SfB in the first place.<\/p>\n\n\n\n<p style=\"font-size:18px\">In this post I will outline how to safely remove the SfB topology.<\/p>\n\n\n\n<p style=\"font-size:18px\">Let me advise against removing the schema modification. I see no massive benefits in that and, as a main motivation not to remove the schema, please remember that all migrated user phone numbers are still managed by the msRTCSIP-Line attribute.<\/p>\n\n\n\n<p class=\"has-vivid-red-color has-text-color\" style=\"font-size:18px\">By the way, the above is also a motivation NOT TO run the massive SfB user disable Get-CsUser | Disable-CsUser -Verbose that is often suggested, if you did not have a prior preparation.<\/p>\n\n\n\n<p style=\"font-size:18px\">If you still want to remove the schema, take a look to Mark Vale\u2019s blog here for a detailed explanation on this specific topic<\/p>\n\n\n\n<p class=\"has-vivid-cyan-blue-color has-text-color\" style=\"font-size:18px\"><a href=\"https:\/\/online.commsverse.com\/do-not-remove-skype-for-business-until-you-have-read-this\/\">https:\/\/online.commsverse.com\/do-not-remove-skype-for-business-until-you-have-read-this\/<\/a><\/p>\n\n\n\n<p style=\"font-size:18px\">I will assume that:<br>\u2022 All the users, analog devices, meeting rooms and response groups heve been already migrated to Microsoft Teams<br>\u2022 Skype for Business hybrid has been removed, as for this Microsoft document \u201cDisable hybrid to complete migration to the cloud\u201d<\/p>\n\n\n\n<p class=\"has-vivid-cyan-blue-color has-text-color\" style=\"font-size:18px\"><a href=\"https:\/\/docs.microsoft.com\/en-us\/skypeforbusiness\/hybrid\/cloud-consolidation-disabling-hybrid\">https:\/\/docs.microsoft.com\/en-us\/skypeforbusiness\/hybrid\/cloud-consolidation-disabling-hybrid<\/a><\/p>\n\n\n\n<p class=\"has-large-font-size\">Emptying the SfB deployment <\/p>\n\n\n\n<p style=\"font-size:18px\">(All the commands have to be executed on one of the Front Ends from the Skype for Business Server Management Shell)<\/p>\n\n\n\n<p style=\"font-size:18px\">\u2022 Remove ONLY the users still on the on-premises pools<\/p>\n\n\n\n<p><code>Get-CsUser -Filter {RegistrarPool -eq \"CurrentPoolFqdn\"} | Disable-CsUser -Verbose<\/code><\/p>\n\n\n\n<p class=\"has-black-color has-text-color\" style=\"font-size:18px\">\u2022 Remove Exchange UM Contacts:<\/p>\n\n\n\n<p style=\"font-size:18px\"><code>Get-CsExUmContact | Remove-CsExUmContact<\/code><br><br>\u2022 Remove Voice Routes<\/p>\n\n\n\n<p style=\"font-size:18px\"><br><code>Get-CsVoiceRoute | Remove-CsVoiceRoute<\/code><\/p>\n\n\n\n<p style=\"font-size:18px\"><br>\u2022 Remove Conferencing Directories (-Force could be required)<\/p>\n\n\n\n<p style=\"font-size:18px\"><br><code>Get-CsConferenceDirectory | Remove-CsConferenceDirectory<\/code><\/p>\n\n\n\n<p style=\"font-size:18px\"><br>Note: you could have to execute this one again when publishing the topology, if you have an error message<\/p>\n\n\n\n<p style=\"font-size:18px\"><br>\u2022 Remove Call Park Orbit policies<\/p>\n\n\n\n<p style=\"font-size:18px\"><br><code>Get-CsCallParkOrbit | Remove-CsCallParkOrbit<\/code><\/p>\n\n\n\n<p style=\"font-size:18px\"><br>\u2022 Remove Unassigned Number configuration<\/p>\n\n\n\n<p style=\"font-size:18px\"><br><code>Get-CsUnassignedNumber | Remove-CsUnassignedNumber<\/code><\/p>\n\n\n\n<p style=\"font-size:18px\"><br>\u2022 Remove Analog Devices<\/p>\n\n\n\n<p style=\"font-size:18px\"><br><code>Get-CsAnalogDevice | Remove-CsAnalogDevice<\/code><\/p>\n\n\n\n<p style=\"font-size:18px\"><br>\u2022 Remove Skype for Business meeting rooms<\/p>\n\n\n\n<p style=\"font-size:18px\"><br><code>Get-CsMeetingRoom | Remove-CsMeetingRoom<\/code><\/p>\n\n\n\n<p style=\"font-size:18px\"><br>\u2022 Remove Response Group workflows<br><\/p>\n\n\n\n<p style=\"font-size:18px\"><code>Get-CsRgsWorkflow | Remove-CsRgsWorkflow<\/code><\/p>\n\n\n\n<p style=\"font-size:18px\"><br>\u2022 Remove trunk configuration<\/p>\n\n\n\n<p style=\"font-size:18px\"><br><code>Get-CsTrunkConfiguration | Remove-CsTrunkConfiguration<\/code><\/p>\n\n\n\n<p class=\"has-large-font-size\">Removing the deployment<\/p>\n\n\n\n<p class=\"has-large-font-size\" style=\"font-size:18px\">1) Open the Topology Builder<br>2) Click Action and navigate to Topology<br>   &#8211; Remove any PSTN Gateway<br>   &#8211; Remove any Persistent Chat Server<br>3) Action &gt; Topology &gt; Remove Deployment<br>4) Action &gt; Topology &gt; Publish. This will publish the removal configuration.<br>5) Progress through the &#8220;Publish the topology&#8221; wizard. If you have trusted applications in the topology you will have a warning that you have to acknowledge before proceeding<br>6) You will still see the last Front End in your topology. Finalize the Skype for Business topology decommission running the following command from the Skype for Business Server Management Shell<\/p>\n\n\n\n<p class=\"has-vivid-purple-color has-text-color\" style=\"font-size:18px\"><code>Publish-CsTopology -FinalizeUninstall<\/code><\/p>\n\n\n\n<p style=\"font-size:18px\"><br>Remove the Configuration Store Location from Active Directory:<\/p>\n\n\n\n<p class=\"has-vivid-purple-color has-text-color\" style=\"font-size:18px\"><br><code>Remove-CsConfigurationStoreLocation<\/code><\/p>\n\n\n\n<p class=\"has-large-font-size\">Note<\/p>\n\n\n\n<p style=\"font-size:18px\">Sometimes, when publishing the topology, you could have the following errors<br><\/p>\n\n\n\n<p style=\"font-size:18px\"><code>Warning: Access control entry (ACE) XXXXXXXX\\RTCUniversalServerReadOnlyGroup; Allow; GenericRead; None; None<br>Warning: The access control entries (ACEs) on the object \"computers container\" are not ready<\/code><\/p>\n\n\n\n<p style=\"font-size:18px\"><br>If Skype for Business Server administrators are not domain administrators, the RTCUniversalServerAdmins group needs the right permissions. Verify it running<\/p>\n\n\n\n<p style=\"font-size:18px\"><br><code>Test-CsSetupPermission -ComputerOU \"ou=CsServers,dc=litwareinc,dc=com\"<\/code><br><\/p>\n\n\n\n<p style=\"font-size:18px\">The result must be \u201cTrue\u201d<br>If the result is false. fix the error running <\/p>\n\n\n\n<p style=\"font-size:18px\"><code>Enable-CsAdDomain -Domain \u201cYourDomain.com\u201d<\/code><\/p>\n\n\n\n<p style=\"font-size:18px\">(More information in the Microsoft document below)<\/p>\n\n\n\n<p class=\"has-vivid-cyan-blue-color has-text-color\" style=\"font-size:18px\"><br>https:\/\/docs.microsoft.com\/en-us\/skypeforbusiness\/manage\/test-admin-topology-rights<\/p>\n","protected":false},"excerpt":{"rendered":"<p>In this post I will outline how to safely remove the Skype for Business topology<\/p>\n","protected":false},"author":1,"featured_media":2211,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_sitemap_exclude":false,"_sitemap_priority":"","_sitemap_frequency":"","twitterCardType":"","cardImageID":0,"cardImage":"","cardTitle":"","cardDesc":"","cardImageAlt":"","cardPlayer":"","cardPlayerWidth":0,"cardPlayerHeight":0,"cardPlayerStream":"","cardPlayerCodec":"","footnotes":""},"categories":[765,753,752,757,690],"tags":[762,759,751,77,691,755],"class_list":["post-2198","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-765","category-microsoft365","category-microsoft-teams","category-office-365","category-skype-for-business","tag-microsoftteams","tag-microsoft-365","tag-microsoft-teams","tag-office-365","tag-skype-for-business","tag-teams"],"_links":{"self":[{"href":"https:\/\/modern-workplace.uk\/index.php?rest_route=\/wp\/v2\/posts\/2198","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/modern-workplace.uk\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/modern-workplace.uk\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/modern-workplace.uk\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/modern-workplace.uk\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=2198"}],"version-history":[{"count":23,"href":"https:\/\/modern-workplace.uk\/index.php?rest_route=\/wp\/v2\/posts\/2198\/revisions"}],"predecessor-version":[{"id":2223,"href":"https:\/\/modern-workplace.uk\/index.php?rest_route=\/wp\/v2\/posts\/2198\/revisions\/2223"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/modern-workplace.uk\/index.php?rest_route=\/wp\/v2\/media\/2211"}],"wp:attachment":[{"href":"https:\/\/modern-workplace.uk\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=2198"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/modern-workplace.uk\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=2198"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/modern-workplace.uk\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=2198"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}