Items specifically related to Exchange 2013 SP1
Imagine this scenario; you have deployed an Exchange 2013 or Exchange 2016 Cumulative update successfully in your environment and you think that all is fine. However you then receive an unpleasant surprise when you go to verify the details of the Exchange Schema and Exchange AD object versions. You can review the process to review the Exchange AD Objects and Schema in addition to the different b… Read the rest “Unexpected Exchange AD Object Values”
As mentioned in the release posts for Exchange 2013 CU16 and Exchange 2016 CU5, both of these Exchange versions now require .NET framework 4.6.2 on all supported OS platforms. This post focusses on Windows 2012 and 2012 R2 installations, see note below about Windows 2016.
Update 25-1-2018 Since the older versions of Exchange 2013 and 2016 CUs are no longer available, the Exchange Support Matrix has be… Read the rest “Exchange 2013 CU16 and Exchange 2016 CU5 .NET Framework Requirement”
Exchange 2013 CU16 has been released to the Microsoft download centre! Exchange 2013 has a different servicing strategy than Exchange 2007/2010 and utilises Cumulative Updates (CUs) rather than the Rollup Updates (RU/UR) which were used previously. CUs are a complete installation of Exchange 2013 and can be used to install a fresh server or to update a previously installed one. Exchange 2013 … Read the rest “Exchange 2013 CU16 Released”
This is one of those handy little tricks to keep in a toolbox to narrow down issues when troubleshooting. It can be useful to understand if the client is connecting via Outlook Anywhere or MAPI/HTTP. To troubleshoot such issues MAPI/HTTP can be disabled on the client, and then re-tested to see if the issue continues. Note that permanently disabling MAPI/HTTP is not an acceptable solution, and t… Read the rest “How To Disable MAPI/HTTP For A Single Mailbox”
Exchange 2013 CU15 has been released to the Microsoft download centre! Exchange 2013 has a different servicing strategy than Exchange 2007/2010 and utilises Cumulative Updates (CUs) rather than the Rollup Updates (RU/UR) which were used previously. CUs are a complete installation of Exchange 2013 and can be used to install a fresh server or to update a previously installed … Read the rest “Exchange 2013 CU15 Released”
This post is to answer a recent customer question regarding if there is a requirement to perform a directory sync cycle after creating a new remote mailbox enabled AD user object before it could have an Office 365 mailbox created.
They believed that the on-premises Exchange tools were directly reaching out to Exchange Online and immediately creating the necessary mailbox in the service. This is w… Read the rest “Enable-RemoteMailbox – Is It A Chicken Or An Egg”
Exchange 2013 CU14 has been released to the Microsoft download centre! Exchange 2013 has a different servicing strategy than Exchange 2007/2010 and utilises Cumulative Updates (CUs) rather than the Rollup Updates (RU/UR) which were used previously. CUs are a complete installation of Exchange 2013 and can be used to install a fresh server or to update a previously installed … Read the rest “Exchange 2013 CU14 Released”
For those who worked with NT and Novell Netware many, many moons ago they became familiar with a handy function– who am I. Windows folks may also recall it when working with the Client and Gateway Services for Netware, and whoami.exe was also added to the NT Resource Kit. Remember the days of all the fun res kit tools? *
The whoami command does exactly what you would expect, it tells you who you … Read the rest “Remote PowerShell – PSSession WhoAmI”
The concept of arbitration mailboxes is not really new, they were first introduced in Exchange 2010. Arbitration mailboxes are used for several special tasks within Exchange and for the most part will tick away quite happily with minimal administrator intervention. System mailboxes have existed for much longer in Exchange, and again perform special tasks which are required by Exchange.
A lot of a… Read the rest “When To Move Arbitration Mailboxes”
After updating Windows 10 you may be unable to connect to a remote PowerShell session. This is an issue for versions of Exchange 2010 onwards as we use remote PowerShell for administration. The same applies for Exchange Online in Office 365. Note that directly loading the Exchange PSSnapin is not supported apart from a limited number of documented scenarios, for example this is one of them. For… Read the rest “Unable Connect Exchange Remote PowerShell Using Windows 10 Anniversary Update”