Template not upgrading via desktop policy

HCL Domino Domino Forum
1

We have desktop policy under mail template info. set to following. (see attachment)

We currently have workstations running Release 9.0.1 FP1 running 852 template but whatever reason it’s not upgrading mail9 template. I did come across an issue where the client version was showing 9.01FP1 but the notes.ini FaultRecovery_Build= only showed Release 9.01.

Since then, I’ve added Release 9.0.1 under Use This Mail Template.

Waiting on the customer to see if it’s working now. Meantime, the question I have for Notes Xperts here is when you upgrade the template via the desktop policy, does the policy looks at the notes.ini or help about in the Notes client? Do both of these need to match in order for it to work? Any other settings the policy looks at?

Thanks in advance…

p.s. I was not able to upload the image. Here is the setting under Mail Template Information.

Old design template name for your mail files: *

If Running This Version Of Notes: Use This Mail Template:

Release 9.0.1FP1 mail9.ntf

Release 9.0.1FP2 mail9.ntf

Release 9.0.1 mail9.ntf

2

Subject: Thanx Mark!

Appreciate the post. I did not know it only runs when client is being upgraded. We’ll give it a try on the workaround. Thanks again…

3

Subject: Yeah, that threw me for awhile.

Sorry - I gave you bum information before. Different issue. Here’s the real deal:

When you upgrade the client, the client version gets written to the User’s Calendar Profile. So, even if you upgrade the client a second time, the mail file upgrade doesn’t get kicked off. This was driving me nuts while I was testing a 6.5.5 to 8.0.2 upgrade scenario.

In order to force the client to look at the Desktop Settings document again, you need to clear out the mail setup fields on the Calendar Profile, then install the client again.

To test - add this agent to your mail file:

Option Public
Sub Initialize
Set session = New NotesSession
Set db = session.currentdatabase
Dim item1 As NotesItem
Dim item2 As NotesItem
Set doc = db.getprofiledocument(“calendarprofile”)
If doc Is Nothing Then
MsgBox “No Calendarprofile Profile…Closing the agent”
Else
Set item1 = doc.ReplaceItemValue( “MailSetup”, “0” )
Set item2 = doc.ReplaceItemValue( “MailUpgradeFolder”, “0” )
Call doc.Save ( True, True)
MsgBox “MailSetup and MailUpgradeFolder item has been reset in Calendarprofile document”
End If

Call session.SetEnvironmentVar(“TemplateSetup”,“000000”,True)
Call session.SetEnvironmentVar(“MailSetup”,“000000”,True)
Call session.SetEnvironmentVar(“MailUpgradeFolder”,“000000”,True)
Call session.SetEnvironmentVar(“Setup”,“1”,True)

End Sub

Once you run it, shut down your client, and reinstall a version that you have listed in your Desktop Setting document.

That should do it. And this should give you a way to test when you make changes to your Desktop Settings doc.

For users already upgraded, just run the mail file upgrade/convert utility on the server.

4

Subject: ONLY runs when client is upgraded

Even though this is set on a desktop Policy, it’s actually only checked when the client is actually upgraded. So, if you’ve upgraded the client, then later update the Policy, nothing happens.

I believe that if you ‘delete’ (or set to ‘0’) the following line, the setting will be checked at the next client start:

TemplateSetup=900100
Setup=900100
MailSetup=900100
MailUpgradeFolder=900100

I don’t know the answer as to whether the Notes.ini or ‘client help’ settings are checked, I believe that it’s the client that kicks off the upgrade, I think by clearing the aforementioned lines the process will kick off.

Hope that helps!

edit 11/25/2014 - deleted incorrect and misleading information. -mat