 |
» |
|
|
|
You may want to load workstation
operating system (OS) files on the network to save workstation disk
space or to allow diskless workstations
to log in to the network. This section explains the following tasks: Loading other applications Assigning trustee rights to OS and application directories
Loading DOS onto the Network | |
A workstation running DOS 3.30
or later The Supervisor or Create right to the directory
where you want to load the application
Create a directory in SYS:PUBLIC for each
workstation type and version of DOS you will be using on your network. Name your directories according to the following convention: SYS:PUBLIC\machine\os_type\os_version |
For each directory, replace machine with the six-character
machine name of the workstation (such as IBM_PC or COMPAQ). Replace os_type with the type of DOS you are using (such as
MSDOS or DRDOS). Replace os_version with the DOS version number. For example, to install MS-DOS 5.0 on an IBM* PC, go to SYS:PUBLIC
to create the DOS subdirectory. To use the DOS MD command, type
the commands shown next (in order): Load DOS. Follow the instructions in the DOS documentation to load the
DOS software into the directory you created. In the system login script,
map the second search drive to the DOS directory. If all users have the same types of computers and are using
the same version of DOS, you will probably have only one DOS directory.
In this case, add a line similar to the following, substituting
the correct directory names: MAP S2:=SYS:PUBLIC\IBM_PC\MSDOS\50 |
If your network has more than one DOS directory, use variables
to indicate the directory path. These variables are replaced by
the correct information from the workstation software when each
user logs in. Enter the following command, exactly as shown, in the login
script: MAP S2:=SYS:PUBLIC\%MACHINE\%OS\%OS_VERSION |
(The first search drive should be mapped to the PUBLIC directory
so that users can access NetWare utilities.) So that the %MACHINE
variable will work, make sure the long machine type is set in each
station's NET.CFG file. For example, a station might have the following line in its
NET.CFG file: LONG MACHINE TYPE = IBM_PC |
Add COMSPEC to the container login script. Following is the proper syntax for the COMSPEC command: This command tells the workstation where to find the command
processor.
Loading Windows onto the Network | |
You can load Windows onto a network in several ways. Load all Windows files on a user's
local hard drive. Load Windows program files on the server, and load
user files on local hard drives. Load all Windows program and user files on the server.
In most cases, this installation provides the easiest maintenance
and most efficient use of resources.
Instructions for the first two options are included in the
documentation that came with your Windows software. Instructions
for loading program and user files on the server are included in
this section. Following are some advantages of having all Windows files
installed on the server: Program and configuration files are
backed up and secure. No hard disk is required on the user workstation. The .INI and driver files for all users can be updated
from one location. Configuration files always match hardware.
The only disadvantage of having all Windows files installed
on the server is that it causes more network traffic. Files Needed for NetWare Functionality in WindowsUse the following files to run Windows with NetWare
functionality. These files are in the Workstation for DOS/Windows
client kit that is installed with NetWare Services. Guidelines for Running Windows on the NetworkFollow these guidelines for running Windows on the network: Use a permanent swap file on a local
hard drive, if possible; do not use network directories for swap
files. If a local swap file is not possible, consider increasing
RAM to a minimum of 8 MB. Ensure that the RAM plus swap file size is at least
10 MB. Remove Windows search drives from the workstation
AUTOEXEC.BAT file. If users are running DR DOS, make sure DR DOS files
are dated 07 April 1992 or later. If users are running DR DOS, make sure their CONFIG.SYS
files install EMM386.SYS and configure it for use with Windows.
See your DR DOS manual or DR DOS online help for configuration information.
Loading and Setting Up WindowsPrerequisites A workstation running DOS 3.30
or later The Supervisor or Create right to the directory
where you are loading Windows A licensed network copy of Windows 3.1 or later 16 MB of available disk space NetWare Client for DOS and Windows
Procedure Install Windows server software using the SETUP /A option. For complete information about the Windows SETUP options and
the installation procedure, see the documentation that came with
your Windows software. Create a Group object for users who will be running
Windows. For instructions on creating a Group object, see "Managing
Group Objects" in Chapter 2. Make the Windows Group object a trustee of the Windows
directory. For instructions on granting trustee assignments, see "Adding
a Trustee to a Directory or File" in this chapter. Create a directory for each user to store user-specific
Windows files. WIN.COM and files such as .GRP and .INI files are stored here. Add the following
information to the system login script. An example of the syntax used for these login script entries
appears at the end of this step. Map a drive to the user-specific directories for the MS Windows
group. Map a search drive to the Windows directory for
the MS Windows Group object. Set the Windows TEMP directory to a subdirectory
of the user directory.
The following example shows the container login script entries
you would add to set up Windows 3.1 on the network: IF MEMBER OF "WIN31" THEN |
MAP INS P:=SYS:USERS\%LOGIN_NAME\WIN31 |
MAP INS S16:=SYS:APPS\WINAPPS\WIN31 |
SET TEMP = "P:\uSERS\%LOGIN_NAME\WIN31\TEMP" |
Set up the workstations by completing the following
steps. Change to the search drive mapped to the Windows directory. Enter the drive letter only. Modify the user AUTOEXEC.BAT and CONFIG.SYS files
by typing SETUP /N <Enter> Select the "Custom" option to make sure
environment variables are correct. When Windows prompts for a path
during setup, enter the drive letter instead of the path. Install the NetWare Workstation for MS Windows
software. Follow the instructions in NetWare Client for DOS/Windows
User Guide to install the workstation software and update NetWare-specific
files in the Windows directory.
Additional Information Loading Other Applications onto the Network | |
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. 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.
To make these search drives permanent, place them in login scripts
that are executed when users log in. 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.
To map a fake root directory, use the MAP ROOT command as explained
in "MAP" in this chapter. 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. If you change the directory path, you need to change only
the Directory Map object's definition.
Assigning Trustee Rights to Operating-System and
Application Directories | |
Application programs need
a set of file system rights that make them available to users yet
protect them from being corrupted. Keep the guidelines that follow
in mind as you assign file and directory rights to executable, application,
and program files. When you are ready to assign file and directory attributes
and rights, see "Making the File System Secure and Accessible"
in this chapter. Use the FLAG utility to assign rights
as follows: Assign the Shareable and Read-Only
attributes to application and workstation operating-system files. Assign the Execute Only attribute to executable
files for which you keep permanent backups. Assign Read and File Scan rights to the User or
Group objects that need to use the application.
|
Printable version
