This blog post covers a summary of the session from Paul Collinge and Jeff Mealiffe about a recommended network architecture to get the most out of Office 365.
The enterprise connectivity challenge is that most customers are using a lot of expensive network equipment for the outgoing and incoming network traffic to and from the Internet. For example, proxy servers, WAN accelerator, secure web gateway, intrusion prevention system, etc. All of this network and connectivity equipment is expected because all things outside is unknown and untrusted.
But this model doesn’t fit with the cloud world of Office 365 and causes various connectivity problems.
Continue reading “BRK3081 – Implementing a modern network architecture to get the most out of Office 365”
Read more at the ENow Software Blog.
I would like to share some Exchange 2010 hybrid migration facts with you that we figured out.
First, again many thanks to Michael Van Horenbeeck! He helped me discuss this with a customer. I’m always very happy to work with him. And many thanks to Ben Winzenz and Jeff Kizner as well, I’m very grateful for your help.
In short: a customer is trying to keep about 65k mailboxes in sync to ensure a short cutover time. We are using a maximum of 1,500 mailboxes per batch, 5 batches per week, and switching 7,500 mailboxes with an overall data of about 5TB per week. For some technical details, we are using Azure ER (800 Mbit) for migration with 4 TMG as a proxy and some kind of F5 load balancing in between, PAW is activated, and two migration endpoints with each 100 sync/complete in parallel. We did some networking measuring and move request statistics and we had an average migration velocity of 18.6GB/h for batches starting the first incremental sync (0% to 95%) which is great. Of course, the migration velocity depends on the number of batches, mailboxes, mailbox items, network workload, etc.
Continue reading “Exchange Hybrid MRS vs. MigrationService Migrations”
Large enterprise customers often have unique and specialized requirements for adoption Exchange Online. This session showcases the lifecycle of an enterprise customer leveraging features designed just for them. Demo and some several new features will be covered, such as Mailbox Plans, Client Access Rules, on send event APIs, and a first look at technology for mergers and divestitures.
The full recorded session can be found here: https://www.youtube.com/watch?v=pN6lsxKRrJQ&t=1503s
This blog post covers a summary of the session. Continue reading “Microsoft Ignite 2017: BRK3155 – Thrive in as an enterprise organization in Microsoft Exchange Online”
What is the best, DAS or SAN? Are SSDs on the way in or are slow spindles here to stay? Should you give up and migrate to the cloud? What about virtualization? This session covers the various Exchange architectures that can be deployed on-premises and hybrid.
- Exchange 2016 now supports up to 192GB of memory
- Item Recovery Enhancements
- Should I follow the PA? Yes. If it is possible, follow the PA. This is the tested and best practices solution from Microsoft running in Exchange Online. This simplifies the operation process in case of outage, failures, etc.
- Should I deploy SSD? No. Jeff Guillet mentioned a good example for this. If you are using SSD’s for Exchange, it is like you are driving a Ferrari on a gravel road.
- Should I virtualize Exchange? Yes and no. Of course, you can virtualize Exchange. Be sure that you use the calculator for virtualization 1:1 as you would do it for physical servers. Physical servers are more easier to manage and deploy because virtualization needs some more things to do.
- What should I do if I plan to have a hybrid deployment with O365? Follow the same approach as you would do it for an on-premises environment. If all your mailboxes are migrated to Exchange Online, use a single Exchange server for recipient management purposes only.
- What size mailbox should I deploy? Are 1GB mailboxes valid anymore? You already get 25GB mailboxes for free today and simple JBOD storage is a very low cost factor.
- Third-party archiving solutions or keep in Exchange? The Microsoft perspective is that archive mailboxes should be retain in Exchange. In case of big mailboxes and Outlook OST slider, there is no reason to use archive mailboxes anymore. If you are having strict compliance regulations for archiving, you can use Exchange, Exchange Online, or of course third-party archiving solutions.
Matt Gossage and Ananth Sundararaj show how Exchange Online works. The engineering leaders who design and build the infrastructure reveal the secrets of deep neural networks, machine learning, substrate, shards, and much more. They also share how these mystical creatures actually impact IT pros and users of Exchange and Outlook.
Continue reading “Microsoft Ignite 2017: BRK4029 – Inside Exchange Online”
I recently had a curious behavior in my customers Exchange 2010 SP3 hybrid environment with centralized mail transport for Exchange 2010 SP3 Edge servers enabled.
Before I describe the topic in more detail I would like to say thank you to the guys from Microsoft: Timothy Heeney, Scott Landry and Tom Kern helped me with my ‘little’ mail flow problem . Appreciate your help.
My customer is using a smtp gateway for external mail flow as usual. Some of the mailboxes have configured smtp forwarding like ForwardingAddress (mail contact) and ForwardingSMTPAddress (external smtp address directly set on the mailbox).
Read more at the atwork.blog
We’re happy to announce our fifth free ‘Office 365 Pills’ conference in Nuremberg, Germany on 16th June this year. We’re looking forward to speak about some Office 365 and Exchange news.
Download my German Exchange 2016 hybrid HOL documentation from the ITvNext conference:
Microsoft released the quarterly servicing update to Exchange Server 2013 – CU8 and updated UM Language Packs. Cumulative Update 8 includes the following new features and improvements:
• Calendar and Contact Modern Public Folders favorites added in Outlook are now accessible in OWA
• Batch Migration of Public Folders to 2013 improves migration throughput and PF migration experience
• The number of supported Public Folders has increased once again for on-premises deployments (O365 limits remain the same)
• Migrating up to 500,000 public folders, a 200% increase from CU7
• Support up to 1,000,000 public folders, a 400% increase from CU7
• Smoother migration for EAS clients to Office 365 with automatic profile redirect upon successful Hybrid migration to Office 365 (EAS client must support HTTP 451 redirect)
You can read the full blog post at the Exchange Team Blog.
Download Cumulative Update 8 for Exchange Server 2013