Friday, February 01, 2008
Zimbra to Yahoo to (possibly) Microsoft?
I envision an episode of Oz or some "reeducation camps" inspired by the Chinese Cultural Revolution.
Whatever comes we're still cranking away on our migration technology -- ironically we've (almost) completed the first prototype for an Exchange to Zimbra migration.
Now, of course, we're also working on migrating Zimbra to Exchange.
This is not a surprise to those of you who have dealt with us in the past. Our decision process on which projects to work on is based on simple free market economics: who is asking us to do things and are they willing to pay for it?
Wednesday, January 23, 2008
Terminated Users, Broken Meetings, and Exchange 2007
We've heard it referred to as the "terminated user" problem and it works like this:
Yorick, a diligent young exec just fresh from his MBA with little experience other than managing his BMW and his credit cards, has been busily setting up meetings with people across all departments. He is now gone but his meetings live on. (Note: We realize this is an idealized scenario. In the real world Yorick would be promoted while people with far more experience but higher salaries and more benefits would be nuked wholesale, but we try not to be bitter.)
So recurring meetings managed by Yorick, which might or might not be relevant anymore, are sitting in calendars across the company.
You the Exchange Administrator would like to get rid of them wholesale, but there's no way of doing this except for logging in as Yorick and manually finding and cancelling all meetings, making sure to send updates. Multiply this hassle by the body count in your reorg.
But it does not need to be like this.
Since as part of our calendar migrations we're creating and deleting meetings ALL THE TIME, we've started experimenting with some tools based off our insertion code that will go through a user's calendar, cancel all meetings they proposed, and automatically send updates to guests.
Problem solved.
We've started with a congruent problem: finding orphan conference rooms from cancelled meetings and built it into our main code via the "Test" button (which those of you in the midst of E2K7 migrations have gotten used to)
To check for orphan conference rooms:
Why are we telling you all of this? Because we're looking for folks who really want the problem solved and are willing to work with some early code to help us work out the best way to invoke and use this in the Exchange environment.You're going to need to set Permissions for a service account to run this app as you would for a migration -- so be advised of that. But we're more than happy to share this with folks who contact us directly looking to try it out.
Sunday, January 20, 2008
Outlook Meeting Reminders: OL2003 + E2K7 = Confusing
15 Minutes seems to be the magic number for a meeting reminder default when you put Outlook 2003 in an Exchange 2007 environment.
Expect that under a variety of conditions of meetings being proposed to and from OL2003 that the default will be set to 15 minutes on the ATTENDEE's calendar, regardless of where it was set in the meeting ORGANIZER's, and regardless of the ATTENDEE's Default reminder setting.
The situation arises with default settings and reminders if Outlook 2003 is the origination point. We haven't (yet) seen problems with OWA or Outlook 2007.
There are in the support database a variety of problems listed with meeting reminders in Outlook (appointments seem to be working OK, but maybe that's just our eyes glazing over).Among the classics:
The reminder for the meeting is removed when you accept a meeting request in Outlook 2003 which is based on Rules removing reminders
A reminder for an all day event meeting request is reset to 18 hours when you send the meeting request in Outlook 2003 which is self-explanatory.
Try just hitting the support.microsoft.com and searching for "Outlook reminders".
Saturday, January 19, 2008
findItem and restrictions in EWS code
Basically: you can't use FindItem with restrictions that use SUBSTRING in an EWS XML query:
<restriction>
<t:contains containmentmode="Substring"
ContainmentComparison="IgnoreCaseAndNonSpacingCharacters">
<t:ExtendedFieldURI PropertySetId="00062008-0000-0000-C000-000000000046"
PropertyId="34100" PropertyType="String"/>
<t:Constant Value="mmConv102659080256Z"/>
</t:Contains>
</restriction>
So in contrast to almost every other release Microsoft has done for Exchange -- SP1 actually IMPROVES the migration process! I feel like Fred Sanford expecting to join Elizabeth imminently.
Friday, January 18, 2008
Exchange 2007: to sp1 or not to sp1?
We do this using keywords.
For Exchange 2007 pre-sp1 because we were under the gun to complete the code for a migration in July, we took a quick path that placed the keyword in the "Subject" line (and created an option to remove these).
For sp1 we no longer insert our keywords into the Subject: line (meaning you get all the benefits of our back out capability without the annoyance of having to remove the keywords).
Bottom line: either pre-sp1 or sp1 will support a calendar migration, but each method requires a different version of the insertion code.
Consult with Sumatra if you need to decide which version to use during your migration.
Update: January 19, 2008: We've confirmed there were some bugs with EWS that the sp1 service pack fixes. We'll blog on it soon.
Wednesday, January 16, 2008
Rate Limiting Steps in an Exchange 2007 migration
Keeping in mind that in 2007 we use EWS, you've got to think of the migration as running via HTML. So network efficiency and I/O are the crucial factors.
Russ produced this list of limiting factors (in priority order)
- Speed of the SAN (Mostly it's I/O bound)
- Speed of the NETWORK (Next, it's related to how fast HTTPS requests are
sent/received) - Speed of the SERVERS (CAS, then MBX) (Third, how fast the Web Services Requests are PROCESSED)
- Speed of the 32-bit (Fourth, how fast those requests are GENERATED)
In Exchange 2000/2003, where we used CDO, the horsepower of the individual back end Exchange server played a more crucial role.
Wednesday, January 09, 2008
Categories and Extended MAPI Properties in Exchange 2007
We set these items on messages in the meeting organizer's calendar. But wait--those categories and extended MAPI properties do not get transmitted with a messages in Exchange 2007! A PSS call yesterday confirmed that this behavior is possibly a bug.!?! I'll re-post if we find a solution
Here's the most relevant part of the code that adds categories (using XML):
<t:CalendarItem>
<t:ItemClass>IPM.Appointment</t:ItemClass>
<t:Subject>Russ and Nancy 1 on 1</t:Subject>
<t:Categories><t:String>mmConv102659080256Z!9</t:String></t:Categories>
<t:ExtendedProperty> <t:ExtendedFieldURI PropertySetId="00020329-0000-0000-C000-000000000046" PropertyName="SumatraKeys" PropertyType="String"/> <t:Value>E1D5E39F08206011E39F9218</t:Value></t:ExtendedProperty>
Tuesday, January 08, 2008
Zimbra and Private Activities / To-Dos
Since Zimbra pre-version 5 does not have Private capability at the meeting level we've done all of these options:
- Delete "Private" Activities / To-Dos before they are inserted (clean, easy to understand, infuriating for some users)
- Pre-pend "PRIVATE:" to the relevant activities (easy to find and the user can deal with them as they will)
- Separate the "Private" items into a separate database and insert into separate calendars. A little time-consuming all around, but it worked this weekend at a migration in Pennsylvania.
In Zimbra 5 this all becomes moot -- but we want to make sure current clients contemplating a Zimbra migration know their options.
Thursday, January 03, 2008
Exchange 2007 sp1
Russ ran an insertion in the test lab with no problems.
We have a field test coming up this weekend and we'll let you know the real world results.
Saturday, December 15, 2007
Contacts Migration into Zimbra
Contacts get exported as CSV files which you can upload with curl or zmprov.
To create them:
- Create a directory called c:\sumatra\contacts
- Open the Database and go to "Macros"
- Double click the macro entitled "M_OutputZimbraContacts"
- Walk away from the machine for about a half hour. We haven't done a good interface for telling where things are in the process, but if you look at the directory you created you'll see the contacts files being created.
- They'll be in the form LOGIN_ID.csv so it's hard to confuse them with the calendar files
Right now this only works for Meeting Maker contacts because we can read them server-side.
For Oracle Calendar Server contacts, which we can only read client-side, we'd need to do something different. Which we will if we hear sufficient demand.
Friday, December 14, 2007
Accessing Exchange Resource Mailboxes
That Microsoft post did say the only way to access disabled-account mailboxes with EWS is to use Delegate Access. Sumatra's support team suggests an additional use for the script as an easier way to set up access to the resources, particularly when an end user "manages" one or more resources.
http://msexchangeteam.com/files/12/attachments/entry447730.aspx
Thursday, December 13, 2007
The 1300 limit and the 256 exception limit
Check out his article. Put that Babelfish translator to the test.
Now, one other limit we've seen is that it's impossible to create more than 256 exceptions to a recurring appointment. While this happens in some legacy data we've seen it usually happens with appointments entitled "lunch" which go back 4-5 years.
Tuesday, December 11, 2007
Exchange 2007 migration - alerts to pagers / cell phones
Those of you who are familiar with SuExchange2007.exe will see the "Configure Alerts" button in the upper right hand corner, along with a tiny cell phone icon.


With fairly straight-forward options and input fields.
Why would you want this? If you're asking you've never been through a migration.
This is going to be great for administrators because:
- Now they can move from their workstation and make sure everything ELSE is going on
- Now they can keep tabs on the process from home or late night pizza
- Now they can keep others informed about migration status
Monday, December 10, 2007
Free/Busy Data, Outlook 2003, and Exchange 2007
Users who use Outlook 2003 cannot publish their free/busy data in Exchange Server 2007
Friday, December 07, 2007
Resource Scheduler for Outlook/Exchange migration flow
This is an excellent overview of scheduling resources in Exchange 2007.
Phase I: Resources scheduled via Outlook

Resource accounts MUST:
- Exist and be mail-enabled in Exchange 2007 and Active Directory
- Be configured to process meeting requests
- Client (that's you) must provide a map between RSOE resource name and Exchange Resource alias/email address
Testing and Use:
Service Account defined with impersonate + send-as permissions
- Test this in a lab prior to running in production
- Sumatra code will run on a 32-bit machine (NOT on a 64-bit server)
- Code will use Exchange Web Services through an Exchange 2007 CAS
- End Users use Outlook 2007
- Meeting updates:
a) Accepted as part of Exchange 2007 features,
b) might remain in all end user’ inbox post-update and will not be removed - The Sumatra process:
a) will not check for resource double-booking or conflicts
b) will work on CURRENT meetings only – it will skip expired/completed meetings as determined by RSOE’s meeting end date
c) will not configure Exchange resources with settings to ensure resource will behave as RSOE resources (i.e., you control the process by provisioning your resources as you want beforehand)
d) Responses from Exchange’s Resource management will remain in the meeting organizer’s inbox
e) Note: Outlook-booked meetings are defined as those meetings, found in the user’s Exchange "Calendar" folder, that have an "RSOE" meeting tag (The tag is attached to the meeting as a hidden MAPI code.)

