After the server migration (Win2003 to Win2012) , new hub server information (IP address) is updated in the client package. So the LN configuration will be done automatically by using HUB servers IP address. We realizes that FQDN should be updated instead of IP address, So Notes client package is updated with FQDN. But need to update existing users local connection document that was created with IP address.
Note: We should not create and send the button to users for updating their connection document. It should be done without involving users.
The most common way I know is to write a script in a database, all users open frequently, like their mail databases. In this case, it could be kn the database PostOpen event‘s handler.
Another way could be using panagenda‘s software, which is included starting with Notes 10 in an limited edition for free.
This can be done with additional tools for client management or with simple LotusScript.
Here is an example script to modify all IP- Addresses in the list to the corresponding hostnames:
Dim db as NotesDatabase
Dim viw as NotesView
Dim viwNav as NotesViewNavigator
Dim ve as NotesViewEntry
Dim doc as NotesDocument
Dim lstrIpAssignment List as String
Dim strIP as String
Set db = New NotesDatabase( “”, “names.nsf” )
Set viw = db.GetView( “Locations” )
Set viwNav = viw.CreateViewNav()
Set ve = viwNav.GetFirst()
While not ve is Nothing
set doc = ve.Document
Forall strServer in lstrIpAssignment
If doc.Getitemvalue( “OptionalNetworkAddress” )(0) = Listtag( strServer ) then
Call doc.Replaceitemvalue( “OptionalNetworkAddress”, strServer )
Call doc.Save( True, True, True )
End If
Next
Set ve = viwNav.GetNext()
Wend
This Script can be either put in the QueryOpen of the mailfile (create a custom Template for that), or in the QueryOpen of a document or database and you send the users a doc link / database link.
Alternatively you use an old notes.ini- Parameter called "StartupDb" (example: StartupDB=852573B2:00627A08, with 852... being the replica id of your "settings database").
This parameter can be set by policy once and your code is then in the queryopen of the database and can then remove the notes.ini entry after everything ran...
Experience has shown that you can't expect a particularly high success rate when the recipients of an email have to then click a button or link. Is this the reason for not wanting to involve them?
If Notes is still being used for email within the organisation and stored forms are permitted, another option would be to create a custom message containing logic in its PostOpen event handler similar to that shared elsewhere in the thread. There is then no need to modify the mail template. All the users need to do is read the message (so they are involved but only passively).
As i mentioned that this should be pushed either through policy or some other way without user intervention because the customer doesn't want to give any kind of task for them employees even press the button for such admin activities.
Since we don't have email setup and it has complete application environment, expecting a solution that can be triggered while open the DB suggested by Thomas Bahn or kind of policy can be used ?
If you need to push this, then with "Normal" policies you can only use the workaround with the StartupDB... Or you could add it to the code of one application that everybody uses (if there is such).
Otherwise I would strongly suggest to your customer to look at third party products as e.g. Panagenda Marvel Client: They can automatically configure these settings
