Thursday, July 31, 2014
MSExchange.org: Exchange 2013 Loose Truncation
from Exchange News Full Article
Wednesday, July 30, 2014
Anderson Patricio: Important update available for Exchange Server 2013 hybrid deployments
from Exchange News Full Article
Exchange Team Blog: Important update available for Exchange Server 2013 hybrid deployments
An important update is now available to resolve issues customers are currently experiencing when using the Hybrid Configuration Wizard (HCW) to create a new or manage an existing hybrid deployment with Microsoft Exchange Server 2013.
If you currently have an Exchange 2013-based hybrid deployment configured, you will not notice any issues unless you rerun the HCW as part of updating or managing your existing hybrid features. Unless you need to reconfigure your hybrid deployment, you can simply wait for the next update of Exchange Server 2013 (Cumulative Update 6) to correct this issue with the HCW.
For Exchange 2013 organizations creating new or managing an existing hybrid configuration with the HCW, the following HCW error message indicates you are experiencing the issue this update addresses:
Subtask CheckPrereqs execution failed: Check Tenant Prerequisites Deserialization fails due to one SerializationException: Microsoft.Exchange.Compliance.Serialization.Formatters.BlockedTypeException: The type to be (de)serialized is not allowed: Microsoft.Exchange.Data.Directory.DirectoryBackendType
If you experience this issue, contact Microsoft support to obtain the fix as documented in KB2988229. This fix requires Exchange Server 2013 Service Pack 1 (SP1) or Cumulative Update 5 (CU5).
Once the Interim Update (IU) is applied, customers can successfully run the HCW and complete configuring a hybrid deployment with Office 365.
Technical Product Manager
FAQ
Q: I’ve already configured a hybrid deployment with Exchange Server 2013 and I don’t need to make any changes to my hybrid configuration or features, do I need to apply this update?
A: No, you can wait for the fix to be delivered in the next Exchange Server 2013 update as long as you don’t have the need to run the Hybrid Configuration Wizard.
Q. I may need to make updates to my Exchange 2013-based hybrid deployment before the next Exchange Server 2013 update, what are my options?
A. If you need to update your hybrid deployment features before the next Exchange Server 2013 update, you’ll need to install the IU to fix the issues in the HCW. Attempting to manually configure a new or update an existing hybrid deployment without HCW can result in unsupported hybrid deployment states.
Q: Are customers who use Exchange Server 2010 impacted by this update?
A: No, this only applies to customers using Exchange Server 2013 to configure a hybrid deployment with Office 365.
Q: If we apply the update specific for SP1 or CU5 do I have to do anything special to update to CU6 or later in the future?
A: The interim update does NOT need to be uninstalled. We allow later CU’s to install over Interim Updates and Security Updates directly as of CU3.
from Exchange News Full Article
Tuesday, July 29, 2014
msexchange.org: Explore enterprise social scenarios
from Exchange News Full Article
msexchange.org: Update Rollup 3 for System Center 2012 R2 Data Protection Manager
from Exchange News Full Article
msexchange.org: Update Rollup 7 for System Center 2012 Data Protection Manager SP1
from Exchange News Full Article
msexchange.org: Automate Office 365™ Message Tracking with PROMODAG StoreLog 4
from Exchange News Full Article
MSExchange.org: Troubleshooting synchronization with Windows Azure Active Directory (WAAD) (Part 3)
from Exchange News Full Article
Saturday, July 26, 2014
Friday, July 25, 2014
msexchange.org: Calendar Checking Tool for Outlook v2.3
from Exchange News Full Article
msexchange.org: Office 2013 Administrative Template files (ADMX/ADML) and Office Customization Tool v15.0.4635.1000
from Exchange News Full Article
msexchange.org: Webinar: Tips for searching Outlook
from Exchange News Full Article
Thursday, July 24, 2014
msexchange.org: Update Rollup 3 for Microsoft Dynamics CRM 2013
from Exchange News Full Article
Tuesday, July 22, 2014
MSExchange.org: Troubleshooting synchronization with Windows Azure Active Directory (WAAD) (Part 2)
from Exchange News Full Article
Friday, July 18, 2014
MSExchange.org: Exchange 2013 with Rights Management Connector (Part 3)
from Exchange News Full Article
MSExchange.org: Deploying an Exchange 2013 Hybrid Lab Environment in Windows Azure (Part 11)
from Exchange News Full Article
MSExchange.org: Exchange 2013 with Rights Management Connector (Part 3)
from Exchange News Full Article
MSExchange.org: Deploying an Exchange 2013 Hybrid Lab Environment in Windows Azure (Part 11)
from Exchange News Full Article
Thursday, July 17, 2014
MSExchange.org: Exchange 2013 with Rights Management Connector (Part 3)
from Exchange News Full Article
Wednesday, July 16, 2014
Tuesday, July 15, 2014
MSExchange.org: Deploying an Exchange 2013 Hybrid Lab Environment in Windows Azure (Part 11)
from Exchange News Full Article
Friday, July 11, 2014
MSExchange.org: Troubleshooting synchronization with Windows Azure Active Directory (WAAD) (Part 1)
from Exchange News Full Article
MSExchange.org: Planning and Migrating a Small Organization from Exchange 2003 to Exchange 2013 (Part 9)
from Exchange News Full Article
Thursday, July 10, 2014
MSExchange.org: Troubleshooting synchronization with Windows Azure Active Directory (WAAD) (Part 1)
from Exchange News Full Article
Tuesday, July 8, 2014
Be Busbared: Unified Boxes, The Sum of all fears
Correction: By mistake I included SQL in the supportability statement, apparently I was was speaking about the stack as hall including backup, sorry for that.
Hi there, earlier this week, fellow MVP Michel Di Rooij published a blog post http://ift.tt/1o2MTHi speaking about NFS/Exchange support “Again”, the post motivated me to delve into the pool and add my experience.
The were some hesitation in the MVP community about if we should blog/speak about it or not, Michel was so brave to jump and speak about the topic, and after exchange some emails, we (including Fellow MVP Dave Stork) agreed that this blog is critical and we created it.
So, from where the story begins ???!!!
I am currently working for a major data center provider. In my current role we try to find new ways, innovate and find new technologies that will save us time, effort and money and my team was working on investigating the unified boxes option.
But before delving into the technical part, let me give you a brief background from where I am coming, my position as an architect in a service provide is an awkward position, I am a customer, partner and a service provide, so I don’t innovate only, I don’t design only, I don’t implement only, I don’t support only and I don’t operate only, I do all of that, and that makes me keen investigating how every piece of new innovations will be designed, implemented, supported and operated.
Now speaking about the unified boxes, I was blown away with their capabilities. The capabilities of saving space, time and effort using these boxes are massive, but there is a catch, they use NFS, the source of all evil.
NFS has been used for years by VMware to provide “cost effective” shared storage option, a lot of customer adopted NFS over FC because of the claimed money saving and complexity, but NFS has its own issues (we will see that later).
I was a fan of the technology, and created a suggestion on ideascale.com to bring the issue to the PG attention, we did our best but Microsoft came back and informed us that NFS won’t be supported, they have their own justifications, we are not here to speak about it because we can’t judge Microsoft, but the bottom line, NFS is not supported as storage connectivity protocol for Exchange.
Now the reason of this post is to highlight to the community 2 things:
- NFS is not supported by Microsoft for Exchange (any version), there is no other workaround this.
- Choosing a unified box as a solution has its own ramifications that you must be aware about.
I am not here to say nutanix/simplivity/VMware VSAN..etc are good or bad, I am highlighting the issues associated with them to you, and the final decision will be yours, totally yours.
I was fortunate to try all of the above, got some boxes to play with and tested them to the bone, the testing revealed some issues, they might not to you, but they are from my point of view:
- Supportability: Microsoft doesn’t support placing Exchange on NFS, with the recent concerns about the value of Exchange virtualization (see a blog post from fellow MVP Devin Ganger http://ift.tt/1xfa5sq) using these boxes and these set of technologies might not the best way for those specific products, you might want to choose going with physical servers or other options for Exchange/SQL rather than going with non-supported configurations, although that vendors might push you to go for their boxes and blinding you with how great and shiny these solutions are. The bottom line, they are not supported by Microsoft and they won’t in the near future.
- Some of the above uses thin provisioned disks, meaning that disks are not provisioned ahead for Exchange which is the only supported configuration for virtual harddisks for Exchange. Disks are thinly provisioned meaning they are dynamically expanded on the fly as storage consumed which is another not supported configuration.
- The above boxes have no extensibility to FC, also you are limited to a max of 2 * 10 GbE connections (I don’t know if some have 4 but I don’t think so) meaning that you have no option to do FC backups, all the backups will have to go through Gbe Network, we can spend years discussing which is faster or slower, in my environment I run TBs if not PBs of backups and they were always slow on GbE networks, all of our backups as to be done over FC.
- The above means you will run backup, operations, production and management traffic on single team on shared networks, maybe 2 teams or will run it over 1 GbE, this might be fine with you, but for larger environments, it is not.
- The above limitations limits you to a max number of network connection, a single team with 2 NICs might be sufficient to your requirements, 2 teams maybe, but some of my customers have different networking requirements and this will not fit them.
- Some of the above boxes does caching for reads/writes, I have some customers ran into issues when running Exchange jetstress and high IO applications, the only solution as provided by the vendor’s support is to restart the servers to flush the cache drives.
- Some of the vendors running compression/deduplication in software and this requires a virtual machine of 32 GB or larger to start utilizing deduplication.
- All of the above uses NFS, meaning you will lose VAAI, VAAI is very critical as it accelerates storage operations by offloading those tasks directly to the array, you can use VAAI with NFS with virtual machines that has snapshots or running virtual machines, meaning that you rely on the cache or you must shutdown the virtual machines to use VAAI, VAAI is very important and critical element, so you must understand what are the effects of losing it.
- Those boxes don’t provide tiering, tiering is another important if you are running your own private cloud, by allowing you to provision different storage grades to different workloads, also it is important if you want to move hot data to faster tiers and cold data to slower tiers. Tiering touches the heart and soul every cloud (private or public) and you must understand how this will affect your business, operations, charging and business model.
- From support/operations and compliance point of view, you still running unsupported configuration from disk provisioning and storage backend, again it is your call to decide.
I am not saying that unified boxes are bad, they are a great solution for VDI, Big Data, branch offices, web servers and applications servers and maybe databases that support this sort of configuration, but certainly not for Exchange.
We can spend years and ages discussing if the above is correct or not, valid or not and logic or not, but certainly they are concerns that might ring some bills at your end, also it is certain that the above configurations are not supported by Microsoft, and unless Microsoft changes its stance, we can do nothing about it.
We, as MVPs, have done our duty and raised this as a suggestion to Microsoft, but the decision was made not support it, and it is up to you to decide if you want to abide to this or not, we can’t enforce you but it is our duty to highlight this risk and bring it to your attention. And as MVPs and independent experts, we are not attracted to the light like butterflies, it is our duty to look deeper and further beyond the flashlights of the brightest and greatest and understand/explain the implications and consequences of going this route so you can come up with the best technical architecture for your company.
from Exchange News Full Article
MSExchange.org: Planning and Migrating a Small Organization from Exchange 2003 to Exchange 2013 (Part 9)
from Exchange News Full Article
Friday, July 4, 2014
Subject Exchange: Weekend reading
from Exchange News Full Article
msexchange.org: Azure: Internal load balancing GA
from Exchange News Full Article
Thursday, July 3, 2014
MSExchange.org: Exchange 2013 with Rights Management Connector (Part 2)
from Exchange News Full Article
Tuesday, July 1, 2014
MSExchange.org: Deploying an Exchange 2013 Hybrid Lab Environment in Windows Azure (Part 10)
from Exchange News Full Article