The organisation I work for has about 5500 notes desktops and we are currently migrating from r4.6 to r6.01.
Because r4.6 did not support multi-user installations we have been running a custom “user switcher” for quite a few years. I am currently looking at how we can upgrade our all of our clients to roaming user/multi-user install. This is going ok until I get to machines that are used by multiple people.
When I do the installation I need the local names.nsf to be updated to the new r6 design. This works fine for the first user as the installation process upgrades this database. But when the second, third , fouth etc users login for the first time they run through the r6 workstation setup but their local names.nsf files are do not have their designs updated.
As we run a customer switcher to download and upload the users files everytime they login and out of notes r46 these problem pretty much effects every desktop on our network. Does anyone know of a way to force the design update of the local names.nsf on workstation setup??
Is there some setting I can put in the “All users” notes.ini file that will do this??. I really don’t want to have to ask 5500 users to manually upgrade their local names.nsf
Subject: R6 client upgrades and local database design problems
I don’t know about an ini setting but you could build a call into your setup routine or elsewhere that calls nconvert.exe names.nsf * pernames.ntf locally on the names.nsf. You may get prompted for a password but that will work.
Subject: RE: R6 client upgrades and local database design problems
HiAnyone knows what triggers an update of the Personal Address Book [names.nsf] to R6 design.
We have had the design updated for some but not for all.
Confirmed that for those that the design upgrade did not take place the user has Manager access to their Personal address book, the location of the file is in the c:\notes\data directory and names= line in notes.ini is correct.
Bookmark.nsf successfully migrated and so too log.nsf
I tried Rob’s suggestion. It works, however has the following issues:
Sends a mail message that the mail file has been upgraded.
Subject: RE: R6 client upgrades and local database design problems
HiAnyone knows what triggers an update of the Personal Address Book [names.nsf] to R6 design.
We have had the design updated for some but not for all.
Confirmed that for those that the design upgrade did not take place the user has Manager access to their Personal address book, the location of the file is in the xx:\notes\data directory and names= line in notes.ini is correct.
Bookmark.nsf successfully migrated and so too log.nsf
I tried Rob’s suggestion. It works, however has the following issues:
Sends a mail message that the mail file has been upgraded.
Subject: RE: R6 client upgrades and local database design problems
You must set the R6.5 Notes.ini settings as follows :
BookmarkDesignReplace=0 (it does not exists in the default R 6.5 notes.ini but it might exists in existing Notes.ini files)
and remove ini setting TemplateSetup=600304
After these few changes I found that the client would upgrade the local NAB to R6.5 at client startup.
From professor ini =>
Q. Could you explain the TemplateSetup parameter and its values?
The TemplateSetup setting and similar setup entries in the NOTES.INI file are used to determine whether certain databases or files should be updated as part of the install/upgrade process. These entries are intended for use by the install/upgrade process only and should not be edited.
