Del Mar College CIS 306 - Managing NOVELL® Networks Instructor: Michael P. Harris
IntranetWare 4.11

IntranetWare Administration Guide

6. Setting Up and Managing the Network File System

Introduction

This section provides basic information about and examples of using the IntranetWare^TM for Small Business network file system so that users and administrators can access network resources easily. If you need additional information, however, refer to Supervising the Network in the NetWare 4.11 online documentation included with this product.

How the Small Business File System Is Structured

The Small Business network is similar to other file systems in that files and directories are stored on a hard drive. The Small Business file system, however, stores files and directories on the server's hard drive rather than a workstation's hard drive and can be accessed through network drives (F: through Z:). The top-level directories are contained in Volume objects.

In the NovellŽ Easy Administration Tool (NEAT), the Small Business file system structure starts with a Volume object in your Directory view. Under the volume, you can create directories, subdirectories, and files such as data and application files.

In the Directory view, for example, the Volume object icon, such as DEMO_SYS:, looks like a file cabinet and directories look like folders as shown in Figure 6-1.

Figure 6-1. Small Business File System

When the network is installed, a SYS: volume is automatically created in the Directory tree and contains Small Business utilities, login utilities, and electronic versions of the documentation set. Table 6-1 lists the contents of the SYS: volume.

Table 6-1. SYS: Volume

Directory Name	Contents
LOGIN	Contains login information.
PUBLIC	Contains Small Business commands and utilities.
SYSTEM	Contains Small Business server operating system files.
DELETED.SAV	Contains all the network files that have been deleted. This file is created when you delete a network file.
NLS	Contains language support utilities.
MAIL	May or may not contain subdirectories and files.
QUEUES	Contains the print queues for the volume. This directory does not appear until you have created a printer and print queue.
DOC	Contains the electronic version of the documentation.
ETC	Contains sample files to help configure the server for TCP/IP protocols.
NETBASIC	Contains a scripting program to modify NetWareŽ utilities.
USERS	Contains all the user information for the network, home directories, and so on.

Plan a Directory Structure for Your Company

Although several directories were installed with the Small Business network, other directories can be added as well. Follow these guidelines when planning your file system directory structure and adding new directories.

• Keep application files separate from data files because application files do not normally change. Frequently, when you install an application, the install program copies directories to a consistent location, such as F:\ACME_SYS:\APPS\WINDOWS for Windows files. You may want to add an APPS directory in SYS: and place all your network applications there. An example of an Application object in the Directory view is highlighted in Figure 6-2.

  Figure 6-2. Application Object

  
  
  
• Keep all your SYS: subdirectories together as they were when Small Business was installed. This makes SYS: easier to administer.

Types of Directories that Can Be Added

Additional directories can be added to the file system as needed and organized in a way that makes sense to you and your company. For example, you could add

• Application directories to store application software that can be run from the network.
• Data directories to store work files for which several users or groups need shared access.
• Other directories that will help you organize and access shared files.

Network directories can be created in the same way you create directories on a local hard drive: with Windows* File Manager or Explorer, from within applications, or from the command line. The only difference is that they are created on a network drive.

Advantages of Using Network Files

Working in files on the network offers many advantages.

• Users have a backup file in case their workstation hard drive becomes corrupted.
• Users can copy files back and forth from their workstation hard drive to a network drive in seconds.
• Users can share each others' files if they have rights.
• Saving files on the network frees up disk space on a workstation hard drive.

Network Drives and Drive Mappings

When Small Business is installed, the first network drive F: is created for you. You can create additional network drives G: through Z:. These network drives point to a directory on the network rather than to a local hard drive.

To locate a file, you follow the path that includes the volume, directory, and any subdirectories leading to the file; for example,

Small Business server\volume: directory \(sub)directory\filename

If you are typing this path at the DOS prompt, in a script file, or in an entry box, make sure you separate the volume and directory with a colon (:). Separate all other elements with a backslash (\). Generally, you will use a browser to select each element and will not need to type the path.

