A server's bindery context can be set to any OU or O that is present in a replica on that server.
For example, given the partitions defined in the following diagram, you could set the bindery context of ACCT_SRV1 to any one of the following containers:
Bindery Contexts for a Specific Server
This Directory tree represents three partitions of the ACMECORP tree. If there were only one partition, the bindery context could be set to any OU, O, or set of OU and O in the tree. But because multiple partitions exist, any context you set in a different partition must include the path all the way to the [Root] of the tree.
Nevertheless, the bindery context must specify the containers that hold the users that want to log in to that server under bindery services.
For example, suppose you want to set the bindery context for the server PROD1_SRV2 in this tree to OU=HQ so that user ESAYERS can log in to that server with a bindery login. Using nwcm(1Mipx), you would type the following:
nwcm -s ds_bindery='HQ.MFG.ACME'This command sets the bindery context to the OU=HQ container and provides the path NDS uses to find that container. In this case, the command specifies that the bindery context OU=HQ is contained in OU=MFG.O=ACME.
Be careful when changing a server's bindery context. Removing a container from that server's bindery context prevents all users in that container from using bindery services.