Altiris Deployment Solution™ from Symantec User’s Guide 337
Configuration. TCP/IP, Microsoft networking, and user information
Applications. The installed applications and information about these applications, such
as the name of the application, publisher, and product ID
Services. Installed Windows services
Devices. Installed Windows devices, such as network adapter, keyboard, and monitors
Location information. Contact name, phone, e-mail, department, mail stop, and site
The Deployment Server Database also contains jobs and other data used to manage
your computers.
Note
You can install a single Deployment Database in each Deployment Server system—you
cannot have two databases storing data for a single computer. If the computer you are
installing the database on has an existing Microsoft SQL Server™, the Deployment
Database is added to that instance of the database engine.
Support for multiple database instances
In Deployment Solution 6.0 and later, you can identify a named instance of the Microsoft
SQL Server when installing Deployment Solution. You can now identify other named
instances of Microsoft SQL Servers instead of accessing only the default instance. This
feature lets you identify and run multiple databases from one clustered Microsoft SQL
Server to manage multiple sites or network segments. This feature is supported in the
silent install .INI file and the GUI install executable. Deployment Solution also supports
a different name for the Deployment Database instead of the default name, eXpress.
See Custom install for Deployment Server on page 344 and Deployment Server
components on page 335.
Deployment share
The Deployment Share is a file server or shared directory where Altiris program files and
packages are stored. The Deployment Share can be a shared directory (default Simple
install in Program Files\ Altiris\eXpress\Deployment Server) or another file server (in the
Custom install, you can assign a Microsoft Windows or Novell NetWare file server).
Deployment Share is where you store image files, registry files, .MSI packages,
Personality Packages, script files, and more. When you are deploying or managing a
computer, the Deployment Server stores and retrieves these packages from the
Deployment Share as needed.
If you want to install Deployment Solution on a remote file server (not
the computer where you are running the install program), create a
share (or give Read/Write rights for NetWare) on the file server where
you want to install the Deployment Server. This share must allow access
to all other components, including managed computers and the user
account that runs the Deployment Server.
You must create this share before you begin installing. If you are
not installing on a remote computer, you can select the option to create
the share during the installation.
To Next Page
Loading...