多年来，我写了一些关于解决Microsoft Exchange中日历损坏、日历委托、错过约会等问题的权威性指南。在过去的几个月里，我收到了一大堆寻求帮助的电子邮件和电话，所以我想是时候在这里更新我的博客了。当我第一次关于外汇日历问题的博客，群众还远远没有遇到问题，但问题确实存在，我认为问题有三个方面:
- Microsoft Exchange(当时是2003年和2007年)在时间同步和消息同步跟踪日历约会方面存在问题。实际上，当多个用户或设备修改日历约会时，Exchange不会按照更改的顺序应用更改。Exchange的早期版本没有预期到对单个对象的多次授权写操作，因为具有多个委托和移动设备的世界在类似的时间对同一个约会进行更改
- ActiveSync实现通过手机供应商(苹果最明显的移动供应商)有bug ActiveSync抓住一个同步连接,不会释放它,或者同步不是正确的时间戳,或一个众所周知的bug,移动用户下降一个反复出现的会议将有整个循环约会之后删除,等等。这些来自苹果在ActiveSync的错误是最常见的错过约会和重复约会的根本原因。
- 日历委托是我在“日历损坏和问题”中发现的第三个问题，在这3个问题中，没有一个热修复或补丁来解决这个问题。并且随着组织日历委托现在工作的多个端点，其中Exec有3-4个设备和Exec管理有3-4个设备，我们看到最近出现了一系列日历问题。
在我的第一篇博客发布几个月后，我写了一篇关于日历问题的更新关键更新。这是2014年的更新，关于解决微软Exchange的日历错误和日历问题。
解决后端问题——#1对于那些仍然使用旧版本Exchange的组织来说，迁移到最新版本Exchange(或迁移到Office 365)已经消除了“后端”这个问题。然而，我看到的是一些组织在进行部分迁移，并将一些有问题的预约提前到新环境中。我曾见过一些使用exchange2007或2010的组织升级exchange2013服务器，并将高管和管理人员放在新服务器上，但仍然遇到日历问题。你在Exchange 2013(或Office 365)上，这只是解决方案的一部分。首先，日历问题仍然受到第2号(设备)和第3号(用户)的影响，因此将用户迁移到最新的Exchange/Office 365只解决了3个问题中的1个。其次,组织一些移动的用户一个新的服务器,如果其他用户在组织仍在旧交换2007/2010服务器,发送重复的人约会的车版的iPad从Exchange 2007邮箱的高管在2013年交换,任命仍将坚持日历iPad和Exchange 2007的腐败问题。如果发送者从他们那有bug的iPad上删除了重复约会中的“本周会议”，它也会删除所有与该约会相关的内容。我们看到这样的例子越来越少了，因为iPad/iPhone的错误在2年前就被修复了(在ios4.3或更早的版本中)，然而令人惊讶的是，有多少次我们进入一个环境，发现有人仍然在用ios4进行同步。x尽管有iOS 7。x最近外出了……除了针对“全新Exchange 2013环境”的用户和设备问题之外，另一个问题是，一旦日历约会被破坏，它将永远被破坏。 As the Exec's mailbox (with old corrupted calendar appointments) is migrated to a shiny new Exchange 2013 server, that mailbox still retains the older corrupt appointments. Example, if a recurring appointment got corrupt and deleted all future instances of the appointment, and then that appointment is migrated to Exchange 2013, Exchange 2013 won't mysteriously re-insert in the recurring appointment meetings. This is one of the most frustrating things in isolating this problem as corrupt appointments remain corrupt.What we have found works best is to jot down any time an appointment is wrong and then fix it by sending out a completely new appointment / recurring appointment to replace the old one. And not simply update/resend the old appointment, I mean create a brand new appointment. That new appointment will not bring along the problemsome issues.BUT, this is where the chicken and egg comes in to play... The org that simply tried to solve this problem by moving just a handful of Execs/Admins to the latest Exchange but did nothing to address other users in the org, to address old versions of endpoint clients, nor address user interactions will only find the problem pops up again. The sequence to solve this problem has been:
是的，对于企业正在经历的日历问题，有一个解决方案，而且我不得不说，至少有三分之二的问题可以从技术上解决。
针对Microsoft Exchange的版本，我们发现，随着一些组织加入到最新的Exchange 2013版本中，或者将他们的电子邮件转移到云端的Microsoft Office 365中，日历损坏的“后端”问题已经得到解决。微软补丁和更新交换2007年和2010年解决尽可能对消息和日历同步,但是微软Exchange 2013的重构(和Office 365, 2013年建立在交换)最小化队列时间和和解消息写时间,这样有更少的延迟和更少的变化,后端是写日历预约的顺序和日历腐败挑战的一部分。
- 首先教育用户/高管/行政管理人员-代表(并要求他们在方法论上勤奋，尽管遗留在日历上的旧东西仍然会出现问题，保持一个干净的例行程序)
- 确保端点已更新，没有旧设备或OS/iOS版本的bug
- 升级到最新版本的Exchange或云中的Office 365
不亚于大多数机构单位我跑地说，他们是他们的某些用户使用的是最新版本，不可避免地，当我们做了现场评估和检查交易所ActiveSync的日志中，我们发现各种连接到Exchange设备。最常见的是，我们找到了Exec的有一些老的iPad，他们的孩子偶尔使用这些天，每个人都忘了这仍然是注册到Exchange，而当设备被连接到无线网络，一下子该系统同步与Exchange和我们”见过插入腐败设备到电子邮件和日历约会。检查Exchange ActiveSync的日志，它会显示哪些设备连接和客户端操作系统的版本使用。任何的iOS 4.x版确实需要更新，很坦率地说什么的iOS V5.x中应该更新too.I没有看到它往往这些天，但任何人在苹果机上运行的Entourage电子邮件应该升级到Office 2011年初。Entourage中的版本很快损坏，日历，因为Entourage中没有公认的图形和附件的日历约会，从而剥离出来，并更新了预约。这一权利腐败插入任何/所有立即日历约会。但是同时我们确实发现Mac用户正在运行Office 2011，再次，有老系统Exec的家里都有自己的配偶使用这些天主要用于上网冲浪出现这种情况还是有在其上运行的Entourage的旧副本，每一个现在然后该系统同步和腐败日历。检查同步将确定连接到Exchange的终端设备相关的Exchange日志，确保你真正了解其客户终端的版本（移动和桌面）都连接到Exchange.SOLVING的用户问题 - ＃3The用户键解决问题压延交换。 As I've related it in previous blog posts, the analogy I use is if we all shared a complex word processing document with lots of fonts, formatting, embedded graphics, special margins and borders and some of use Word 2013, some use Word Perfect, some use WordPad, some use Word 2007, some use Google docs, would ANYONE wonder why the document somehow lost its formatting, fonts got screwed up, margins got screwed up? Every time you open that word processing document with a different word processor, you can assume "something" in that document will get screwed up.THAT is what is happening with calendars, plain and simple. Calendar appointments commonly have embedded fonts and graphics (yes, your auto-signature at the bottom with the company logo, or the "please be green" graphic is part of the calendar appointment). Recurring appointments, to this day, are foreign to a lot of calendar apps on mobile phones that simply think of an appointment as a single event, even prior to iOS 4.3, Apple didn't recognize recurring appointments properly. So every time users open up, edit, change, decline an appointment from one device or another, they are effectively "editing" the appointment with a different calendar software program, no different than someone opening up a word processing document that doesn't support graphics, which strips out the stuff it doesn't understand, and saves the information with the edited (missing) information.SO, the request to users, especially those with delegates, is to minimize the number of different client endpoints (and different types of endpoints) in use. If the Exec is using Outlook 2013, then the Exec Admin should run Outlook 2013. For accepting and declining appointments, if the Exec Admin is in charge of the calendar, then the Exec Admin should always accept and decline appointments, try to have the Exec themselves refrain from also accepting and declining appointments.Regarding this last point, when the Exec declines, and the Exec Admin accepts the appointment, which one is it? You'd think it goes sequential, so if the Exec declines and THEN the Exec Admin accepts, that Exchange should ignore the 1st request, but wait, what if you first decline an appointment and later you realize you can attend the meeting and you accept, then the subsequent change should take affect.But the challenge is what if the Exec declines from their phone, but is in a fringe area and there's no signal. The Exec Admin accepts from their desktop, so the acccept is registered as the current state. The Exec's phone comes into signal range and the decline is processed, but Exchange sees the time of the decline as occurring BEFORE the accept, so Exchange ignores that change because it proceeds the decline, but wait, didn't we state that the last request should take place? THIS is why calendaring is not a perfect science, and to confuse the matter even further, Microsoft and Apple have changed the behavior back and forth (and back and forth again) with varying versions of Exchange, iPhone/iPads, patches/updates, etc. One version of iPad against one version of Exchange will have a different experience that another version of iPad against another version of Exchange.End of the day, the only thing that we've seen that has addressed this problem is to:
解决客户端软件/设备问题- #2
后台已更新到Exchange(或Office 365)的最新版本，请确保所有终端设备都使用最新版本的客户端软件。不管是针对Windows的最新Outlook 2013，还是针对苹果mac电脑的最新Office 2011，还是针对iphone / ipad的最新iOS，还是针对安卓/三星等设备的最新更新。
我讨厌把它称为“用户问题”，因为这会冒犯用户，而且坦率地说，用户日复一日的行为不应该是这些日历损坏问题的原因，然而，也许从政治上讲，这应该被称为“用户对解决方案的贡献”。坦率地说，微软、苹果、谷歌等公司都对这个问题做出了一些奇怪的贡献，最终，美国用户不得不尽自己的一份力量来解决这个软件的怪癖……
- 保持日历只接受/拒绝一个用户。如果执行管理员负责日历，所有的接受和拒绝只能由个人来做
- 保持日历只接受/拒绝一个系统。使用一个高度连接的(网络上的桌面/笔记本电脑)作为接受/拒绝约会的设备。当超过1人管理日程表时，不要使用移动设备来接受、拒绝、编辑、更改约会。由于连通性不佳，结果也不一致
- 如果你不能保持日历接受/拒绝1用户和高度连接系统,那么至少确保Exec / Exec管理系统类型是相同的(如果迫不得已,保持最新版本的Microsoft Outlook在Windows系统上(Windows)即:Office 2013)作为默认。
各种各样的物品
所以我现在已经解决了这个大问题。在序列: