Altiris 7.1 Installation Guide

Posted on Posted in Altiris

In this post I’ll explain how install the basic infrastructure for Altiris 7.1.

Altiris Deployment Solution software helps reduce the cost of deploying and managing servers, desktops, notebooks, and thin clients from a centralized location in your environment. An easy-to-use, automated deployment solution offers OS deployment, configuration, PC “personality” migration, and software deployment across hardware platforms and OS types, including Microsoft Windows 7 and Windows Server 2008 R2.

This consist in two Windows 2008 R2 one of these contains the SQL DataBase Server and the other one the Altiris Manager Server. The minimum and recommended requirements are:

  • SQL Server

 

  • Notification Server + Site Server

 

SQL Installation

Pre-Requisites

The installation for the SQL server need the Microsoft NET Framework 3.5

Disk Format

Ok, my recommended storage distribution is:

DISK1 80GB (C:) --> S.O + SQLSERVER BINARY
DISK2 15GB (E:) --> SQLSERVER DATA
DISK3 5GB (F:) --> SQLSERVER LOGS

NTFS formatting blocks of 64kb
The disks that hold the log files and data is formatted to 64kb per block to improve the performance of SQL Server.

Binary Installation

This is a normal SQL installation follow the pictures:

 Select this features:

Specify the name of your Instance:

Select the user with the who run the SQL services, and the user (normally the same) with the Administrative role:

This is very Important, separate the DATA and SQL Server LOGS in different partitions created previously:

Desactivate the FILESTREAM:

Allow the user with the Administrative role with the Analysis Services:

Select C:\ to install the binary files:

And finally install in Native mode: 

When installation finished, install the SQL Server SP2 Package

SQL Server configuration

We must apply special configurations as dictates BestPractics document (applicable to any
SQLSERVER).

AWE

If the machine have more than 2GB is recommended activate AWE support (When AWE is sic enabled, SQL Server always attempts to use AWE-mapped memory).

First in the security policy add the User who run the service SQLSERVER

Security Settings/Local Policies/User Rights Assignment/Lock pages in memory

Activate AWE:

Autogrowth

Increase Autogrowth, ie increase the autogrow data files, thereby improving the performance of the BD.
This expanded Databases folder and open the properties of our DB:
Set the File Growth to a value Such As 500MB or 10%

Autoshrink

The Autoshrink causes fragmentation in the database, thus decreasing performance. To turn it off we need to open SQL Management Studio and make a new query.

DECLARE @Base SYSNAME

DECLARE database_cursor CURSOR FOR
    SELECT QUOTENAME(name) AS Base
    FROM master..sysdatabases
    WHERE DATABASEPROPERTYEX(name, 'Status') = 'ONLINE'
          AND DATABASEPROPERTYEX(name, 'IsAutoShrink') = 1

OPEN database_cursor
FETCH NEXT FROM database_cursor INTO @Base

WHILE @@FETCH_STATUS = 0
BEGIN
    EXEC ('ALTER DATABASE ' + @BASE + ' SET AUTO_SHRINK OFF')
    FETCH NEXT FROM database_cursor INTO @Base
END
CLOSE database_cursor
DEALLOCATE database_cursor

Management Platform 7.1

To install Management Platform follow the official Symantec Installation Guide

If you have some question about Altiris (auto-deploy ghost, join Domain, change Computer name, etc). I have experience in configurate new installation’s, work with it, and created personalized scripts to automatize the process. you can contact me:

Leave a Reply

Your email address will not be published. Required fields are marked *