Creating non-scoped file shares configured with VCS

Last published : Aug 05, 2026
File shares configured with VCS on Windows Server are accessible only using the virtual server name (Lanman resource). These file shares are not accessible using the IP address.
The FileShare agent is enhanced to address this issue. The FileShare agent behavior can be controlled using the following registry key:
HKLM\SOFTWARE\VERITAS\VCS\BundledAgents\Lanman\virtualName\DisableServerNameScoping
Set the DisableServerNameScoping key to have the FileShare agent support non-scoped file shares.
You must create this registry key manually.
Note: Incorrectly editing the registry may severely damage your system. Back up the registry before making changes.
To configure the DisableServerNameScoping registry key
  1. To open the Registry Editor, press **Window+R**on the desktop (opens the Run dialog box), type regedit, and then click OK.
  2. In the registry tree (on the left), navigate to the following location:
    HKLM\SOFTWARE\VERITAS\VCS\BundledAgents
    1. Click Edit > New > Key and create a key by the nameLanman , if it does not exist already.
    2. Select the Lanman key and clickEdit > New > Key and create a key by the name***virtualName***.
    Here, virtualName should be the virtual computer name assigned to the file share server. This is the VirtualName attribute of the Lanman resource in the file share service group.
    The newly created registry key should look like this:
    HKLM\SOFTWARE\VERITAS\VCS\BundledAgents\
    Lanman\virtualName
  3. Select the key that you created in step 4 (*virtualName*) and add a DWORD type of value.
The value name should be DisableServerNameScoping and value data should be 1.
The value 1 indicates that the FileShare and Lanman agents support non-scoped file shares on Windows Server systems.
  1. If there are multiple file share service groups to be used in the non-scoped mode, repeat steps 4 and 5 for each Lanman resource that is configured in the file share service group.
  2. Save and exit the Registry Editor.
You must create this key only for Lanman resources that are part of VCS file share service groups. Configuring this key for Lanman resources that are part of other VCS service groups may result in unexpected behavior.