With the latest Cumulative Updates for Exchange server 2013 and 2016 Microsoft has made a change to “Mailbox Anchoring”. What does this mean? Why did they do it? How will it affect me? Read on, and I shall attempt to explain.
Read MoreIn a recent article I explained the process of sizing your processors for Exchange 2013. Hopefully I explained that process is a clear and understandable way, but there is something I left out. How do virtual servers affect this process? The answer, as always, is “it depends”.
Read MoreIn June of 2013, Microsoft released an update to the DirSync appliance that allowed it to sync passwords from an on-premises Active Directory into Azure Active Directory for use in authentication. Since then, Microsoft has also released AADSync, which is a more advance version of DirSync that allows for more complex on-premises Active Directory configurations to be connected to Azure Active Directory. Recently AADSync was updated to include the password sync feature.
Read MoreOne component of properly sizing Exchange deployments that I do not think is well understood is the process of sizing processors. In this post, I am going to walk you through the process of sizing the processor for your new Exchange 2013 server deployment.
Read MoreI’m working on an Exchange migration project. I did a green field Exchange 2013 deployment to migrate users to from a hosted solution. During the process I created about 3200 new mailboxes, and I must have done something wrong because those mailboxes ended up all clumped up in a couple of the databases. The problem I ran into is there is no good way to see your mailbox distribution across a number of databases in the Exchange Admin Console.
Read MoreI recent ran across a case where a customer had recently migrated to Exchange 2013. As one of the final steps in the migration, they migrated their public folders to modern public folders on Exchange 2013. After the public folder migration was complete, the users were unable to delete or modify pre-existing public folder items even though they appeared to have the correct permissions
Read MoreThe new phonebook is here!
OK maybe you don’t need to be that excited about this version of my Get-EDSData script. I have just completed rewriting this script to work off a CSV file instead of using parameters for input. This means that you can create a csv file with a list of as many performance counters as you’d like and then run Get-EDSData against that csv file to find out if those performance counters went over the thresholds you sent during the period of time you have Daily Performance Logs on your Exchange 2013 server.
Read MoreWhen we left our intrepid hero, I had just completed a very basic script to collate a single performance counter from the daily performance logs of an Exchange 2013 server into its own .blg file. The code for this script looked like this...
Read MoreIf you saw my blog post last week on Pulling performance counter data from daily performance logs you now know, as I do, that Exchange 2013 records a ton of performance data on your Exchange server by default. I was recently out on a walk, where I do some of my best thinking, trying to come up with a way to make use of all that data. Thusly was the Get-EDSData project was born. I am by no means a PowerShell expert. I’m not quite a PowerShell novice, but honestly I am probably closer to being a novice than an expert.
Read MoreServer virtualization is a very common trend in almost all corporate data centers. In many cases virtualization provides a lot of benefits. Today I am going to talk about why virtualization is almost never the best option for Exchange 2013. I’ll address several aspects; supportability, hardware utilization, economy, and high availability.
Read More