File System Rights

Small Business file system rights are simple and straightforward. Users can read and modify files or they cannot, depending on the rights assigned to them. Rights can be assigned to the Organization (all users share the same rights), to a group (group members share the same rights), or to one user. When you make explicit assignments to users, you can give them more rights than they share through membership in a group or an organization, but not fewer. Make sure you understand the Novell Easy Administration Tool (NEAT) rights before you attempt to set rights up.

Small Business includes the following rights:

• Full. Users can open the directory or file and change its contents.
• Read. Users can open the directory, but not change its contents.
• None. Users cannot open the directory or file or change its contents.

These rights should suffice for single-tree companies. If you need greater control, use the rights functionality provided by NetWare Administrator and other NetWare utilities. See "Making the File System Secure and Accessible " in Supervising the Network in the NetWare 4.11 online documentation for more information.

Understanding Network Applications

The applications you install on your company's file server can be shared by network users who have been assigned access to them. When you install applications on a server, you must maintain control over your network applications, know where to install them, and know how to use the Novell network application tools.

Network Application Types

Network applications are the productivity tools for your company. How you manage these tools depends on the type of applications you are using.

Network applications can be divided into three types:

• Network-aware
  Applications that run efficiently on the network and do not use any special network features such as storage and messaging services. An example of this type of application is the NetWare Application Manager^TM (NAL^TM ).
• Network-enabled
  Applications that run efficiently on the network and use proprietary solutions for services such as authentication, print management, and messaging. An example of this type of application is GroupWise^TM .
• Network-integrated
  Applications that are designed to take advantage of special network features such as the NDS^TM database and storage services. An example of this type of application is WordPerfect*.

Application Directory Structure

You could create an APPS directory on the same level as SYS: (see Figure 6-1) and add your network applications to APPS. You can use the NEAT utility to create the directory and assign users and group access to the applications in this directory. See "Assigning Users and Groups to Applications" for more information.

Application Management Guidelines

The following guidelines will help you set up applications for your company on the network.

• Install all applications while logged in as ADMIN. This keeps the ownership of network applications consistent and manageable.
• Observe the license restrictions on all software.
• Use Directory Map objects to simplify access to programs and applications. Directory Map objects map the path to an application using a simple name. For example, if you install an application in SYS:APPS\WINDOWS \WIN31, you can create a Directory Map object called WIN and users never need to know the exact path to the application. They only need to know that the application is called WIN. You must use NetWare Administrator to create a Directory Map object.
• Use NetWare Application Manager (NAM) and NetWare Application Launcher ^TM (NAL) to simplify distribution, installation, and access to network applications. See "Novell Application Tools" for more information.
• Ensure that all users who need access to the applications have it. See "Assigning Users and Groups to Applications" for more information.

Novell Application Tools

Small Business provides application management software that helps you set up and manage network applications from a single administrative point.

The benefits are these:

• Simplifies administration of network applications
• Eliminates the need for login scripts
• Simplifies user access to network applications
• Dynamically updates user desktops
• Eases application installation and upgrades

Various Small Business tools can help you manage your applications on the network:

• Novell Easy Administration Tool (NEAT) allows you to link users and groups to applications. See "Assigning Users and Groups to Applications" for more information.
• Novell Application Manager (NAM) is installed by default into the NetWare Administrator utility. It includes the management tools to set up and configure Application objects in the Directory view. NetWare Administrator is located in SYS:\PUBLIC and can be installed as an icon on a workstation desktop.
• Novell Application Launcher (NAL) allows users to run applications that were previously configured by a network administrator. The applications are displayed as icons. Users double-click the icon to launch the application.
  When a user runs NAL, the software checks for applications the user is allowed to access. It locates the user's applications and accesses them transparently when the user clicks on the icon in Windows*. Users do not need to worry about drive mappings, paths, or accessibility to application directories.
  NAL offers easy distribution, updating, version control, and license management for applications stored on the network.

