03-13-2019 07:09 AM
03-13-2019 07:09 AM
Not sure if I am running into a bug or if it's working as designed.
1. Skype for Business and Teams are both cloud based
2. AD is synced from On-prem, all accounts are local
3. Org default is "Islands" and My personal default is "Teams only"
Here is what I am seeing
I am only able to see presence of people who have Teams turned on, when I create a new Message to someone they do not get it unless they have Teams open.
A skype user is able to see my presence, they are able to IM me and I am able to respond. I am able to see their presence once they initiate the IM and I see two entries in my Teams client one of them the one they never receive and then one with Skype logo on it.
What I want is to be able to see Skype presence in Teams and be able to send IM's to skype users if they are not signed into Teams.
03-13-2019 09:03 AM
03-13-2019 09:06 AM - edited 03-13-2019 09:09 AM
Guessing because we haven't gotten to this point yet... You may have to set the user to a Skype for Business modality (via powershell SfBOnly, SfBWithTeamsCollab, SfBWithTeamsCollabAndMeetings) so the interop knows which client to target.
Reference https://aka.ms/teams-upgrade-deck - Slides 74 - 79. The matrix on slide 79 is really helpful.
EDIT/Advisory: You may want to set the modality to a test user to try it out... I recall that this was being worked on to revert a user back to Islands mode. Don't remember where I read it though.
03-13-2019 09:10 AM
03-13-2019 11:07 AM
So far, from our experience, setting the Org-Wide to Skype Only did not solve the problem (same issue as OP). I can only message people that have sent me a message first from Skype to Teams. I noticed in our setup, those messages actually have the Skype icon on the same line as the preview and it mentions at the top, this is a Skype user. I havent tried changing the Org-Wide to teams then switching the users to Skype yet.
03-13-2019 11:38 AM
03-13-2019 01:58 PM
I have the same issue. The problem here is in migration process from SfB to Teams and/or doing a POC. So we want to trial a group in teams, but the way it is setup right now does not work as advertised. We have over 1,000 users, so I can't just change the org wide setting to Teams Only easily. (Well that is debatable, I am decent with powershell but not these commands). However, I can't use the solution presented, because new users would be automatically added as Teams Only and we don't want that. So I would have to script around that as well. Would be nice if this was as easy as the video's and documents say it is. What is the point of the org-wide setting? Seems to be irrelevant.
On a side note, as the only one in my org who is Teams Only at the moment, My directory status simply says online, while everyone else's states "Hybrid (online)". Maybe this is why I can't initiate a chat with anyone in Skype? It seems to think they all have Teams up and running (Islands Mode).
03-13-2019 02:10 PM
03-14-2019 05:29 AM
Yea, I knew the islands would not work. However I expected when I set the org-wide setting to Skype Only that it would then work. But it doesn't. Sorry if I was not clear on that.
I did set the org wide to Skype Only using the web UI, and like others posted it did not change anything. So I don't know if that is because we were on islands initially? Maybe?
I will give your site a shot and use powershell to set it to Skype Only and see if that works.
I did figure out that group chat doesn't work in this scenario as you stated, found it in my testing.
Thanks Chris for being so involved in the community and sharing your knowledge and experience.
03-14-2019 06:02 AM
When did you change coexistence mode to SkypeOnly mode? I've seen delays for a couple of days up to a week before it works when moving from Islands to SkypeOnly. Microsoft support have not been able to help with this, it just started to work and then messages arrived in the Skype client as they should.
Also I recommend disable chat and Meetings when running SkypeOnly mode until the real SkypeOnly coexistence modes starts to roll out (starting 25th of March), you get an warning about this when you set SkypeOnly modes with powershell.
Grant-CsTeamsMessagingPolicy -Identity firstname.lastname@example.org -PolicyName “Disable Chat”
Grant-CsTeamsCallingPolicy -Identity email@example.com -PolicyName “DisallowCalling”
Grant-CsTeamsMeetingPolicy -Identity firstname.lastname@example.org -PolicyName “AllOff”
03-14-2019 06:04 AM
03-14-2019 06:10 AM
03-14-2019 07:45 AM
Thanks Linus and Chris!
I changed my org-wide setting a couple weeks ago, and the issues still remain. Interestingly I noticed that in my "suggested" people under chat it suggests users with the skype logo. Which was not the case before I change my org wide setting to SfB.
However when I attempt to type that same name in a new chat it goes to their teams account.
I will follow the information that you two have posted. I have been digging into the transition documentation, but it seems there is quite a bit of moving parts (coming features) and transition experience that would be nice to know without finding out the hard way.
03-26-2019 04:22 PM
we are seeing the same problem. Org has been changed to SkypeOnly, 3 test users have been set to TeamsOnly. After 72 hours, the test users are still unable to start a conversation with a Skype user from Teams (They can receive messages though)
03-26-2019 09:09 PM
03-27-2019 05:10 AM
It does eventually transition over. Our organization took over a week but at this point, when I search a person in teams, it will show they are using Skype and I can initiate the chat. One note, that I havent seen mentioned (and it does mentioned it in Teams); it will be with limited functionality. You cannot screen share which that one did not surprise me but the one thing that did... you cannot send attachments or screenshots. As one in IT, that is kind of a bummer, as I am always sending users screenshots and vise versa. The screen share is not a big deal as we use Teamviewer.
03-27-2019 11:07 AM
@Chris Webb It doesnt work in the web client yet either. The change was made on Sunday, so I'll keep waiting. Concerning to see there is this much delay because when we start moving people over to Teams Only, the response we have to give end users is 'it will work sometime in the next week, i dont know when'
03-27-2019 11:50 AM
03-27-2019 12:11 PM - edited 03-27-2019 12:12 PM
I switched the entire company to Skype for Business only (and myself and a couple others are Teams Only)
After waiting over the weekened, now when I initiate a conversation in Teams with a user I've never chatted with before, some will show up as "Using Skype for Business" and these chats work perfectly, but some show up as just "Starting a new conversation" and these continue to not work. Will wait another week or two to see if these start moving over.
03-28-2019 02:41 AM
03-28-2019 07:04 AM
Looks like we'll just have to force everyone over to Teams as fast as possible to avoid interruption. Good thing we only have 500 some employees - how would you deal with this if you have 5-10k? Why couldn't Microsoft just release an update that turns Skype for Business into Teams... I don't understand.
03-28-2019 07:12 AM
03-28-2019 07:27 AM
Oh I am not upset we have to move to Teams, it is a lot better than S4B, it's just frustrating how the upgrade process works (or doesn't work)
03-28-2019 08:21 AM
I have been working with support on it. What I had to do to get it to work is
1. Set One user to SFB only and the other Teams only
2. They made me clear out all of the SFB users AppData for Lync/SFB and Credentials Manager
3. Made me delete Teams only users lot files in AppData (not sure if that one was necessary)
Then once both logged back in it finally recognized that SFB only user
03-28-2019 09:07 AM
@Daniel Schmidt That's good info there.
@microsoft feel like it should be written into an article for troubleshooting... maybe a best practice to run a script to clear out caches on first run when modalities are turned on during off hours for users. Maybe publish near this article in particular: https://docs.microsoft.com/en-us/microsoftteams/migration-interop-guidance-for-teams-with-skype ;) ;) Nudge Nudge saynomore.