Article

This guide assumes that you’ve got some sort of virtualization infrastructure in place – this could be a VMware product, Microsoft Hyper-V, Citrix XEN and so on.

This guide assumes that you’ve got some sort of virtualization management tool, and a library where you store all the virtual machine templates and master images. This guide is NOT product specific.

This guide assumes that you’ve got the ObserveIT Application server and ObserveIT database server up and running. For more information about how to properly install ObserveIT, please consult with the product’s documentation. For an online version please visit the following link:

http://www.observeit-sys.com/documentation/Documentation-V5/index.html

Please make a note of the server name or IP address on which the ObserveIT Application Server is installed, plus the TCP port on which it listens. By default, ObserveIT will create a web site that will be configured to listen to TCP port 4884. By doing so, all the ObserveIT Agents will communicate with the ObserveIT Application Server by using TCP port 4884.

If there's a firewall between the ObserveIT Agents and the ObserveIT Application Server, you must allow traffic for the TCP ports that the ObserveIT Application Server communicates on through that firewall. As previously noted, new ObserveIT installations use TCP port 4884, but this port can be changed to meet the organization's requirements.

In addition, this guide assumes that you’ve got basic knowledge about how to set up and run your virtualization product, that you are knowledgeable about setting up virtual machines, and about the proper procedure to install and configure a Windows-based operating system on these virtual machines.

Lastly, this guide assumes that you’re knowledgeable about the proper procedures needed to be taken prior to creating a virtual machine clone, how to use SYSPREP (the system preparation tool from Microsoft), and how to create proper answer files for the preparation procedure.

To download SYSPREP for Windows Server 2003/R2 and Windows XP, please use one of these links:

Download details: System Preparation tool for Windows Server 2003 Service Pack 2 Deployment
http://www.microsoft.com/downloads/details.aspx?FamilyID=93f20bb1-97aa-4356-8b43-9584b7e72556&displaylang=en

Download details: System Preparation tool for Windows Server 2003 Service Pack 2 Deployment (x64)
http://www.microsoft.com/downloads/details.aspx?familyid=C2684C95-6864-4091-BC9A-52AEC5491AF7&displaylang=en

Download details: Windows XP Service Pack 3 Deployment Tools
http://www.microsoft.com/downloads/details.aspx?familyid=673A1019-8E3E-4BE0-AC31-70DD21B5AFA7&displaylang=en

Note that in Windows Server 2008/R2, Windows Vista/7 – the SYSPREP tool is already included in the operating system, therefore there’s no need to download it.

To create the proper answer file under Windows Server 2003/R2 and Windows XP, you need to either manually edit an existing SYSPREP.INF file, or create one for your needs. To create a SYSPREP.INF answer file for Windows Server 2003/R2 and Windows XP you can use the SETUPMGR.EXE tool found inside the Deployment Tools. Use the above links to get the proper version for your needs.

To create the proper answer file under Windows Server 2008/R2, Windows Vista/7, you need to either manually edit an existing answer file, or create one for your needs.  . To create an answer file for Windows Server 2008/R2, Windows Vista/7, you must use the tools available in the Windows Automated Installation Kit (AIK).

Download details: Windows Automated Installation Kit (AIK)
http://www.microsoft.com/downloads/details.aspx?FamilyID=C7D4BC6D-15F3-4284-9123-679830D629F2&displaylang=en

Installing the ObserveIT Agent

The ObserveIT Agent must be installed on all Windows systems which require monitoring. The Agent can be installed silently via software distribution applications like Microsoft System Management Server or interactively via the console.

Minimum system requirements for the Agent installation are:

·         Microsoft Windows Server 2000/2003/2003 R2/2008, Windows 2000 Pro, Windows XP Pro, Windows Vista (we recommend to always use the latest Service Pack for your operating system).

·         .NET Framework (version 1.1 is the minimum required)

·         1 GHz or faster Intel or AMD processor

·         512 MB RAM or more

·         At least 10 MB of free hard disk space.

·         10/100 Ethernet adapter (Gigabit recommended)

Looking at these requirements, and assuming you’ll be using Windows XP/Vista/7, make sure that your virtual machine has sufficient memory, and that you have .NET Framework installed, which can be done by using Windows Update (or WSUS).

The simplest way to install the Agent is to run the Setup.exe file in the ObserveITAgent subdirectory created when you extracted the installation files. However, since we will be installing the Agent in a manner that will NOT register the Agent in the ObserveIT Application server, you MUST run the Agent installation from a command line by using the MSIEXEC command with the proper installation switches and installation parameters.

To install the Agent, open a command prompt window and navigate to the ObserveITAgent setup directory.

Use the installation command based upon this example:

msiexec /i "ObserveIT.ClientSetup.msi" /quiet /norestart SERVERURL="offline~http://servername:4884/ObserveITApplicationServer" /leo "C:\ObserveIT_Agent_setup.txt" SRVPOLTMPL="00000000-0000-0000-0000-000000000000" PWD="" NoRunOnInstall="1"

• SERVERURL (mandatory) - Directs it to communicate with the specified Application Server. You can also specify the port number. For example:

SERVERURL=”http://srv1:4884/ObserveITApplicationServer”

You can use a hostname, an FQDN, or an IP address.