Loading and Setting Up Applications on the Network

Follow the general rules in this section before you install your network applications.

Guidelines for Loading Applications

You can load various types of network applications, such as word processing or spreadsheet programs, to make them available to users. When loading applications, keep the following in mind:

• You need the Create right in the directory where you will be loading the application. The NEAT utility has a Full rights option which includes the Create right. See "Assigning File System Rights" for information.
• Follow the instructions in the application's documentation for loading the application onto a network.
• Make sure the application is designed for network (multiuser) use, and that you observe any licensing restrictions on the number of users who can access the application.
• To allow users to access network-based applications, map search drives to the directories that contain these applications. A network search drive mapping is a network drive that has been inserted into the DOS PATH command to allow DOS to find executable files on network drives. For example, you could type
  MAP INS S1:=ACME_SYS:APPS\WP
  This creates a drive mapping and places the search into the first position. S1: will begin searching at drive Z:. It will also overwrite the first drive letter in the DOS PATH statement.
• If the application requires that it be installed at the root of a volume, but you would rather install it in a subdirectory for security reasons, you can map the directory to a fake root. For example, you could type
  MAP ROOT S5:=ACME_SYS:APPS\WP
  This creates a search drive using a root mapping. This means the drive searched at S5 is a root drive for the application.
• You can create a Directory Map object that points to an application directory.
  Directory Map objects are useful in login scripts. Instead of mapping a drive to a specific directory path, you map a drive to a Directory Map object that points to a directory. Then if you change the directory path, you need only to change the Directory Map object's definition rather than the path.
  See "Application Management Guidelines" or " Creating and Using Directory Map Objects" in Supervising the Network (NetWare 4.11 online documentation) for more information.

General Instructions for Loading Applications

Follow these general steps to load and make applications accessible to users on the network.

• Select a volume. Determine in which volume the applications will be placed; for example, you could install your company's applications in the SYS: volume.
• Create a directory in the volume. Create a directory in that volume for the applications; for example, you could create an APPS directory under the volume SYS:, then create a subdirectory for each application.
• Install the applications. Install the applications into the correct volume and directory on the network.
• Add an Application object to Novell Directory Services. With NEAT, add the Application object. See "Adding Applications to Novell Directory Services" for information.
• Add users and groups to the Application object. With NEAT, add the users and groups who will need access to the application. See "Assigning Users and Groups to Applications" for information.
• Assign access rights to users and groups. With NEAT, assign rights that users and groups will need to access network applications. See "Assigning File System Rights" for information.

Adding Applications to Novell Directory Services

Before employees can launch network applications on their workstations, you must add the Application object to the NDS database.

Add a New Application

To add a new network Application object, do the following.

Prerequisites

• Install the application on a network drive
• Add users and groups to NDS
• Log in to the network as ADMIN
• Double-click the NEAT icon

Procedure

1. From the New menu, click Application or click Add a New Application on the toolbar.

2. Enter the path to the application's executable file.

   1. Click on the folder icon to browse the file system for the executable file.

   2. Locate and double-click the executable file to add it to the path entry box.

      For example, if you are creating an Application object for GroupWise, and the executable file (OFWIN.EXE) is stored in \\SERVER\SYS: PUBLIC\APPS\OFWIN, you would browse for \\SERVER\SYS:PUBLIC\APPS\WIN\OFWIN. EXE.

3. Click the software platform on which the application runs (DOS, Win 3.x, Win 95, etc.).

   Some applications are not compatible with all versions of Windows. Users who have desktop platforms that are not compatible may not be able to view or open the application.

4. Click Next.

5. Enter a name for the application.

6. (Optional) Click the folder to browse the file system and select a path for the working directory or accept the default.

   This is the path to common files on the network or to a workstation's hard drive.

