Q: Is there a way to enable an Inbox rule for a mailbox? A: Yes. You can use the Enable-InboxRule cmdlet to enable an Inbox rule. Inbox rules process messages in an Inbox based on conditions specified and take actions. The enable/disable InboxRule cmdelts, assist in troubleshooting end user’s mailboxes. Enable-InboxRule "Move To Junk Mail" -Mailbox

Exchange Certificates Prior to Exchange Server 2013, the Exchange application did not automatically notify administrators of a pending upcoming certificate expiring. One of the issues we administrators run into is expiring certificates. If the Exchange environment has a certificate that expires, then typically, trusted access via clients is interrupted. The good news is, you should ask

Q: Can network ports be restricted between Exchange servers within an environment? A: No. We continue to receive the question about putting firewalls in between Exchange servers. It’s a bad idea, so don’t do it. However, if your security team says you must do it, then we do have guidance available: https://blogs.technet.microsoft.com/exchange/2013/02/18/exchange-firewalls-and-support-oh-my/ The short answer

Q: Is there a way to disable an Inbox rule for a mailbox? A: Yes. You can use the Disable-InboxRule cmdlet to enable an Inbox rule. Inbox rules process messages in an Inbox based on conditions specified and take actions. The enable/disable InboxRule cmdelts, assist in troubleshooting end user’s mailboxes. Disable-InboxRule -Identity "MoveAnnouncements" -Mailbox "Joe@Contoso.com" This example

Q: We’re getting reports that Outlook is prompting users for a restart, is this normal? A: This is expected…once again. Even using Exchange 2013 or 2016 versions. History: The Exchange and Outlook product groups try their best to minimize any disruptions that impact end uses. However, sometimes there are technologies that are built in that

Q: Is there a way to change or set an Inbox rule on an end user’s mailbox? A: Yes. The Set-InboxRule cmdlet allows you to modify, enable, disable, or even create a rule with this cmdlet. Other than the Get-InboxRule cmdlet, one could argue, the Set-InboxRule is the only other cmdlet you need to know

The Exchange product group has announced support for putting your Exchange 2013 File Share Witness (FSW) server in Azure. http://blogs.technet.com/b/exchange/archive/2015/01/09/using-an-azure-vm-as-a-dag-witness-server.aspx I think this is the next big advancement with the marriage of Exchange and the cloud. Yes you can migrate to O365 and leverage all of the integration with: Exchange, Lync, SharePoint, OneDrive, Teams, and/or StaffHub. While some organizations do have the

Q: Is there a way to enable the rule option in Outlook? A: Yes. The ruler option in Word is also available in Outlook. Easy enough to turn on for specific client machines or for every Outlook client within your domain environment by applying a GPO. Set the following registry key value: [HKEY_CURRENT_USER\Software\Microsoft\Office\16.0\Word\Options\WordMail] "Ruler"=dword:00000001 (Enables

Q: Is there a way to create a new Inbox rule for a mailbox? A: Yes. The New-InboxRule cmdlet creates an Inbox rule to process messages and perform tasks for an Exchange mailbox. This cmdlet works both for on premises and online versions of Exchange. Actions can be taken such as move, copy, or even

Here is a quick and easy one line PowerShell script to set all of the Organizational Units (OU's) in your Active Directory (AD) to protect from accidental deletion. I know others have posted similar information, but it never hurts to raise awareness of this setting. And also, since I run into many customers that do