Tips and Tricks:
Tip: In Exchange Server 2016 the architecture was simplified when compared with previous versions, and nowadays we have only two roles: Mailbox and Edge. Where the Mailbox is the role that is located in the internal network with access to the Active Directory.
Tip Exchange 2013 sp1: the Edge role reappears
Tip: ReFS not supported as File System
Tip: No storage on SMB is supported
Tip: OWA support the certificates and ADFS (strong authent scenario)
Tip: dedicate CAS servers behind hw load balancer – with public URL. the Certificate is managed by internal PKI.
Tip: prefer using Win2012 R2 and Exchange 2013 SP1 (better together!)
Tip: prefer using the command lines to install exchange 2013 role
Tip: when using cmdlets: always for details do | fl prop1,*prop2  or  | ft -autosize

Topology best practice (after SP1 of Exch 2013):

internet —–  FW —– edge server (dmz / in a wkg) —– FW —– hwlb – CAS servers —– MBX servers — FW — AD / PKI servers

 

Exchange installation prerequisites:

For Exchange 2016: http://www.itprocentral.com/exchange-server-2016-prerequisites/

For Exchange 2013: http://www.itprocentral.com/prepare-windows-server-2012-r2-support-exchange-server-2013-sp1/

Exchange 2016 step by steps: https://judeperera.wordpress.com/2015/07/24/step-by-step-guide-for-installing-exchange-server-2016-preview/

Cumulative updates:

https://www.microsoft.com/en-us/download/details.aspx?id=51499

 

Exchange and certificates:

public or internal PKI server certificates only on CAS servers, follow the recommendations here: http://blogs.technet.com/b/exchange/archive/2014/03/19/certificate-planning-in-exchange-2013.aspx

also the client computers are joined to the AD domain and have also a computer certificate.

 

Exchange and Firewalls:

http://blogs.technet.com/b/exchange/archive/2013/02/18/exchange-firewalls-and-support-oh-my.aspx

 

Deployment assistant for Exchange:

http://technet.microsoft.com/en-us/exdeploy2013/Checklist?state=2284-W-AAAAAAAAQAAAAAEAAAAAAA%7e%7e 

 

Exchange sizing:

http://blogs.technet.com/b/exchange/archive/2013/05/14/released-exchange-2013-server-role-requirements-calculator.aspx

http://blogs.technet.com/b/exchange/archive/2013/05/06/ask-the-perf-guy-sizing-exchange-2013-deployments.aspx

HP sizer for Exchange 2013:http://h71019.www7.hp.com/ActiveAnswers/cache/70255-0-0-225-121.html

 

How to dedicate DC to Exchange? and It is recommended to exclude the DC PDC server.

https://support.microsoft.com/en-us/kb/298879

http://smtpport25.wordpress.com/2009/03/20/statically-pointing-exchange-2007-servers-to-dedicated-domain-controllers-and-global-catalogs-and-excluding-other-domain-controllers/

How to separate roles for AD admins and roles for Exchange admins? ==> RBAC split permissions and AD split permissions
Troubleshooting:

Test connectivity: https://testconnectivity.microsoft.com/

ExLogAnalyzer to the rescue:http://blogs.technet.com/b/mspfe/archive/2013/12/04/dude-what-s-flowing-in-my-exchange-environment.aspx

Database maintenance: http://blogs.technet.com/b/exchange/archive/2011/12/14/database-maintenance-in-exchange-2010.aspx

With Outlook 2013 installed; CTRL+ right-click Outlook icon on the taskbar; then Check Outlook Connectivity and Test Messaging configuration

Validation and monitoring of storage:

When implementing a storage solution for Exchange, an easily overlooked step is the evaluation of storage after it has been put in place to determine a baseline for that storage. Microsoft makes tools to enable this testing. Jetstress and LoadGen available for Exchange 2010/2013 can be used to test storage or Exchange overall and establish a baseline for future comparison.

Jetstress 2013: http://www.microsoft.com/en-us/download/details.aspx?id=36849

LoadGen 2013: http://www.microsoft.com/en-us/download/details.aspx?id=40726

 How to install the Exchange management tools and PowerShell cmdlets:For Exchange 2013/2016:

https://technet.microsoft.com/en-us/library/bb232090(v=exchg.160).aspx

in short: Setup.exe /Role:ManagementTools /IAcceptExchangeServerLicenseTerms

Best practices:

Connecting to Exchange on-premises using PowerShell remoting is a simple task, and means that you do not need to go the trouble of installing the Exchange management tools on your computer just to perform day to day administrative tasks.

There are three steps to establishing a remote PowerShell session to your Exchange server:

  • Capture admin credentials
  • Create a new PSSession
  • Import the PSSession

https://practical365.com/exchange-server/powershell-function-to-connect-to-exchange-on-premises/

Usage: Connect-Exchange -URL exchange2.mydomain.local

Scripts repository for Exchange:

https://github.com/cunninghamp/Powershell-Exchange

 

 

 

Advertisements