7. (Optional) Add any command line parameters.

   These are additional command line options you can use to customize the application when it launches. For example, if you enter application name /@u - login name, the application is customized for that user. This makes it so the user doesn't have to enter special login command options every time the application is launched.

8. Click Next.

9. Grant users and groups access to the application.

   You can grant access for users or groups now or later.

   If you grant access later, go to "Assigning Users and Groups to Applications" or "Grant Access to an Application" when you are ready.

   To grant access to users and groups now, click Add. Select the users or groups from the list. Click OK.

10. Click Finish.

    Product icons for the applications you add are automatically distributed to the users and groups specified and are displayed in the NetWare Application Launcher (NAL) on the users' desktops. Users can then launch the applications by double-clicking the application's icon.

Change Application Information

To change the properties of an application, do the following.

Procedure

1. From the Directory view, select the application.

2. From the Property view, select the General tab.

3. Figure 6-3. Application Properties

   
   
   

4. Set or change any of the parameters as needed:

   • Application path and filename. If the application has been moved, or you are about to move it within the file system, click the folder icon to browse the file system for the application's executable file.
   • Application name. You may choose to change the application's name inside this field. Because this setting has no effect on how the application runs or works with the network, any name can be used.
   • Working directory. Indicate which directory the application will use as its default working directory. This determines the location from which files will be opened and saved. Some applications require a working directory; others do not.
   • Command-line parameters. Enter any options the application requires to run in a desired mode. Command line parameters automate the execution of an application so you do not have to enter options every time you open the application. For example, if you do not want users to be required to enter their login names every time they run GroupWise, you would supply the following parameter: C:\OFWIN40\OFWIN.EXE/@u- login name.

5. Click Add.

6. Select the users or groups to be added. To select several groups, press <Ctrl> while clicking on the users or groups.

7. Click OK.

Grant Access to an Application

The Applications tab displays applications to which the user currently has access.

To change an application's properties, do the following.

Procedure

1. From the Directory view, select the application.

2. From the Property view, select the Users, Group tab to displays any users who currently have access to the application.

   Figure 6-4. Grant Access to Applications

   
   
   

3. Click Add.

4. Select the users or groups to be added. To select several groups, press <Ctrl> while clicking on the users or groups.

5. Click OK.

Remove Access to an Application

To remove access to an application, do the following.

Procedure

1. From the Directory view, select the application.

2. Click the Users, Groups tab.

3. Click the user or group.

4. Click Remove.

5. Click Yes to confirm your action.

Assigning Users and Groups to Applications

To add users and groups to a new application, do the following.

Prerequisites

• Log in to the network as ADMIN.
• Double-click the NEAT icon.

Procedure

1. From the Directory view, select the user or group to add.

2. Click the Applications tab.

   Figure 6-5. Assign a User Application

   
   
   

3. Click Add.

   1. From the list, select a user or group. To select multiple users, press <Ctrl> while clicking on the desired users or groups.

   2. Click OK.

4. Click Finish.

Assigning File System Rights

Application programs or directories containing applications need to be assigned rights so that users can access the applications yet the applications can be protected from being corrupted.

The way you assign file and directory security determines who can access files and directories and what users can do with them. As the administrator, you have the Supervisor right, which means you can grant directory and file rights to other users. You have all rights.

The Small Business file system has two types of rights:

• Directory rights control what a user can do with a directory. These rights can be assigned using the NEAT utility.
• File rights control what a user can do with a file. These rights must be assigned using NetWare Administrator.

Directory and File Rights

Rights to network directories can be assigned to the Organization object, to groups, or to one user; however, the following constraints apply.

• Organization rights. If directory rights are assigned to an Organization object, those rights apply to everyone in the organization. You can assign a group or a user more rights, but not fewer. It is best to keep these rights at a minimum.
• Group rights. If directory rights are assigned to a group, those rights apply to everyone in the group. A group member can be assigned more, but not fewer, rights than the group has.
• User rights. Explicit assignments to a user can be superseded by rights assigned to either the organization or a group of which the user is a member. A user can be given more, but not fewer, rights.

