Aumentar Tamaño Archivos Adjuntos EXchange

8/13/2019 Aumentar Tamaño Archivos Adjuntos EXchange

http://slidepdf.com/reader/full/aumentar-tamano-archivos-adjuntos-exchange 1/9

A huge amount of business happens through the medium of email and, as such, email is naturally one ofthe Business Critical applications in almost every organization. With that in mind, maximizing theperformance of your Exchange infrastructure is clearly a priority, and restricting the average message sizewhich your users can send/receive is a good step in that direction. However, in the course of conducting

said business, High Profile email users may have to share large attachments between other internal andexternal users, and indeed may do so regularly and urgently.

An organization’s High Profile users tend to be people in positions of authority or influence, and those of usin IT are their backbone, providing the support they need to run the business. As such, we need to makechanges in our Infrastructure to meet shifting business needs, and we need to make sure that our users’needs are met. So, asking your CIO to upload attachments to start using an FTP server or SharePoint todistribute files is not really an ideal solution. What your CIO wants is to be able to send a large email totheir counter-part in another company as soon as possible in order to close a business deal, so we’re goingto look at how you can quickly and easily make that possible.

To put this situation into a simple context, let’s say that, for whatever reason, a new set of businessrequirements have been drafted which mean that a subset of your email users now need to be able to sendemails with attachments up to 30MB in size:

Bearing in mind that we need to have minimal disruption for both sets of users, we can achieve this in oneof two ways; you just need to decide which solution will best f it with your organization. I’ll guide you, step-by-step, through each solution, and demonstrate where appropriate.

As an aside, you also need to remember to factor content conversion into your storage provisioning. WhenExchange converts a message from MAPI/Exchange format to Internal/ MIME Message format and vice

versa, this normally increases the message size by 30 percent.

Solution 1

This solution would be ideal for a very smaller organization, when it’s feasible for the administrator to makeconfiguration adjustments on individual mailboxes when required. It’s perhaps not the most elegant solutionavailable, but it’s quick and it works.

Global Transport Organization Configuration

First we need to make changes to the Transport Organization (Global) configuration. The command belowgives us the details of the current MaxSendSize and MaxReceiveSize limits:

Get-TransportConfig | fl MaxSendSize,MaxReceiveSize

Figure 1. The current MaxSendSize and MaxReceiveSize limits



As we see in the Figure 1. Current MaxSendSize and MaxReceiveSize is set to 10MB. This Globalconfiguration is naturally applied to all the Exchange Hub Transport Servers. Let’s see how to Increase theMaxSend and MaxReceive Size limits on the Organization level.

Set-TransportConfig -MaxReceiveSize 30MB -MaxSendSize 30MB

Figure 2. Setting the new MaxSend and MaxReceive size limits.

I know that we only want to increase the limits for a subset of users and yet we’ve just made a globalconfiguration change to MaxReceive and MaxSend. If you’re wondering why that is, I’ll show you how wecan limit the scope of this size increase in just a moment.

Active Directory Configuration

Exchange 2010 uses Active Directory (AD) site topology to determine the lowest-cost path to route email

along if the destination user is located in a different site. If Message to be delivered to the remote AD sizeis larger then the limits set on Site link then message delivery will failed. Thankfully, MaxMessageSize onthe AD Site link is set to unlimited by default. If we are changing the Maxsize limitation, it’s important thatyou check if there are any limits set on the AD site link...

Get-Adsitelink <AdSitelink> | select Maxmessagesize

Figure 3. Confirming the message size limit of the AD site link.

...and change it accordingly if required. Strictly speaking, we don’t need to adjust the link in this instance,but we’ll do so to ensure this walkthrough is comprehensive. Below is the command to set the newMaxMessageSize for the AD link:

Set-Adsitelink <Sitelinkname> -MaxMessageSize 30MB

Send Connector Configuration

Although we just made global configuration changes to allow users to send and receive bigger email, thisconfiguration will only affect items sent and received internally . To Send bigger emails out to the Internet,we need to make sure that the appropriate Send connectors are configured correctly with the appropriatemessage size. To get the current MaxMessageSize configuration on the send connecters, use thiscommand:

Get-Sendconnector "<Connectorname>" | fl Name,MaxMessageSize



Figure 4. Confirming the maximum message size limit for the “To Internet” Send Connector.

Once you’ve confirmed that the connector needs to be reconfigured, we can use a simple Powershellcommand to set the MaxMessageSize limit:

Set-Sendconnector "<Connectorname>" -MaxMessageSize 30MB

Receive Connector Configuration

Bearing in mind that sending a large email requires that message to first be sent from the user’s Outlook orOWA session to the Hub Transport server, you also need to make sure that you increase the MaxMessage size on the Hub Transport Server’s Default Receive connector to 30 MB. This is regardless ofwhat limits you want to apply to messages coming from the internet.

That’s got you covered for sending out larger emails, but now we need to turn our attention to thosemessages coming from the Internet, as our requirement is that High Profile users should also be able toreceive larger emails. For this, we need to reconfigure the receive connector which receives email fromInternet. To get the current size limit on the appropriate receive connector, we use the command below:

Get-Receiveconnector -Identity "<Connectorname>" | fl Name,MaxMessagesize

Figure 5. Determining the current maximum message size limit on the appropriate Receive Connector

To Set the MaxMessage size to 30 MB, we then need to use the below command for the same connector:

Set-ReceiveConnector -Identity "<connectorname> -MaxMessageSize 30MB

User Mailbox Configuration

