exchange activesync 调整手机端发送邮件的限制

 Good afternoon,

This is a two part question.  

Question 1:  Taking some old notes from my Exchange 2007 deployment, I want to set the MAX Message size limits for Exchange 2010.  Do these same settings translate from Exchange 2007 to Exchange 2010?  I notice in my Exchange 2010 environment the web.config file entires are already set to high numbers for  the tag httpRuntime maxRequestLength  for ActiveSync  "10240"K and EWS "2097151"K.....  I am running Exchange 2010 SP1 RU4.

How I set these settings in Exchange 2007:

Create Message Size Limits (50 MB
OWA Attachment Sizes:  (Note: This must be completed on every CAS server)
Use Notepad to change the maxRequestLength value

1. Find the Outlook Web App Web.config file on the Client Access server. The default location is <drive>\Program Files\Microsoft\Exchange Server\V14\ClientAccess\Owa.
2. Make a backup copy of the web.config file.
3. Open the original file using an editor such as Notepad. Don't use Internet Information Services (IIS) Manager to edit the Web.config file.
4. Find maxRequestLength and change it to the value that you want. The value is stored in kilobytes (KB). The default value is 35000. The following example shows the maxRequestLength value in the Web.config file.
<httpRuntime maxRequestLength="51200" />
Note: This is 50 MB (1024 X 50)
5. Save and close the file.

EWS Attachment Sizes:  (Note: This must be completed on every CAS server)
1. Find the EWS Web.config file on the Client Access server. The default location is C:\Program Files\Microsoft\Exchange Server\V14\ClientAccess\exchweb\ews
2. Make a backup copy of the web.config file.
3. Open the original file using an editor such as Notepad. Don't use Internet Information Services (IIS) Manager to edit the Web.config file.
4. Find maxRequestLength and change it to the value that you want. The value is stored in kilobytes (KB). The default value is 35000. The following example shows the maxRequestLength value in the Web.config file.
<httpRuntime maxRequestLength="51200" />
Note: This is 50 MB (1024 X 50)
5. Save and close the file.
Restart IIS.

ActiveSync Attachment Sizes:  (Note: This must be completed on every CAS server)
1. Find the EWS Web.config file on the Client Access server. The default location is C:\Program Files\Microsoft\Exchange Server\V14\ClientAccess\Sync
2. Make a backup copy of the web.config file.
3. Open the original file using an editor such as Notepad. Don't use Internet Information Services (IIS) Manager to edit the Web.config file.
4. Find maxRequestLength and change it to the value that you want. The value is stored in kilobytes (KB). The default value is 35000. The following example shows the maxRequestLength value in the Web.config file.
<httpRuntime maxRequestLength="51200" />
Note: This is 50 MB (1024 X 50)
5. Save and close the file.
Restart IIS.

Set IIS 7 settings
Open a command prompt and go to the follow directory:  cd %windir%\system32\inetsrv
Type each of these commands separately and hit enter.

appcmd set config "Default Web Site/ews" -section:requestFiltering -requestLimits.maxAllowedContentLength:51200000
appcmd set config "Default Web Site/owa" -section:requestFiltering -requestLimits.maxAllowedContentLength:51200000
appcmd set config "Default Web Site/Microsoft-Server-ActiveSync" -section:requestFiltering -requestLimits.maxAllowedContentLength:51200000

4. IISreset or reboot to apply these changes.

Question 2: The second part of my questions is regarding errors I am seeing while trying to apply the appcmd settings to IIS.

The error is

 "C:\Windows\System32\inetsrv>appcmd set config "Default Web Site/owa" -section:requestFiltering -requestLimits.maxAllowedContentLength:51200000
ERROR ( message:Can not set attribute "maxAllowedContentLength" to value "512000
00".. Reason: This configuration section cannot be used at this path. This happens when the section is locked at a parent level. Locking is either by default (overrideModeDefault="Deny"), or set explicitly by a location tag with overrideMode="Deny" or the legacy allowOverride="false".. )"

I suspect this has something to do with the applicationhost file settings for IIS, but I do not see this in my test lab that is built identically.

Does anyone have experience settings these message size limits and\or have you experienced the same error I am seeing?

Any help is greatly appreciated.

Ed McKinzie