If you try to make assignments that do not meet these criteria, you are notified that the assignment cannot be made. You need to determine whether a group's or organization's rights are interfering with the explicit assignment.

Small Business rights (Full, Read, or None) can be assigned to a user or group at the directory level.

You assign limited rights (Full, Read, or None) with the NEAT utility.

Assign File System Rights to a User or Group

To allow users and groups to access files and directories on the network, do the following.

Prerequisites

• Log in to the network as ADMIN.
• Double-click the NEAT icon.

Procedure

1. From the Directory view, select the user or group.

2. From the Property view, select the Security tab.

3. Click File System Rights.

   Figure 6-6. Access to Files and Directories

   
   
   

4. Select the directory to which you want to give the user or group access.

   1. Click Set Rights.

   2. To change rights, click Full, Read, or None.

      IMPORTANT: User rights cannot be decreased if the user belongs to a group that has the rights you want to eliminate. To decrease the rights, you must go to the group and change the group rights or delete the user from the group.

5. If the directory does not exist, do the following; otherwise, go to Step 6.

   1. Select the directory or volume in which the new directory will be placed.

   2. Click Create a New Directory.

   3. Enter the name of the directory.

   4. Click OK.

6. Click OK.

Assign File System Rights to an Organization

All users in this organization will inherit the same right assignments. In this case, a user can be assigned more, but not fewer, rights than those in the organization. For best results, keep the rights assignment at this level to a minimum. When only a few users need rights to a directory, create a group and grant rights to the group rather than assigning rights to the organization.

To allow everyone in your organization to access files and directories on the network, do the following.

Procedure

1. From the Directory view, select the Organization object.

2. From the Property view, click the General tab.

3. Click Set Directory Rights.

4. Figure 6-7. Access to Files and Directories

   
   
   

5. Select the directory to which you want to give the user or group access.

   1. Click Set Rights.

   2. To change rights, click Full, Read, or None.

      IMPORTANT: User rights cannot be decreased if the user belongs to a group. To decrease the rights that has the rights you want to eliminate, you must go to the group and change the group rights or delete the user from the group.

6. If the directory does not exist, do the following; otherwise, go to Step 6.

   1. Select the directory or volume in which the new directory will be placed.

   2. Click Create a New Directory.

   3. Enter the name of the directory.

   4. Click OK.

7. Click OK.

Display and Change File System Rights

To view or change file system rights, do the following.

Procedure

1. From the Directory view, select the user or group for whom you want to change rights.

2. From the Property view, select the Security tab.

3. Click File System Rights.

4. View the files and directories to see the rights for this user or group.

   1. Click Set Rights.

   2. To change rights, click Full, Read, or None.

      IMPORTANT: User rights cannot be decreased if the user belongs to a group that has the rights you want to eliminate. To decrease those rights, you must go to the group and change the group rights or delete the user from the group.

5. Click OK.

Remove File and Directory Access

To remove all access to a directory or file for a user or group, do the following.

Procedure

1. From the Directory view, select the user or group.

2. From the Property view, select the Security tab.

3. Click File System Rights.

4. View the files and directories to see what rights the user or group has.

   1. Click Set Rights.

   2. To remove all access rights, click None.

      IMPORTANT: User rights cannot be decreased if the user belongs to a group that has the rights you want to eliminate. To decrease those rights, you must go to the group and change the group rights or delete the user from the group.

5. Click OK.

Create Directories and Copy Files

Users normally create directories and work with files in their workstation operating system, such as File Manager in Windows*. New directories can also be created using the NovellŽ Easy Administration Tool (NEAT).

Prerequisites

• Log in to the network as ADMIN.
• Double-click the NEAT icon.

Procedure

1. From the Directory view, select a user or group.

