![]() Recently I had to troubleshoot Office Web Apps Server deployments at a couple of customer sites. If you to have strange errors like not being able to forward calls, check for pending windows updates, install them and reboot the server.It is also a good practice to patch the clients the same time you patch the servers, since each, client and server, may be part of a solution to a problem.For a more detailed description on how to patch your servers I find this blogpost to be most helpful by Charbel Hanna.Reboot is not required after this procedure.When patching your servers it is a good thing to stop all Lync services first, patch the server and then restart the services.Remember, all servers with UCMA installed, like Exchange, should be patched for Lync as well.This will give you all involved servers, including gateways which you should ignore.To find what servers have core components installed, you can run this cmdlet.Since all servers should be at the same patch level, it is a good practice to check installed version on all of the servers with core components installed, including trusted servers.A good way to check the patch number with what time it was deployed I check the list in this blogpost by Murat.$Properties = Get-ADUser -Filter | ft Name, Version -AutoSize #Get all msRTCSIP properties for a user that has a value Based on the type of configuration the user had before servers were removed, the properties with a value may be different per user so using ‘msRTCSIP*’ is a good way to catch the attributes for that specific user. More often than not, we see that this command is not run before decommissioning the deployment, so you need to remove the properties manually, here is a routine to detect all msRTCSIP attributes and then to clear them in Active Directory. The best way is to use Disable-CsUser to remove all Skype for Business related attributes on a user. If InterpretedUserType has the value of HybridOnpremSfBUser, then you need to clean up on-premises attributes if you are fully moving to Microsoft Teams and are decommissioning your on-premises deployment. ![]() Read this useful GitHub article that goes into this in more detail If for some reason the user is disabled it will show in this attribute as something with disabled such a s DirSyncDisabledSfBUser. ![]() If you have any attributes in local Active Directory it will be set to HybridOnpremSfBUser. InterpretedUserType – is a great source of information.If you clear this attribute, you get write access to the OnPremLineURI online. You should also know that if you are not able to set OnPremLineURI using Set-CsUser using online PowerShell, then you have msRTCSIP-LineURI populated in local Active Directory. This is good to know if you are troubleshooting why LineURI is not updated by OnPremLineURI for Direct Routing. LineURI, OnPremLineURI, and VoicePolicy – if your VoicePolicy is set to BusinessVoice you have a Calling Plan assigned, if it is set to HybridVoice, you are using Direct Routing.UsageLocation is set using the MSol PowerShell module. You should supplement with TenantDialplans, don’t crate them yourself, use by MVP Ken Lasko. The default DialPlan just adds a plus and country code to whatever you type in Teams and is rarely good enough. It decides the number you get as part of AudioConferencing and your DialPlan. UsageLocation, DialPlan, and TenantDialPlan – When using enterprise voice together with Microsoft Teams, UsageLocation is important.TeamsUpgradeEffectiveMode – Should be set to TeamsOnly, if not, try to change it again and look at the error message.Hope this helps you in your post-migration cleanup process Get-CsOnlineUser | Format-List UserPrincipalName, DisplayName, SipAddress, Enabled, TeamsUpgradeEffectiveMode, EnterpriseVoiceEnabled, HostedVoiceMail, City, UsageLocation, DialPlan, TenantDialPlan, OnlineVoiceRoutingPolicy, LineURI, OnPremLineURI, OnlineDialinConferencingPolicy, TeamsVideoInteropServicePolicy, TeamsCallingPolicy, HostingProvider, InterpretedUserType, VoicePolicy, CountryOrRegionDisplayName I found that this Skype for Business Online PowerShell oneliner gave me the overview I needed to see if there were configuration issues or wrong settings. If the migration also includes moving Enterprise Voice workloads and switching to a Direct Routing or Calling Plan setup, you may find it difficult to get a full overview of what state the user is in and if all settings are correct. When migrating from Skype for Business Server to Microsoft Teams you may find that users are not migrated with the correct features as intended.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |