Tuesday, October 15, 2013

Exchange 2013 Attachment Size

So I had to increase an Exchange 2013 server the other day and could not find any definite "This is how you do this on Exchange 2013" but found plenty on Exchange 2010 and lower. Well I tried some commands and the following worked for my situation where a recipient of the specific domain needed to receive a larger file attachment and those who were sending the client attachments were getting the message:

Delivery has failed to these recipients or groups:

<User>
This message is too large to send. To be able to send it, make the message smaller, for example, by removing attachments.




The fix to get this to work is to execute the following commands in Exchange command:

Set-TransportConfig -MaxReceiveSize (X)MB -MaxSendSize (X)MB

IE: Set-TransportConfig -MaxReceiveSize 30MB -MaxSendSize 30MB

In my situation I did not have to restart any services, just simply resent the previously denied email and the client received it.


My reference site:
https://www.simple-talk.com/sysadmin/exchange/increasing-email-size-limits-for-your-high-profile-users-in-exchange-2010/




I am in no way responsible for the actions you take with the information provided. Please note that this worked on my Exchange 2013 server but not necessarily with all servers. I provide this information on an educational basis and from educated experience only. If you are unsure about if this will work in your situation please continue researching it. 

Wednesday, June 5, 2013

ESXi 5.1 5.X Locks Up On megaraid_sas

I have to give HUGE props to twincarre on youtube for their post on the original fix that led me to the following fix:

It appears in the use of some LSI controllers will freeze up on install when attempting to load the megaraid drivers. This also includes Intel RS2WC040 controllers since they run the LSI 2008 controller.

The Fix is to disable legacy booting. This is either in the PCI configuration, or in the boot configuration, depending on BIOS configuration. Huge props to Twincarre for helping at least direct me toward this fix!



Source: http://www.youtube.com/watch?v=e6Kkr-Ba3rU