Welcome to Kraft Kennedy

Autonomy (HP) recently released WorkSite Server 8.5 SP1 Update 6, with a new enhanced server-side email duplication detection technology.  Previously, the FileSite client would evaluate duplicates based on the MSG_ID value from Exchange.  This often caused problems with forwarded messages, or certain Outlook forms that share a MSG_ID.  Update 6 enables server-side duplicate detection based on the message send date and message subject, in addition to the MSG_ID.   So this now means that forwarded messages are NOT duplicates, and would also be filed – a little something to keep in mind when it comes to expected storage on your file servers and indexers.  More emails will be filed with the new algorithm.

Continue reading…

I recently performed an upgrade from iManage 8.2 to iManage 8.5 Update 4.    Update 4 was released on January 14th and resolves several issues regarding service stability and wildcard searching.  It adds support for the new WorkSite FileShare, iManage Workflow Manager, and iManage Digital Safe.  I plan on blogging about these modules soon, so keep an eye out for that.

But the real reason for this post is that Update 4 sets the database schema version as 8.51 (all previous releases of 8.5 had set the schema version as 8.50).  This value is listed as the MHVERNUM column in the MHGROUP.VERINFO table of the WorkSite database.   For those of you looking to migrate from an environment with WorkSite Indexer 8.2 SP1 P2 (Verity), there is a compatibility problem with this change.   Although Indexer 8.2 SP1 P2 was released in order to support iManage 8.5 servers for a transitional period, the 8.2 Indexer services fail to start when the database has been upgraded to the 8.5 Update 4 schema.   Autonomy’s workaround for now is to modify the MHVERNUM value and set it to 8.50.  This can be done by executing the following SQL query:

Continue reading…