Microsoft Exchange Installing Exchange Server 2016 on Windows Server 2016 Installing Exchange Server 2016 on Windows Server 2016 only First make sure your existing Exchange 2013 Servers are patched to at least CU10, if you have any. Install Exchange 2016 CU3 and above
Microsoft Exchange Exchange 2013 & Exchange 2016 - Troubleshooting Before you start calling Microsoft, I highly recommend you visit this technet blog and ensure you have completed these steps which will save you a lot of hassle, like it did with me!
Cisco ASAv Cisco ASA/Exchange 2013/Exchange 2016 - RPC Errors Well, this took me a long time to figure out what ended up being a pretty simple issue to fix! For a while now I have been getting a lot of weird RPC
Microsoft Exchange Microsoft Exchange Server 2016 - Upgrade to Exchange Server 2016 CU1/CU2 Check the AD Schema version before and after the upgrade to verify the schema as updated by running this in Powershell: $root = [ADSI]"LDAP://RootDSE" $m = [ADSI]("LDAP://" + "
Microsoft Exchange Microsoft Exchange Server 2016 - Configuring and migrating to Exchange 2016 in an existing Exchange 2013 environment Once you have followed the previous step in installing Exchange 2016, now you need to configure it. From the newly deployed Exchange 2016 Server, Open Exchange Management Shell. Enter the product key: Set-ExchangeServer
Microsoft Exchange Microsoft Exchange Server 2016 - Installing Exchange 2016 in an existing Exchange 2013 environment First make sure your existing Exchange Servers are patched to at least CU10. Disk requirements: 60GB OS Disk (NTFS), 60GB Exchange install disk (NTFS), 30GB Exchange database (ReFS), 5GB Exchange logs (ReFS) For
Microsoft Exchange Exchange 2013 SP1 - Content Index failing I came across this issue in my own Exchange Environment which includes a DAG and has a second Database copy for each database. However this issue will also occur for anyone moving mailboxes
Microsoft Exchange Exchange 2013 SP1 - IP-less DAG It's true! Exchange 2013 SP1 allows creating a Database Availability Group without specifying a DAG IP address on Windows Server 2012 R2! What does this mean? It basically means DAGS are much simpler,
Microsoft Exchange Exchange 2013 SP1 - MAPI over HTTP Exchange 2013 SP1's most significant new feature is adding MAPI over HTTP support. Traditionally Outlook clients connect to Exchange via RPC over HTTP, a very old technology originally designed to work on small