Groupwise updating mailbox decompressing

Free Busy has long been the holy grail of e-mail migration coexistence. Users can survive without it where they can’t easily survive without mail flow, and the migration can’t even start with some provisioning solution.

Factor in the additional cost for a coexistence products to deliver the optional benefits, and many customers in many projects proceed without free busy as an option.

These two components when configured correctly can handle: 1) Object provisioning, matching and merging 2) Mail routing 3) Provide free busy There is a very well written series of articles here that can walk you through this if you are interested, and as recently as September 2013 I’ve had requests to assist with this setup, so while it’s old technology it’s still very much on the table.

It does however rely on even older technology on the Group Wise side.

Exchange 2003 as a target system does provide the “Connector for Novell Group Wise” and the “Calendar connector”.

On Wed, GMT, Simon Shilton Simon Tim ___________________ Tim Heywood (SYSOP) NDS8 Scotland (God's Country) ___________________ In theory, practice and theory are the same In Practice, they are different Group Wise Clients that Cache do not update their Group Wise Address books I am running Group Wise 6.0 Sp3 POA/MTA/GWIA/WEBACCESS and clients.Your agency's IT department will set up the EMCAP tool in your Group Wise client so that it looks like any other folder.This means that archiving your e-mail is similar to moving messages to a cabinet folder.Some third-party connectors exist, including Scalix, Zarafa, Zimbra, and the Google Apps BES Connector, although these are not supported by Black Berry Limited.Prior to version 4.0, BES was largely two separate codebases, with the 2.2 version for Domino and the 3.6 version for Exchange.

Leave a Reply