Public Folder Replica Script – Office 365 Preparation

Public Folders. Yes. Even in 2019 we are still talking about Public Folders. Whether this is so we can remove them, fix them or sync them to Office 365, they are still around. For the last option, syncing Public Folders to Office 365, first you may think ‘Why?’, but come to the conclusion that you have no alternative and need to move them. If you are planning to move them to the cloud, knowing your data sources for syncing as well as remote access of the Public Folders for mailboxes already moved to Office 365, can be important. This means checking your replicas. If your replicas are off, syncing Public Folders may miss information and those users in Office 365 may not see some folders.
How to Check Replicas?
Public Folder replicas are almost a thing of the past. Once support for Exchange 2010 is gone and companies finally move off, we never have to worry about Public Folder Replication again. This is because Exchange 2013 introduced Modern Public Folders where HA or ‘replica’ copying was provided by Database Availability Groups. Thus a Pubic Folder, stored in a mailbox, which was store in a mailbox database that had multiple copies was now protected by the DAG replication. For this exercise, we don’t have that to look to and must examine what replicas were configured manually for each Public Folder in the environment. Here are some quick one-liners to see these replicas:
Continue reading

Quick Powershell Stuff 30

Wanted to share an interesting find while using PowerShell in Exchange 2019. The cmdlet is ‘Get-OrganizationConfig’ and I Was looking over some information from a summary report I had exported for a client and noticed an interesting field called ‘OrganizationSummary’. So I did a little digging.

Get-OrganizationConfig | Ft OrganizationSummary

We see this information about the Exchange environment:
Continue reading

Adding Exchange 2016 CU14 to Hybrid Exchange 2010/3

Recently Microsoft has made some changes where you are required to run a few extra commands prior to upgrading your Exchange 2016 servers to the latest Cumulative Update (CU) 14. The change relates to permissions needed for Exchange and the first change was made in CU12 for Exchange 2016 – KB4490059. A further change was introduced in Exchange 2016 CU13 – June 2019 Quarterly Updates article.. In the article, the wording is a bit unclear as to what steps we need to take (see bolded words):
In order to apply these changes, a directory admin will need to run the cumulative update setup program we are releasing today with the /PrepareAD parameter. When multiple Exchange versions co-exist in a single Active Directory forest, the cumulative update matching the latest version of Exchange deployed should be used. Setup will automatically run /PrepareDomain in the domain where /PrepareAD is executed. Environments with multiple domains in the forest will need to run the cumulative update setup program using the /PrepareDomain parameter in all domains in the forest. These steps will update the rights granted to Exchange Servers in the Active Directory to meet the new permissions scope. More information on /PrepareAD and /PrepareDomain is available at this link.
Continue reading

.NET Versions and Exchange

Microsoft has their own Exchange Supportability Matrix which covers many parts of what is supported with a particular version of Exchange. What you will find is that some charts that are included are a bit wanting. A Lot of older and historical information has been pulled. A fellow MVP, Michel de Rooij posted a a good reference chart for Exchange servers. From that I created a new one and separated all CU’s out and updated it to include the newest CU’s released in June 2019. The chart will look like this:

I plan to bookmark this on the menu bar of my blog to be used as a good reference. If you like it, please make sure to leave feedback. Thanks!

Cumulative Update Repository

To help those who manage Exchange On-Premises, I wanted to create a repository for CU and UR updates for various versions of Exchange. This project had moved forward much slower than I wanted to and am now at around 95% done uploading CUs for Exchange 2013 and 2016 as well as 100% done for Exchange 2010 SP1/SP2/SP3 URs. If you are looking for any Exchange 2019 downloads, they will never be posted here. These are only available via the Microsoft Volume Licensing Center. Please do not ask for a copy as I cannot provide it.

To download old CUs and URs, please refer to the below links:

Exchange 2016 Cumulative Updates (95%)
Exchange 2013 Cumulative Updates (100%)
Exchange 2010 (100%)


** NOTE **

For those who are running Exchange 2019, please note that the Volume License Center does not appear to hold the previous versions of Exchange 2019. Only the current CU appears to be listed. Right now the RTM version is not listed on the site. As there is no public trial or download of the RTM version of Exchange 2019, there is no ability to compare versions. We should be able to confirm if this is the future when CU2 comes out. If it does, this will confirm an even more drastic version of Exchange update availability than has previously been known. With 2013 and 2016, there were usually 3 versions available for download (Current CU and then the teo previous CUs). Now we only have one available version.

The move object info message is too large. Current size 17,592,186,042,368 MB limit 480 MB

THAT message. Yes THAT message. I received this for a bunch of mailboxes I was moving From Exchange 2010 to Exchange 2016. The complete error is confounding and does not make much sense:
So what is the solution? The error’s solution is rather simple. There is an existing move request for the mailbox being moved. The solution is to remove any move requests. However, if the move request exists in Exchange 2010 and we try to remove this request from Exchange 2016’s PowerShell interface we get this error: Continue reading