Set-Sendconnector

In my Exchange environment I have 2 SMTP Gateways. 1 Active 1 Passive.
I created 2 Send Connectors but I was unsure how to weight the 2.

Power Shell Command
The first command I used was :

set-sendconnector -id SMTPGT2 smtp:*;2


Which did not give me an error, and it did not change anything!

So I think the smtp:*;2 is considered a multi value string or something to that effect.
I put it in Quotes "" and it worked just fine.

set-sendconnector -id SMTPGT2 "smtp:*;2"

Here are the parameter for the AddressSpaces on a sendconnector.

This parameter is required unless this connector is linked to a Receive connector. If a linked Receive connector is specified by using the LinkedReceiveConnector parameter, the value of AddressSpaces must be $null. Otherwise, the AddressSpaces parameter specifies the domain names to which the Send connector sends messages. You may specify multiple address spaces by separating the address spaces with commas. The complete syntax for entering each address space is as follows:

<ConnectorScope>:<AddressSpaceType>:<AddressSpace>;<AddressSpaceCost>

• ConnectorScope If you specify a value of Local, the connector can only be used by other Hub Transport servers that exist in the same Active Directory site as the source Hub Transport server on which you are running the New-SendConnector cmdlet. If you omit the ConnectorScope qualifier, the connector can be used by all Hub Transport servers that exist in the whole Exchange 2007 organization.
  
• AddressSpaceType For SMTP address spaces, this value must be SMTP. For non-SMTP address spaces, this value may be any descriptive text string, such as "Lotus Notes".
  
• AddressSpace For SMTP address spaces, the domain name system (DNS) wildcard character (*) as defined in RFC 1035 can be used. For example, you can use "*", "*.com.", or *.contoso.com". For non-SMTP address spaces, you can use wildcard characters (*) and other characters, such as "*contoso.com" or "@contoso".
  
• AddressSpaceCost The valid input range for the cost is 1 to 100. A lower cost indicates a better route. This parameter is optional. If you omit the AddressSpaceCost qualifier when you enter an address space by using the complete syntax, a cost of 1 is assumed.
  

You only need to use the complete syntax for the AddressSpaces parameter for the following conditions:

• Scoped connectors that have the Local qualifier
  
• Non-SMTP address spaces
  
• SMTP address spaces with a cost other than 1
  

If you enter a domain name or a comma separated list of domain names for the value of the AddressSpaces parameter, the address space type of SMTP and a cost of 1 is assumed for each domain name. Send connectors that are configured on Edge Transport servers only support SMTP address spaces. Send connectors that are configured on Hub Transport servers support SMTP and non-SMTP address spaces.

Calendars "Managing Resource"

Check out Nick’s Exchange and Scripting Blog, he has great Blog on Managing Resource Mailbox Calendars.

Can't Send an attachment over 10mb WHY!!??

Now we're on to Exchange 2007 settings:

Open a Power Shell Command:
Type in get-transportconfig | fl *
I have already set my transportconfig to 30mb
Here is what it shows me.

MaxReceiveSize : 30MB
MaxRecipientEnvelopeLimit : 31457280
MaxSendSize : 30MB

To change these setting use the following commands:

Set-transportconfig -MaxReceiveSize
MaxReceiveSize the default value is Unlimited. You can change it to what ever with an an MB following it
Set-transportconfig -MaxReceiveSize 30mb

Set-transportconfig -MaxRecipientEnvelopeLimit
The default size is Unlimited. The valid input range for this parameter is 0 to 2147483647.

Set-transportconfig -MaxSendSize
The default size is Unlimited. You can change it to what ever with an an MB following it

Next we need to look at the receive Connectors. Now we did change this in the ADSI Edit, but we need to make sure exchange 2007 took the setting correctly.

Use the following commands:
get-ReceiveConnector
This will list all of your ReceiveConnector.

Take the complete name and enter it into this command.

get-ReceiveConnector -Identity "Receive Connector name" | fl *
Then look for MaxMessageSize, mine was set for 30MB which is correct.

