To edit the Samba configuration file:

1. On your OES Linux server, open the following configuration file in a text editor:

   /etc/samba/smb.conf
   

2. Copy an existing share section to the end of the file and paste it as many times as you have NCP shares to add, then edit the copied sections to be:

   [share1]
   comment = for access to the NCP share
   path = /usr/novell/share1
   write list =@ntadmin root
   force group = netadmin
   create mask = 0644
   directory mask = 0755
   

   [share2]
   comment = for access to the NCP share
   path = /usr/novell/share2
   write list =@ntadmin root
   force group = netadmin
   create mask = 0644
   directory mask = 0755
   

   where share1 and share1 are the NCP share names, such as sys and apps. Note that the share names are used both within the brackets and in the path. The share names in the smb.conf file and in NCP must be the same.

   NOTE:The last four lines for each new share setion do not need to be edited from whatever is contained in the original copied section. The values shown above in these lines are not used by Tiered Electronic Distribution.

   To display which NCP shares are available, enter ncpcon on the OES Linux server console and type help or --h for a list of the NCP command line options.

3. Save the file and exit the text editor.

   When a Desktop Application Distribution is configured with a golden application containing a path such as \\192.68.1.203\sys\firefox, the sys volume is interpreted as a share on the OES Linux server, allowing the Firefox application to be written to the /usr/novell/sys/firefox directory.

4. Identify the servers that have a location where:

   • The application files are to be written to (Subscribers)

   • The application files are to be distributed from (Distributors)

   then do one of the following:

   • If you have only a few servers to configure, repeat Step 1 through Step 3 for each Linux Subscriber and Distributor server where access to an NCP share name is required.

   • If you have very many servers that need this configuration change, use a Text File Changes policy (in the Distributed Server Package) to roll out an updated smb.conf file to them. For more information, see Text File Changes.