Top of Form Translate Page Anonymous Log on Help Lotus Notes and Domino wiki All Wikis Home

e Community Articles Product Documentation Learning Center

Search Advanced Search

Categories - undefined + Lotus Notes + Lotus Domino + Lotus iNotes + Lotus Notes Traveler + Lotus Protector for Mail Security * Lotus Protector for Mail Encryption * Alloy by IBM and SAP + IBM Redbooks Publications * Resources for administrators * Spotlight articles * * - Japanese Tag Cloud 0

6.0 6.5 6.5.4 6.x 7.0 7.0.2 7.5 7.x 8.0 8.0.1 8.0.2

8.5 8.5.1 8.5.2 8.5.x 8.x address admin Administration administrator attachment best practice BlackBerry cache calendar Client deployment Cluster DAOS database database properties db2 DCT demo deployment deployment Notes directory document documents domino Domino Server Domino Web Access Domino Web server dwa email getting started HTTP IMAP iNotes install iPhone LDAP logging Lotus iNotes lotus notes Lotus Notes Traveler mail mail file

max media_Notes8.5.1 memory message messages messaging MIME moving_advanced moving_cal moving_mail ND6 notes Notes ID Vault notes.ini NotesBench NSF performance performance plug-ins Policies preferences R5 reference card replication router Sametime search security Server smtp table text tips to do traveler Troubleshooting Upgrade user video VideoFest views web Widgets and Live Text windows Edit ArticleAdd an ArticleSharePrint Subscribe

Home > Lotus Notes > Understanding the IBM Lotus Notes 8.5.x client directory structure (1 rating) Understanding the IBM Lotus Notes 8.5.x client directory structure
true

Abstract Abstract This article explains the changes that were introduced in the IBM Lotus Notes 8.5 File System installation and describes them with respect to the installation, setup/launch/run, and uninstall phases in the client's life cycle. Also included are answers to some FAQs on the client file system. ShowTable of Contents HideTable of Contents 1 Files created during install of the Notes client 1.1 Client configuration properties 2 Files created and modified during setup and launch and run 3 Files remaining after client uninstall 4 FAQs 5 Conclusion 6 Resources 7 About the authors Files created during install of the Notes client Directories and files are created in two installation phases, the Microsoft Software Installer (MSI) install and feature provisioning. In the MSI install phase, files of Notes Core, Lotus Expeditor Runtime, and Lotus Domino Admin (if selected by the user) are created based on user customizations from the UI and MSI transforms settings. (For more information on the transforms settings, refer to the topic Customizing Notes install using the tuner in the Lotus Domino and Notes information center). In the provisioning phase, plug-ins of Lotus Expeditor and applications (Lotus Domino Designer, Lotus Sametime, Notes Composite Applications Editor, IBM Lotus Connections, and IBM Lotus SymphonyTM) are created based on the user customizations from the UI and provisioning manifest settings: install.xml. After the client is installed, you'll see the following file structure: <PROGDIR> / ( Program Files Directory as defined during install) Notes Core: DLLs, executable files, and other resource files Notes.ini: Client configuration file JVM /: JavaTM Virtual Machine (JVM) for Notes client Licenses /: Product license files including non_ibm_license icc /: DLL files for Crypto

