11.2 Prerequisites and Guidelines for DFS Junctions

Use the prerequisites and guidelines in this section for planning and managing DFS junctions:

  • The junction's volume must be an existing NSS volume on one of the following supported operating systems (or later versions):

    • OES 2018 SP1

    • OES 2018

    • OES 2015 SP1

    • OES 2015

    • OES 11 SP2

    • OES 11 SP1

    • OES 2 Linux

    • NetWare 6.5 SP8

  • The target volume must be an existing NSS volume on one of the following supported operating systems (or later versions):

    • OES 2018 SP1

    • OES 2018

    • OES 2015 SP1

    • OES 2015

    • OES 11 SP2

    • OES 11 SP1

    • OES 2 Linux

    • NetWare 6.5 SP8

  • The junction’s volume and the target volume must be in the same Novell eDirectory tree.

  • Junctions can exist in or out of a DFS management context. If a junction is in a DFS management context, the context can be the same or different than the one for the target volume.

  • The target volume must be in an existing DFS management context where its VLDB service is up and running. For information about creating a DFS management context, see Section 10.1, Creating a DFS Management Context.

  • Make sure the source and target volumes are mounted and active.

  • If you plan to create the junction in a directory, that directory path must exist.

  • If you plan to point the junction to a directory on the target volume, that directory path must exist.

  • The users must be defined with User objects in Novell eDirectory and Active Directory in order to be available as potential trustees.

  • Both the junction and target locations inherit trustees and trustee rights relative to their actual locations in accordance with the OES Trustee Model. You must set explicit rights on both locations to block any rights that you do not want to be inherited.

    For information about the OES Trustee Model, see Understanding File System Access Control Using Trustees in the OES 2018: File Systems Management Guide.