Tag: Exchange on premises

cmdlet: Remove-InboxRule

Q: Is there a way to remove an Inbox rule for a mailbox? A: Yes. You can use the Remove-InboxRule cmdlet to remove an Inbox rule from a mailbox. Inbox rules process messages in an Inbox based on conditions specified and take actions. Removing an Inbox Rule can assist in troubleshooting end user’s mailboxes. Remove-InboxRule -Mailbox

cmdlet: Enable-InboxRule

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 and network ports

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

cmdlet: Disable-InboxRule

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

Outlook prompting for restart

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

cmdlet: Set-InboxRule

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

Support for Exchange 2013+ File Share Witness server in Azure

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

cmdlet: New-InboxRule

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

cmdlet: Get-InboxRule

Q: Is there a way to get a list of Inbox rules from a mailbox? A: Yes. The Get-InboxRule is available both on premises and online versions of Exchange. This cmdlet allows you to review all or specific Inbox rules on an end user’s mailbox. Get-InboxRule -Mailbox Joe@Contoso.com This example retrieves all Inbox rules for the

Load balancer design options

As I visit companies, I run into many that are doing different designs when it comes to leveraging load balancers. I’m not a network engineer and there is just way too much information to present in one article, but here are some thoughts at a high level design I’d like to share. TCP ports 80/443. In Exchange 2013, we