xmlschemes/: Schemas use for DXL validation xsp/: Xpages JAR files and Themes Framework/: RCP/: deploy/: extras/: presetfeeds.opml: Default Feed options kithistory/: Stores updated install manifest files: lastInstall.xml install.8.0.0.200xxxxx..xxxx .keystore.JCEKS.IBM_J9_VM.install: The keystore that Notes provides for security. install.xml: Provisioning manifest file eclipse/: Plugins for XPD Platform scripts/: Contains three debug level setting files for CAI plugin_customization.ini: This file is used to set the default preference values for preferences defined by other plug-ins. rcplauncher.exe: Platform launcher executable rcplauncher.properties: This file is generated by the installer and contains a set of properties utilized by the platform launcher executable. startcollector.bat: Command Line ISA log collector utility (Windows) startcollector.sh: Command Line ISA log collector utility (Linux) Shared/: Plugins for shared applications that are configured in install.xml. Eclipse/: Plugins for applications .provisioning_rc: Provisioning status file; if you cannot find .provisioning_rc, it means that the provisioning process failed to launch or was terminated before the status could be determined. uninstall.bat: Script file to uninstall the Notes client <DATADIR> / (Data Files Directory. For all client single mode, it is defined during installation; for multi-user mode, it defaults to \local Settings\Application Data\Lotus for Windows XP) Notes Common Data Files: For a multi-user install, the common data files are stored at :\Documents and Settings\All Users\ Application Data\Lotus\Notes\Data\Shared for Windows XP, and in C:\ProgramData\Lotus\Notes\Data for Windows Vista and Windows 7. Activities\: Activities configuration information autocorr\: Auto correct resource domino/ : Resource files for Domino Designer and Xpages Help/ : Contains help files for the Notes client IBM_TECHNICAL_SUPPORT/: Contains diagnostic log files for Notes Core: Path for this entire directory can be relocated with the logfile_dir= notes.ini parameter [Specified path must exist]

SmartUpgrade\: Log file for client Smart Upgrade nsd_W32I__<year _<Month _<Day @<time .log: Diagnostic log for client crash properties/: (Xpage properties files) acf-config.xml proxy-config.properties xsp.properties theme/ LowVisTheme.css: Cascading style sheet for Low Vision configuration workspace/: The workspace is used to store instance data between client launches and contains the configuration data for the Eclipse/Expeditor [java based] portions of the standard client. The initial workspace is created during the first install. .config/ : (User Configuration Data Area). rcpinstall.properties: User-specific instance of the system properties file for Notes Client. This file contains many critical properties, including the default logging and tracing configurations and settings for the JRE. config.ini: Standard properties file for configuration of components at run time. For a full list of the supported properties, refer to the Eclipse run time options document. This file is critical to successful launch of the client. args.properties: Captures the options that are typically loaded with rcplauncher in order to ensure that, when the platform is restarted, the same options can be applied to the launch. org.eclipse.core.runtime/: Contains Eclipse Core Runtime data org.eclipse.equinox.app/: Contains RCP launcher cache data org.eclipse.osgi/: Contains cache data of OSGI bundles that need to be loaded at client launch. org.eclipse.update/: Contains Eclipse Update manager data .metadata/: (User Instance Data Area) .plugins/: stores state data for each plugin applications: For a multi-user install, un-shared features will be provisioned into this location. logs/: LotusInstall.log: Record of the whole installation process. Overwritten when upgrades or fixes are applied to the client. provisioning.log: Record of feature provisioning error-log-x.xml: Error log data for the Eclipse/Expeditor [Java] portions of the standard client trace-log-x.xml: Trace log data for the Eclipse/Expeditor [Java] portions of the standard client - Error and Trace logs are renamed [x+1] for each launch of Notes. Total of 6 copies are

maintained [5+1 copy is dropped] Log_viewer.xml: XSL Transform required to view error log Trace_viewer.xml: XSL Transform required to view trace log .rcp.lock: Used to help determine if a valid Eclipse instance is already running. If this file contains inaccurate information, it may prevent the client workbench from being displayed. xsl: Data for XPages Client configuration properties Notes.ini. For all client and single-install modes, the Notes.ini file is created in during installation. For the multi-user mode, this file is created at that location for data of All Users (for example, C:\Documents and Settings\All Users\Application Data\Lotus\Notes\Data for XP) during installation. The initial Notes.ini file has only a few lines: [Notes] KitType=1: ( 1 Workstation 2 Server) Directory=C:\Program Files\IBM\Lotus\Notes\Data : ( Data Directory Path) InstallType=2: (2 - All client install 6 - Notes client only) InstallMode=1: ( 1: Standard Client, 0 : Basic Client) NotesProgram=C:\Program Files\IBM\Lotus\Notes\ :( Program Files Path) For more information, refer to the developerWorks Technical Library document, Lotus Notes/Domino notes.ini settings. Install.xml. This file is the client install manifest. It contains a complete list of the default set of features to be installed and enabled in the Notes runtime client. During the product installation process, the install manifest corresponding to the chosen install configuration is processed (replacing any supported variables) and copied to {install.dir}framework/rcp/deploy/install.xml. The location of this file then passes to the platform provisioning component to begin the provisioning process. For more information, refer to the Lotus Expeditor Information Center topic, Preloading certificates for initial install and provisioning of signed plugins. Files created and modified during setup and launch and run As users launch a client (including setup) and operate the features, there are file changes related to the creation and modification of user instance data and client runtime data. Below is a list of the user private files and runtime data files that are changed as the client runs. User Private Instance Data: <DATADIR>\

