Chat icon missing after switching from Islands

[Helios Comms]

With our trial of Teams complete and with the impending sword of Damocles of the forced switch to Teams by Microsoft next month, I changed the org-wide setting from Islands to SfB only this evening and configured a handful of users (who have been using Teams in Islands for a while) over to Teams only.

According to this excellent article, this sounds like a sensible approach so you can migrate users to Teams under control. When org-wide is SfB and individual users are Teams, routing of instant messaging is more logical.

https://regarding365.com/beware-of-the-island-understanding-teams-and-skype-coexistence-modes-300bcf...

However, three hours later and whilst incoming calls are going into Teams on my PC, the chat icon is missing so I'm unable to IM other users (Sfb or Teams) or make a voice call.

Is this to be expected??

Org-wide settings:

My account:

[#2]

I read in another similar thread, that one should check with Get-CsOnlineUser so here is my account:

[#3]

I would wait til tomorrow and see if it’s still the same! Just check the messaging policy so chat isn’t disabled!

[#4]

If you were already running in islands for awhile you should have left it. You want to start out on Skype Only but if it's been sitting, you Changing it to Skype Only then to Teams Only, it probably took hold then got cached on Skype Only mode. Try signing out and back in, or checking web see if it's missing. The mode change delay and caching is terrible and really should have been addressed a long time ago before forcing upgrades.

Anyway, you might want to try setting it to Teams only again for yourself via powershell to see if it helps.

Grant-CsTeamsUpgradePolicy -PolicyName UpgradeToTeams -Identity user@user.com

[#5]

>If you were already running in islands for awhile you should have left it. 

That wasn't/isn't a viable option due to the islands works - it would cause all sorts of confusion with users. Those left in islands mode wouldn't be able to send instant messages to their colleagues using SfB. They'd have to remember to use Teams - and we've not rolled out the Teams app to everyone yet.

I've just raised a support ticket because 12+ hours later, the chat icon is still missing.

Just waiting to here from the other five users switched across whether they have chat functionality or it's just my account. I had switched my account to teams mode and then back to SfB a few weeks ago as part of the test.

I'll try your other suggestions as well.

This switch to Teams isn't going down too well with my client. They've already had confusion from their clients with existing meeting requests going out again and their clients saying they don't have Teams and why aren't we using Skype. Not good... Client has already said "Ohh forget it, let's just switch to Zoom". Knee jerk reaction but it does show a certain level of feeling.

[#6]

@Helios Comms 

and remember to do a proper logout of the Teams client! Just not close it..

Have you checked the web client? Other users yet?

In my experience 12 hours is sometimes not enough either :\

You should be able to use S4B - S4b when both is in Island mode or other user in S4b only mode!  That's the point of it! But if they are sending IM to aTeams Only user, it will land in Teams! 

Teams-only users can connect to existing and new Skype meetings via S4b client or webbapp, just not create them ( there is a less great work around though )

Also, the clients can connect to a Teams meeting via the web also! Will be same thing with Zoom! They have to get used to something else than Skype!!

[#7]

Later... the switch over to Teams is now just plain broken :(

The five other users switched over to "Teams only" are still receiving instant messages in SfB from users who are using the org-wide settings of "SfB only". That shouldn't be happening according to the documentation - when org-wide is set to "SfB" and some individual users are set to "Teams", instant messages should be routed to the correct client app.

They are caught in a sort of limbo where SfB says this when the launch it (so it knows they are using Teams), but messages are not been routed correctly.

[#8]

>In my experience 12 hours is sometimes not enough either :\

I suspect you're right. Yes, I've logged out of Teams. Can't send instant messages in any client: teams app on PC or Android, Teams on web or SfB.

However, the other five users do have the chat window in Teams. Just asking them to check where incoming calls go.

[#9]

Also, is there a way to determine where the migration process from SfB to Teams is up to?

[#10]

@Helios Comms 

What do you mean?

[#11]

We have org-wide settings S4B Only and early adopters are moved to Teams Only. The change in regards to chat usually takes at least eight hours but I have also seen 72 hours.

[#12]

It looks like there is some kind of queuing/task system that occurs when you switch a user from SfB to Teams as it isn't instant (hence the comments about 12 hours not been enough). Is there a way to get a report of the status of the migration per user?

I've had an update for the five other users. Their chat icon is working so it's just me with that problem. But even though everyone else is "SfB only" mode (via org-wide) and they are "Teams only" individually, messages sent from SfB are arriving in SfB, not the Teams app.

Fortunately, their PSTN voice functionality has switched across to Teams which was my biggest concern, i.e. they would be missing calls.

[#13]

There is no way that I am aware of to see the migration status. My guess is that the switch of the org-wide setting also will take a lot of time before it is replicated through out the system. I would also recommend the Teams users to quit the Teams app and start it again as it seems some caching is done on startup.

[#14]

Shame... whilst we're chatting here, the teams users are commenting that instant messages from SfB users are starting to come through in Teams so that's good news. I can't say whether this is a result of waiting a bit longer or me raising a support ticket. Unusually for Microsoft, they haven't called back/replied to ticket for over two hours. Normally they are on the phone pretty quickly.

So it's just my account that's struggling with the missing chat icon. I've shutdown the Teams app a couple of times.

Immediate problem with sharing screens between Teams and SfB users but suspect that's a different issue.

[#15]

Check your webclient also in between! Make sure not only shut down client but do a proper logout!

Screen sharing isn’t supported you need to set up a meeting for this

[#16]

Yeah. The upgrades are a mess. I e seen message routing take up to a week to converge. Microsoft said they are trying to make this less than 24 hours.

[#17]

Thanks Chris and everyone else who chipped in here. The switch over to Teams has settled down as the day has gone on and we're now over or at least understand some of the gotchas. I know Microsoft has been preparing us for this for months, but human nature is to put off something not that urgent. See PPI claims in the UK :)

The new PSTN voice features are worth the upgrade alone.