This script helps you to configure mailbox quotas for
on a database level across all Exchange Server 2013/2016 databases in your environment or for a specific user.
Set all Exchange 2013/2016 databases to 1GB max mailbox size and use default percentage (90%/80%) for prohibit send and issue warning.
.\Set-MailboxQuota.ps1 -MaxMailboxSize 1GB -AllDatabases
Set max mailbox size to 10Gb for a dedicated user and use default percentage (90%/80%) for prohibit send and issue warning.
.\Set-MailboxQuota.ps1 -EmailAddress firstname.lastname@example.org -MaxMailboxSize 10GB
Join ENow on Sept. 24 during MSExchange Con 2015 for our segment “Can You Trust Office 365?” hosted by ENow’s Exchange Server MVP Michael Van Horenbeeck.
In this webinar, we’ll recap the Office 365 outage, offer troubleshooting and monitoring strategies, and serve up hybrid best practices to provide visibility in a cloudy world.
Ultimately, we’ll answer the question – Can you trust Office 365?
When you install the Exchange Server Security Update KB 3087126 on a server running the Exchange Server 2013 management tools only, you might receive an error message when starting the Exchange Management Shell.
The error might look like this:
The error message indicates that WinRM is having issues.This is not the case.
The problem occues due to registry changes performed by the patch setup and due to the way how ConnectFunctions.ps1 (used by RemoteExchange.ps1) determines the Exchange Server to connect to.
The script tries to connect to the local FQDN, if any Exchange role is installed on the local server. This is determined by querying the registry using the following command:
if (@(get-item HKLM:\SOFTWARE\Microsoft\ExchangeServer\v15\*role -erroraction:silentlycontinue).length -gt 0)
The queried registry does not exist prior to installation of KB 3087126.
When having installed the Exchange Server 2013 management tools only, which might be the case on a monitoring or scheduled task server, do the following:
Enjoy the Exchange Management Shell.
Mailscape 365 - Hybrid Exchange & Office 365 Monitoring and Reporting
Many organizations are choosing to use a mix of on-premise Microsoft Exchange and hosted Office 365 to meet their staff needs. These deployments, however, are challenging to support, with several 'moving parts' that need to be monitored in order to ensure reliable messaging and calendaring services - Test Drive Mailscape for Exchange Online
A new PowerShell script to add multiple legacy public folder replicas has been published to TechNet Gallery and Github
The script supports public folder migration during migration phases when upgrading to a new version of Exchange. Depending on the timespan for a migration project and the internal requirements of public folder replication, you might need a different apporach to add legacy public folder replicas.
Add replicas for SERVER01, SERVER02 to all sub folders of \COMMUNICATIONS\PR
.\Add-PFReplica.ps1 -ServersToAdd SERVER01,SERVER02 -PublicFolderServer SERVER01 -TopPublicFolder "\COMMUNICATIONS\PR"
The script is intended to work with legacy public folders on Exchange Server 2007 and Exchange Server 2010.
The community script Copy-ReceiveConnector has been updated. Receive Connectors that do exist on a specified target server can now be updated.
Besides the receive connector communication the assigned permissions of the source connector can be copied as well.
Are you unsure, if you should migrate to Office 365? You want to know more about security of cloud applications and services? Your Exchange Server infrastructure requires an upgrade? Contact me via email: email@example.com