bookmark.nsf: Database for bookmark/history function Cache.NDK: Cache of all design elements cluster.ncf: Lists the Notes canonical server name for primary and others. desktop8.ndk: Lists the Workspace pages and database information in pages headline.nsf: Database for headline JOBSCHED.NJF: Scheduled Replication Job list localfeedcontent.nsf: Local store for feed names.nsf: Database for contact notesbook.nsf: User private record. user.id: Notes ID file notes.ini: Client configuration file. For all client modes, this file is created in <PROGDIR> during installation and modified to update user information at setup; for multi-user mode, the file is created for each user in their private data directory(XP is @nowiki@5Local Settings\Application Data\Lotus\Notes) as the user sets up client. <DATADIR>\Workspace/.metadata(RCP Instance Data Area) .plugins\ com.ibm.rcp.managedsettings\: Contains data for client setting policy provider, those files are obfuscated and stored with a checksum. com.ibm.collaboration.realtime.alertmanager\: Contains data for Sametime alert settings and autostatus settings. com.ibm.collaboration.realtime.community.impl\: Contains Sametime community configuration data com.ibm.collaboration.realtime.imhub\: Contains Sametime local contact list com.ibm.collaboration.realtime.people.impl\: Contains Sametime person cache com.ibm.collaboration.realtime.login\: Contains Sametime login information com.ibm.collaboration.realtime.palettes\: Contains image resources for Lotus Sametime (such as emoticon images) com.ibm.collaboration.realtime.primarybuddies\: Contains primary contact information com.ibm.content.operations.registry\: Contains cache of operation URL map com.ibm.notes.client\: Contains WSDL data for applications com.ibm.portal.app\: Contains data for CA applications com.ibm.rcp.csiviews\ : Contains view status of each application com.ibm.rcp.personality.framework\personalityWindowState\: Stores window display state for the user. com.ibm.rcp.portal.app\: Contains URL data for each application com.ibm.rcp.search.ui\: Contains search history data com.ibm.rcp.topologyhandler\: Contains perspective data of each view. com.ibm.productivity.tools.autosave\: Contains autosaved Symphony doc com.ibm.productivity.tools.service\: Contains perspective map of editor org.eclipse.core.runtime\ ( Plugins Preference data area): Stores preference data based on each plugin): .settings\com.ibm.notes.branding.prefs .settings\com.ibm.notes.desktopsets.prefs .settings\com.ibm.notes.mail.quota.prefs

.settings\com.ibm.notes.managedsettings.provider.prefs .settings\com.ibm.notes.secsets.prefs .settings\com.ibm.rcp.aaf.prefs .settings\com.ibm.rcp.accounts.prefs .settings\com.ibm.rcp.ca.utils.prefs .settings\com.ibm.rcp.content.prefs .settings\com.ibm.rcp.jfaceex.prefs .settings\com.ibm.rcp.locationmanager.prefs .settings\com.ibm.rcp.managedsettings.prefs .settings\com.ibm.rcp.net.http.prefs .settings\com.ibm.rcp.offline.prefs .settings\com.ibm.rcp.portal.app.prefs .settings\com.ibm.rcp.roaming.service.prefs .settings\com.ibm.rcp.search.ui.prefs .settings\com.ibm.rcp.security.update.prefs .settings\com.ibm.rcp.toolbox.admin.prefs .settings\com.ibm.rcp.toolbox .settings\com.ibm.rcp.topologyhandler.prefs .settings\com.ibm.rcp.topologyhandler.ui.prefs .settings\com.ibm.rcp.ui.prefs .settings\org.eclipse.core.resources.prefs .settings\org.eclipse.ui.workbench.prefs .settings\com.ibm.collaboration.realtime.calendar .settings\com.ibm.collaboration.realtime.community .settings\com.ibm.collaboration.realtime.imhub .settings\com.ibm.collaboration.realtime.location .settings\com.ibm.collaboration.realtime.login .settings\com.ibm.collaboration.realtime.policy Client Runtime Data: <PROGDIR> diagindex.nbf: File that tracks diagnostic files created ini.nbf: .ini list table log.nsf: Database to store logs of client pid.nbf: Process ID table of all Notes process (deleted and recreated) IBM_TECHNICAL_SUPPORT\: Stores diagnostic logs for Notes Core: console.log ENVDEBUG.TXT SEMDEBUG.TXT nsd_W32I_<SysName>_<year>_<Month>_<Day>@<time>.log SmartUpgrade\SmartUpgrade.log workspace\logs\: Stores logs for Notes installation and plug-ins that are running:

