Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Chris Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Smart Upgrade ---> Replace Template

Status
Not open for further replies.

csjoseph

MIS
Jan 2, 2001
247
US
I'm new to this and I've just implemented Smart Upgrade to our test base. Most upgrades are from 6.5.? to 7.0.2. My problem is the new features are not available after upgrade because mail template is still iNotes6. I need them all on dwa7.

Is there a way to do this during the upgrade? Automatically another way? From Administrator client? Or do I have to do it on the users desktop?

Thanks for the help.
 
The quick and easy way would be to simply rename the R7 template name to the R6 template name.

Not to be confusing, I will detail the issue.

A Notes database has three possible names : the filename, the name users see on the workspace, and the template name. Of these three, two are generally filled in : the filename (mandatory) and the db title (generally but not mandatory).

To add to the confusion, filenames can have two possible extensions : nsf and ntf (Notes Storage Format and Notes Template Format). The ntf is generally the extension of template files, but that has nothing to do with the fact that file can be used for updating other files. Actually, the extension doesn't count. What counts is if the file has a template name. Nsf files can very well be used as templates !

The template name is optional and, in fact, most databases do not have a template name. However, many databases inherit their design from a template, which is a database that does have a template name.

The template name is a simple string of characters that should (ideally) uniquely describe the template. For instance, by default all mail files inherit from the Notes Mail template of a given version.

Thus, you should have on your server a template file for R6 mail that is named something like mailR6.ntf. This file (if you check the Properties) has a template name.

If you have upgraded to R7, then you should also have a mailR7.ntf somewhere, with a different template name.

All this explaining now comes to this point : simply copy the R6 template name to the R7 template database. After doing so, do not forget to modify the R6 database template name to something else (add a few chars) to break the link and make the R7 file the "real" template.

That done, the next time the server runs the update task, the design of all mail files that use the R6 template name will be updated to the R7 design.

Now for a word of caution : when upgrading a Notes server, there is generally a procedure that automates updating the mail files. It may not be enough to just update the design, so you should check that there is not a command to enter once the design update is done.

Hope this helps.

Pascal.


I've got nothing to hide, and I'd very much like to keep that away from prying eyes.
 
Thank you for the info. The method I found is that in the Desktop Settings policy you can specify a version / template combonation. This way anyone that connects with the new 7.0.2 should get dwa7.ntf.

Wonderful!

Thanks again.
 
Looks like you already figured this one out on your own, my suggestion was to set a policy on the Admin server so when upgraded clients login, they will be moved to the LN Client desired.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top