Yesterday, Microsoft issued its monthly security bulletin. This time around, the bulletin also includes a fix for a vulnerability that affects only Exchange 2013 environments.
When designing for a migration to Exchange Server 2013, chances are you’ll have to deal with public folders. Given that Exchange 2013 has been around for a while, you might think such a task would be a proverbial walk in the park. Of course, if you are looking at a cookie-cutter environment, you might be right. However, in every design there are elements specific to the customer that require a different approach.
On March 17th, Microsoft released Cumulative Update 8 for Exchange Server 2013. By now, we're all used to the idea that cumulative updates and not only Service Packs have also become a vehicle to introduce new features into Exchange. Hence, it is no surprise that CU8 comes with a bunch of new features and improvements alongside a myriad of bug fixes.
Often times I’ll find myself writing a blog post because the topic recently became relevant due to customer need. Other times I spend hours banging my head against the keyboard trying to resolve an issue and would like to keep others from going through the same ordeal.
In this particular case, I found myself thinking of this fall’s release of Apple iOS 8 & some of the traditional unexpected consequences that arose when used to connect to Exchange via ActiveSync.
Exchange Online running on Microsoft’s Office 365 cloud platform operates more than 100,000 servers to support some 60 million mailboxes. At least, that’s the best-guess estimate based on information provided by Microsoft at the Exchange Conference 2014, data in their most recent financial reports, and consultant analysis.
Anyone who runs an on-premises Exchange environment today would be forgiven for wondering how long their job will last, at least in its current shape. The sales pressure from Microsoft and other vendors to influence CIOs to consider moving workloads to cloud platforms increases all the time and the inevitable fear is that jobs disappear once work is transitioned.
For as long as Microsoft Exchange has existed, Outlook meeting corruption has been a consideration for those who rely on calendaring. Meeting corruption can appear in many forms. However, meeting corruption typically occurs when meetings disappear, when duplicate meetings appear or through other unusual anomalies that users may experience with an appointment.
Exchange 2010 recently introduced a new feature called "cmdlet extension agents." These agents can be called when a cmdlet is running, and can also perform extra tasks as a part of the original cmdlet. A recent Microsoft article has great information on understanding the Cmdlet Extension Agents. You can see which cmdlet extension agents are available by running this command in the Exchange Management Console (EMC):
Many people want to use multiple IP addresses on a single NIC interface with Exchange 2013 and Windows Server 2012. There are several reasons for this multi-homed IP configuration, such as various receive connectors for diverse applications (fax, SharePoint, gateways, etc.), or for an additional IIS website, amongst other things.