The day of the test came and I had 10 test accounts to do my worst.
DISABLE SKYPE FOR BUSINESS STARTUP REGISTRY WINDOWS
With all good due diligence I highlighted the importance of a test before arranging change windows with each site. would mean they temporarily lose dial capabilities to the PSTN. Meetings with the customer I highlighted that this process would lead to an outage period for the affected users because clearing, waiting for AzureAD sync etc. I had been working on a script that would collect people’s LineURIs from the msRTCSIP-Line attribute, clear the offending attribute and reapply the lineuri directly into Teams releasing the dependance to this attribute and thus allowing for the schema to be removed. I even cited the article I wrote a few weeks back to them: Īfter a lot of persuasion due to lack of clarification from Microsoft I convinced them to see caution and not remove the Schema until such time as we have successfully moved people’s phone number control over to Teams. You have a meeting and I called out that removing the Skype for Business schema is probably a bad idea since all user’s phone numbers are managed by the msRTCSIP-Line attribute as they are migrated accounts. The losing service provider now wants to decommission Skype for Business. You’ve successfully migrated 16,000 users across the globe from Skype for Business to Microsoft Teams after months of painstaking voice infrastructure deployments, number porting, and a truck load of user adoption and change management. Last week I endured the day from hell! Heed this warning otherwise it will happen to you.
0 kommentar(er)