LotusInstall.log provisioning.log rcplauncher.log error-log-x.xml (x: 0~5) trace-log-x.xml (x: 0~5) sodc_crash_win32_<SysName>_<year>_<Month>_<Day>@<time>.log workspace\.config\ (RCP Configuration Data Area) org.eclipse.core.runtime/: Contains data for Eclipse Core Runtime org.eclipse.equinox.app/: Contains cache data for RCP launcher org.eclipse.osgi/: Contains cache data of OSGI bundles that must be loaded at client launch org.eclipse.update/: Contains data for Eclipse Update manager Table 1 describes the relationship between user information and data files. Table 1. Relationship between data files and operations Related User data Basic Notes.ini client config uration Book Bookmark.nsf mark Operat Bookmark.nsf ion cor.urimap.cache history Home Bookmark.nsf Page setting s Works Desktop8.ndk pace

Operation Scenarios for file change Users changes configuration via File > Preferences > Basic Notes Client Configuration User creates bookmarks User opens .nsf document; User accesses Web pages or .nsf database User changes Home Page setting

Replic JOBSCHED.NJF ation config uration Locati Names.nsf

User adds database links; changes page settings; (Server updates the database information) User configures replication schedule

User adds/changes

on setting s Server Names.nsf connec tions Certifi Names.nsf cate

Location documents User changes current location. User adds/deletes server connections User accept Certificate creation as access database; Certificate downloads from server based on policy configuration. User configures Sametime login User configures Activities login User adds account via Contacts or Preferences User adds/deletes contact list User changes Web browser settings (Default Browser, Browser history setting)

Accou Names.nsf nts

Contac Names.nsf ts Web com.ibm.rcp.ui.browser.launcher.prefs browse r config uration Web Workspace\BrowserHistory User accesses Web page browse with Embedded Browser r history Widge com.ibm.rcp.toolbox.admin.prefs User sets up widget t catalog location config uration Feeds com.ibm.rcp.feedreader.providers.prefs User changes Feeds config configuration via uration Preferences Feeds localfeedcontent.nsf User adds subscription data Activit \Activities\server.xml User sets up Activities ies Search . User submits search via history metadata\.plugins\com.ibm.rcp.search.ui\searchHistory.x SearchBar ml

Search com.ibm.rcp.search.ui.prefs option s setting s Symph com.ibm.productivity.tools.standalone.prefs ony config uration Symph .metadata\.plugins\com.ibm.productivity.tools.autosave\ ony autosa ved doc

User changes search options settings via Preferences

User changes settings via Preferences

Symph com.ibm.productivity.tools.standalone.prefs ony Recent Files list Sameti com.ibm.collaboration.realtime.community.prefs me com.ibm.collaboration.realtime.login.prefs config com.ibm.collaboration.realtime.chat.logging.prefs uration

If user configures File recovery in Preferences, edited document will be auto saved into com.ibm.productivity.to ols.autosave, based on Preferences setting. As user opens a document for editing

