Share your ideas with us
This idea has been merged into another idea. To comment or vote on this idea, please visit CUSTCOM-I-1137 Ring Central Video Ability to connect Non 365 Outlook Calendar- Feature Request.
Hi All, I would like to ask that the new Ring Central Scheduler is provided via a .msi or .exe file. Currently you have to log into the Microsoft Store to be able to get the Outlook Addin. For organizations that do not have Office 365 and have Exchange on premise turns this process of having to create a MS user for each employee and then logging that user into the MS Store just to be able to download the RC Scheduler. Please provide an .msi or .exe file to avoid these extra steps.
Maria, thanks for the heads up about the article. I have updated it.
We don't have msi or exe file. You could install RingCentral Scheduler via MS Store or you could install RingCentral Scheduler in the admin center: https://docs.microsoft.com/en-us/microsoft-365/admin/manage/manage-deployment-of-add-ins?view=o365-worldwide
Scheduler manifest link: https://apps.ringcentral.com/integration/office-add-ins/prod/rc/manifest.xml
Hi there- the article posted is no longer valid - is there an option to have as .msi?
Agreed! We have 365 in our organization for the subscription of Office, but do not subscribe to the cloud services. We still use an Exchange environment. In order for me to get an integrated scheduler, I would have to take on extra expense to upgrade my 365 subscription just to gain access the RC scheduler, which is just ridiculous.
We have scheduler working following those instructions for our on-premise Exchange 2016 server - Have found it easiest to get the URL to the .xml file referenced in the KB Becky posted and install in ECP (https://OWA_URL/ecp) under organization -> add-ins picking option to Add from URL
Hi Becky, this will not work unfortunately as we are running Exchange Server on premise and not 365. Really need this new plugin to work with on-prem Exchange Server as the RC Meetings Plugin did. Thanks ! Derek
Hey, does this KB work for your issue?
If not, please let us know.