Why Microsoft can’t stop Lotus Notes

While hunting for something completely unrelated, Google presented me with this analysis on CNNMoney dated back to 2004 1994 (Thanks Carl!). It’s an interesting read and some of the stuff could actually be highlighted again as part of the LotusKnows campaign.

And now that I got your attention I might actually share the search phrase I was typing in: “lotus policy change is clearing replication history -click”

I am having an issue here where a change in dynamic desktop settings is clearing out the replication history of local databases on laptop computers, enforcing them to run the ‘one time only – replication setup’ again. This is a bit of a problem as most of the Laptops are still connected via pretty old dial-up.
The desktop settings document got a new database link added to the list of databases to be created as new replicas on the user’s machine.

New database link

Has anyone had this behaviour before? Is there any workaround for that? Server and Client version are both 8.0.2.

4 Responses to “Why Microsoft can’t stop Lotus Notes”

  1. JYR Says:

    Hi,

    From Gregg Eldred’s blog
    Policy Training and Tips
    http://www.ns-tech.com/blog/geldred.nsf/d6plinks/GELD-7E769P

    Also, to debug your policy, you may try this Notes.ini setting

    DEBUG_DYNCONFIG=1
    DEBUG_OUTFILE=
    DEBUG_THREADID=1

    JYR

  2. Carl Tyler Says:

    And within a year of the article, IBM had merged with Lotus.

  3. Carl Tyler Says:

    Because it was 1994 not 2004.

  4. Carl Tyler Says:

    The really interesting thing about that article though, is no mention of the internet.

Leave a Reply


Creative Commons Attribution-NonCommercial 3.0 Unported
This work by cubetoon is licensed under a Creative Commons Attribution-NonCommercial 3.0 Unported.