As user sets up Sametime or changes community settings As user sets up Sametime or changes login user name and settings As user changes Sametime content logging settings Sameti . As user me metadata\.plugins\com.ibm.collaboration.realtime.imhub adds/deletes/changes Local \buddylist.xml contact and group Contac t list Sameti . As user adds contact to me plugins\com.ibm.collaboration.realtime.people.impl\Pers Buddy list, person Contac onCache information and picture t will be downloaded into Person this cache. cache Same . As user drags Sametime Primar plugins\com.ibm.collaboration.realtime.primarybuddies\ contacts into Primary

y primbuds.xml Contac ts Windo com.ibm.rcp.ui.prefs w com.ibm.rcp.personality.framework.prefs setting s

Contacts panel.

As user changes window display settings (Window mode, Toolbar setting) As user changes DEFAULT_RESTORE _TABS_PREFERENCE Windo . As user opens a display w plugins\com.ibm.rcp.personality.framework\personality window or changes State WindowState\com.ibm.rcp.platform.personality.config.x window display settings data ml Sideba . As user opens & r State plugins\com.ibm.rcp.personality.framework\personality collapses sidebar, or data WindowState\com.ibm.rcp.platform.personality.config.x user enable sidebar ml display of features. Sidebar state data are stored at section. As user configures Toolbar settings

UI com.ibm.rcp.ui.prefs Toolba r state Files remaining after client uninstall

With a regular uninstall method, almost all client files are removed. Those that remain are listed below. <PROGDIR>\ license\ nlnvp.dll: NSF Hook notes.ini dbghelp_x86_v6.8.40.dll (for Windows) <DATADIR>\ bookmark.nsf Cache.NDK cluster.ncf desktop8.ndk diagindex.nbf frstrings headline.nsf ini.nbf

JOBSCHED.NJF localfeedcontent.nsf log.nsf names.nsf pid.nbf ticket.idt user.id workspace\ .config\ .metadata\ applications\ logs\ .rcp.lock FAQs What files can the user delete and/or change without impacting client run? Table 2 lists the relevant files, whether they can be deleted, the impact of deletion, and how to resolve an incorrect deletion. Table 2. Result of deleting files and how to resolve if incorrectly deleted Files Deletable Impacts if deleted How to resolve or not wrong delete action bookmark.nsf Yes Loss of user Automatically bookmarks, Home restored on relaunch Page settings, and history. This file can be recreated at launch. desktop8.ndk Yes Loss of previous Automatically desktop data restored on relaunch names.nsf No Client cannot be Copy a names.nsf or launched. re-setup the client. localfeedcontent.nsf Yes Loss of some feed Automatic on content relaunch headline.nsf Yes Loss of some user Automatic on data relaunch JOBSCHED.NJF Yes Los of replication Automatic on scheduled data relaunch Notes.ini No Client cannot be Copy an original launched notes.ini file and resetup client

Cache.NDK User.id

Yes No

Other files (NTF, .in ) in <DATADIR>

No

Files in <PROGDIR> and JVM folder

No

Files in Framework folder

No

Files in Yes <DATADIR>\workspace\.config

Files in <DATADIR> workspace\.metadata Files in <DATADIR> workspace\.sodc Files in <DATADIR> workspace\applications

Yes

Yes

No

Files in <DATADIR> workspace\logs Others

No No

Loss of some user Automatic on data relaunch Client cannot be Copy a user ID launched if it cannot get an appropriate user ID Client cannot be Copy appropriate launched, or some files into folder features won't work well. Client cannot be Repair client or launched, or some reinstall features won't work well. Client cannot be Repair client or launched, or some reinstall features won't work well. Loss of previous Can be recreated at runtime data. Updated launch, and updated features with Eclipse features must be update won't work. reinstalled. Loss of user Can be recreated at configuration and launch, but user must preferences data. re-configure features. Loss of configuration Can be recreated at of Symphony editor. launch, but user must re-configure features. If there are deployed Repair client or non-shared features in reinstall this folder, Client cannot be launched, or some features won't work well. Loss of log Automatic on information relaunch Some features won't Repair client or work well since Other reinstall files are mostly resource file of features.

Your Notes client cannot be launched or a feature does not work properly after some