Use the offline~ parameter at the beginning of the URL in order to direct the Agent not to register itself on the ObserveIT Application Server during the installation. This parameter should be used with the NoRunOnInstall="1" parameter appearing later in this section.

• SRVPOLTMPL (optional) - Server Policies Template to inherit policy-based configuration from upon installation. The default is "00000000-0000-0000-0000-000000000000", and it will point the Agent to the Default Configuration Policy. For example:

SRVPOLTMPL="00000000-0000-0000-0000-000000000000"

• NoRunOnInstall (optional) – Directs the Agent not to run after the installation was completed. Note that this parameter will NOT prevent the Agent from running upon the next logon of any user to that system. This parameter should be used with the offline~ parameter appearing previously in this section. For example:

NoRunOnInstall="1"

After running the above command, the Agent will be installed on the system, but it will not auto start and will not self-register on the ObserveIT Application Server.

Preparing the system for cloning

Prior to cloning the virtual machine there are several steps that you must accomplish. For example, some of the preparation tasks should include:

Note that unlike cloning physical machines, since we will be cloning virtual machines, there is not hardware abstraction layer that we need to worry about, no mass storage devices, and no other devices that need to be detected and installed.

•  Log on to the computer as an administrator.

• Install and customize applications, such as Microsoft Office, Internet Explorer favorite items, and so on.

• Customize the Default User profile.

• Update Windows and other software components.

• Clean temporary files.

• Defragment the disk, and compact the VHD file.

After performing the initial setup steps on a single system, you need to run the SYSPREP utility to prepare the sample computer for cloning.

As stated above, there is a major difference between cloning systems running Windows Server 2003/XP and those running Windows Server 2008/Vista/7.

Here are some links that will help you get started:

How to Prepare Images for Disk Duplication with SYSPREP
http://technet.microsoft.com/en-us/library/bb457067.aspx

How to use the SYSPREP tool to automate successful deployment of Windows XP
http://support.microsoft.com/kb/302577

Create the SYSPREP.inf answer file for Windows Server 2003/XP

The SYSPREP.inf answer file is a text file that scripts the answers for a series of graphical user interface (GUI) dialog boxes. To create a SYSPREP.inf answer file that is used by the SYSPREP tool, you can use a text editor or you can use the Setup Manager tool that is included on the Windows XP CD and is also included with the Microsoft Windows XP Resource Kit. The answer file must be renamed to SYSPREP.inf, and must reside in the SYSPREP folder in the root of the drive where Windows XP is installed, or these files can reside on a floppy disk. If the SYSPREP folder is named differently, the Setup program ignores it. There is not a parameter for specifying the Mini-Setup Wizard answer file.

After preparing the answer file, run the SYSPREP tool from the C:\SYSPREP folder:

Select the “Use Mini Setup” and then click on “Reseal”:

Computer will shut down. At that  moment, if it’s a physical computer – take out the hard drive and use any cloning mechanism that you may have (i.e. Ghost etc.). If it’s a virtual machine, either use existing virtualization tools such as System Center Virtual Machine Manager (SCVMM), or simply copy the VHD file. When using virtual machines, you will need to create the settings for an X number of cloned virtual machines, and then simply connect them to the copied VHD files.

After starting up each cloned machine, if the answer file has been properly created, you will need to enter the computer name and the entire process will automatically run.

How to use the Sysprep tool to automate successful deployment of Windows XP
http://support.microsoft.com/kb/302577

Create the Sysprep.inf answer file for Windows Server 2008/Vista/7

Unlike previous versions, the unattended Windows Setup answer file in Windows Server 2008/Vista/7, is an XML file typically called Unattend.xml. This is the answer file for Windows Setup that is created by using Windows System Image Manager (Windows SIM). The answer file enables the configuration of default Windows settings, as well as the addition of drivers, software updates, and other applications. The answer file enables OEMs and corporations to customize Windows Setup tasks, for example, specifying disk configuration, changing the default values for Internet Explorer, and installing additional drivers.

After preparing the answer file, run the SYSPREP tool from the C:\Windows\System32\sysprep folder:

Select the “Shutdown” and then click on “OK”:

Computer will shut down. At that  moment, if it’s a physical computer – take out the hard drive and use any cloning mechanism that you may have (i.e. Ghost etc.). If it’s a virtual machine, either use existing virtualization tools such as System Center Virtual Machine Manager (SCVMM), or simply copy the VHD file. When using virtual machines, you will need to create the settings for an X number of cloned virtual machines, and then simply connect them to the copied VHD files.

After starting up each cloned machine, even if no answer file has been created, you will be prompted to configure the computer name and some other settings. Of course, creating an answer file will greatly ease this process, and the entire process will automatically run.

how can I SYSPREP Windows Vista?
http://www.windows-noob.com/forums/index.php?/topic/195-how-can-i-sysprep-windows-vista/

Download details: Windows AIK User's Guide and Unattended Setup Reference (Documentation Update 1)
http://www.microsoft.com/downloads/details.aspx?familyid=993c567d-f12c-4676-917f-05d9de73ada4&displaylang=en

Download details: Windows AIK for Windows 7 documentation (October 2009 update)
http://www.microsoft.com/downloads/details.aspx?familyid=F1BAE135-4190-4D7C-B193-19123141EDAA&displaylang=en