NotesDriverShim: Using a Windows Mapped Driver to Create Lotus Notes user.id Files

pnuffer Absent Member.
Absent Member.
0 0 4,030
0 Likes

Question:


Can the NotesDriverShim utilize a Windows 'mapped drive' to specify the location for creating a newly registered Notes user's user.id file?

Answer:


Yes. The driver's subscriber option parameter ID File Storage Location (cert-path) specifies the default location in which all newly created Notes user.id files will be created. This parameter can be overridden by the custom parameters user-id-file and user-id-path. You can search for these parameters in the online documentation for more information.

A successful configuration using mapped drives is generally determined by proper file access rights. If a mapped drive is not accessible to the NotesDriverShim, the Lotus Notes registration process will produce an error (Message = Error registering new user) when the NotesDriverShim attempts to register the new user, resulting in a failed user add command. Windows configurations with strict security policy may not allow mapped drives. When using a Windows version prior to Windows Server 2003, mapping drives for usage by a service such as the IDM Remote Loader or the IDM engine is fairly straight forward. And we recommend using file paths in UNC format, such as: \\servername\sharename\subdir.

However, Windows 2003 and beyond forbids a service to see any network drive mappings that were mapped by a logged in user. And an error such as "_A service should not directly access local or network resources through mapped drive letters._" may be seen. On Windows Server 2003, each logon session receives its own set of drive letters, A through Z. Therefore, redirected drives cannot be shared between processes that are running under different user accounts. Additionally, a service (or any process that is running in its own logon session) cannot access the drive letters that are established in a different logon session. However, drive letters that are mapped from a service that is running under the local System account are visible to all logon sessions. Thus, the only way around this problem is to write your own service to map the drive. Here are a couple links that could help you get started on configuring your own drive mapping service.
http://support.microsoft.com/default.aspx?scid=http://support.microsoft.com:80/support/kb/articles/Q243/4/86.ASP&NoWebContent=1
http://forum.osnn.net/showthread.php?t=86544
Tags (1)
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.