configurations and operations. How do you fix this issue? This situation is generally due to data file changes (runtime data, user instance data) associated with feature setup or other operations. To resolve the issue, try the following: Reset workspace configuration data. With client launcher mechanism, runtime data (such as plug-in dependencies, plug-in extension point/contributions, plug-in bundles information, and caches) must be created and stored in the RCP Configuration Data Area (<PROGDIR>\workspace\.config) as the basis of the next client launch. If a user performs an operation that leads to a client hang or crash, the corresponding bad runtime context information may be retained in the Configuration Area, and then client cannot be launched the next time due to bad context runtime data. To resolve bad state situations, use the following command to re-set the client configuration data: <PROGDIR>\notes.exe -rparams -resetconfig Note that -resetconfig was originally designed to restore the base configuration defined in the install.xml. However, now that all installed features are merged into the install.xml, a -resetconfig will not likely help this situation, but you might be able to combine the -resetconfig with a modified or older install manifest file. Reset user private data. As stated above, user private data is updated in user data files and preference files with feature configurations and operations. When users perform operations that lead to a client hang or crash, the corresponding user data or status will be updated inthe data files and will cause the next client launch to fail. To resolve this issue, you can manually reset the user private data based on the relationship between features and data files described in Table 1 above. For example, suppose a user wants to add a widgets catalog from a blog site, but in his review he entered the wrong name for the .nsf file, and now the Notes client cannot launch without crashing. To resolve this problem, find the data file (com.ibm.rcp.toolbox.admin.prefs), which contains the widget setup information, and delete this file or change the line entry (toolboxCatalogLocalDBName=) of the file to the correct .nsf file name. Repeat setup of the Notes client. If you are still unable to fix the problem with the above methods, back up your private data files (there is a list of private data files for backup at the end of this section), clear the data files for initial client status and re-setup the Notes client. To do this: 1. First, delete the files in <DATADIR> (bookmark.nsf, names.nsf, localfeedcontent.nsf, Cache.ndk, Desktop8.ndk..) and the delete files in <DATADIR>\workspace

2. Second, revert the Notes.ini back to initial status as follows: [Notes] KitType=1: (1 Workstation 2 Server) Directory=C:\Program Files\IBM\Lotus\Notes\Data: (Data Directory Setting) InstallType=2: (2 - All client install 6 - Notes client only) InstallMode=1: ( 1: Standard Client, 0 : Basic Client) NotesProgram=C:\Program Files\IBM\Lotus\Notes\: (Program Files Directory) 3. Then, launch and set up the client. Some features don't work properly after some configurations and operations. What can you do? Sometimes a feature is not working properly or the client status is not what the user wants, or worse, the user has no way to roll back their previous operations since not all user data/statuses can be reset via the user interface. To resolve this problem, modify the appropriate data based on the listings in table 1. For example: If a user cannot see Day-at-a-Glance in the sidebar, they can check corresponding line entries in the file: . plugins\com.ibm.rcp.personality.framework\personalityWindowState\com.ibm.rcp.platfor m.personality.config.xml and verify whether there is a <ShelfState> tag for com.ibm.workplace.ui.sidecalendar.views.SideCalendarViewPart in the <SidebarState> section. If there's not, add <ShelfState bottomIconBarIndex="-1" collapsed="true|false" expanded="false|ture" id="com.ibm.workplace.ui.sidecalendar.views.SideCalendarViewPart" index="3" ratio="13108" topIconBarIndex= "-1"/> to the <SidebarState> section. How do you determine whether the appropriate features are installed? There is a spreadsheet file (Files Map for Notes Client.ods) that lists installed directories and files map based on application and components. You can compare the installed client with that file list, to verify if the appropriate features are installed. For application plug-ins, use the plug-in information in [Plug-ins Details] via Help --> About IBM Lotus Notes Panel, and verify if features plug-ins and dependent plug-ins are installed and enabled.

