Unsolved Outlook 2016 conference room access denied
-
It was working fine in Outlook 2013?
-
It did as of three weeks ago.
My user is trying it on their backup machine now.
-
The user has reported that YES it does work as before in Outlook 2013.
-
You sure it isn't a borked Outlook profile on that 2016 instance?
-
@AVI-NetworkGuy said:
You sure it isn't a borked Outlook profile on that 2016 instance?
Pretty sure, it happens to both the mentioned user and myself, both of us have clean installed Windows 10 Pro machines with Office 2016 KMS version.
I also created a second Outlook profile on my machine for my domain admin user to make sure it wasn't a permissions issues with the conference room - same issue. But as I mentioned above... my normal user also has god like rights over the conference account.
-
This sounds like there may be a compatibility issue between Exchange 2010 and Outlook 2016.
-
@coliver said:
This sounds like there may be a compatibility issue between Exchange 2010 and Outlook 2016.
Yeah, I'm thinking the same thing. Time to upgrade I guess.
I need to anyhow - I want to move everyone in my office office of Outlook and into OWA use full time. That will make the migration to O365 possible for me. Otherwise cached mode in Outlook prevents me from going to O365 because I need live, real time access to the physician's calendars.
-
@Dashrender said:
@coliver said:
This sounds like there may be a compatibility issue between Exchange 2010 and Outlook 2016.
Yeah, I'm thinking the same thing. Time to upgrade I guess.
I need to anyhow - I want to move everyone in my office office of Outlook and into OWA use full time. That will make the migration to O365 possible for me. Otherwise cached mode in Outlook prevents me from going to O365 because I need live, real time access to the physician's calendars.
Haha... good luck moving people away from Outlook... you're going to have so much pushback it probably isn't worth it.
One of the things that you could do is setup each physician with a Sharepoint Online calendar. This would make access for other users 100x easier and management would be that much simpler as well.
-
@coliver said:
One of the things that you could do is setup each physician with a SharePoint Online calendar. This would make access for other users 100x easier and management would be that much simpler as well.
That would only work if the SP calendar can be set as the primary sync'ed calendar to the physician device of choice (iPhone, iPad, Android device, etc).
I've done a tiny amount of searching for a calendaring only app that we might be able to use that would break it away from Outlook altogether, an app that also has a mobile version for the physician devices... I didn't find anything the last time I looked.
If you have a suggestion, I'm all ears.
-
Also, why do you think it will be hard? OWA 2010 looks very close to Outlook 2010, OWA 2013 looks very much like Outlook 2013. We use no advanced features or add-ons (unlike @Minion-Queen ) so that's not a worry.
-
@Dashrender said:
@coliver said:
One of the things that you could do is setup each physician with a SharePoint Online calendar. This would make access for other users 100x easier and management would be that much simpler as well.
That would only work if the SP calendar can be set as the primary sync'ed calendar to the physician device of choice (iPhone, iPad, Android device, etc).
I've done a tiny amount of searching for a calendaring only app that we might be able to use that would break it away from Outlook altogether, an app that also has a mobile version for the physician devices... I didn't find anything the last time I looked.
If you have a suggestion, I'm all ears.
Sharepoint Calendars are CALdav calendars. You should be able to add them to anything that does CALDav. Have you checked the Outlook app on Android and iOS. I'm pretty sure you can sync Sharepoint Calendars with it.
-
@Dashrender said:
Also, why do you think it will be hard? OWA 2010 looks very close to Outlook 2010, OWA 2013 looks very much like Outlook 2013. We use no advanced features or add-ons (unlike @Minion-Queen ) so that's not a worry.
Because people are adverse to change.
-
@coliver said:
@Dashrender said:
Also, why do you think it will be hard? OWA 2010 looks very close to Outlook 2010, OWA 2013 looks very much like Outlook 2013. We use no advanced features or add-ons (unlike @Minion-Queen ) so that's not a worry.
Because people are adverse to change.
Touche - though because things look pretty much the same, I think this will be an easy change. Who knows.. I could be wrong.
-
@Dashrender said:
@coliver said:
@Dashrender said:
Also, why do you think it will be hard? OWA 2010 looks very close to Outlook 2010, OWA 2013 looks very much like Outlook 2013. We use no advanced features or add-ons (unlike @Minion-Queen ) so that's not a worry.
Because people are adverse to change.
Touche - though because things look pretty much the same, I think this will be an easy change. Who knows.. I could be wrong.
I had issues with people not liking Outlook 2013 and requesting 2010... which was denied. OWA may not look different but it works differently enough to cause some issues with people who don't like to experiment. Your users may be much better at the adaptation though.
-
@coliver said:
@Dashrender said:
@coliver said:
@Dashrender said:
Also, why do you think it will be hard? OWA 2010 looks very close to Outlook 2010, OWA 2013 looks very much like Outlook 2013. We use no advanced features or add-ons (unlike @Minion-Queen ) so that's not a worry.
Because people are adverse to change.
Touche - though because things look pretty much the same, I think this will be an easy change. Who knows.. I could be wrong.
I had issues with people not liking Outlook 2013 and requesting 2010... which was denied. OWA may not look different but it works differently enough to cause some issues with people who don't like to experiment. Your users may be much better at the adaptation though.
LOL - I could only wish, but yeah.. they are not. But they are such limited users, in general, that they will barely notice the difference. That said, a few, like my boss, will definitely notice and she may or may not like OWA. But for her it wouldn't matter as much, since she's not in their calendars very often.
-
@Dashrender said:
@coliver said:
@Dashrender said:
@coliver said:
@Dashrender said:
Also, why do you think it will be hard? OWA 2010 looks very close to Outlook 2010, OWA 2013 looks very much like Outlook 2013. We use no advanced features or add-ons (unlike @Minion-Queen ) so that's not a worry.
Because people are adverse to change.
Touche - though because things look pretty much the same, I think this will be an easy change. Who knows.. I could be wrong.
I had issues with people not liking Outlook 2013 and requesting 2010... which was denied. OWA may not look different but it works differently enough to cause some issues with people who don't like to experiment. Your users may be much better at the adaptation though.
LOL - I could only wish, but yeah.. they are not. But they are such limited users, in general, that they will barely notice the difference. That said, a few, like my boss, will definitely notice and she may or may not like OWA. But for her it wouldn't matter as much, since she's not in their calendars very often.
You should buy a license or two O365, through a partner, just to test with. You will get an email address of [email protected] which is mostly route-able.
-
@coliver said:
You should buy a license or two O365, through a partner, just to test with. You will get an email address of [email protected] which is mostly route-able.
To what end exactly?
I have in-house Exchange. Currently on 2010, though soon I'll be moving to 2016. Won't OWA there be the same as O365?
-
@Dashrender said:
@coliver said:
You should buy a license or two O365, through a partner, just to test with. You will get an email address of [email protected] which is mostly route-able.
To what end exactly?
I have in-house Exchange. Currently on 2010, though soon I'll be moving to 2016. Won't OWA there be the same as O365?
Yes. But now you can build a test environment to show off a few things to get management buy in.
-
@coliver said:
@Dashrender said:
@coliver said:
You should buy a license or two O365, through a partner, just to test with. You will get an email address of [email protected] which is mostly route-able.
To what end exactly?
I have in-house Exchange. Currently on 2010, though soon I'll be moving to 2016. Won't OWA there be the same as O365?
Yes. But now you can build a test environment to show off a few things to get management buy in.
You mean like SP?
-
@Dashrender said:
@coliver said:
@Dashrender said:
@coliver said:
You should buy a license or two O365, through a partner, just to test with. You will get an email address of [email protected] which is mostly route-able.
To what end exactly?
I have in-house Exchange. Currently on 2010, though soon I'll be moving to 2016. Won't OWA there be the same as O365?
Yes. But now you can build a test environment to show off a few things to get management buy in.
You mean like SP?
Sharepoint, ODfB, Office Online, etc... there are a ton of tools available that may be useful to people if they knew they were there.
