Wednesday, April 22, 2009
New feature - File Server Roaming in Notes and Domino 8.5 - Anyone is planning to use it?
Highlighting important information related to File Server Roaming in Notes and Domino 8.5
Doc #: 1329414
What is File Server roaming?
File server roaming is the ability to house a roaming user's files on a standard file server instead of a Domino server. This functionality has been requested by customers who have users who roam between multiple workstations but in a location without a "local" Domino server.
Did you know?
Anyone is planning to use it?
I'm gonna look in that directions, it seems vey interesting because it can be enabled via policies. It could also be enable in conjunction with the ID Vault
Original post
Offline folder - Running a Notes client data directory on a File Server
Tuesday, April 21, 2009
Offline folder - Running a Notes client data directory on a File Server
Is running Client Notes.ini and/or Notes Data directory on a File Server a supported configuration?
We are currently installed this way. If I want to remove this configuration and put all the Data files on the local drive, how would you handle this situation in your environment?
How can I back-up personal users' files (Names.nsf desktop, id)?
For our laptop users, actually, we have a batch script that copies network files to the local drive every time the users connects itself to the network.
Would it be possible to remove this batch and only use the Offline folder of Windows? The files would still be on a network drive.
Would it be useful to use .DIR files?
If I use the Offline folder via the My documents folder, would it be possible to modify the Notes shortcut to validate that a network connection eixst, if not launch Notes with the local data directory
Monday, April 20, 2009
US Soldiers' new weapon : An IPod
Blackberry - Unread documents - Lotus - Symantec Enterprise Vault
In the advanced db option, here's the info
I've read technote 1159331from IBM and few others from RIM but nothing useful.
The only thing we see right now, is the interraction with our archiving process from Symantec. This process reads every mails to see if it can be archive. We wonder if it can modify in some sort, the documents.
Thursday, April 16, 2009
Only a few days left for Notes-Domino 7 certifications
Wednesday, April 15, 2009
Answer - Archiving - View indexes - Size really does matter?
Like Graham said, the document size does not matter, those view sizes would be the same. The view is calculated based on number of documents, columns and sorting.
I've done a test. In this example, the Inbox is 88megs and the All documents view is 102 megs.
I did a test on a smaller db. I've removed almost every documents from the Inbox with this script (keeping only the last 90 days) : Link
My inbox's size have dropped to 700ko. It was 4,5 megs before. The size of the all documents's view hasn't change which is ok.
I will do the test on the biggest db (6,3gb) . On this db, the user have more than 25000 documents in his Inbox. I know that it's not recommanded (http://www.ibm.com/developerworks/lotus/library/notes-mail-files/)
Here's the script:
CleanUp agent
' CleanupInbox – moves older documents out of inbox
Sub Initialize
Dim s As New NotesSession
Dim db As NotesDatabase
Set db = s.CurrentDatabase
Dim dr1 As notesdaterange
Dim v As notesview
Dim dc1 As NotesDocumentCollection
Dim gracedoc As NotesDocument
Dim stime1 As New NotesDateTime("0/0/0")
Dim etime1 As New NotesDateTime("Today")
Set gracedoc = db.GetProfileDocument("inboxgracedays")
Dim graceval As Variant
Dim gracedays As Integer
' if no profile doc has been prepared, default is 90 days
If gracedoc.HasItem("gracedays") Then
graceval = gracedoc.GetItemValue("gracedays")
gracedays = Cint(graceval(0))
Else
gracedays = 90
End If
etime1.AdjustDay(-1*gracedays)
' create a daterange excluding docs newer than graceperiod
Set dr1 = s.CreateDateRange()
Set dr1.StartDateTime = stime1
Set dr1.EndDateTime = etime1
'dc1: collection of 'old' documents from inbox
(before or on Today - gracedays)
Set v = db.GetView("($Inbox)")
Set dc1 = v.GetAllDocumentsByKey(dr1)
'pull out expired docs
dc1.RemoveAllFromFolder("($Inbox)")
End Sub
'SetInboxGracePeriod agent – sets the grace period for inbox
Sub Initialize
Dim s As New NotesSession
Dim db As NotesDatabase
Set db = s.CurrentDatabase
Dim gracedoc As NotesDocument
Dim gracedays As Integer
Dim inputgracedays As Integer
Dim maxdays As Integer
Dim graceval As Variant
Dim gracevar As Variant
maxdays = 1000
Set gracedoc = db.GetProfileDocument("inboxgracedays")
If gracedoc.HasItem("gracedays") Then
graceval = gracedoc.GetItemValue("gracedays")
gracedays = Cint(graceval(0))
Else
gracedays = 90
End If
getInput:
inputgracedays = -1
gracevar = Inputbox("Days to retain in Inbox? (currently " &
gracedays & ")" )
If (gracevar <> "") Then
inputgracedays = Cint(gracevar)
End If
While (inputgracedays > maxdays)
Msgbox("Maximum of " & maxdays
& " days exceeded")
Goto getInput
Wend
If inputgracedays <> -1 Then
gracedays = inputgracedays
End If
Set gracedoc = db.GetProfileDocument("inboxgracedays")
gracedoc.ReplaceItemValue "gracedays",gracedays
Call gracedoc.Save(False,False)
End Sub
Tuesday, April 14, 2009
Steps for migrating from Exchange to Domino
Install OutLook on the client that will run the tool
Define a profile in OutLook, it must be configured
Define OutLook as the default messaging client
Run in full Admin mode
We’ve used a dedicated computer to do the migration. We were not allowed to connected from server to server. The dedicated computer must have a lot of disk space. In our case, we have used a test server. In our case, the users were already registered in our NAB.
All the new user's mail files were locally replicated to our test server.
To facilitate this step, a view should ideally be created in the public address book. This view contains only the files to migrate users using a search criteria, such CompanyName = "ABC". If this is not possible, do all the same to the next step. It is based on the hypothesis that the Notes users are already created.
To quickly create replicas of local databases, you could add temporarly to the public address book a new action button.
Dim dbCheck1 As NotesDatabase
Dim replica As NotesDatabase
For i = 1 To coll.Count
Set doc=coll.getnthdocument(i)
Set dbCheck1= session.GetDatabase(doc.MailServer(0),doc.mailfile(0)+".nsf")
If Not(dbCheck1 Is Nothing) Then
If dbCheck1.isopen Then
Call workspace.AddDatabase( dbCheck1.server,doc.mailfile(0)+".nsf")
Directory = Localpath +doc.mailfile(0)+".nsf"
'* http://www-1.ibm.com/support/docview.wss?rs=475&context=SSKTWP&context=SSKTMJ&dc=DB520&dc=DB560&q1=4005&uid=swg21155739&loc=en_US&cs=utf-8&lang=en
On Error 4005 Resume Next
Set replica = dbCheck1.CreateReplica( "", directory )
On Error 4005 Goto 0 'This causes the error handling to revert to normal error handling
'On Error 4005 Goto Error_Handling 'If the application has a error handling section then revert to it instead
Call workspace.AddDatabase( "",repertoire)
End If
End If
Next
Etc.etc.
End Sub
The first goal is a huge gain of performance and processing time. Although the tool can run from server to server, this approach was more appropriate for our scenario.
Following the creation of local replicas, it is possible to start the creation of profiles in the database from BinaryTree knowing that we already know the destination PST files to be converted.
The last preparatory step is to adjust the user's profile into the bineryTree's CMT database
How to Create Profiles in "BinaryTree"
Open the binary db, click the button to launch the "Wizard"
Follow the steps below in red which will select the names of the persons to be converted
This step may be carried out before the day of migration based on the location of files (PST) provided
Once completed these steps, go to the "End User Migration" menu
For each user, we must specify the location of the PST file. Each person will have their own.
In edit mode, in "Server Migration Info (1)
A-Select Microsoft Exchange (Point 2).
B-Enter the location of the PST file from this user. We need a format with double \ \ in the beginning.
C-select this option (Item 4)
A replica of the Binary db must also be created on the test server, to avoid transfers over the network.
In the preferences of the user’s client Lotus Notes in the Mail tab, disable the reception of new emails prevent transfers over the network.
In the location document of the Personal Address Book (names.nsf) of the client that will make the conversion, under the Server tab, you must blank the value Server \ Host messaging to avoid transfers over the network
In the Mail Setup tab, specify the local server instead of to avoid transfers over the network
Launch of the conversion
Once the prerequisites of BinaryTree is completed for all users, you can click on "Server Migration". The system will then propose a list of all users for which you have chosen Microsoft Exchange.
Select the users you want, one or several.
You wait until the conversion is completed. When you're done, you can go and see if errors occurred during conversion. Event logs are located in each file of the database users BinaryTree CMT.
By default, the databases will be deposited in the Data folder of local Lotus Notes client under UnRepertoire \ MAIL \ xxx.nsf where xxx is the file name correspondance.
At the end of the conversion, you must close the Lotus Notes client
Once the migration is completed, you will have many local mail dbs that will need to be copy to your Domino Server. You could initiate a replication but it would be too long. So , you just need to do an OS copy of the local db to your destination server. Be careful of Technote 156522 from 1997, Duplictes of databases created at OS level do not replicate Link
How to Copy of local databases to the Domino server
- Close the Domino server which was started the initial replication (The mail server of the users).
By making a copy using the operating system, it does not change the replica ID of the bases.
- Restart the Domino server to the end of the copy.
The next 2 points are optional if there is a difference in the number of documents in the cluster following the launch of replications.
- Clear the history of replicates on these bases because of potential problems can arise when databases are copied via the operating system (See IBM Technote)
- Compare the number of documents from the 2 sides of the cluster if the history of replication is emptied.
Wednesday, April 08, 2009
Archiving - View indexes - Size really does matter
I'm beginning to suspect the view indexes. I've ran a script and many of our users keeps more than 1000 messages in their Inbox, the biggest one has more than 37000 (I know, i should teach them GTD :-). The inbox is one of the most sollicitated design elements in a mail file.
Best practices for large Lotus Notes mail files
With that amount of mails in the Inbox, could it explain (in part) the "missing recovered space"?
Example:
A- In Db1 ,1000 documents in my Inbox. Each documents are 1ko in size
B- In Db2,1000 documents in my Inbox. Each documents are 1Mb in size.
Which db will have the biggest view indexes? Will it be the same?
Does the view indexes depends on the document's size or only the type of columns (Sorting,etc)
If I have the same dbs but I move 900 documents from the Inbox to another folder, the view indexes will decrease? Am I right?
Ref: Size really does matter
What causes Notes database indexes to rebuild?
Tuesday, April 07, 2009
Support information for RIM's Blackberry Server (BES) for Notes/Domino 8
Resolving the problem
A few statements:
- Blackberry Enterprise Server v 4.1 Service Pack 6 (4.1.6) is certified for Lotus Domino 8.0.x and 8.5. See the BlackBerry® Enterprise Server for IBM® Lotus® Domino® Compatibility Matrix for more details.
- For Wired Synchronization, Blackberry Desktop Manager 4.3.0 or higher will be required for Notes 8 support.
- RIM's next major release of the BlackBerry Enterprise Server, code-named “Argon,” will also officially support Notes/Domino 8.0
- Notes/Domino 8.0, or any 8.0 templates, will not be supported in any BlackBerry Enterprise Server version prior to 4.1.5. Also, Notes and Domino 8.0 will not be supported in any BlackBerry Enterprise Server 4.0.x version.