By default DirSync will run a delta copy of your Active Directory to Azure/Office 365 every 3 hours. You can, of course, log into the DirSync server and force it to run at any time. While this is a perfectly acceptable solution, it would be a better solution if there was a way to force DirSync to run without having to log into the DirSync server. As it happens, PowerShell does provide us with a way to do this.
Read moreHow long does it take to migrate a mailbox to Exchange Online?
On question I get from customers fairly often is how long it will take to migrate my mailboxes to Exchange Online from my on-premises Exchange organization with a Hybrid Exchange environment. As a consultant, I am required to answer “It depends”.
Read moreExporting email from Exchange Online
One question that comes up fairly often is “how do I get my email out of Exchange Online?” As with many questions about Office 365, the answer can be a bit less straightforward than you might think.
Read moreWhat do I use to replace TMG/UAG for my Exchange 2013 deployment?
Microsoft has stopped selling Forefront Threat Management Gateway, and will stop selling Forefront Unified Access Gateway later this year. With these products going away, a very common question I am hearing from customers these days is “What do I do to secure my Exchange deployment now?” As a consultant I love this question because it gives me a chance to give my favorite answer; “It depends”.
Read moreRBAC: Exchange vs Lync
On 10.11.12 Microsoft released Exchange 2013, Lync 2013, and SharePoint 2013. These three products were designed to work together in new and unprecedented ways. None of these products is “complete” without being intergraded with the other two. Given that, one would assume that if you know how a feature like RBAC works for one of these products you would know how it works for the others. Turns out that is not the case.
Read moreWhat is Managed Availability?
If there is one thing I have learned in my 20 years as a messaging architect, it’s that things change. Technology advances, new software becomes available, hardware becomes less expensive and/or more reliable.
Read moreHow is an Exchange 2013 Service Pack (SP) different from a Cumulative Update (CU)?
Assigning licenses to Exchange Online users with PowerShell
You’ve setup your Office 365 tenant, you’ve configured DirSync, and you’ve done a test migration. Now you’re ready to start migrating your user’s mailboxes to Exchange Online in bulk. The last hurdle before you can do a big batch migration of mailboxes is assigning licenses to user’s accounts in the Office 365 portal. Sure you can click through each user in the portal one-by-one and assign licenses, but I’ve done migrations with tens and even hundreds of thousands of mailboxes and assigning all those licenses one-by-one would make anyone crazy. Good news loyal readers, I’m going to show you how to license those user’s accounts with PowerShell.
Read moreScripting your remote PowerShell connection to Exchange Online
When migrating a customer to Exchange Online, one of the most time consuming parts of the project is training the administrators how to use a new set of interfaces for managing their new Exchange environment. Even administrators who are well versed in PowerShell tend to be unfamiliar with the process of connecting to the remote PowerShell instance of their new Exchange Online tenant. Today I am going to share with you a simple script that will make that learning curve a little easier.
Read moreVirtualizing Exchange 2013
Server 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 moreMailbox Size Limits for Exchange 2013 Mailboxes
You’ve decided to upgrade to Exchange 2013. You’ve heard that Exchange 2013 causes “Mailbox bloat.” You’ve got tons of different mailbox quotas, and there does not seem to be any real rhyme or reason as to why they are applied.
Read moreServer Maintenance with Exchange 2013 – A Step by Step Guide
So you’ve deployed Exchange 2013 in a highly available configuration. Now it’s a couple of days after “patch Tuesday,” and you’re ready to update your servers. You’ve applied the patches in question to a test server, and you’re confident that they will not have adverse effects on your Exchange servers.
Now what? Do you just apply the patches, and let the high availability features in Exchange keep your users connected? What is the proper order in which to patch your servers? Do all of your servers need to be running at the same patch level, or can you apply some patches to one server, but not another?
Load Balancing Exchange 2013 CAS
Exchange 2013 has reached RTM, and is now available for sale. In late February, we expect the Service Packs to be available that allow us to deploy Exchange 2013 into existing Exchange environments. With Exchange 2013, we will have several new options for load balancing the Client Access servers and I would like to quickly go over those options now.
Exchange 2013 Architecture
Exchange 2013 has been designed with some architecture changes from the previous versions of Exchange. One of the biggest changes is that Exchange 2013 has been released with only 2 server roles. Those roles are the Client Access Server and the Mailbox Server. The functionality of the Hub Transport and Unified Communications roles from the previous two versions has been added into these two roles. Additionally the CAS role been redesigned so that its only job is to proxy connections to the proper Mailbox Server. (There is a single instance where the CAS server redirects connections instead of proxying them, but that is not relevant to this post). In doing this redesign, one of Microsoft’s major goals was to enable better High Availability options for the CAS role.
Read more