Does the Exchange Migration Wizard 2005 for Lotus Notes support the migration of local Lotus Notes Mail Archive Databases?
The MigWiz does not support migrating local Notes mail archive databases currently. You have two options in this scenario:
1. Have the end user replicate their mail archive database(s) to the server and use the MigWiz to migrate them.
2. Use third part tools that support migration of local Notes mail archive databases.
Does Application Analyzer 2006 for Lotus Domino (AA06) support older versions of the Domino server (like R5 and R4)?
We have tested and support running AA06 against Domino R5 and 6 servers. Customers have told us that they have successfully run AA06 against Domino 4 servers, but we have not tested this configuration.
Have a great St. Patricks day and stay safe!
I have a few questions that I have posted on my blog. Maybe not questions exactly but maybe you can speak to them. I would be interested in your response to what my finding on the MSAA for Domino tool is. If I have gotten the working of the tool wrong, let me know. (since I am unsure of your support for html tags, I will direct you to my blog and the two most recent entries.)
I'll chime in on this one since I have bloged about a similar question last week.
You had some interesting comments about how the tool is/can be used. We have already posted about most of this but I will highlight some relevant points.
A> Using the tool; The tool is intended to help customers considering a transition get an accurate picture of their existing Domino applications based on ussage and a quadrant classification model. (IE: What applications are based on templates vs custom, and identify what applications contain workflow.)
B> Finding template applications; Template applications are important to report on since the strategy can be repeated for all applications of that template. Say a company has a template that they use for customer-tracking. If they find that template used 100 times, then whatever their plan is for that application <coexistence, migration, leave in Domino, etc.> they can apply that same solution for the rest of the instances.
C> Customizing the reports; Given that there is not an 'industry standard' set of templates, and that customers plans/solutions will need to be unique, we allow for the customer to customize what applications are considered as templates and what the recommended solution should be. Say a customer decides knows that they have an common 'expense reporting' template used by different groups and would like it left in Domino for what ever reason, then they can modify the XML to indicate that the recommendation for this template is to be on Domino.
D> Misuse of the AA; The ability to modify what templates are reported along with recommendations is to allow customers to customize the AA to get an accuate understanding of their specific application set and their specific plans. Mis-using the AA (by modifying the AA without the customer involvement and/or their understanding of the changes) by anyone with he intent to give the customer an inaccurate view of an environment is bluntly dis-honest and a misuse of the tool. (Although we have not specifically blogged about the mis-use of the AA this seems obvious.)
E> Using the tool/Sharing Configurations; Anyone can use the tool, customers, partners, IBM partners, etc. We have no restrictions on who can use the tool. Also, we figured that configurations might be shared (This allows for common templates that may be seen in different companies or common solutions can be shared.) I see no real issue with this as long as the customer is aware of the mappings and it represents the customers plans/desires. Our default mappings that we ship with the tool are well documented and based on the standard IBM templates mapping them to similar WSS solutions.
Anyway, thanks for looking at the tool. Our intent is and will continue to be to help customers who are transiting to a MS platform with guidance and tools around the planning, coexistence and migration phases of these projects.
So, this is indeed a sales tool.
Additionally, how would a customer know that the tool has or has not been bastardized to suit the needs of say a company who wants to move business to their own preference? The customer should not be left wide open to this possibility so maybe this download needs to have some sort of disclaimer stating the data contained was developed using a perferences file. There are customer that may not know about this and could affect both IBM and Microsoft customers.
I am sure that there are unsavory types that would abuse this tool. At the very least, protect the customers that could be making decisions based on this tool.
Don't get me wrong, a sales tool is a sales tool, but the customer needs to be protected since this is so easily customizable.
It is a planning tool used in the <Plan and Prepare phase> of the PPCM process (I blogged about that process here) I do expect a go/no go decision during the planning phase so yes having accurate data will help make that decision. But I also intend that the data from the AA to be used/helpful beyond just that decision, during project plan, proof-of-concept, and other planning operations in this initial phase.
I think that the feedback of bubbling up the customizations changes in the XML (or the fact that the XML might have been changed) is great feedback and something that we should consider in an update. I am sure that someone who is dishonest could get around whatever we do, (heck they can just mock up their own report), but I think it would still help especially since customers can run this tool themselves.
Anyway, thanks for the comments.