Mounting the NFS share on a Windows server

The HCL Docs Conversion server needs access to the File Viewer and HCL Docs shared storage to be able to store the document data after converting from the native file types. Since Conversion is only supported on Windows, the shared data folders will need to be mounted as Windows shares and provide the proper access for reading and writing from these shares.

The following steps are for Windows 2008 Server. Instructions for Windows 2012 are presented in additional notes.

  1. Ensure that you are logged into the Windows server as an administrator.
  2. Start the command console as the administrator (Click Start > All Programs > Accessories > Windows Powershell or Command Prompt)
  3. Right-click the Windows Powershell or Command Prompt, and select Run as administrator.
    Note: Ensure to select Windows Powershell, not Windows Powershell(x86).
  4. Run the following command to install FS-NFS-Services:

    servermanagercmd.exe -install FS-NFS-Services

    Note: To Windows Server 2012 Datacenter/Standard/Essentials Edition, you can run the command through powerscript:
    Import-Module ServerManager
    Install-WindowsFeature -Name FS-NFS-Service
    Install-WindowsFeature NFS-Client
    You can also do the steps:
    1. Run servermanager.exe.
    2. From the Add Roles and Features Wizard, under Server Roles, select File and Storage Services if it has not been installed.
    3. Under File and iSCSI Services, select File Server and Server for NFS. Click Add Features to select Client for NFS.
  5. Open a command prompt with administrative rights. Run the following command:
    • For HCL Docs: umount –f W:
    • For File Viewer: umount –f Y:
    • For Document Format Conversion:
      umount –f W:
      umount –f Y:
  6. Run:

    nfsadmin client stop

  7. Open Regedit and navigate to the following branch:


  8. In the main window, right-click and select New > DWORD 32-bit Value. Set the name as AnonymousGID.
  9. Right-click and select New > DWORD 32-bit Value again. Set the name as AnonymousUID.
  10. Double-click on AnonymousGID and AnonymousUID, set the value as 0 and the base as Decimal respectively.
  11. Click OK.
  12. Close Regedit.
  13. In the command prompt, run:

    nfsadmin client start

  14. Close the Windows Powershell Console.
  15. Open a command prompt.
  16. Run the following command in a command prompt (not Powershell) to set the NFS configuration:

    nfsadmin client localhost config fileaccess=755 SecFlavors=+sys -krb5 -krb5i

  17. Run the following commands to mount the share:
    • For HCL Docs: mount -o mtype=soft acdirmin=0 retry=10 timeout=6 casesensitive=yes anon W:
    • For File Viewer: mount -o mtype=soft acdirmin=0 retry=10 timeout=6 casesensitive=yes anon Y:
    • For Document Format Conversion:
      mount -o mtype=soft acdirmin=0 retry=10 timeout=6 casesensitive=yes anon W:
      mount -o mtype=soft acdirmin=0 retry=10 timeout=6 casesensitive=yes anon Y:
    • If you do not mount successfully, run umount –f W: or umount –f Y: and then repeat again.
    • Make sure you mount the viewer_data directory to the server where you deploy Connections.
  18. In order to mount the share automatically with windows restart:
    1. Create a batch file, for example, c:\IBMConversionNFS\nfsmount.bat, and type:
      mount -o mtype=soft acdirmin=0 retry=10 timeout=6 casesensitive=yes anon W:
      mount -o mtype=soft acdirmin=0 retry=10 timeout=6 casesensitive=yes anon Y:
    2. Click Start > Administrative Tools > Task Scheduler.
    3. Click Create Task in Task Scheduler (Local).
    4. Click General, and type nfs_auto_mount for Name. In Security options, click Change User or Group > Advanced > Find Now, and select SYSTEM. Select Run whether user is logged on or not Select, along with Do not store password, and then select Run with highest privileges. Finally click OK.
    5. Click Triggers > New, select At startup for Begin the task. Click OK.
    6. Click Actions > New > Browse, select c:\IBMConversionNFS\nfsmount.bat and click OK.
    7. Click OK.
    8. Restart the machine.
    9. The client mounted points will be displayed in Windows explorer as Disconnected Network drivers, and this is the expected normal status. This will ensure the scheduled task is working, as well as causing the drives to be mounted as SYSTEM, which is necessary for the install procedure.
    • If the node and server are configured to start automatically along with the Windows Operating System, they will be system services running with a user name of SYSTEM. Looking at the services with the Task Manager, the user name for java.exe will show SYSTEM. In this case, the mount must also be done with a user of SYSTEM (as previously shown) or the NFS shares will not be able to be accessed from the node or server.
    • To verify the SYSTEM user has access to the mounted drive. Download the tool PSEXEC from following link: This tool will start a command prompt as SYSTEM user, and you can change directory to the mounted drive in the command prompt to check the accessibility.
    • If the mount action is done using a user name of SYSTEM, the NFS shares will be able to be accessed regardless of what user name the node or server is running as.
    • Another NFS setup is specified in the technote In this setup both mount command and Websphere are running by the same login Windows user other than SYSTEM.


If W: or Y: cannot be found, open the Task Scheduler window, find the error code in "Last Run Result" of the auto mount task that is just created. Fix the error and then restart the machine.