search cancel

Ghost Solution Suite 3.0 architecture and data flow diagram


Article ID: 185023


Updated On:


Ghost Solution Suite


The following document lists the dataflow between the components of Ghost Solution Suite 3.0 for some of the most commonly used tasks.


Architecture and components of GSS 3.0:

The following diagram displays the various components and services of Ghost Solution Suite 3.0:

Ghost Solution Suite Share or eXpress share

The eXpress share is used to store images, packages and program files. This folder (file server path) must be accessible from all Ghost Solution Suite agents.

Ghost Solution Suite Server

The Ghost Solution Suite Server is the central component of a GSS system and manages the GSS Database, the communication between the different components, and schedules jobs to run on managed computers.

Ghost Solution Suite Database

The GSS Database provides the back-end data store that stores details about the computers, groups, and jobs of the Ghost Solution Suite. Most of the times, you don’t have the need to interact directly with the database. For the SQL Server Instance, use default port number 1433 which is required to communicate over a firewall.

Ghost Solution Suite Agent

This agent runs on the managed computers to report inventory, run software and scripts, perform power control, and boot the computer into automation. A Remote Agent Installer quickly installs the agent on multiple Windows computers. Linux computers can install the agent using startup scripts and other automated processes. The agent connects to all the GSS Servers using the port 402.

PXE server

Automation is the preboot environment loaded by GSS Server to perform tasks which need to happen outside of the normal operating system. If you have ever used a disk imaging utility, or booted a computer using an installation CD, you are probably familiar with running computers in a similar environment. GSS provides several tools to boot computers to this environment and supports several automation operating systems.

A DHCP server is required for network and PXE server to work properly.

Remote Agent Installation:

Before you start with any other configuration and tasks, to manage the client computers you must first install an agent on the client computers that are present in the network.

Creating a PXE Boot image:

PXE boot image is the preboot image that is used to boot a client computer in automation environment over the network.

PXE manager:

PXE Manager is a service that synchronizes Ghost Solution Suite Server and all PXE Servers that are installed and configured across the network. It keeps track of all PXE Server boot menu options and checks if they are shared or local. PXE Manager also gathers data from all PXE Servers and stores the information in the PXE Manager.ini file. PXE Manager creates and distributes the appropriate PXE.ini file for each PXE Server on the network.


Running a task on a client computer that is booted in production environment:

You can run a task such as modifying configuring of a client computer. The following diagram depicts the flow of data when a task is scheduled for a client computer that is booted in production environment:


Creating and installing an automation folder configuration:

An automation folder is a package that contains the Preboot configuration files and drivers that are required to boot a client computer in the automation environment.
The automation folder configuration is installed on a client computer. You can boot the client computer in automation environment using the automation folder even when the client computer is disconnected from the network.

Running a Task in Automation environment using PXE Server:

A few tasks are run when the client computer is booted in the automation environment. Tasks such as imaging a client computer are carried out when the computer is booted in the preboot environment.

Running a task in automation environment when the client computer is booted using the automation folder:

The following diagram displays the flow of data when the client computer is booted in automation environment using an automation folder.