Your client cannot be uninstalled cleanly. What can you do? In a Windows environment, you might encounter problem whereby the Notes client cannot be uninstalled cleanly. You may get a message from the installer stating that there is an existing Notes client installed when you re-launch the client install. This problem cannot be resolved even by deleting all files in <PROGDIR> and <DATADIR> as there is some information stored in the System Registry file. To resolve the problem, refer to the Microsoft Support article, Use the Windows Installer CleanUp Utility to remove Office 2000, Office XP, or Office 2003. The Notes client installation is based on the Windows Installer, so you can use the Windows Install Clean Up tool to remove files and Registry information related to the Notes client (see figure 1). Figure 1. Installer Clean Up window

NOTE: Make sure to remove any remaining footprints in the System Registry database. After the Notes client uninstall, you can check if there are related items remaining in following locations: -HKEY_LOCAL_MACHINE\Software\Lotus\Notes -HKEY_LOCAL_MACHINE\Software\Lotus\Notes\8.0 -HKEY_LOCAL_MACHINE\Software\IBM\Lotus\Expeditor

HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\User Data\S-1-5-18\Products\<Product ID> HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Uninstall\<Pr oduct Code>\ HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\User Data\S-1-5-18\Components\ -HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\SharedDLLs What files should be backed up before attempting a reinstall? As described above, user private information is stored in data files, so you should back up these data files to seamlessly migrate/upgrade the Notes client. Files to back up include Names.nsf, Bookmark.nsf, Notesbook.nsf, Localfeedcontent.nsf, Desktop8.ndk, and User.id. Conclusion You should now have a good idea of the file changes with respect to the Notes 8.5 installation, setup/running, and uninstall phases in the client's life cycle, as well as how general user operations change the files. We also provided some representative problems and fix methods in FAQ's section, based on our extensive testing experience of the Notes client. Resources developerWorks Notes and Domino product page: http://www.ibm.com/developerworks/lotus/products/notesdomino/? S_TACT=105AGX13&S_CMP=LP Notes and Domino discussion forum: http://www-10.lotus.com/ldd/nd85forum.nsf Lotus Notes 8.5 information center: http://publib.boulder.ibm.com/infocenter/domhelp/v8r0/index.jsp? topic=/com.ibm.notes85.help.doc/fram_what_new_85_r.html Lotus Expeditor information center: http://publib.boulder.ibm.com/infocenter/ledoc/v6r11/index.jsp Microsoft's Support site: http://support.microsoft.com/ About the authors Chih-Hung Chiang is a Lotus software developer based at IBM's Massachusetts Lab in Littleton, MA. He joined IBM after finishing his Doctoral degree in Computer Science in 2007, working on the Expeditor Platform UI project where he focused on the launcher UI

area. Hong Tao Wei is a Lotus software tester based at IBM's China Lab in Beijing, working as a Notes Installation Testing leader. He joined IBM in 2004.
false

Article information Article information Category: Lotus Notes Tags: This Version: Version 36 March 18, 2011 Edit Article
true

11:40:28 AM by Ilana Weiser

Attachments (0) Attachments (0)

true

Versions (36) Versions (36)

false

Version Comparison Version Comparison Compare version versions Version This version (36) 35

with version

