Announcement

Collapse
No announcement yet.

Outlook Programmatic Access

Collapse
X
 
  • Filter
  • Time
Clear All
new posts

    Outlook Programmatic Access

    When ranger tries to send email on our terminal server through outlook, outlook keeps asking for us to allow it. You must say yes every 10 minutes.

    We don't have this issue with other software on the server that uses POP, but ranger access outlook directly which causes this issue.

    The outlook security settings that disable the "Programmatic Access" are disabled on a server. Everyone is complaining.

    Can ranger be made to be compatible with this security feature?

    We didnt have this issue on our old server which was 2012R2, but it seems to be an office 2019 thing.

    Re: Outlook Programmatic Access

    Thank you for posting this.

    In case setting the 'Programmatic Access' to 'Never warn' does not help, then you should either update anti-virus on the terminal server or fix the Windows level problem regarding why it thinks that the anti-virus isn't configured correctly.

    You can read about this warning in this Microsoft's support article.

    Comment


      Re: Outlook Programmatic Access

      Microsoft AV detection is disabled on terminal servers. Doesn't matter which AV is installed, outlook doesn't detect it.

      What is the windows level problem we should fix?

      Comment


        Re: Outlook Programmatic Access

        That's on Outlook domain. I see that we also discussed a similar case with you a few months back (here), maybe the same would apply in this case, besides, maybe try to Google it, many answers there.

        Hope this helps.

        Comment


          Re: Outlook Programmatic Access

          If we did not use outlook, how does commit send emails?

          Comment


            Re: Outlook Programmatic Access

            We did discuss this very thing on that thread. The screenshot added by support was probably from a desktop. Those options are not available on a terminal server (maybe any server).

            Microsoft says "The generally accepted way to avoid problems is to use an updated version of the application that avoids setting off the security prompt"

            With 4 other programs on the server that send mail, ranger is the only one that causes this popup.

            How is this not a ranger issue?

            Comment


              Re: Outlook Programmatic Access

              Re no-Outlook - The RangerMSP client app will try to use the default email client installed on your PC, however, when it works - you don't have all the benefits you now do with Outlook, like using Email Templates or having sent email messages automatically filed in the app. So, Outlook is recommended.

              And, if you're using the Web interface, you can compose simple email replies, nothing fancy, that will be sent via the CRM Server Windows service that runs on your server.

              Re server - it's commonly used in similar configuration w/o any issues, or issues that cannot be resolved. Some apps working does not mean some of the Outlook security settings are valid and they need to get reviewed/changed. Unfortunately we do not have the knowledge of how to troubleshoot Outlook on all configurations, we have shared the details we're aware of or helped others. I hope it'll get resolved soon. Please keep us posted.

              Hope this helps.

              Comment


                Re: Outlook Programmatic Access

                If anyone has been following this, the main issue is how Ranger accesses outlook 2019 using a depreciated method.

                There are updated admx files that "seem" to addresses the outlook programmatic issue for server 2019.

                Comment

                Working...
                X