Thursday, March 19, 2009

How to scan 400 users's local Notes data files?

We have a bunch of users (approx 400). They all have the same particular settings. So for that reasons, a few years ago, it was decided to have a ghost image of a single configuration that was duplicate accross those 400 users's computer. One of those files were the names.nsf, bookmark.nsf. ..(NSF,same replica ID).

Everything was working fine ...until lately. Some of those users(12) were converted to roaming users because they were given a new Blackberry.

When you activate a roaming profile, some files need to be replicate to the mail server.
General information and FAQ about Roaming User feature of Notes/Domino 6.0.x and 6.5.x

What happened? Every local files of those users were replicated to the server.

What happens when a database with the same replica ID as another one is put on a server?....It replicates!!!! So now, we now have 12 users, who shares the same names.nsf db (Remember the ghost image, with the same db). They all have the contacts of each others.
As long as those files were local, it was not a problem but now they are on a server.

What's next?

First, we need to fix the issue with the 12 users. easy.

Second, the thoughest part.

I need to scan every computers (400) for their local files (names and bookmark) and what's more fun, some of them don't have a journal.NSF needed in a roaming process.
So, my plan for Local files

1-Scan private address books, for names.nsf.
A- Look if they have the right version (Not old R4 template because they miss the ($Policies). This view is required to apply policies to your clients) , if not do a replace design from the master template

B- Scan all the documnts because a few years ago, a problem was present with some documents (The form name was incorrect over the Notes version Person, Business Card-Carte de visite.)

C -Try to compact the local address book, ...but it will fail (Address book : "could not be compacted at this time. The compact will be performed later.)
Replicas are not successfully generated during roaming upgrade process

D-Assign a new random replicaID


2- Scan the bookmark file
A-Assign a new random replicaID

3- Check for the existence of the journal.nsf db,
if it exist, assign a new random replicaID.
If not, create from the master template

About Random ReplicaID - Impact on servers?
http://jyriver.blogspot.com/2009/03/random-replicaid-impact-on-servers.html

Whoooooo, it will be fun!!!!

4 comments:

Anonymous said...

Sounds like you have a "fun" project on your hands.

Anonymous said...

Hi JYR,

I have an interresting starting code for you. Mail me @ nikolay.krastev@greenhouse.lotus.com

I will send you what I have and we'll discuss ;)...

Have a nice weekend,
N

JYR said...

Hi nikolay,

Thank you for your help, I have already begin my application.

Will probably post the results

JYR

Keith Brooks said...

Why would they be converted to roaming just because they have Blackberries?
Also change your ghost so there is no names.nsf, bookmarks, etc initially and the first time they or support clicks on the icon it will set them up then policies kick in and push updates or you can create a simple email with agent to populate it all.
ask me for help if you need it.