User Profile
MattShafer
Copper Contributor
Joined Jul 28, 2020
User Widgets
Recent Discussions
Re: iOS - Guided access app unavailable. please contact your administrator
As far as I know, MS is ending the Company Portal enrollment model. (see https://techcommunity.microsoft.com/t5/intune-customer-success/move-to-setup-assistant-with-modern-authentication-for-automated/bc-p/3193803#M3192) Our company has the exact same scenario as you, but we've made the jump to Setup Assistant with Modern Auth. The scenario you describe where the process jumps all over the place due to Apple's prompts stepping on the MS ones is a huge struggle.... but you can get the device enrolled. All I can say is make some noise.23KViews0likes0CommentsRe: Sync button on channel not working anymore
We are also seeing the same problem across Teams, OneDrive, and Windows builds. I just tested on my machine which is one of the more up to date in the org and the behavior is the same. Teams: 1.3.00.34662 (32-bit) OneDrive: 21.011.0117.0001 Windows: 19042.746 Using the SharePoint workaround is acceptable, but our service desk is getting a lot of questions as to why they can't use this sync button and then disbelief that it "just doesn't work"2.3KViews0likes1CommentRe: User Mailbox migrated to EXO, still no calendar in Teams
ChrisWebbTech and LinusCansby Thanks for your responses. The synchronization in the background, and not-so-instant nature of O365, is understood. The issue I have is the inconsistency with the timeline. Some users are instant, others take 24 hours, others have taken multiple (so far as many as 5) days. My first test user was instantaneous, but that has not held true for any subsequent migrations even with the same account. I really hope I don't need to tell my ~600 users that after migration they may need to wait up to a week, or not at all, for something as simple as calendar access to be granted. I have to say I'm a bit shocked by everyone's position that this is acceptable. As for troubleshooting, we have attempted all of the following to move it along without success. This indicates to me it's a backend issue. close and reopen application sign out and sign in reinstall of Teams on PC (system wide installer) We have also investigated MDM as a possible contributor, and have ruled it out I hear your point about it being enabled on the client. However, the behavior is the same across all access methods (PC, web, native iOS). This is "the big feature" that really makes Teams shine for them post migration because there is so much integration between EXO and Teams. It's very frustrating that Microsoft can't make it reasonably consistent. In many companies, a frustrating initial experience can be a death stroke for an application before it even gets started, and that is my fear here. We are already combating the, "Why do we need Teams when we have Skype" people. This will be my users first experience with Microsoft 365 as a SaaS app. We have deployed the CTR apps for years with on-prem services. Also, sometimes a Friday night migration is not appropriate as not all businesses stop for the weekend, or have a consistent 5-day 8-5 M-F work week. In answer to the specific question about completing the batch, yes they are being completed manually, so far within an hour of the initial sync completing. I appreciate the responses.13KViews0likes0CommentsRe: User Mailbox migrated to EXO, still no calendar in Teams
PeterRising We had a test account that experienced this first. We had moved the test account up to EXO, and had full teams functionality immediately. Testing functionality, we moved it back to our on-prem servers to confirm we could do it (business req); then moved it back up to EXO successfully. After this migration it took 4 full calendar days to appear, during which time I ran the mentioned support case. Support closed it claiming something I did in troubleshooting resolved the issue. Yesterday I migrated my account as the first LIVE user account to move from on-prem to EXO. Nearly 24 hours later, almost to the minute, from my migration it has appeared without warning. I migrated another user later in the day yesterday. That user's migration ended up completing around midnight last night. They still do not have the calendar, but do have other EXO integrated apps like To-do. Hopefully when they log in tomorrow morning, they will have the calendar. It's a bit anticlimactic considering this is one of the key features users will be looking for (that we're missing on EX2013). I'm really looking to see if there's any PowerShell cmdlet or script I can run to help make this more consistent.14KViews0likes3CommentsUser Mailbox migrated to EXO, still no calendar in Teams
All the research I've done has shown that while the organization is in Hybrid mode with Exchange 2013 on-prem, the on-prem mailbox users will not be able to access the Calendar and some other functions in Teams. It also shows that once we migrate said user's mailbox to Exchange Online (assuming proper licensing) that the functionality should appear. I have observed that it can take days (up to 4) for this to happen and provide the user full functionality. I've ran a case on this and support has not been helpful. Has anyone else encountered this? The calendar is still missing in Teams after migrating to O365.Solved14KViews0likes9Comments
Recent Blog Articles
No content to show