MVP - Most Valuable Professional
rss

Just can't get enough of IT

This blog is about mostly anything in IT. But the primary focuses are Microsoft Technologies like Exchange, Office 365, Azure and Cloud Security.

Description

This script helps you to configure mailbox quotas for

  • ProhibitSendReceive
  • ProhibitSend
  • IssueWarning
  • ArchiveQuota
  • ArchiveWarningQuota

on a database level across all Exchange Server 2013/2016 databases in your environment or for a specific user.

Examples

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 usera@mcsmemail.de -MaxMailboxSize 10GB

Version History

  • 1.0, Initial community release
  • 1.1, Archive support added
  • 1.2, Refactored to functions
  • 1.3, PowerShell hygiene
  • 1.4, Parameters reordered, PowerShell hygiene

Links

Last updated: 2017-04-20

 

Follow

 

 

Read More »

Problem

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:

PowerShell Error KB3087126

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.

Regustry Keyy added by KB3087126 on a Management Tools only server

Solution

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:

  • Delete the registry key ClientAccessRole
  • Open a new Exchange Power Shell session

Enjoy the Exchange Management Shell.

Links

 


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

 

Read More »

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"

 

Note

The script is intended to work with legacy public folders on Exchange Server 2007 and Exchange Server 2010.

Links

 


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

Read More »

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.
 

Links

 


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: thomas@mcsmemail.de

Read More »

A new community PowerShell script to simplify Exchange Server mailbox migrations has been published to TechNet Gallery and Github.

Features

  • Validate CSV file for required column EmailAddress prior to creating migration batch in Exchange
  • Automatic batch naming based on CSV file name
  • Common notification email address settings
  • Variable AutoComplete of batches
  • Common logging of script activities

See script help for examples.

Links

 


Checkout the professional services provided by Granikos for planning and migration your exisiting Exchange Server infrastructure to the cloud. Protect your cloud services using the CloudSOC™ technology provided by Elastica.

Read More »