Setting Size Limits for incoming and outgoing mail SBS 2011

The text below is taken from Technet blogs, but there is an error:  in the set-receivesize script, the -identity switch must be added.  See below.  Global settings correct, but individual server settings wrong.

Size limits for email messages are controlled in a variety of places in Exchange. Settings are placed globally at the transport level, on each individual send or receive connector, at each individual mailbox, and controlled at individual web applications such as EWS and OWA . Your business needs should determine if you need to change these settings and at which location(s). In order to accomplish this successfully, you must know that more restrictive settings override less restrictive settings as you flow up the chain from individual mailbox settings to SMTP connectors and finally to global transport settings.

Global Transport Settings

Get-TransportConfig displays global transport settings for all Hub and Edge Transport servers in the Exchange Organization. By default, there is a 10MB size limit on send and receive. This will override all other less restrictive message size limit settings set elsewhere.

NOTE: Exchange considers message submission to the store driver as a “send” operation. Therefore, if you are attempting to receive an email message on an SBS server from the internet that is greater than the MaxSendSize of the global transport configuration, delivery will fail.

Get-TransportConfig | ft MaxSendSize, MaxReceiveSize

Example:

Set-TransportConfig –MaxSendSize 20MB –MaxReceiveSize 20MB

Receive Connector Settings

Each receive connector is created with a default 10MB message size limit. A default install of SBS will contain a default receive connector (created during Exchange setup, do not remove this), an internet facing receive connector, and a receive connector for fax receipts and Sharepoint email notifications. The Windows SBS Internet Receive connector is the only one that you should ever need to adjust settings for. NOTE: If the global receive size is more restrictive, it will override this setting

Get-ReceiveConnector | ft name, MaxMessageSize

Example:

Set-ReceiveConnector -identity “Windows SBS Internet Receive Servername” –MaxMessageSize 20MB

Send Connector Settings

Each send connector is created with a default 10MB message size limit. In SBS , a single send connector is created for email destined for mail hosts outside of the site. If you need to adjust the size of messages flowing out of the SBS server, then you would change it here. **If the global send size is more restrictive, it will override this setting**

Get-SendConnector | ft name, MaxMessageSize

Example:

Set-SendConnector -identity “Windows SBS Internet Send Servername” –MaxMessageSize 20MB

Mailbox Settings

Exchange does not govern message size limits at the mailbox level by default, as it relies on elements in the transport service for this. However, you can set size limits here if you want granular control without potentially affecting all senders and recipients. **More restrictive settings at the SMTP connector level will override here; more restrictive settings at the global level will override both**

Get-mailbox | ft Name, MaxSendSize, MaxReceiveSize

Example:

Set-Mailbox “test” –MaxSendSize 10MB –MaxReceiveSize 10MB

This from tt-systems.co.uk :  Less detailed but more accurate:

Increase SBS 2008 and SBS 2011 exchange server email message size limit

digg

0
inShare

To globally increase the Microsoft Exchange email message size on SBS 2008 and SBS 2011 to 30MB, open up a Exchange Management Shell and enter the following commands:

Set-TransportConfig -MaxReceiveSize 30MB -MaxSendSize 30MB

Set-Sendconnector “Windows SBS Internet Send yourservername” -MaxMessageSize 30MB

Set-ReceiveConnector -Identity “Windows SBS Internet Receive yourservername” -MaxMessageSize 30MB

Note: replace yourservername with the name of the server that you are running the commands on.

To check the settings have been applied use the following commands

Get-TransportConfig | fl MaxSendSize,MaxReceiveSize

Get-Sendconnector “Windows SBS Internet Send yourservername” | fl Name,MaxMessageSize

Get-Receiveconnector -Identity “Windows SBS Internet Receive yourservername” | fl Name,MaxMessagesize

Note: replace yourservername with the name of the server that you are running the commands on.

Adding disks to SBS 2011 backup schedule.

Adding disks by running the SBS console doesn’t work.  It needs to be done through an administrator enabled command line.  (See below, from Technet)

To resolve this issue, use one of the following options.

Note To configure or modify a daily backup schedule, you must be a member of the Administrators group. In addition, you must run the wbadmin command from an elevated command prompt. To open an elevated command prompt, click Start, right-click Command Prompt, and then click Run as administrator.

Option 1

1. Reattach the missing disk or disks.
2. Make sure that all the disks that are defined as backup destination disks are attached to the server.
3. Try again to add an additional disk to a scheduled backup by using the Windows Server Backup Schedule Wizard.

Note If you are using offsite storage, or if another situation prevents all destination disks from being attached at the same time, go to option 3.

 

Option 2

If the missing disk is no longer available, remove it as a destination disk from the backup wizard.

Note If the missing disk is the only destination disk that is defined in the backup schedule, you will receive the following error message when you try to remove it. If this occurs, click Stop backup, and then create a new backup schedule.

“Error: You cannot remove this backup storage destination unless you add another storage destination or stop the scheduled backup. A schedule backup requires at least one backup storage destination.

To remove a destination disk from a scheduled backup, follow these steps: 

1. In the Windows Server Backup snap-in, click Backup Schedule.
2. Click Modify backup, and then click Next.
3. Leave the Backup Configuration setting unchanged, and then click Next.
4. Leave the Backup Time setting unchanged, and then click Next.
5. Leave the Destination Type setting unchanged, and then click Next.
6. Select Remove current backup destinations, and then click Next.
7. Select the backup destination that is no longer attached, and then click Next.
   Note Typically, the disk will have the name “(Disk offline).”
8. Verify that the configuration is correct, and then click Finish.

 

Option 3

Add a new disk to the backup schedule by running the wbadmin command from an elevated command prompt.

1. Run the following command from an elevated command prompt to determine the Disk Identifier of the new disk:
        wbadmin get disks
   
2. Based on the output, locate the disk that will be added to the scheduled backup. Make a note of the Disk Identifier. The output will resemble the following:
   Disk name: xxxxxxxxxxx
   Disk number: x
   Disk identifier: {xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx}
   Total space: xxx.xx GB
   Used space : xxx.xx GB
3. Run the following command to add the new disk to the Scheduled backup.  Use the Disk Identifier from the previous step as the “AddTarget” parameter.
        WBADMIN ENABLE BACKUP -addtarget:{xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx}
   
4. When you receive the following prompt, type Y for Yes.

“Do you want to enable scheduled backups with the above settings?”