After setting up and Exchange 2013 SP1 server on Server 2012 R2 I ran into this small issue with a customer. Even though I had all of the send/receive connectors in the ECP set at 100M, I was still hitting the default 10M attachment size limits. Here's how to fix that by changing the Global Transport Settings: (short answer) Check to see what the size limits currently are - Get-TransportConfig | ft MaxSendSize, MaxReceiveSize Once you know those sizes then here's the command to change them to what you need - Set-TransportConfig –MaxSendSize 100MB –MaxReceiveSize 100MB I know these sizes are a little large but just using them as an example. Go ahead and bounce the Transport service just to be sure the settings take effect and you'll be good to go. All of the other size limits can be set using the ECP under Mailflow and then Send Connectors and Receive Connectors.
Update: I've just completed reading almost all of Mastering Microsoft Exchange Server 2013
. This is an excellent read that will give you tons of insight into installing, maintaining, and mastering all there is to Exchange 2013. I highly recommend you give the book a read.
Here’s the process to prevent SBS2003 from shutting down after 21 days of migration have passed. The basic principle is to disable the SBS Core Service (sbscrexe.exe). The problem is when you just turn off the service, it will restart itself automatically. To achieve this goal follow the steps below:
PROBLEM: The WS-Management service cannot process the request. The user load quota of 1000 requests per 2 seconds has been exceeded. Send future requests at a slower rate or raise the quota for this user. The next request from this user will not be approved for at least XX milliseconds.
This can happen if a certificate on Exchange expires (SSL or UCC) and the IIS service has not been restarted since.
All you need to do is open a command prompt (Run as Administrator if using UAC) and the type in IISRESET. Press ENTER and wait.
Now you should be able to login to the Exchange 2010 EMC with no issues.
Ok so I've setup a new Exchange 2013 server for a customer and got it installed with no errors. These instructions pertain to installation on Windows Server 2012/2012R2. I have condensed it down to make sense. We all know TechNet instructions look like they were written by a lawyer. I hope this helps with your install. Good luck.
1. Install all OS updates
2. Install all the following prereqs
- .NET Framework (already on Server 2012R2). Just use the server manager to install this as a Feature.
3. Extend the AD schema. Use Command Prompt to drive letter with Exchange ( setup.exe /PrepareSchema /IAcceptExchangeServerLicenseTerms ). When setup completes allow some time for AD replication to complete across all DCs.
4. Prepare AD for Exchange. Use Command Prompt to drive letter with Exchange ( Setup.exe /PrepareAD /OrganizationName:"" /IAcceptExchangeServerLicenseTerms )
5. Prepare all domains for Exchange 2013. Use Command Prompt to drive letter with Exchange ( Setup.exe /PrepareAllDomains /IAcceptExchangeServerLicenseTerms )
8. Run setup.exe. Follow prompts and allow wizard to complete install.
That's pretty much all there is to it to get it installed.
If you want more information on detailed installation, configuration after install, and maintaining then I highly recommend you read Mastering Microsoft Exchange Server 2013. I did and it has been a tremendous reference point for me now that Exchange 2013 deployments are becoming more common for me.
I recently had a request from a customer to provide some reports on how well their AD replication was working. I found these come in helpful during routine maintenance or for specific requests on health checks.
Hope these help.
Dcdiag.exe /v >> c:\temp\pre_dcdiag.txt
This is a must! It will always tell you if there is trouble with your DCs and/or services associated with it.
Netdiag.exe /v >> c:\temp\pre_Netdiag.txtThis will let you know if there are issues with the networking components on the DC.
Netsh dhcp show server >> c:\temp\pre_dhcp.txtYou may not want to do this but I've ran into issues with a DHCP server somehow not being authorized after a patch. This allows me verify the server count and names.
Repadmin /showreps >> c:\temp\pre_rep_partners.txtThis shows all replication and if it was successful or not. Be aware that Global Catalogs will have more info than a normal domain controller.
repadmin /replsum /errorsonly >> c:\temp\pre_repadmin_err.txtThis command takes a while to run but will let you know which server are having issues replicating.
Update 04/08/15: Below is the text you can put into a script file that will dump everything you need into one text file for you to use for troubleshooting. The commands above are great if that's all you need but now I use this script to grab it all at once.
@Echo Off ECHO Running AD Health Checks - Notepad will open after completion ECHO This Command Prompt will close after you close Notepad set logfile=%userprofile%\Desktop\ADHealth.txt echo You can share this log using http://pastie.org/pastes/new > %logfile% echo. >> %logfile% echo. >> %logfile% REM Finds system boot time echo System Boot Time ------------------------------------------------------------- >> %logfile% systeminfo | find "System Boot Time:" >> %logfile% systeminfo | find "System Up Time:" >> %logfile% echo. >> %logfile% echo. >> %logfile% REM Displays all current TCP/IP network configuration values echo IPCONFIG ------------------------------------------------------------- >> %logfile% ipconfig /all >> %logfile% echo. >> %logfile% echo. >> %logfile% REM Analyse the state of domain controllers in a forest and reports any problems to assist in troubleshooting echo DCDIAG ------------------------------------------------------------- >> %logfile% dcdiag /a >> %logfile% echo. >> %logfile% echo. >> %logfile% REM The replsummary operation quickly summarizes the replication state and relative health echo Replsummary ------------------------------------------------------------- >> %logfile% repadmin /replsummary >> %logfile% echo. >> %logfile% echo. >> %logfile% REM Displays the replication partners for each directory partition on the specified domain controller echo Showrepl ------------------------------------------------------------- >> %logfile% repadmin /showrepl >> %logfile% echo. >> %logfile% echo. >> %logfile% REM Query FSMO roles echo NETDOM Query FSMO ------------------------------------------------------------- >> %logfile% netdom query fsmo >> %logfile% REM Query Global Catalogs echo List Global Catalogs ------------------------------------------------------------- >> %logfile% for /f "tokens=2" %%a in ('systeminfo ^| findstr Domain:') do set domain=%%a nslookup -querytype=srv _gc._tcp.%domain% >> %logfile% notepad %logfile%
. This is an excellent read that will give you tons of insight into installing, maintaining, and mastering all there is to Exchange 2013. I highly recommend you give the book a read.
