Client Automation Tool
The Client Automation Tool provides automatic, centralised management of local Notes Mail, Archives and Address Books.
It allows Administrators to control otherwise inaccessible data on User PCs, from a central location.
The Client Automation Tool protects local Notes data, ensuring it is secure, backed up, and accessible for data migration.
It also allows automatic migration of local Mail and Archive NSFs to PST.
Administrators can identify local Notes Mail and Archives, decrypt Mail and Archives prior to migrating, synchronise Address Book Contacts, upload local Archives to a central Domino Server, or migrate local Mail directly to PSTs in-place on User PCs.
Multiple options provide full control for the Administrator, including conversion settings, logging, status reports and reprocessing control.
The tool is deployed in the environment using standard Notes Desktop Policies, and integrates with Notes Pipeliner functionality.
This allows centralised preparation of the entire Notes/Domino environment, including data held only locally on PCs, prior to migration.
Description
Client Automation is deployed on a Domino Server as a small database with open design, and a Notes Desktop Policy is used to set this as a 'Startup DB' on the Notes Client. When the Notes Client launches, the Client Automation database starts a background agent which runs invisibly on the Notes Client. This agent performs tasks as defined by the Administrator, but is not seen by the user (running in the background). In this way Notes Administrators can perform pre-migration tasks on remote User PCs.
Because the Client Automation agent runs on the Notes Client using the ID of the Notes User, it can perform tasks restricted to that ID (e.g. mail decryption) and also local to the PC (e.g. identifying local mail archives).
Options
1. Identify Local Mail & Archives. Discover which users have local Archives prior to migration. This information is logged in the Pipeliner.
2. Synch Address Book with Mail. Synchronise local Personal Address Book Contacts with the user Mail File to ensure that all Contacts are in the Mail File to be migrated.
3. Decrypt Mail. It is important to decrypt encrypted mail sent to the user, in either production Mail or Archives, local or Server-based, prior to migration. Otherwise this mail cannot be migrated by a Server-run process.
4. Decrypt Local Mail DBs. This is useful to decrypt any local Mail or Archives where the NSF itself is encrypted.
5. Upload Local Archives. Local archives can be uploaded to a server-based NSF for migration, e.g. when migrating to MS365. Administrators can also choose to merge local archives with the Users production mail file, an existing archive mail file, or a new archive mail file.
6. Export Local Archives to PST. Local Notes Archives can be migrated in-place to a local PST on the Users PC. Administrators have various options to control this migration process.
Key Features
✓ Centrally controlled by the Administrator.
✓ All action and errors logged centrally in the Pipeliner.
✓ Automatic Installation and Operation.
✓ Runs invisibly to the User.
✓ Identifies local Archive Databases.
✓ Decrypts Mail and Archives using the User ID.
✓ Synchronises Mail and Address Book Contacts and Groups.
✓ Uploads local Archives to a Domino Server.
✓ Uploads local Sametime Chats to a Domino Server.
✓ Synchronises local Address Book contacts with Mail.
✓ Converts local Archives to PSTs on the PC, with full fidelity.
✓ Does not require Microsoft Outlook.
✓ Retains Metadata and Folder structures.
✓ Supports multiple character sets.
✓ Leaves original data intact.
Trusted by Leading Organizations