We need to force a replace design of the mailfile and the local addrtess boon (names.nsf) of users for a migration from 6.5.1 to 6.5.4, so they can have the new Sametime and DWA features available.
We are considering using Policies for the mailfile part, but what about the local address book template? We thought about using a button in a memo we’d send to users, but that would require a lot of follow-up and rely too much on users to complete the task. Is there a better way to do it without the need for complex software push scripts and such?
Subject: Best way to force a design replace of Local Address Book after Client Migration from 6.5.1 to 6.5.4
For the follow up, you could create a mail-db to keep track of users who received the button.
In your button, put a “return receipt” flag for those who have clicked on your button. Those flags would be return to your mail-in. So, you would have a centralize db with your users who didn’t click on your button yet.
Subject: RE: Best way to force a design replace of Local Address Book after Client Migration from 6.5.1 to 6.5.4
Thanks for the answer. Seems liek it was already what we were planning, I just wanted to see if anyone else would have a better idea. Thanks for the input!