4 Administrator Guide for SAS 9.1.3 Foundation for Microsoft Windows
AutoPlay on the SAS Setup Disk. The SSN was written in Java, to take advantage of the
platform independence offered by that programming language.
In addition to supporting the installation tools described in this chapter, the SAS Software
Navigator provides access to online installation and configuration documentation,
installation qualification tests, and links to the Install Center, SAS Technical Support, and the
installation steps for other platforms.
Administrators who install SAS across a multiplatform and/or multi-machine environment
should also refer to the SAS Intelligence Platform: Planning and Administration Guide and
the SAS Intelligence Platform: Installation Guide which are located at
http://support.sas.com/documentation/configuration/index.html
Classifying Your End Users
Before you deploy SAS software, you should identify the various classes of end users that you
will support. End users can be divided into three classes:
1. Client Users
Client users install a minimal set of components on their local PCs, but run the majority of
their SAS Software from a network image that you create.
2. Personal Users with Network Access
Personal Users with network access are users who install all SAS software that they will
use on their local PCs from a network image that you create.
3. Personal Users without Network Access
Personal Users who do not have access to the network must install all SAS software that
they will use on their local PCs using their own set of CDs.
Client User Model
Advantages of this model:
• The amount of disk space required to run SAS is minimized.
• Any configuration changes can be done on the server and inherited by all of the clients.
Operations such as updating a SAS Installation Data file (including SETINIT) can be
managed more efficiently.
Disadvantages of this model:
• All of the clients are dependent on the server to operate. If this server goes down, none of
the clients will be able to run SAS.
• There is a strong network dependency for all of the clients. Performance may be hindered
due to the amount of network traffic and any additional load on the SAS Server.
Personal User Model
Advantages of this model:
• Each copy of SAS is unique and has no dependencies. There are no dependencies on the
network or on any one server. The server is used only as a location from which to perform
an installation.
• In most cases, personal installations yield the best performance, since all of the files are
local to the user’s system
Disadvantages of this model:
• All SAS System files are present on each computer that has SAS installed. A large amount
of disk space is required so that SAS can run independently.
