Forum Discussion
Skype to Teams Migration Issues (Skype Server Standard 2019 - On Prem 7.0.2046.244)
Hi all,
Just looking for some advice here for a Skype on-prem to Teams migration. I'll try keep this as short as possible but please find some info below:
Background
Customer A is moving from using Skype 2019 on prem with Anywhere365 core (also on-prem) over to Teams only with Anywhere365 dialogue cloud. We are at the stage where we are almost ready to switch over, however have uncovered some issues with the migration process to rehome the users. From reading it looks like Microsoft now require you to be on a minimum version of 2019 on-prem to be able to migrate the users over to Teams:
As of July 31, 2022, to move users between an on-premises deployment and the cloud, you must be using the following minimum versions of either Skype for Business Server or Lync Server:
On-premises product Required minimum version Required minimum build
| Skype for Business Server 2019 | CU6 | 7.0.2046.385 |
| Skype for Business Server 2015 | CU12 | 6.0.9319.619 |
| Lync Server 2013 | CU10 with Hotfix 7 | 5.0.8308.1182 |
The problem we have, I believe is basically down to the fact we have inheritied a Anywere365 and Skype installation which has not been kept up to date and is stopping us from progressing any further. Customer A is 24/7 so we are trying to find the best way around this without having to upgrade the Skype environment, Anywhere365 core (this is needed to work with newer versions of Skype) to then just bin these servers off after the migration. Its going to cause unecessary disruption and potential wasted engineer time.
Question
My question is, has anyone been in the same position with migrating skype for business 2019 on prem over to Teams and is there any workaround without upgrading the kit and successfully using hybrid connectivity with the migration commands?
Further Information
- I have done some testing with the current kit, all hybrid connectivity is configured I believe the migration failure is now just down to the skype version.
- I have tested a potential workaround, which involves deleting a user from on prem Skype (not removing their AD user) so that the majority of the skype flags against a user get cleared, line uri, enterprise voice config etc.. and allowed this to sync back to 365. I tried then applying the direct routing configuration on Teams only to still get an error that the user is using Skype on prem and to migrate them. I then went into on-prem AD and cleared the remaining msRTCSIP attribute which was the PrimaryHomeServer from SRV: to <not set>. When I have checked this morning, after the sync overnight to 365, the user is now showing with the correct attributes such as:
- HostingProvider : sipfed.online.lync.com
- AccountType : User
- TeamsUpgradeEffectiveMode : TeamsOnly
- TeamsUpgradeNotificationsEnabled : False
- TeamsUpgradeOverridePolicy :
- TeamsUpgradePolicy : UpgradeToTeamsThis would suggest to me that I can now correctly configure this user for direct routing which I am going to test this morning.
Its a bit of a dirty workaround however, it could be the preferred option depending on the upgrade possibilities and downtime. Has anyone done this before and would this cause issues in the future if the microsoft 'official' process isnt followed?
Any help or advice is appriciated!
Thanks
- Hi,
Just some general thoughts from me. The best would of course be that you upgrade SfB to the latest version.
Another option would be to try to move users without upgrading, the minimum supported version could be just for support in case you get case you get some issues, of course this is not recommended.
You could also remove the hybrid setup and change all Teams users to Teams Only and move over to Teams in a big bang. Users will not keep their contacts and meetings would not be migrated from SfB to Teams. But that could be a way.