At this stage, we are pretty much done with the configuration on the organization and Connectors end ofthings. Now the final step is to increase the Message Size restriction on the appropriate users’ mailboxes.By default, all users will be able to send and receive emails based on the global configuration, and if anyusers want to send or receive larger emails, then we need to increase the global Sending and ReceivingMaxMessageSize from mailbox configuration. This is because, if you try and adjust the limit on a per-userbasis, there is a gotcha here which you should know about:

Setting higher limits on the individual recipients’ mailboxes will bypass the global size limits, but it is onlyinternal . Mailboxes which are individually configured with higher limits cannot send or receive larger emailsto or from the Internet, but they will be able to send and receive emails containing attachments within theglobal size limits.

This is the reason why we have to configure higher message-size limits and higher connecter limits on anorganization-wide basis, in order for users to send and receive larger emails. However, with the higherTransport Organization size limits, all users will now be able to send and receive larger emails, and wewanted only a few select users to have this ability, and the rest to retain the original 10 MB limit. For this,we need to change the maximum message size limit on the individual mailbox configurations of all ourusers except the high profile ones (as I’ve already mentioned, setting individual mailbox limits will overridethe organization limits).

So, to get started, the command below will get you the current Send and Receive Size configuration on agiven mailbox. By default, it is currently set to unlimited, give that it is using the Global size limits:



By now our users can send and receive larger emails both internally and also out to the Internet. Given thatwe also want internal users to be able to receive bigger emails, we need to make some configurationchanges to the receive connector (Figure 5).

Transport Rules

As with solution 1, by this point we are essentially done with the configurations on the organization level.Now, all users are able to send and receive 30 MB emails, but our requirement is still to allow only 1000users to have this ability. This final piece of the puzzle can be configured with Transport rules, as I’ll showyou now.

Before configuring Transport rules, let’s create a Distribution group whose members are just th e HighProfile users. You can create the group using the cmdlet below, and then you can add the required (1000)users to this group.

New-DistributionGroup -Name 'HighProfileUsers' -Type 'Distribution' -Samaccountname

'Highprofileusers' -Alias 'Highprofileusers'

Now let’s create a new Transport rule. Open your Exchange Management console, expand theOrganization Configuration, and click on Hub Transport Server . In the Results pane, click on theTransport Rules Tab, and then click on New Transport Rule in the Action pane.

Figure 8. Creating a new Transport Rule.

1. Provide a suitable name (and, if you find it helpful, an explanatory comment) for the new transportrule. If there are multiples rules in your Exchange environment, then a suitably unique name will

help make it easy to identify rules if you have to adjust the High Profile attachment size limitsagain. Once this is done, click on Next.

2. On the Conditions screen, Select the When the size of any attachment is greater than orequal to <limit> option, enter the value 10240 (10 MB) in the edit pane at the bottom of thewindow (see figure 9), and click on Next.



Figure 9. Setting the conditions of the new Transport Rule

3. On the Actions screen, select the Send rejection message to the sender with enhanced statuscode option, and enter the appropriate bounce message and error code (see figure 10). Enabling

this option will restrict users from sending emails with attachments larger than 10 MB, and if theytry and send a larger email, then this will be the error message which the offending users will begetting in return. This message should be very clear, as your users should be able to quicklyidentify the issue themselves, and then send a smaller email attachment. Once you’ve crafted asuitable message, click on Next.



Figure 10. Configuring the transport rule to reject overly large messages, and return anappropriate explanatory bounce message to the over-ambitious sender.

4. Lastly we need to select when (if ever) there are any exceptions to our new rule. In this case, wecreate an exception for situations when the message is sent to or from a member of the recently-created High Profile Users distribution group (see figure 11). Given that have designed this newTransport rule to not apply to our High Profile set of users, their maximum message size is nowset as 30 MB, as this is the global configuration which we created at the start of the solution. Withthis rule restricting the email sizes for the vast majority of your users, only the High Profilecommunicators can enjoy the privilege of emails with bigger attachments. Obviously, this setup isdependent on the High Profile distribution group, so you’ll need to make sure that any new HighProfiles user s are added to the distribution group as necessary. Once you’re happy that you’ve setthe exception correctly, click on Next.



Conclusion

A transport rule is simply a method to control the flow of emails based on a predetermined set ofconditions, as set up by the SysAdmin. These rules exist on the Hub Transport server, through which allemails pass, and so actions can be applied to all emails as necessary, depending on which ones matchyour necessary conditions. You can create quite sophisticated mail flow control systems using these rules,and the situation I’ve described here is really just a simple implementation to solve a specific problem.

In terms of raising the attachment size limit for a subset of your users, a solution employing transport ruleswould be the easiest option in all but the most niche cases. The ability to achieve that without having tomake changes on individual mailboxes, and the ability to rapidly scale this solution to everyone in theorganization (i.e. just by removing the transport rule) makes this method both powerful and efficient.

If I were an administrator for an organization of around 50-100 users, then I probably wouldn’t mindincreasing the email size limit for my CIO and a few other High Profile users, but in a larger organization Iwould certainly deploy transport rules. That being said, you naturally have the choice to use either solution,as you are the best person to decide which solution is a better fit for your organization.

Whichever solution you choose, bear in mind that bigger emails will cause additional load on your SMTPservers and Hub Transport servers, and you may also need to provision addition storage for the mailbox

servers as well. If you’re going to implemen t larger email limits for any of your users, you need to makesure that you have sufficient infrastructure in place to support this decision. Making any configurationchanges without considering these points could bring your environment into an unstable condition, whichwill undermine the whole point of the exercise

Aumentar Tamaño Archivos Adjuntos EXchange

Documents

Transcript of Aumentar Tamaño Archivos Adjuntos EXchange