-
Notifications
You must be signed in to change notification settings - Fork 214
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Automatically detect New Outlook client #1826
Comments
I had to install the new Outlook client, but I found as long as the old client is still present, OGCS will connect to it and use it for syncing. This is working fine for me, but I am glad that you had the notice that the new client doesn't work because I was about to uninstall the old client. |
Thanks for posting, very useful information 👍🏻 |
Not sure where to add this comment, but it looks like my work's policy has me switched over to the 'new' Outlook client, if/when you have a portable version for it, I'd be happy to help out with testing if it'd be useful. |
@TheJacksonian Does that mean the old Outlook client has been uninstalled and/or they've removed the toggle to switch back? |
@phw198 - I can still switch between the 2, but I am trying to get used to the new one. I find I have to switch to the old one, fire up OGCS then switch back to the new one. As the user above states, it's then a slight issue with the reminders popping up from both. |
Is your feature request related to a problem? Please describe.
If users try and use OGCS against the New Outlook, it will not work.
Describe the solution you'd like
Proactively detect the issue and direct the user to guidance/documentation on what to do if they wish to use OGCS (revert back to "old" Outlook).
The text was updated successfully, but these errors were encountered: