CU5 upgrade can’t continue because powershell has open files

Issue: While installing Exchange 2013 CU5 you receive the following error message: "Setup can't continue with the upgrade because the powershell has open files.  Close the process, and then restart Setup." Solution: I didn't have powershell running, and could not easily locate the process and didn't want to start killing processes so I rebooted the server and then re-tried setup and the powershell error did not show up again.  If you determine what process causes this, please post it in Read more [...]

Upgrade existing Exchange 2013 installation to CU21 step-by-step

Issue:  You need to confidently upgrade an existing Exchange 2013 environment to the latest version of Exchange 2013, CU21. According to Microsoft you can upgrade from any version of Exchange 2013 to Exchange 2013 CU21. Upgrade to CU21 Step by Step: 1) Follow this link to download the latest version of Exchange 2013. Note: if you are running a DAG, review this article: How to install Exchange CU updates on a DAG. 2) Execute the downloaded file on the first Exchange server you will be upgrading Read more [...]

Exchange 2013 CU6 Released

Exchange 2013 CU6 (Cumulative Update 6) was released on 8-26-2014.  Note: CU6 has been replaced, click here for CU9. Microsoft has made significant progress in resolving the public folder limitations of Exchange 2013 in CU6 by increasing the public folder limit to 100,000 folders. Public folder migration processes may be streamlined/improved in CU6 CU5 does not fix the bug requiring IIS app pools to be recycled to allow ActiveSync connections after mailboxes are moved to Exchange 2013 Read more [...]

email backed up in Submission Queue “mailbox database thread limit exceeded”

Issues: email is backing up in the Exchange Submission Queue and the following errors are displayed in Queue Viewer: 432 4.3.2 storedriver component has been retired 432 4.3.2 STOREDRV.Deliver; mailbox database thread limit exceeded Processor is also pegged at 100% or close to it on the hub transport server Potential causes of this issue for others but were not the cause in my cause: -exceeded mailbox size quotas on the database, especially a journal mailbox / database -under-powered Hub Read more [...]

How to allow outside senders on a set of Distribution Groups

Issue:  You need to allow mail from outside senders to all or a large set of Distribution Groups using the Exchange Management Shell rather than modifying each group one by one using the GUI Exchange Admin Center or Management Console. Solution: Use Management Shell commands to search for any distribution groups or dynamic distribution groups that match a phrase and modify the Outside Senders setting. Note: you will need to specify your group name you want to search for followed by a "*" Read more [...]