Before we can install our Deployment Server there are a number of things that we should do before this can happen.
- Hardware and Software Requirements
- Purchase or obtain the license file that is needed for installation
- Pre-boot automation files are needed, locate and save them.
- Create your Administrative or service account with rights to install the Deployment Server
- Decide on your Deployment System naming convention.
- Download and install Microsoft .NET 1.1 and SQL 2000 SP3 or SQL 2005
- Decide on either a simple or custom installation
Now that we have our list of things to do, let's start!
Hardware and Software Requirements:
Before you start your installation, go over the Hardware specs of the server and make sure that it meets the following specs to run efficiently:
- Xeon Processor or any Server architecture
- 2GHz or faster processor
- 2GB RAM
- At least 100GB of Hard disk space
- If the database is going to be hosted on the same server, an additional 1GB RAM is recommended. And if the database is located off the Deployment Server and will be accessed over the network, the network connection speed should be at least 1GB for best performance.
- Windows Server 2003 SP2
- SQL 2000 SP3 or SQL 2005
Licensing Options:
There are a number of licensing options to consider.
- Server computers require server licenses
What counts as a server?
- HP, IBM, Dell Servers
- Desktop running Server OS
- Desktop with Linux OS
- All other computers require client licenses
You may either use the 30-day evaluation license that is sent by e-mail when the software was downloaded from the Altiris site. The only limitation of this evaluation license is that it only supports 10 nodes. If you are evaluating the software, why need more than 10 licenses?
If you do not have your purchased license yet and your 30-day evaluation license has expired, there is an option that you can use. Altiris gives you a FREE 7-day license to use, also with the 10 node limitations, but all the other functions are still available.
Note: Only HP provides the users that purchased any commercial desktop or notebook computers with a free 30-day Deployment Server license per device.
Pre-Boot Automation Files
Operating System that can be used for Pre-Boot automation are:
- Microsoft DOS 98
- Microsoft WinPE
- Fedora Linux
- FreeDOS
Note: During Simple install only 1 Pre-boot OS can be installed. But during Custom install, more than 1 pre-boot OS can be installed.
Where to get these Pre-Boot files:
FreeDOS - It's free and can be downloaded from the Altiris website.
Microsoft DOS 98 - Can be installed from a Windos 98 cd or a bootdisk or downloaded from http://www.alttech.co.za/DeploymentServer_Tutorials_Altiris%20Deployment%20Solution%206_9%20Support.html website.
Linux - It's a free operating system and can also be downloaded from the Altiris website.
WinPE - WinPE can be purchased from Microsoft or Altiris. This is a stripped down version of Windows XP Professional. What makes it better than DOS is that it has better driver support, increased speeds and more functionality. Downside is it's size and load time.
Administrative Accounts:
This user account will need rights to Install Deployment Server, run the Deployment Services, rights to access the eXpress database, rights to access the deployment share, join computers to the domain and rights to access the Deployment Server console.
By the looks of all the rights needed and functions that the account will undertake, I would suggest that we create a service account, whose password does not expire and has domain admin rights.
- Create a domain admins account, this should eliminate any administrative problems that may occur during the installation process.
- When installing the SQL database, make sure you use this same account for the installation other than the SA account. As it is easier to remember 1 username and password.
Note: Make a note of the username and password used, people tend to forget what it is and wastes time having to do a re-install of the database.
Naming Convention:
It is not recommended to change the Deployment Server name after the Deployment software has been installed. So make sure of your Deployment Server and SQL database server name beforehand.
If the Deployment Server name is changed after the Software is installed you will have to re-configure all the client machines that connect to that server, as they will still be connected to the old Deployment Server name and will not be managed under the new Deployment Server.
Note: Please make sure that your Deployment server has a static IP Address, as this can cause problems if the IP address changes every couple of days when the DHCP lease expires. And bootworks also maps to the old server name with the NET USE command and that needs to change as well otherwise you will not be able to image computers using the network boot method in DOS.
Download and Install Microsoft .NET 1.1 and SQL 2000 SP3 or SQL 2005
The Deployment Server software cannot be installed unless Microsoft SQL Server 7/2000/2005 or MSDE 2000 SP3a and Microsoft .NET Framework 1.1 has been installed on the server.
Microsoft .NET Framework needs to be installed on the server where the Deployment Server WEB Console and Win32 Console will be hosted and SQL will need to be installed on the server where the eXpress database will be hosted. If the Deployment Server and the database are to be hosted on the same server then SQL and Microsoft .NET Framework 1.1 needs to be installed on the same server.
Note: Deployment Solution 6.5 needs Microsoft .NET Framework 1.1 and MDAC 2.7 SP1 or higher. Software can be downloaded from the Microsoft website.
Installation Options:
There are 3 installation options to choose from:
- Simple Install (Include PXE Server)
- Custom Install
- Component Install
Simple Install
Installs all of the Deployment Server components on the same computer. You also have the option to install the PXE server on the same computer as the Deployment Server.
Custom Install
You are able to choose the installation components. Good for only installing a single component like the Web Console or Deployment Console to manage your Deployment Server.
Component Install
Gives you the option to install any of the following components after Deployment Server has already been installed:
- Deployment Console
- Web Console
- PXE Servers
- Deployment Agent Software
- Sysprep Files
- Install Deployment Server using the Simple Installation Method
From the Setup menu, select simple install and if you want the PXE server to be on the same computer then make sure you have checked that box.
Note: If upgrading the Deployment Server, there is no need to include the PXE server option as it is already installed and will not need to be re-installed.
When you are presented with the above mentioned screen, confirm your installation directory, and also make sure that that the "Create Deployment Share" is also selected, otherwise you will not be able to connect to your images.
Also enter your license file location if you have one other wise use the "Free 7 day License" option. Last but not least on this page, make sure that you enter your Administrative account and password for the installation to take place.
The next phase in the simple installation process is the Pre-boot OS, unfortunately I haven't created a screenshot of this. But here you will have to install one of the following and point to the install file locations:
- Windows DOS 98
- Linux
- WinPE
- FreeDOS
Note: Only one pre-boot OS at this time and additional pre-boot OS's can be added after the installation has been completed, under the "Boot Disk Creator" tab.
After you have configured the Deployment share and pre-boot automation OS information, an installation summary page will appear. Giving you a chance to review all of your installation options.
After you have reviewed the installation info and clicked Install, the installation will begin.
Note: Everything that has been posted here is available in PDF format for download attached to this article.