Skip to Main Content
HCL Domino Ideas Portal

Welcome to the #dominoforever Product Ideas Forum! The place where you can submit product ideas and enhancement request. We encourage you to participate by voting on, commenting on, and creating new ideas. All new ideas will be evaluated by HCL Product Management & Engineering teams, and the next steps will be communicated. While not all submitted ideas will be executed upon, community feedback will play a key role in influencing which ideas are and when they will be implemented.

For more information and upcoming events around #dominoforever, please visit our Destination Domino Page

Status Needs Review
Workspace Notes
Created by Guest
Created on Feb 5, 2026

Sametime geographic location in HCL Notes client

We would like to submit an enhancement request related to the handling of geographic location profiles in HCL Notes when using IPSEC VPN connections.

Problem Description
In our environment, users are required to connect via an IPSEC VPN. When Notes is launched under this connection type, the following file is updated:

C:\Users\<username>\AppData\Local\HCL\Notes\Data\workspace\.metadata\.plugins\com.ibm.collaboration.realtime.location\locprofile-config.xml

The geographic location entry created in this file does not contain an IP address or a MAC address. Because no MAC address is recorded, the Notes client treats the connection as a new geographic location on every subsequent launch, repeatedly creating new location entries.

Technical Background
This behavior appears to be related to the nature of IPSEC VPN connections:

  • IPSEC operates at Layer 3 (L3) and does not create a virtual network interface.

  • As a result, there is no MAC address associated with the VPN connection.

  • The IP address is assigned from a VPN IP pool rather than via DHCP.

  • The Notes client does not appear to persist or use the assigned IP address in the location profile.

Due to the absence of a MAC address (and apparently the lack of a stored IP address), the client cannot reliably identify the connection as an existing geographic location.

Impact

  • Repeated creation of new geographic locations for the same VPN connection

  • Location profile clutter and inconsistent client behavior

  • Increased administrative and user overhead

Enhancement Requests
We would like to request one or more of the following enhancements:

  1. Provide an option to disable the creation of geographic locations when no MAC address is available.

  2. Allow geographic locations to be identified and reused based on a defined IP address range or VPN IP pool.

  3. Persist and use the assigned IP address (even when not DHCP-based) as part of the location identification logic.

  4. Provide configuration options or documentation that allow administrators to influence which connection parameters (e.g., IP, subnet, adapter type) are used to determine geographic location.

  5. Clearly document how the Notes client currently distinguishes and assigns geographic locations, including which network parameters are evaluated.

    This enhancement is addition to https://domino-ideas.hcltechsw.com/ideas/STC-I-657

  • Attach files