Many of the clients I work with have been taken an interest in implementing warning banners for all emails received from outside of their organizations in an effort to combat the ever increasing phishing emails that make it through their SPAM filters. A great write
I recently had to deploy SecurEnvoy 2FA with Exchange Server 2016’s OWA and noticed that there wasn’t official documentation for the configuration so I thought I’d write this blog post to outline the steps I used. Note that the steps outlined in the Exchange 2013
Problem You’ve completed configuring your Exchange 2013/2016 OWA (Outlook Web App) for 2-factor authentication with SecurEnvoy and proceed to test the login portal: You’re proceed to enter the 2nd factor passcode: The authentication is successful with the following message displayed: Authentication OK Logging on to
Problem You’ve been using the Test-ExchangeServerHealth.ps1 Exchange Server health check script for sometime but noticed that it has began falsely reporting the Client Access Server Role, Hub Transport Server Role, Mailbox Server Role and Mailbox Server Role services as being in a Fail state: Solution
Problem You’ve downloaded the latest SecurEnvoy Version 9.1.501 package as of May 2018 from: https://www.securenvoy.com/support/downloads.shtm Then used the following guide to configure your on-premise Exchange 2016 OWA access for 2FA: Microsoft Outlook Web Access 2013 – SecurEnvoy https://www.securenvoy.com/IntegrationGuides/Microsoft/Outlook-Web-Access-2013.pdf … but receive the following error when
I’ve been asked several times in the past by colleagues how would they go about monitoring Exchange message queues so that they would be notified if a threshold is exceeded and while I usually recommend looking for this feature in their existing monitoring solution, an
Most enterprise environments have solutions that provide monitoring services to ensure Microsoft Exchange Server services are running and if they are not, restart the service and send an email notification to administrators but I have constantly come across smaller business that may not be able
Problem You’ve just completed integrating Skype for Business Server 2015 with Exchange Server 2016 Unified Messaging to provide voicemail services but noticed that voicemails left for users are not being delivered and the following errors are being logged on the Exchange 2016 server: Log Name:
Problem You would like to migrate Exchange 2016 resource mailboxes from one database to another but noticed that the Move Mailbox To another database is not available when you select the resource mailbox: Shared mailboxes does not have this issue: Solution I’m not sure if
Problem You’ve started the installation of Exchange Server 2016 Cumulative Update 7 but notice that it fails at the step Mailbox role: Transport service with the following error: Error: The following error was generated when “$error.Clear(); Install-ExchangeCertificate -services IIS -DomainController $RoleDomainController if ($RoleIsDatacenter -ne $true