PROCESS ASSUMPTIONS:
See assumptions from Phase 1.
Phase 2 should be run after phase 1 completes
The Sumatra process:
- Creates a meeting with the name "RSOE_Migrated" in the organizer’s calendar. The meeting with have the resource as the only "attendee". All Direct-booked meetings will be created as one-time meetings.
- Does not check for double-booking or conflicts (That's what Exchange is for).
For the resource: If a conflict exists, Exchange will decline the meeting request
For the meeting organizer: A "double booked" meeting will be added to the end-user’s calendar - Works on CURRENT meetings only – it skips expired/completed meetings as determined by RSOE’s meeting end date
- Does not attempt to link or match this meeting to an existing meeting in the
organizer’s calendar - Note: direct-booked meetings are defined as those meetings in booked in RSOE that do not have an outlook "RSOE" tag.
- Responses from Exchange’s Resource management will remain in the meeting organizer’s inbox
- Meeting times are recorded in RSOE as the server’s "local" time, and will be added to the meeting organizer’s calendar in the "local" time and time zone (even if the meeting organizer is in a different time zone.)
Friday, November 30, 2007
Migrating from Oracle Calendar or Meeting Maker? Upgrade to Zimbra 4.5.10
Ms. Migrations recommends upgrading to Zimbra 4.5.10 if you are migrating from either of the legacy systems Oracle Calendar Server or Meeting Maker.
Version 4.5.10 fixes this problem:
http://bugzilla.zimbra.com/long_list.cgi?buglist=20684 which you are likely to encounter in a migration.
Thursday, November 29, 2007
Exchange 2007 Permissions
Exchange 2007 is shaping up to be a bigger headache. Think migraine. Think migraine with sinusitis. Then double it. You know what I mean. We have had to create an entire Label for permissions.
However, we would really like to thank Rohit from Extreme Networks for coming up with the following variation on setting permissions.
He was looking to migrate Resource Scheduler, but it's just as viable for general calendar migrations.
If you're using Ex2007 as the service account to run our code, execute this command:
Get-OrganizationConfig Add-AdPermission -user ex2007 -accessRights GenericAll -extendedrights "Receive as","Send as", "ms-Exch-EPI-May-Impersonate", "ms-Exch-EPI-Impersonation" -InheritanceType All
Takes care of all necessary permissions with one swoop.
(Note: Revised 2/15/2008 -- a pipe ("") should be place between get-organizationconfig and add-adpermission. It was stripped when pasting the command line in this blog)
Update 11/11/2010:1) Added '-InheritanceType All' to the commandlet. Sometimes permission inheritance issues prevent access to calendars.
2) Remember that RESOURCE accounts must be ENABLED (via ADU&C)
3) If you want to look at calendars via OWA, you need fullaccess. This commandlet grants 'exsu' full access to all accounts in the domain:
Get-Mailbox -resultsize unlimited add-mailboxpermission -user exsu -accessrights: fullaccess -InheritanceType: All
--Russ
Tuesday, November 20, 2007
Migrating RSOE (Resource Scheduler for Exchange) data into Exchange 2007
Well, because of a request from the West Coast we went ahead and did it. They mainly use RSOE for straight-forward room reservations and are looking to simply transition to the resource reservation features in Exchange 2007. So all we're interested in is moving the reservations in as few steps as possible into Exchange. We make no effort to recreate most of the other features of RSOE (prep time, cleanup times, etc.), all we're doing is transitioning the resource management over.
Here's how it works.
There are two ways to reserve a resource in RSOE:
- Via a from in Outlook
- Directly from a web browser
So we deal with each of these cases differently.
From Outlook
This is the easy case. Resource Scheduler puts a MAPI flag and an RSOE identification number in the meeting.
Technical background: Those of you who know how to use OutlookSpy (an invaluable tool for the Exchange developer) can look for RSOCEntryID.
We read this from the RSOE SQL database into an Access database and (since we know the meeting organizer and can uniquely identify the meeting via the MAPI tag), we add the E2K7 resource to the meeting and update it.
The code relies on Outlook 2007/Exchange 2007 to automatically apply meeting updates if an end user has already accepted that meeting. e.g. a time or location change to the meeting is received, the meeting will be automatically updated and the old invitation marked out of date so users will not accidentally accept it. See the TechNet article:
http://www.microsoft.com/technet/technetmag/issues/2006/12/outlook/default.aspx
DONE.
From the Web
This is a more interesting case and we took the most general way of solving it.
Since there is no unambiguous link between the meeting reservation in RSOE and any existing data in Outlook (and a quick look at real world data will convince you that just being at the same time and date is not enough), we just create one meeting owned by the resource owner, with the resource in E2K7.
E2K7 books it and then the meeting organizer can add users or modify as they see fit.
PROCESS ASSUMPTIONS
- Resource accounts MUST:
a) exist and be mail-enabled in Exchange 2007, Active Directory
b) be configured to process meeting requests
c) Client must provide a map between RSOE resource name and Exchange Resource alias/email address - Testing and Use:
a) Service Account defined with Impersonate and Send-As permissions
b) Test in a lab prior to running in production!!
c) Sumatra code runs on a 32-bit machine (NOT on a 64-bit Exchange server)
d) Code uses Exchange Web Services through an Exchange 2007 CAS - End Users use Outlook 2007
- Meeting updates:
a) accepted as part of Exchange 2007 features,
b) might remain in all end user’ inbox post-update and will not be removed by our code (up to the end user). - The Sumatra process:
a) does not check for resource double-booking or conflicts
b) works on CURRENT meetings only – it will skip expired/completed meetings as determined by RSOE’s meeting end date
Wednesday, November 07, 2007
Oracle Calendar Command Line Conversion
For an Oracle Calendar to Zimbra migration he suggested "Why not make the OCS conversion command-line driven? Then we can script the entire process end to end."
Not a bad idea -- so we went ahead and did it.
OraCalReader.exe is our tool that takes OCS Export files from UNICPOUTU and turns them into our intermediate format (from here they can go into Exchange or Zimbra).
So now to run this on the DOS command line:
OraCalReader /ALL /TZ:tzValue /TH:xx /DROPDT:"dt" /EXPDIR:pp /OUTDB:ppdb
Notes:
- If you run /ALL without any other command line parameters, the code takes the DEFAULT settings saved in the UI preferences. UI preferences are visible by running the application without any switches on the command line
- The code will read the export files and insert them into the database.
- The code's default behavior is to delete ALL existing data in the database prior to insertion.
- Two Logfiles are generated: _OraCalReader_log.log, and _OraCalReader_Error.log
/TZ:tz Timezone.
Acceptable values are: EST5EDT CST6CDT MST-3MDT PST8PDT
NAST9NADT MST7MDT GMT0BST MET-1METDST MEZ-1MESZ
CIST-12:45CIDT IST-2IDT MST-3MDT UCT-5:30 UCT-7 CST-8 UCT-8
JST EST-10EDT UCT6 UCT4 UCT EST5EDT
/Th:xx Threshold xx is a percent, ranging from 1 to 100, Default is 80
This is a number, not a decimal. Exclude the percent sign
/DROPDT:dt DROP/Cutoff Date Where dt is any valid date format in US format time, e.g., mm/dd/yyyy, mm-dd-yyyy
One year from today
/EXPDIR:pa OCS export file directory (path) Where: Pa is any path, e.g.:“f:\data\ocsout”
Defaults to the current path. The path should be enclosed in quotes. Do not include a trailing "\"
/OUTDB:db MS Access Output database Where db is the name of the database, including the path NO DEFAULT You must specify this parameter!
So the following would be a real world example:
oracalreader /all /TH:80 /TZ:"EST5EDT" /EXPDIR:"C:\Documents and Settings\Zyg\Desktop\Tech Data" /OUTDB:"C:\Documents and Settings\Zyg\Desktop\Tech Data\gt3-prime.mdb" /DROPDT:"11/1/2006"
The above command specifies an 80% recurrence threshold, Oracle's Eastern Standard Time, directories and database as shown, and to only take calendar data AFTER November 1, 2006.
Wednesday, October 31, 2007
Zimbra Insertion: Suppress Resource Responses
BUT you notice that the INBOXes of meeting organizers is full of responses from the resources post-migration.
Not to worry -- you can turn that off with:
zmprov mcr
Just don't forget to turn it on again when you go live.
Many thanks to the folks at Zimbra for cluing me in and to Jennifer who field tested it!