Compare selected Summary of changes Minor change Addional Indentation Fixes I had edits in wrong location [common data instead of user specific da... Added

Date Mar 18, 2011 11:40:28 AM Mar 18, 2011 11:37:32 AM

Changed by Ilana Weiser Ilana Weiser

34

Mar 18, 2011 11:31:07 AM

Ilana Weiser

33

Mar 18, 2011 11:08:36 AM

Ilana Weiser

information on console log, corrected confusion with indenting w... 32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1

false

Sep 24, 2010 9:54:01 AM Mar 19, 2010 11:51:07 AM Mar 19, 2010 10:45:23 AM Mar 18, 2010 6:40:56 PM Mar 18, 2010 6:22:54 PM Mar 18, 2010 6:19:57 PM Mar 18, 2010 6:19:10 PM Mar 18, 2010 6:18:52 PM Mar 18, 2010 6:18:35 PM Mar 18, 2010 6:18:25 PM Mar 18, 2010 6:17:04 PM Mar 18, 2010 6:16:38 PM Mar 18, 2010 6:16:18 PM Mar 18, 2010 6:16:00 PM Mar 18, 2010 6:15:27 PM Mar 18, 2010 6:14:44 PM Mar 18, 2010 6:14:20 PM Mar 18, 2010 6:13:02 PM Mar 18, 2010 6:11:43 PM Mar 18, 2010 6:11:07 PM Mar 18, 2010 6:10:14 PM Mar 18, 2010 6:09:36 PM Mar 18, 2010 6:07:05 PM Mar 18, 2010 6:03:57 PM Mar 18, 2010 5:21:39 PM Mar 18, 2010 5:05:20 PM Mar 18, 2010 4:32:09 PM Mar 18, 2010 4:10:57 PM Mar 18, 2010 4:10:17 PM Mar 18, 2010 4:02:39 PM Mar 17, 2010 2:04:45 AM Mar 17, 2010 2:04:05 AM

Christoph Stoettner Leslie Gallo Leslie Gallo Leslie Gallo Amanda J Bauman Amanda J Bauman Amanda J Bauman Amanda J Bauman Amanda J Bauman Amanda J Bauman Amanda J Bauman Amanda J Bauman Amanda J Bauman Amanda J Bauman Amanda J Bauman Amanda J Bauman Amanda J Bauman Amanda J Bauman Amanda J Bauman Amanda J Bauman Amanda J Bauman Amanda J Bauman Amanda J Bauman Amanda J Bauman Leslie Gallo Leslie Gallo Leslie Gallo Leslie Gallo Leslie Gallo Leslie Gallo Wei HongTao Wei HongTao

Comments (3) Comments (3) Submitted by Ilana Weiser on Mar 18, 2011 10:40:04 AM

Re: Understanding the IBM Lotus Notes 8.5.x client directory structure Regarding Christian's comment on the roamingdata.nsf, this file is created when a user is upgraded to a roaming user and is one of the 5 files which 'roams' with the user. It contains the minimal information [preferences and associated data from the [notesdata]\workspace directory] needed for a user to roam to other machines. User-based settings/preferences and associated data stored in [notesdata]\workspace are imported to this file, which replicates with the roaming server. When a user roams to a new machine, this information is exported and used to create the [notesdata]\workspace on the new machine. Submitted by Mike R Harvey on Apr 12, 2010 11:51:48 AM Understanding the IBM Lotus Notes 8.5.x client directory structure Where can I find the spreadsheet "Files Map for Notes Client.ods" that is mentioned in the article? Submitted by Christian Henseler on Mar 19, 2010 4:00:58 AM Understanding the IBM Lotus Notes 8.5.x client directory structure Thank you very much for this detailed description :-) The file nlnvp.dll is not a Notes client file, but a Symantec Antivirus Corporate Edition plugin, so it's a 3rd Party addon. roamingdata.nsf is of interest, too, because it contains a sub set of plugin settings. What about Technote #1267893, where the usage of -resetconfig is not recommended for XPD 6.2 based product, but for 6.1.x based ones? Add comment Subscribe to Go Elsewhere Stay Connected Help About RSS About Lotus Tech Info All Lotus and WebSphere IBM on Twitter Recently Portal wikis Privacy Lotus Tech Info Wiki Help added IBM developerWorks Contact on Facebook Forgot user Lotus TechInfo IBM Recently Lotus product name/password Community IBM edited forums Wiki design IBM Software support Terms of Lotus Tech Info Recently feedback Lotus Technical use Added blog About the wiki Information and Wiki Lotus Tech Info Comments Education Team Blog terms of Community use

Return to English Arabic Chinese Simplified Chinese Traditional French German Italian

+ + + + + + +

Japanese Korean Portuguese Russian Spanish

!cx1kxrw j6r! view :_id1

+ + + + +

Bottom of Form Link to this articlex Copy and paste this wiki markup to link to this article from another article in this wiki. Link:

Tip: When linking to articles use the original title, not the edited title. The alias for the link can be the edited title. Close Email Facebook Twitter LinkedIn Delicious Digg StumbleUpon Print article only Print article and comments
Submit

+ + + + + + + + + + +

Recent Edits to this Article Recently Added Comments to this Article