Not yet. When we implement the Filters concept, that's the kind of thing that'll be available (i.e., filter by date-range, filter by exchange category, etc.).

'Though not as easy, one strategy is to copy the calendar (e.g., via Outlook) then remove entries such that you have an archive/history calendar and a current one.

Personally, for active mailboxes, calendars, etc. I typically archive entries by year, normally doing the item move a month or a quarter "behind" so my current mailbox/calendar/whatever has sufficient history that suits the typical workflow for that mailbox/calendar/whatever. I prefer this strategy because it tends to help performance, reduce "clutter" (especially enabling more focused search results) and reduces risk of corruption and makes recovery easier in the event of any problems — not that software ever has any problems, of course.   #;-)

Nope, sorry. Sync'Em will not be supporting Exchange 2003 — time to upgrade!   #;-)

If you're using a hosting service that doesn't have Exchange 2007 available, you can find providers that work with Sync'Em on our Exchange Hosting Providers page.

The EWS (Exchange Web Services) interfaces were not present in Exchange 2003 so we'd need to use the OWA interfaces. Aside from the fact that that would require reverse-engineering, it'd also prevent us from being able to do the same kind of job that can be done with Exchange 2007. In addition, the market for an Exchange 2003 version is on a fairly steady decline.

Good to hear things are working smoothly. Yes, don't know how that little memory leak slipped into 1.23, but it's gone with 1.24 (so I guess things weren't "as easy as 1 2 3").   #:-)

Not sure what you mean by a "private" calendar but, in addition to personal folders (maybe that's all you mean), Exchange shared and public folders are also supported so there shouldn't be any problem as long as you have adequate Exchange permissions. See the Knowledgebase articles about syncing Exchange shared folders and syncing Exchange public folders for more information.

Events are sync'd with the Exchange calendar folder and iCal calendar as defined by the setup in your Sync'Em preferences. To sync different calendars, you'll need to use different sync setups since a given sync setup is for aggregating — i.e., syncing "together" — a given collection of information sources. Sync'Em is not limited to syncing only A <=> B, but can multi-sync A <=> B <=> C <=> etc.

You should view the Sync'Em Tour video to learn about using the Advanced Setup capabilities, if you've not done that already. The videos are available via the Videos tab in the Sync'Em preferences or the Download page.

If you mark calendar events as "private" in Exchange, that information will be shown as part of the "[SyncEm Data]" in the iCal calendar event. See the Knowledgebase article about the "[SyncEm Data]" stuff for more information. In fact, the example iCal graphic in the article about how Exchange categories are represented in iCal calendars shows an event that was marked as private in Exchange. As long as you maintain the same "[SyncEm Data]" format, you can add/change/delete "[SyncEm Data]" entries and they'll be sync'd as changes. So, I'm guessing, "awesome" it is!"   #;-)

[a few seconds later...]
As I committed the response, I (finally) noticed the "Subject" (du-oh!) and see that you're asking a bit of a different question.

Bidirectional syncing means that all the information sources that are being sync'd will brought to the same content/state. Thus, the only way you can sync multiple iCal calendars into a single Exchange calendar (and not have them all end up being the same) is to sync unidirectionally — i.e., set the information sources to sync "From" the iCal calendars "To" the Exchange calendar. That means that any changes made in the Exchange calendar will be ignored. Fortunately, Sync'Em will let you do exactly this. So I'm still thinking "awesome it is!"   #;-))