2. From the Property view, select the Security tab.

3. Click File System Rights.

4. Click Create a New Directory.

5. From the list, select the directory in which you want the new directory to be placed.

6. Enter the name of the new directory.

7. Click OK.

   The new directory retains the same directory rights as the directory above it.

8. Click Close.

Retrieve Deleted Files and Directories

Files deleted from a server remain on disk in DELETED.SAV until the deleted files are removed from a workstation by deleting files in the wastebasket or using the PURGE command at the command line. You can retrieve deleted files anytime before they are removed from the hard drive.

Removing files frees disk space used to store the deleted files on the server's hard disk. If a disk runs out of space, Small Business automatically removes the files that were deleted first.

You cannot retrieve and remove files with NEAT. To do this, you must use NetWare Administrator, which is located in the SYS:PUBLIC directory under NWADMIN.

Directory and File Commands

Table 6-2 lists some command line utilities you may find useful. For usage information type the command plus /? . For help while in the utility, press <F1 >. You can use these commands at your workstation.

Table 6-2. Directory and File Utilities

Command	Purpose	Syntax
FILER	Allows you to modify or view files; change current directory; modify, add, or view directories or subdirectories; modify or view rights to directories and files; view trustees for directories and files; retrieve deleted network files.	FILER
FLAG	Allows you to modify file and directory attributes; modify the owner of a file or directory; and view or modify the search mode of executable files.	FLAG path [[+ | -] attribute...] [/ option]
MAP	At the command line or in a login script, allows you to view drive mappings, create or change network mappings, or map a drive to a fake root directory (for applications that must use a root directory). This command is also useful in user login scripts. Some directories are mapped by default when Small Business is installed. This command maps to the next (n) available drive. This command maps drive F: to a volume or a directory as a fake root.	MAP [ drive] := [ path] Example: MAP g:=accounting\kim Example: MAP n [ server] [ volume]:[ path] Example: MAP ROOT F:=[ path]:
NCOPY	Allows you to copy files and directories from one directory to another.	NCOPY [ source_path] filename target_path [ filename] Example: NCOPY c:\dos*.* D:\temp
NDIR	Allows you to view information about files and directories; view volume information; sort information by date, owner, file, or directory attributes.	NDIR [ path] [/ option] Example: NDIR F:\*.*/DO allows you to view only directories on drive F:.
NLIST	Similar to the DOS DIR command. Allows you to view information about objects and searches objects and object properties. The DOS DIR command searches only directories and files.	NLIST [ class type] [ property search option] [ object name] [/ basic option] [ display option] Example: NLIST VOLUME=VOL1 SHOW SERVER

Additional Information

For More Information About	Go To
Drive Mapping	"Drive Mapping" in NetWare 4.11 Concepts
FILER	"FILER" in NetWare 4.11 Utilities Reference
File System	"File System" in NetWare 4.11 Concepts
FLAG	"FLAG" in NetWare 4.11 Utilities Reference
MAP	"MAP" in NetWare 4.11 Utilities Reference
NCOPY	"NCOPY" in NetWare 4.11 Utilities Reference
NDIR	"NDIR" in NetWare 4.11 Utilities Reference
NetWare Administrator (NWADMIN)	"NetWare Administrator" in NetWare 4.11 Utilities Reference " Managing Print Services with the NetWare Administrator Utility" in Print Services
Network Applications	"Loading Operating Systems and Applications onto the Network" in Supervising the Network
NLIST	"NLIST" in NetWare 4.11 Utilities Reference
PURGE	"PURGE" in NetWare 4.11 Utilities Reference
Rights (Directory, File System, Object, and Property)	"Rights" in NetWare 4.11 Concepts

---

Prior

Main Index

Next

---

    This page is maintained by:   Michael P. Harris

---

	viking.delmar.edu Last Updated: Sep 20		mpharris@surf.delmar.edu Copyright © 1998