Do this for all of your Receive Connectors

Next we need to look at the Send Connectors. Now we did change this in the ADSI Edit, but we need to make sure exchange 2007 took the setting correctly.

Use the following commands:
get-SendConnector
This will list all of your SendConnector.

Take the complete name and enter it into this command.

get-SendConnector-Identity "Receive Connector name" | fl *
Then look for MaxMessageSize, mine was set for "Unlimited" which is correct.

Can't Send an attachment over 10mb WHY!!??

Go to your Domain Controller and open ADSI Edit change the Connection Setting / Naming Context to Configuration.

For incoming e-mail:
CN=Configuration\CN=Services\CN=Microsoft Exchange\
CN=\CN=Administrative Groups\CN=Exchange Administrative Group (FYDIBOHF23SPDLT)\CN=Servers\CN='server'\CN=Protocols\CN=SMTP Receive Connectors msExchSmtpReceiveMaxMessageSize 10485760
Here is the first spot, notice it set to 10mb also notice its in Bytes!

Next spot:
For outgoing e-mail:
CN=Configuration\CN=Services\CN=Microsoft Exchange\
CN=\CN=Administrative Groups\CN=Exchange Administrative Group(FYDIBOHF23SPDLT)\CN=Routing Groups\CN=Routing Group (DWBGZMFD01QNBJR)\CN=Connections
delivContLength 10240
Here is the second spot, notice it set to 10mb also notice its in kilobytes

Next Spot:

CN=Configuration\CN=Services\CN=Microsoft Exchange\
CN=\CN=Global Settings\CN=Message Delivery <--Right Click Properties.

Look for the following:
delivContLength this value is in kilobytes change it
SubmissionContLength this value is in bytes change it
msExchRecipLimit this value is in kilobytes change it

Now we're on to Exchange 2007 settings:

Can't Send an attachment over 10mb WHY!!??

The other day I was trying to send an attachment that was 12mb. I got an error 0x80040610.

My ReceiveConnector and SendConnector was set for Unlimited.

Where was the issue!!!

The issue was with my Active Directory! It seems there is a known issue with New and Upgraded installs of Exchange 2007.

Here are the Global Limits:
Active Directory
delivContLength
10240 KB for the following circumstances:

* Exchange 2007 was the first Exchange server installed in the organization.
* The organization was upgraded from Exchange 2003 to Exchange 2007, and the value of the global Incoming message size limit was set to No Limit.

If the organization was upgraded from Exchange 2003, and a specific value was set for Incoming message size, that value is preserved after the upgrade to Exchange 2007.
submissionContLength
10240 KB for the following circumstances:

* Exchange 2007 was the first Exchange server installed in the organization.
* The organization was upgraded from Exchange 2003 to Exchange 2007, and the value of the global Outgoing message size limit was set to No Limit.

If the organization was upgraded from Exchange 2003, and a specific value was set for Incoming message size, that value is preserved after the upgrade to Exchange 2007

msExchRecipLimit
5000 for the following circumstances:

* Exchange 2007 was the first Exchange server installed in the organization.
* The organization was upgraded from Exchange 2003 to Exchange 2007, and the value of the global Maximum number of recipients limit was set to No Limit.

If the organization was upgraded from Exchange 2003, and a specific value was set for Maximum number of recipients, that value is preserved after the upgrade to Exchange 2007.
So with that explained where do you change these settings?! See Next Post!

power shell commands to live by!

So you want to access someone mail file!

ADD-MailboxPermission -Identity "mailbox you want access to" -User "your id" -Accessright FullAccess -InheritanceType all


Done! You have 100% access

So your Company wants to migrate to Exchange 07!

So your Company wants to migrate to Exchange 2007!

Plan Plan Plan!!!

There are so many Gotcha's its not funny!

My Mistakes!
1. Don't let Management bully you into a Really Really tight time frame!
2. Document everything! I got burned on E-mails Alaises the were configure wrong in Lotus Notes
3. Get other Department involved. When you make a major change little item will reappear!

Mark