WinINSTALL 8.7 Desktop Management Suite and Desktop ...docs.attachmate.com/wininstall/8.70.0400/enu/dms-das/DMS...Such a setup would also require a PXE server at each site. Client

. . .

. .

WinINSTALL 8.7Desktop Management Suite and Desktop

Availability Suite

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installation Guide

. . .

. .

Disclaimer

The information contained in this publication is subject to change without notice. Attachmate Corporation makes no warranty of any kind with regard to this manual, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose. Attachmate Corporation shall not be liable for errors contained herein or for incidental or consequential damages in connection with the furnishing, performance, or use of this manual.

Copyright

© Copyright 1991-2006 by Attachmate Corporation. All Rights Reserved.Migration Engine © Copyright 1998-2006 by Tranxition Corporation. All Rights Reserved.

. . .

. .

September, 2006 Installation Guide 3

TABLE OF CONTENTS

Chapter 1: Installation Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5WinINSTALL Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

Hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5Display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

WinINSTALL Share . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6Hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

WinINSTALL Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Client Workstations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7Hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

WinINSTALL Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8Hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Reference Machine (clean machine on which packages are discovered) . . . . . . . . . . . . . . . . . . . 9Hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

PXE Client Reset Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10Basic PXE Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10WinINSTALL PXE Client Reset Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

WinINSTALL Administrator Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Chapter 2: Installing the Console and Share . . . . . . . . . . . . . . . . . . . . . . . . . . .13Installation Steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13Install the WinINSTALL Console and Share . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14Install Additional WinINSTALL Consoles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18Install Additional WinINSTALL Shares . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18Install MSDE 2000 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

4 WinINSTALL Desktop Management Suite and Desktop Availability Suite

Chapter 3: Setting up the WinINSTALL Database . . . . . . . . . . . . . . . . . . . . . . .21Centralized vs. Decentralized Database Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21Supported Database Platforms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

Microsoft® SQL Server 2000 Desktop Engine (MSDE 2000) . . . . . . . . . . . . . . . . . . . . 22Microsoft® SQL Server 2000 or 2005 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23Oracle® 9i or later . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

WinINSTALL Database Schemas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24How to Set up the WinINSTALL Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

Preliminary Step (MSDE 2000 Only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25How to Use the Database Setup Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25Configure the Database Manually . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26How to Configure an Oracle database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

Chapter 4: Configuring the Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .29Configuration Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29Preliminary Steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

Specify a WinINSTALL Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30Specify a Primary WinINSTALL Share for the Console . . . . . . . . . . . . . . . . . . . . . . . . . 30Set Other Console Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

Add Machines in Your Network to the Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31Add Machines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31Assign Roles to Machines – Server or Workstation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32Specify a Share for each Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32Assign a Server for each Workstation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

Deploy the WinINSTALL Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33Deploying the Agent When Adding the Machine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33Deploying the Agent from a Menu Selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34Deploying the Agent from a Secure Manual Deployment (SMD) File . . . . . . . . . . . . . . 34


. . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .INSTALLATION REQUIREMENTS 1

he minimum installation requirements for each of the WinINSTALL components is detailed below, along with a short explanation of what each component is and what role it plays in the WinINSTALL environment.

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . W I N I N S T A L L C O N S O L EThe WinINSTALL Console is the graphical user interface (GUI) used to administer the entire WinINSTALL environment. Each machine on which you install a Console must meet the following requirements:

HARDWARE• 85 MB of disk space (for the local components of WinINSTALL).

SOFTWARE• Operating System - Windows 2000, SP4/Windows XP/2003.

• Microsoft Windows Installer 2.0 or greater.

WinINSTALL checks for the presence of this program during setup and will automatically install or upgrade it as required.

• Database Client Software.

If you are using Oracle® as your database, you must first manually install the client software in order to have database connectivity. Database connectivity is required for you to run the Console or use the Database Creation Wizard to initialize your WinINSTALL database.

The Microsoft SQL Server client software must be installed in order for you to use the Database Creation Wizard to create and initialize the WinINSTALL database. Except for the web-based installation, all other installation methods offer the option of installing the client software.

DISPLAY

R E S O L U T I O N• 1024 X 768 or higher.

T

I N S T A L L A T I O N R E Q U I R E M E N T SWinINSTALL Share


1

C O L O R• 16-bit or better.

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . W I N I N S T A L L S H A R EThe WinINSTALL share serves multiple purposes. It holds the configuration files, executables, help files, reports, software packages, client reset templates, and other files used by the Console. It is used to store data that is moved by WinINSTALL agents between workstations and the database. Each machine on which you install a share must meet the following requirements:

HARDWARE• 235 MB of disk space (for the network components of WinINSTALL).

• Adequate disk space to store application packages and optional client reset templates.

SOFTWARE• Operating System.

The WinINSTALL share is a shared hierarchy of folders and files. As a result, the WinINSTALL share machine can be running any operating system.

The machine running setup must be running Windows 2000 or greater. The WinINSTALL share setup allows installing the share to a network drive.

• Windows Installer

Setup requires Microsoft Windows Installer 2.0 or greater. WinINSTALL checks for the presence of this program during setup and will automatically install or upgrade it as required.

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . W I N I N S T A L L S E R V E R A WinINSTALL server is a machine with full WinINSTALL agent functionality deployed. A server performs server agent functions both for itself and for the workstations that are assigned to it, and it also performs workstation agent functions for itself as a local machine in the WinINSTALL environment. Each machine with the role of WinINSTALL server must meet the following requirements:

. . .

. .I N S T A L L A T I O N R E Q U I R E M E N T SClient Workstations



Recommended: Windows Server 2000/2003.

Alternate: Windows NT 4.0 with SP 6a and IE5.5 or greater installed.


This file is included with Windows Server 2000/2003, but must be installed separately with Windows NT 4.0. WinINSTALL checks for the presence of this program during setup and will automatically install or upgrade it as required.

Deploying the WinINSTALL Agent will install or upgrade to Windows Installer 2.0 as necessary.

• Microsoft Data Access Components 2.71

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C L I E N T W O R K S T A T I O N SA WinINSTALL workstation is a machine with the WinINSTALL workstation agent deployed. A workstation performs workstation agent functions for itself only. Each machine with the role of WinINSTALL workstation must meet the following requirements:

HARDWARE• As required for applications being installed.

• 15 MB of disk space (for local components of WinINSTALL).

NOTE: WinINSTALL does not require a dedicated server. WinINSTALL servers may also be operating as file servers, print servers, application servers, database servers, etc.

WARNING: If an earlier version of MDAC is already installed on the server at the time when the WinINSTALL server agent is deployed, the MDAC upgrade is liable to cause the server to reboot.

I N S T A L L A T I O N R E Q U I R E M E N T SWinINSTALL Database


1


Windows XP/2000/98 with IE 4.0/95 with IE 4.0 and WinSock 2/NT 4.0 with SP 6a and IE5.5 or greater installed.


This program is included with Windows Server 2000/2003, but must be installed separately with Windows NT 4.0.

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . W I N I N S T A L L D A T A B A S EThe WinINSTALL database holds all of the information used internally by WinINSTALL and displayed in the console.

HARDWARE• Adequate disk space for database.

NOTE: PXE client machines must have at least the Microsoft-recommended minimum amount of RAM for the operating system being installed (Windows 2000: 64MB, Windows XP and 2003: 128MB).

NOTE: Some non-English versions of Windows 95 and Windows NT 4.0 contain no native support for encryption/decryption. Because WinINSTALL uses encryption for agent deployment and communication, such systems require the addition of an update which includes CryptoAPI support, such as that provided in Internet Explorer v6.

NOTE: WinINSTALL does not require a dedicated database server. The WinINSTALL database may be located on a machine functioning in other capacities, including as a database server for other applications.

. . .

. .I N S T A L L A T I O N R E Q U I R E M E N T SReference Machine (clean machine on which packages are discovered)


SOFTWARE• Software for any of the following databases:

Microsoft® SQL Server 2000 Desktop Engine (MSDE 2000).

Microsoft® SQL Server 2000.

Microsoft® SQL Server 2005.

Oracle® 9i or later.

R E F E R E N C E M A C H I N E ( C L E A N M A C H I N E O N

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . W H I C H P A C K A G E S A R E D I S C O V E R E D )A reference machine is a special machine that is used solely for the purpose of building packages and the creation of transforms. No part of WinINSTALL is installed on a reference machine.

Technically, a reference machine should be a clean machine, with only the operating system and any necessary service packs installed. Because a reference machine does not need to be large and expensive, some administrators have two or more. In this way, they can create a package on one machine while returning a previously-used machine to its clean state. This practice reduces downtime - and the temptation to cut corners by using a dirty machine.

Today, a number of commercial products are available to simplify the process of returning a reference machine to its clean state. For instance, some products allow you to create a virtual machine and save it in a clean state, build a package on it, and then discard all changes and return to the original clean state during reboot. These virtual machines save a great deal of time because you install the operating system only once for each operating system used in your network. This convenience is particularly useful because each package must be created on a machine with the same operating system as the network client on which it will be installed.

HARDWARE• As required for applications being packaged.


Windows 2003/XP/2000/98 with IE 4.0/95 with IE 4.0/NT 4.0 with SP 6a and IE5.5 or greater installed.


I N S T A L L A T I O N R E Q U I R E M E N T SPXE Client Reset Requirements


1

This program is required to build Windows Installer packages. It is included with Windows 2003/XP/2000, but it must be installed separately on other operating systems. When Windows 9x or Windows NT 4.0 is installed on the reference machine, you cannot create a Windows Installer package directly with the Discover Wizard. You must first create a WinINSTALL package and then convert it to a Windows Installer package on a machine running Windows 2000 or later.

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . P X E C L I E N T R E S E T R E Q U I R E M E N T S

BASIC PXE REQUIREMENTSThere are several requirements for a client machine to be PXE-bootable. The machine’s BIOS must support “Network” as a boot device. Also the machine’s NIC must support the PXE standard (first introduced in the PC98 specification). Optionally the NIC can contain the PXE boot ROM. NICs that contain the ROM are often called “managed NICs” or “NICs for managed PCs.” If the NIC supports PXE but does not contain the ROM image, a network boot is only possible by booting the system with a floppy disk containing the ROM image. Almost all PCs sold after 1998 support “Network” boot in the BIOS and most NICs support PXE.

There are two distinct versions of PXE; DHCP-based (Dynamic Host Configuration Protocol) and RPL (Remote Program Load). DHCP-based is used across most network environments, whereas RPL is most often used in NetWare environments. PXE-capable NICs support either DHCP-based, RPL-based, or both. A PXE-capable NIC that supports only RPL will not work in a Windows environment.

The fact that PXE requires DHCP imposes additional restrictions on the network setup. First, use of PXE is not possible in a static IP environment. Second, since DHCP does not typically cross subnets, each subnet containing a DHCP server must also contain a PXE server. For example, a company with offices in LA and NYC would typically have a DHCP server at each site. Such a setup would also require a PXE server at each site. Client machines in LA could not connect to a PXE server in NYC.

The DHCP server must also support DHCP options. DHCP options are identified by number, and PXE requires DHCP options 66 and 67. DHCP options are supported by most DHCP servers, including the DHCP server included with Windows NT/2000/2003 Servers. Examples of DHCP servers that may not support DHCP options include small DHCP-capable routers and firewalls from companies like LinkSys, NetGear, D-Link, and SonicWall. Since these network appliances do not support DHCP options, they cannot be used in a PXE environment.

. . .

. .I N S T A L L A T I O N R E Q U I R E M E N T SWinINSTALL Administrator Requirements


WININSTALL PXE CLIENT RESET REQUIREMENTSWinINSTALL PXE Client Reset requires the following components, over and above those for the rest of the WinINSTALL product:

• DHCP Server

The network must be configured to use DHCP, and therefore it must include a DHCP server on or for each subnet where WinINSTALL PXE Client Reset will be configured. In addition, to support PXE, each DHCP server must have options 66 and 67 enabled. WinINSTALL can automatically set these options on Windows servers which are providing DHCP services. Other DHCP servers will need to have these options enabled manually.

• Windows Install Set

Operating system installation files must be provided (via the WinINSTALL PXE Client Reset Template Wizard, below) for installation on client machines. Windows 2000, Windows XP, and Windows 2003 can be installed in this fashion.

• PXE-Capable Client

Every client machine must be PXE-capable. This means the BIOS must support Network as a boot device and the NIC must be DHCP-PXE-capable.

W I N I N S T A L L A D M I N I S T R A T O R

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . R E Q U I R E M E N T SAn effective WinINSTALL administrator should have an in-depth understanding of the organization’s network and security policies, and the necessary security rights to access appropriate network resources. In addition, it is helpful to have the following qualifications:

• A solid understanding of all the Windows platforms in use on the network.

WARNING: Windows 2000, XP, and 2003 can be installed through PXE. Windows 95/98/ME and NT cannot.

NOTE: PXE client machines must have at least the Microsoft-recommended minimum amount of RAM for the operating system being installed (Windows 2000: 64MB, Windows XP and 2003: 128MB).

I N S T A L L A T I O N R E Q U I R E M E N T SWinINSTALL Administrator Requirements


1

• A working knowledge of the Windows registry.

An understanding of the Windows registry can be invaluable when building packages. After WinINSTALL has Discovered an application, you may need to modify a registry entry to fit your network needs. You should be familiar with the use of REGEDIT.EXE and REGEDT32.EXE, and the differences between these two registry editors. These two utilities can be found in the \Winnt and \Winnt\System32 directories, respectively.

• An understanding of the Microsoft Windows Installer and MSI technology.

Knowledge of Windows Installer technology and terminology is helpful when you are working with MSI files. A solid understanding of the MSI table relationships and MSI properties is recommended if you will be building and using Windows Installer packages.

• Familiarity with scripting languages and writing scripts.

For certain complex situations, some users prefer to use scripts in their packages. This is usually unnecessary, but in the event that it is needed or desired, any scripting language supported by Windows Scripting Host can be used in WinINSTALL packages. Scripting in WinINSTALL packages is accomplished through external processes (see the WinINSTALL Administrators Guide for more on scripting in WinINSTALL packages), while scripting in Windows Installer packages is accomplished through custom actions.


. . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .INSTALLING THE CONSOLE AND SHARE 2

efore initiating installation, you need to know which database management system you will use for the WinINSTALL database and where the Console and share will be located. WinINSTALL supports three database management systems:

Microsoft® SQL Server 2000 Desktop Engine (MSDE 2000), Microsoft® SQL Server 2000, and Oracle® 9i or later. WinINSTALL provides MSDE 2000 with the product. Please see the next chapter for information on

When you launch the WinINSTALL setup, two checks are made for the existence of specific software before the actual setup process begins.

• First, the MSI file that installs WinINSTALL verifies that version 2.0 or later of the Windows Installer is installed on the Console machine. If necessary, the Windows Installer is installed or upgraded automatically. Once the installation or upgrade is complete, you must click OK in order to continue. If an install or upgrade of the Windows Installer is not needed, the setup program proceeds automatically to the second software check.

• Second, the setup program checks for the presence of an existing installation of WinINSTALL on the Console machine. If setup detects an existing WinINSTALL installation, it aborts the setup process and prompts you to remove the earlier version. Use Add/Remove Programs on the Control Panel to uninstall the existing version of WinINSTALL and then restart the WinINSTALL setup program. If no prior installation of WinINSTALL is detected, setup proceeds automatically.

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . I N S T A L L A T I O N S T E P SThe following steps will result in a successful WinINSTALL installation:

1 If a prior version of WinINSTALL is installed, it must first be removed.

A prior version of WinINSTALL must be uninstalled before you proceed with the installation of the current version of WinINSTALL. If you attempt to install a newer version and setup detects an existing WinINSTALL installation, it will abort the current installation process and prompt you to remove the earlier version. Use Add/Remove Programs on the Control Panel to uninstall the existing version of WinINSTALL and then restart the WinINSTALL setup program.

2 Determine what database management system you will use for the central WinINSTALL database.

B

I N S T A L L I N G T H E C O N S O L E A N D S H A R EInstall the WinINSTALL Console and Share


2

Setup will offer to automatically install MSDE 2000, Microsoft’s simplified, desktop version of SQL Server 2000. MSDE 2000 is a simple, transparent solution requiring little or no attention, but it does have some limitations. If you are evaluating the product or your organization has a small network with no other supported database installed, letting setup create an MSDE 2000 database is simple and expedient. Otherwise, you can choose to use an existing Microsoft® SQL Server 2000 or Oracle® database, if your environment warrants this more robust facility.

Full details on choosing and setting up the database appear in the Setting up the WinINSTALL Database chapter.

3 Decide where the primary WinINSTALL Console and share will be located.

4 Install the primary WinINSTALL Console and share.

5 If desired, install one or more additional WinINSTALL shares.

6 If desired, install one or more additional WinINSTALL Consoles

Once you have finished these steps, you will have installed WinINSTALL. If you allowed setup to launch the Database Setup Wizard (to install and/or configure any of the supported database management systems), you are now ready to open the WinINSTALL Console and configure your WinINSTALL environment. When you open the console for the first time, the Default Settings Wizard helps you set the WinINSTALL share and database that will be used by the WinINSTALL Console. The installation portion of WinINSTALL is described in detail in the following sections of this chapter. The following chapters provide full details on database setup and basic WinINSTALL configuration.

I N S T A L L T H E W I N I N S T A L L C O N S O L E A N D

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . S H A R E1 Insert the WinINSTALL installation CD into the CD-ROM of the Console machine.

Installation should begin automatically. If it does not begin, right-click the CD-ROM drive letter and select Autoplay from the popup context menu. On the WinINSTALL splash screen, click Run Setup to begin setup. Various messages display to keep you informed about what is happening.

Setup checks the version of the Windows Installer on the Console machine and upgrades it if necessary. Setup then checks for the existence of a prior installation of WinINSTALL and aborts the installation if one is found. It prompts you to uninstall the earlier version and requires that you click OK to continue. If it does not find a prior installation, setup continues. Please be patient as these activities may take a few minutes.

. . .

. .I N S T A L L I N G T H E C O N S O L E A N D S H A R EInstall the WinINSTALL Console and Share


2 The Welcome to the WinINSTALL Setup Wizard panel displays. The setup wizard begins extracting files and preparing for installation. Please be patient as this may take a few minutes. When the button becomes active, click Next to continue.

3 The End-User License Agreement panel displays. Check the radio button that accepts the terms of the license agreement and click Next to continue.

4 The Customer Information panel displays. Verify that the user name and organization are correct – making changes if necessary – and then specify the type of installation you are performing:

If you are installing an evaluation copy of the software, you will not be required to enter a license key, but the software will expire after 30 days. Click the Details button to see an explanation of the features available in each product.

If you have purchased a licensed copy of the software, select the Licensed Product radio button and enter the license key provided with your copy of WinINSTALL.

Click Next to continue.

5 The License Verification panel displays, confirming the type of license associated with the choice you made on the previous panel. If the license type is incorrect, click the Back button to return to the previous dialog and verify that you entered the correct license key or selected the appropriate radio button. If the license type is correct, click Next to continue.

6 If you are installing an evaluation copy of the product, the Registration Information panel displays. Enter your e-mail address and telephone number. (This information is solely for internal use. Click the Privacy Policy button to see how Attachmate Corporation uses and protects the information you provide.) Check the Sign me up … checkbox to receive a free copy of WinINSTALL News, an e-newsletter that provides product information, updates, special offers, and more. Click Next to continue.

7 The Selecting WinINSTALL Share panel displays. WinINSTALL requires that you install at least one share, which holds configuration files, WinINSTALL utilities, client reset files, and packages. Specify that you want setup to install a WinINSTALL share, where it should be located and what you want to name the share.

To install a WinINSTALL share:

Check the Install the WinINSTALL Share checkbox (checked by default), accept or browse for the share location (the default share location is c:\WinINSTALL\), and accept or change the share name. (The default share name is WinINSTALL).


8 The Selecting WinINSTALL Console panel appears. Specify that you want setup to install a WinINSTALL console and where it should be located. WinINSTALL requires that you install at least one console, which provides the user interface for WinINSTALL. To install a WinINSTALL console, check the Install the WinINSTALL Console checkbox

I N S T A L L I N G T H E C O N S O L E A N D S H A R EInstall the WinINSTALL Console and Share


2

(default) and accept or browse for the console location. (The default location is c:\Program Files\OnDemand\WinINSTALL\).


9 The Selecting Microsoft SQL Server 2000 Desktop Engine (MSDE 2000) panel appears, offering to automatically install MSDE 2000 for you and allowing you to view or set advanced MSDE 2000 properties.

If you do not want setup to install MSDE 2000, select the Do Not Install MSDE 2000 radio button.

If you do want setup to install MSDE 2000, select the Install MSDE 2000 radio button and specify whether you want to view or set advanced MSDE 2000 properties by clicking the Show advanced MSDE properties checkbox at the bottom of the panel.


10 If you checked the Show advanced MSDE properties checkbox, the Microsoft SQL Server 2000 Desktop Engine panel allows you to specify whether you want to use Windows integrated security (default) or SQL security and whether you want to enable network access. You can also set the data directory and provide the instance name and collation name. Click Next to continue.

11 If you chose not to have setup install MSDE 2000 (or if you chose to install MSDE 2000 and checked the Show advanced MSDE properties checkbox), the Installing the WinINSTALL Database panel appears.

At this point, you can specify whether or not to have the WinINSTALL Database Setup Wizard run at the end of setup. This wizard will create and initialize a SQL Server or MSDE 2000 database or initialize an existing Oracle 9i (or later) database. (For Oracle, you must have already created the database, which the wizard will then initialize with all of the necessary WinINSTALL tables.)

The appropriate database software (sqlplus or osql) must be available on the machine where you are running setup, or else the wizard will be unable to create the tables.


TIP: The WinINSTALL agents are always installed to [ProgramFilesFolder]OnDemand\WinINSTALL\ (usually C:\Program Files\OnDemand\WinINSTALL\). During setup of the console, you can change the installation directory for the console to something other than the default, which is also [ProgramFilesFolder]OnDemand\WinINSTALL\. We strongly recommend that you not redirect the console install directory because it will make later maintenance of WinINSTALL simpler if both the agents and console are in the same directory.

. . .

. .I N S T A L L I N G T H E C O N S O L E A N D S H A R EInstall the WinINSTALL Console and Share


12 The Ready to Install dialog displays. It lists the WinINSTALL components you have chosen to install – share and/or console and/or MSDE database. Click Install to begin the installation.

13 The Installing WinINSTALL panel displays, with a status bar indicating the progress of the installation. Please be patient.

14 If you chose to have the Database Setup Wizard run during setup, the Database Type panel will display at the end of setup (note that setup will likely run for a few minutes before reaching this point). If you are using a Microsoft SQL Server or MSDE 2000 database, select the Microsoft SQL Server radio button; otherwise, select the Oracle radio button. Click Next to continue.

15 If you chose to have the Database Setup Wizard run during setup, the Database Server Options panel will appear next. If you are creating and initializing a Microsoft SQL Server or MSDE 2000 database, you must specify the database server and the name of the database that the wizard will initialize with WinINSTALL tables. If you are initializing an Oracle 9i database, you must specify the name of the database service. For any of these databases, you must select the appropriate radio button for the desired access method for the database: Windows Authentication or Provide Credentials. If you choose the latter option, you must supply a username and password enabling access to the database.


16 If you chose to have the Database Setup Wizard run during setup, the Database Creation panel will finally display. Click Create and the wizard will attempt to create the database.

The following issues could possibly cause this action to fail:

• The specified database does not exist.

• The specified database exists but is already initialized with tables. (In some cases, this condition may give you error messages, but still work.)

• The required database software does not exist on the setup machine.

• The credentials supplied do not have sufficient rights.

Click Next to return to setup.

17 When installation is complete, the Completing the WinINSTALL Share Setup Wizard panel will appear. To view the ReadMe file, a brief listing of helpful and important information, check the View ReadMe checkbox. (We recommend that you look at this file, at least the first time that you use the setup program.) When you are ready to proceed, click Finish.

18 If setup had to install or upgrade the Windows Installer on the Console machine, it will now ask you to reboot. If you intend to begin using any part of WinINSTALL that

I N S T A L L I N G T H E C O N S O L E A N D S H A R EInstall Additional WinINSTALL Consoles


2

involves Windows Installer technology, you should reboot the Console machine at this time. Otherwise, you can wait until later to reboot.

Installation is now complete. You can open the WinINSTALL Console, or, if desired or required, you can install additional WinINSTALL shares and consoles before proceeding. In addition, if you did not choose to have setup install MSDE 2000 or create a WinINSTALL database, you can do that before proceeding as well.

The first time that you open a WinINSTALL Console, the Default Settings Wizard is invoked. This wizard lets you review and/or reset the WinINSTALL share and database information for that console.

I N S T A L L A D D I T I O N A L W I N I N S T A L L

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C O N S O L E SIn some WinINSTALL environments, you may want to install additional Consoles. You execute the installation of additional Consoles from each of the machines where you want to run the Console. From each of these machines, navigate to the \bin directory of the WinINSTALL share and run WICONSOLE.msi to install the Console.

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . I N S T A L L A D D I T I O N A L W I N I N S T A L L S H A R E SIn some WinINSTALL environments, you may want to install additional WinINSTALL shares. You can do this in one of two ways:

1 Copy an existing WinINSTALL share to a new location. (the share installation is an administrative installation.)

2 Use the WinINSTALL setup CD or downloaded install and follow the WinINSTALL Share installation instructions provided above, making sure to do the following:

• On the Selecting WinINSTALL Share panel, specify that you want setup to install a WinINSTALL share and indicate where it should be located and what you want to name it:

Check the Install the WinINSTALL Share checkbox (default).

Accept or browse for the share location. (The default share location that is provided for you - c:\WinINSTALL\ - is generally appropriate if you are running setup on the machine where you want to install the share).

Accept or change the share name. (The default share name is WinINSTALL).

• On the Selecting Microsoft SQL Server 2000 Desktop Engine (MSDE 2000) panel, specify that you do not want setup to install MSDE 2000 for you.

. . .

. .I N S T A L L I N G T H E C O N S O L E A N D S H A R EInstall MSDE 2000


• On the Installing the WinINSTALL Database panel, specify that you do not want the WinINSTALL Database Setup Wizard to run during setup.

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . I N S T A L L M S D E 2 0 0 0If you did not choose to have MSDE 2000 installed during setup, you can still have WinINSTALL install it later. For instructions on how to do this, refer to the Setting up the WinINSTALL Database chapter.

I N S T A L L I N G T H E C O N S O L E A N D S H A R EInstall MSDE 2000


2


. . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .SETTING UP THE WININSTALL DATABASE 3

inINSTALL stores all of the information needed for total desktop management in one central data repository. Decision-makers at all levels can view the appropriate consolidated information required for making informed decisions,

and network administrators can manage and propagate configuration information from one central location throughout the enterprise. The key to the power of WinINSTALL is this central database, which integrates for the entire organization all information used for asset management, inventory, package management, conflict assessment, software distribution, client reset, replication, console logging, personality transfer and WinINSTALL agent activity.

For organizations with multiple discrete WinINSTALL environments, WinINSTALL makes it possible to gather the information from these separate distributed databases into one enterprise-level data repository that can be used for consolidated reporting and data mining.

C E N T R A L I Z E D V S . D E C E N T R A L I Z E D

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D A T A B A S E M O D E LWinINSTALL is typically installed in a centralized configuration, where all WinINSTALL servers report to a single database. In this configuration, each organizational unit might maintain its own WinINSTALL share and server, but each server reports to the same centralized database. This database can then serve as the center for both operational control and enterprise-wide reporting of desktop management activities.

An alternate to the centralized configuration is a distributed WinINSTALL environment, where each separate organizational unit not only maintains its own WinINSTALL share and server, but it also manages its own local database. This configuration essentially provides multiple, discrete WinINSTALL installations. The primary drawback with a decentralized configuration is that the data available for reporting in a given location is limited to the data from that location. WinINSTALL provides a rollup capability to enable the consolidation of data to a central database for enterprise-level reporting.

WARNING: Multiple separate databases which consolidate their data to a centralized database are useful for centralized reporting and data mining. But they do not permit centralized control of WinINSTALL desktop management functions. For centralized control, use a single, centralized database.

W

S E T T I N G U P T H E W I N I N S TA L L D A T A B A S ESupported Database Platforms


3

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . S U P P O R T E D D A T A B A S E P L A T F O R M SWinINSTALL supports the three database management systems (DBMS) listed below. For each DBMS, the listing includes a profile of recommended organizational users, a description of any database restrictions, and a list of prerequisites (database-related requirements that must be met before installing WinINSTALL). Each listing also includes the setup options needed for each DBMS and the list of actions that the Database Setup Wizard will perform for you during setup. If you choose, you can create and populate the WinINSTALL database manually, but the Database Setup Wizard makes the process simple and error-free. A description of this wizard and an explanation of how to create the database manually are provided later in this chapter.

MICROSOFT® SQL SERVER 2000 DESKTOP ENGINE (MSDE 2000)

R E C O M M E N D E D E N V I R O N M E N T S :• Small locations with less than 100 computers.

• Organizations evaluating WinINSTALL.

D A T A B A S E R E S T R I C T I O N S :• 2-GB database size limit.

• 5-session concurrency limit.

P R E R E Q U I S I T E S :• None (MSDE 2000 with sp 3a is included with WinINSTALL and can be installed

automatically by setup).

• MDAC 2.6 or greater installed.

R E Q U I R E D S E T U P O P T I O N S :• On the Selecting Microsoft SQL Server 2000 Desktop Engine (MSDE 2000) panel, select

the Install MSDE 2000 radio button and check the Show advanced … checkbox.

• On the Installing the WinINSTALL Database panel, specify that you want the WinINSTALL Database Setup Wizard to start automatically during setup.

D A T A B A S E S E T U P W I Z A R D A C T I O N S :• Creates an MSDE 2000 WinINSTALL database and populates it with the appropriate

tables.

. . .

. .S E T T I N G U P T H E W I N I N S TA L L D A T A B A S ESupported Database Platforms


MICROSOFT® SQL SERVER 2000 OR 2005

R E C O M M E N D E D E N V I R O N M E N T S :• Larger organizations that need a more robust database engine.

• Organizations that prefer to use a Microsoft database.

D A T A B A S E R E S T R I C T I O N S :• None.

P R E R E Q U I S I T E S :• Licensed copy of Microsoft® SQL Server 2000 or 2005 installed.

• Latest service packs installed.

• MDAC 2.6 or greater installed.

R E Q U I R E D S E T U P O P T I O N S :• On the Selecting Microsoft SQL Server 2000 Desktop Engine (MSDE 2000) panel,

deselect the Install MSDE 2000 radio button.


D A T A B A S E S E T U P W I Z A R D A C T I O N S :• Creates a Microsoft® SQL Server WinINSTALL database and populates it with the

appropriate tables.

ORACLE® 9I OR LATER

R E C O M M E N D E D E N V I R O N M E N T S :• Larger organizations that need a more robust database engine.

• Organizations that prefer to use an Oracle database.

D A T A B A S E R E S T R I C T I O N S :• None.

P R E R E Q U I S I T E S :• Licensed copy of Oracle® server software installed on the database machine.

S E T T I N G U P T H E W I N I N S TA L L D A T A B A S EWinINSTALL Database Schemas


3

• Licensed copy of Oracle® client software installed on the Console machine and on all machines that will have the role of WinINSTALL server.

• An existing WinINSTALL database on the database machine.

R E Q U I R E D S E T U P O P T I O N S :• On the Selecting Microsoft SQL Server 2000 Desktop Engine (MSDE 2000) panel,

deselect the Install MSDE 2000 radio button.


D A T A B A S E S E T U P W I Z A R D A C T I O N S :• Initializes an existing WinINSTALL Oracle 9i or later database with the appropriate

tables.

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . W I N I N S T A L L D A T A B A S E S C H E M A SThe database schemas for Microsoft databases and Oracle databases are slightly different. A complete listing of all tables in the WinINSTALL database is included with the product as a separate file, DBSchema.htm, located in the WinINSTALL share in the \Bin\Help folder and on console machines in the \Program Files\OnDemand\WinINSTALL\Help folder.

This schema information is helpful when using third-party database mining or reporting tools such as Crystal Designer to create custom queries and reports.

In addition, WinINSTALL also includes two .DDL files which can be used to initialize a WinINSTALL database without the Database Setup Wizard. These files, also located in the WININSTALL Share \Bin directory, are named WINSTALL.DB.DDL (Microsoft databases) and WINSTALL.DB_ORC.DDL (Oracle databases).

NOTE: WinINSTALL supports the Oracle Instant Client, as well as the Oracle full-size client.

. . .

. .S E T T I N G U P T H E W I N I N S TA L L D A T A B A S EHow to Set up the WinINSTALL Database


H O W T O S E T U P T H E W I N I N S T A L L

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D A T A B A S EYou can set up the WinINSTALL database in either of two ways: automatically, using the WinINSTALL Database Setup Wizard, or manually. Each method is explained in detail below.

PRELIMINARY STEP (MSDE 2000 ONLY)If you chose to have the WinINSTALL setup install MSDE 2000, verify that the database service has started. Look in the system tray in the lower right hand corner of your computer. If the service is started, you should see a service icon with a green arrow, like this:

If the service icon does not display a green arrow, double-click the icon to display the MSDE SQL Server Service Manager dialog. Click the Start/Continue button to start the database and make sure that the checkbox for Auto-start service when OS starts is checked.

HOW TO USE THE DATABASE SETUP WIZARDThe WinINSTALL Database Setup Wizard either creates and initializes a WinINSTALL database under Microsoft® SQL Server or MSDE 2000 database, or initializes an already-created WinINSTALL database under Oracle 9i.

When you install WinINSTALL, you have the option of running the Database Setup Wizard at the end of setup. If you choose this option, the wizard executes automatically as the final step in setup. Alternatively, after you have installed WinINSTALL, you can invoke the wizard manually, by navigating to the WININSTALL Share \Bin directory and double-clicking WIDBSetup.exe.

1 After the Welcome screen, he Database Type dialog provides a choice of database types. For either a Microsoft SQL Server or MSDE 2000 database, select the MS SQL Server radio button. If you are initializing an Oracle 9i database, select the Oracle radio button.


NOTE: If you are using Oracle for your WinINSTALL database, you must have created the WinINSTALL database before initializing it with the WinINSTALL Database Setup Wizard.

S E T T I N G U P T H E W I N I N S TA L L D A T A B A S EHow to Set up the WinINSTALL Database


3

2 The Database Server Options dialog displays, providing the opportunity to enter connection information.

For a Microsoft database, enter or select the following three items:

• The name of the server on which the database will reside.

• The name of the WinINSTALL database. (You can accept the default database name – WINSTALL8 – or change it.)

• The credentials needed to log on to the database. (You can use Windows authentication or you can provide a database-specific username and password.)

For an Oracle database, enter or select the following two items:

• The name of the Oracle database service.

• The credentials needed to log on to the database. (You can use Windows authentication or you can provide a database-specific username and password.)


3 The Database Collation Option dialog appears. The wizard will present the typical collation option as the default, and the drop-down will be populated with additional valid selections. You can accept the default collation option or select another option from the drop-down. Click Next to continue.

4 The Database Creation dialog displays. Click the Create button and the progress and results of the database and/or table creation process will appear. When the process is complete, click Next to continue.

5 The Completing the WinINSTALL Database Setup Wizard dialog displays. Click Finish to exit.

CONFIGURE THE DATABASE MANUALLYThe easiest way to set up a new database is to use the DB Setup Wizard. However, users who prefer to install the database with a SQL Server or Oracle utility can use one of the two following DDLs:

If you choose not to use the WinINSTALL Database Setup Wizard, the following steps will enable you to manually configure the WinINSTALL database.

H O W T O C O N F I G U R E A M I C R O S O F T D A T A B A S E1 Make sure that the database service is running. For MSDE 2000, the icon in the far right

of the system tray should look like this (the green arrow indicates that the MSDE service is running):

WINSTALL.DB.DDL • for use with SQL Server and MSDE 2000

WINSTALL.DB_ORC.DDL • for use with Oracle 9

. . .

. .S E T T I N G U P T H E W I N I N S TA L L D A T A B A S EHow to Set up the WinINSTALL Database


If the database service is not running, start it.

2 Open a command prompt window and do one of the following:

• If you accepted the defaults during installation, or if you want to use Windows authentication, create the database using the following command. The command line below creates a database called WINSTALL8, but you can change the database name by substituting a different name.

C:\>OSQL –E -Q “create database WINSTALL8”

• If you did not accept the defaults during installation, or if you want to use SQL Server authentication, create the database using the following command. Again, the command line below creates a database called WINSTALL8, but you can change the database name by substituting a different name.

C:\>OSQL -U sa -P <password> -Q “create database WINSTALL8”

In either case, the following lines display:

The CREATE DATABASE process is allocating 0.63 MB on disk 'WINSTALL8'.

The CREATE DATABASE process is allocating 0.49 MB on disk 'WINSTALL8_log'.

3 To create the tables needed by WinINSTALL, use the appropriate one of the following commands (change the database name as needed).

• If you accepted the defaults during installation or are using Windows authentication, create the tables using the following command:

C:\>OSQL -E -d WINSTALL8 -I -i \\server\WIShare\Bin\WINSTALLDB.DDL

• If you did not accept the defaults during installation or are using SQL Server authentication, create the tables using the following command:

C:\>OSQL -U sa -P <p/w> -d WINSTALL8 -I -i \\server\WIShare\Bin\WINSTALLDB.DDL

4 As the tables are created and populated, numbers will appear across the screen from OSQL. When you return to a command prompt, the database has been created.

HOW TO CONFIGURE AN ORACLE DATABASE1 Before you can configure an Oracle database for use with WinINSTALL, the database

itself must have been created and its service name must be available. The service name mappings are found in the file TNSNAMES.ORA in the \Oracle\ora90\network\admin directory.

S E T T I N G U P T H E W I N I N S TA L L D A T A B A S EHow to Set up the WinINSTALL Database


3

2 To initialize the WinINSTALL database, you run the oracle utility SQLPLUS, found in the Oracle \bin directory (e.g. C:\Oracle\ora90\bin) to process the supplied DDL script WINSTALL.DB_ORC.DDL, located in the WinINSTALL Share \bin directory.

Once you have verified that the Oracle database has been created, open a command prompt window to execute sqlplus.exe.

To use SQLPLUS to execute the DDL script, enter this command line:

sqlplus SYSTEM/password@MYDBSERVICENAME @C:\WINSTALL.DB_ORC.DDL

This command line tells sqlplus to login as the user: SYSTEM, with a password of password to the database indicated by MYDBSERVICENAME and to execute the DDL file C:\WINSTALL.DB_ORC.DDL.

If you don't supply a service name after the password, sqlplus will connect to the default (local) database, which may or may not be correct.

NOTE: When creating a Japanese-language Oracle database, the following language specifications are recommended:

Database Character Set: JA16SJIS

National Character Set: AL16UTF16


. . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .CONFIGURING THE ENVIRONMENT 4

fter you have installed WinINSTALL and created a WinINSTALL database, you are ready to configure your WinINSTALL environment. Before you can run the Console, however, you must specify the WinINSTALL share and database that will

be used by the Console. If these items have not been accomplished during setup, then when you attempt to open the Console for the first time, the Default Settings Wizard will step you through these selections and allow you select a few additional console settings. You can always change these selections on the Console Options dialog, but doing so will affect the information that you see in the Console. You access the Console Options dialog by choosing Console Options from the View menu at the top of the screen.

The recommended practice is to use a single WinINSTALL database and not change it. Both the Console and the managed WinINSTALL servers should use this one database. This configuration will ensure that you capture all of the information generated by Console actions and that this captured information displays in the Console and reports.

The Default Settings Wizard automatically supplies the path to the default WinINSTALL share (i.e., the one installed or used during setup). You can accept this default or select an alternate share. The WinINSTALL share provides the configuration files, executable programs, help files, report files and other information needed by WinINSTALL. Changing the share will affect such things as configuration settings that you have made and new reports that you have added. The Default Settings Wizard also displays the database connection string if it is accessible.

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C O N F I G U R A T I O N O V E R V I E WOnce the Console is open, you need to perform the following actions to configure your WinINSTALL environment.

1 Add machines in your network to the Console. (These are called managed machines)

2 Assign a role to each managed machine: Server or Workstation.

3 Specify a share for each Server.

4 Assign a server to each Workstation.

5 Deploy the WinINSTALL Agent to each server and workstation.

6 Start the WinINSTALL Agent on each managed machine.

The Add Machines Wizard will walk you through the steps listed above, making the job very simple--but if you choose, you can also perform any or all of these steps manually.

A

C O N F I G U R I N G T H E E N V I R O N M E N TPreliminary Steps


4

The following sections explain each of these steps in more detail.

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . P R E L I M I N A R Y S T E P SThe Default Settings Wizard guides you through the process of specifying a database and a share and allows you to make a few additional Console settings. The Default Settings Wizard opens automatically the first time you try to open the Console and cannot be invoked manually. But you can change any of these settings later on the Console Options dialog, available from the View menu at the top of the screen.

SPECIFY A WININSTALL DATABASEAll servers in your Console should point to the same database as the Console. WinINSTALL uses this central database to store all of the information that is logged during performance of various tasks, such as software distribution, replication, inventory, conflict assessment, and client reset. This central database acts as the hub for the flow of information between workstations, WinINSTALL servers, and WinINSTALL shares. WinINSTALL supports Microsoft® SQL Server 2000 and 2005 databases, MSDE 2000 (Microsoft® SQL Server 2000 Desktop Engine) databases, and Oracle 9i and later databases. For security, you can use either Windows NT Integrated security or you can use the security provided by the database itself. Once you have specified a database, you will not be prompted to do so again.

For details on setting up the WinINSTALL database, please see the chapter, Setting up the WinINSTALL Database, earlier in this guide.

SPECIFY A PRIMARY WININSTALL SHARE FOR THE CONSOLEThe WinINSTALL share serves a variety of purposes. In addition to housing the configuration files, executable programs, help files, reports and other information needed by WinINSTALL, it also acts as the store and forward point for information flowing from the database to the servers and workstations and back from these machines to the database. Once you have specified a primary WinINSTALL share, you will not be prompted to do so

WARNING: While you can change the database at any time from the Console, database configuration remains an option from the Console primarily so that you can change the database settings or have the server connect to the database using a different connection string – not to allow you to change to a different database server.

. . .

. .C O N F I G U R I N G T H E E N V I R O N M E N TAdd Machines in Your Network to the Console


again. However, you can change the primary share at any time from the Console on the Console Options dialog, accessible from the View menu at the top of the screen.

SET OTHER CONSOLE OPTIONSYou can also set additional console configuration options:

• You can turn on Console logging to the WinINSTALL database, to the NT Event log, or to both. Console logging is an audit trail that reports all of the Console-related activities that take place. This logging is different from the logging performed by the WinINSTALL Agent and is not intended for diagnostic purposes.

• If you have a licensed copy of Crystal Reports Designer installed on the Console machine, you can specify the path to the executable program. WinINSTALL comes with an extensive set of ready-to-use reports, but it is also tightly coupled with Crystal Designer. Once you specify the path to Crystal Designer, you can launch it from the Console. Without ever having to leave WinINSTALL, you can create new reports and add them to the list of existing reports in the Console.

• You can specify whether the Share Replication Wizard should be run at startup. This wizard creates and configures jobs to replicate application and patch packages, client reset templates, and personality transfer files from this share to other shares on your network. It runs automatically when you open the console if the following conditions exist:

• You have at least two servers with WinINSTALL shares.

• No replication jobs reference the current share, either as source or target.

• The Run Share Replication Wizard on Startup checkbox at the bottom of the Console Options dialog is checked (default):

A D D M A C H I N E S I N Y O U R N E T W O R K T O T H E

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C O N S O L EThe Add Machines Wizard guides you through the process of adding managed machines, specifying shares for servers, assigning servers to workstations, and deploying the agent to servers and workstations. The Wizard lets you add machines from the network or manually. If you choose, you can also add machines manually from a menu option.

ADD MACHINESThe first step in configuring your environment is to add the machines in your network to the WinINSTALL Console. The wizard enables you to add machines manually (using the Add

C O N F I G U R I N G T H E E N V I R O N M E N TAdd Machines in Your Network to the Console


4

Machine Manually panel in the wizard) or simply import them from your existing network structure, either Microsoft Networks or Active Directory.

ASSIGN ROLES TO MACHINES – SERVER OR WORKSTATIONAll managed machines in the WinINSTALL environment act as either servers or workstations. You must set at least one machine to act as a WinINSTALL server to manage the data flow to and from the central database. Before deploying the WinINSTALL agent, the role of the target machine can be specified in any of three places - the Welcome to the Add Machines Wizard panel, the Add Machine dialog, or the Machines Properties dialog.

SPECIFY A SHARE FOR EACH SERVEREvery WinINSTALL server must be associated with a specific WinINSTALL share, which serves multiple purposes.

• First of all, data is stored on the WinINSTALL share during its movement between the workstations and the database and vice-versa.

The WinINSTALL Agent on each workstation moves workstation data to the share associated with that workstation’s server. The WinINSTALL Agent on the server then merges that data from the share into the database. Conversely, the agent on the server publishes data from the database to the share, where retrieved by the workstation agents.

• In addition, the WinINSTALL binaries, including the installers, utilities, and msi packages to install agents, are all stored on the WinINSTALL share.

• WinINSTALL application packages and lists are stored in a folder within the WinINSTALL share, where workstation agents access them for software distribution tasks.

• Personality Transfer information repositories and Client Reset Template information are stored in folders within the WinINSTALL share.

The share can be specified in any of three places – on the Specify WinINSTALL Share panel of the Add Machines Wizard, on the Add Machine dialog, or on the Machines Properties dialog.

It is strongly recommended that you not configure the same share for multiple servers. Each server should have its own share. Shares are typically (but not necessarily) located on the servers to which they are assigned. Replication (of software packages and client reset templates) can take place only between WinINSTALL servers.

TIP: If a machine is not going to be managed by WinINSTALL, it is recommended that you remove the WinINSTALL Agent from the machine and remove the machine from the machine list.

. . .

. .C O N F I G U R I N G T H E E N V I R O N M E N TDeploy the WinINSTALL Agent


ASSIGN A SERVER FOR EACH WORKSTATION Every machine with the role of WinINSTALL workstation is assigned to a specific WinINSTALL server and therefore uses the same share as that server. The server to which a workstation is assigned moves data between the server’s share and the database.

The server can be specified in any of three places – on the Select Server panel of the Add Machines Wizard, on the Add Machine dialog, or on the Machines Properties dialog.

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D E P L O Y T H E W I N I N S T A L L A G E N TThe final step in configuring your environment is to deploy the WinINSTALL Agent to each machine.

The WinINSTALL Agent manages a variety of tasks, including performing inventories, distributing software, running replication jobs, merging data to the database, publishing data from the database, and scheduling tasks. It is deployed only once to each machine. Once deployed, the WinINSTALL Agent can be stopped and started from the Console or by using the Control Panel in the same way that you start and stop any other service. Agent tasks can be scheduled or they can be run in real-time from the Console.

You have several choices for deploying the WinINSTALL Agent.

DEPLOYING THE AGENT WHEN ADDING THE MACHINEThe simplest method of deployment is to deploy the agent as part of adding the machine. To do so, simply check the Deploy the WinINSTALL Agent to the Machines checkbox on the Completing the Add Machines Wizard panel. The agent will be immediately deployed to all the machines being added. The Agent Activity dialog will display the progress as the deployment proceeds on each target machine.

TIP: To deploy the WinINSTALL agent automatically from the Console, the logged-in account of the Console user must have administrative rights to the machine to which the agent is being deployed. (The credentials specified in the deployment UI are for the operation of the agents on the target machine, not for the process of deploying the agent).

C O N F I G U R I N G T H E E N V I R O N M E N TDeploy the WinINSTALL Agent


4

DEPLOYING THE AGENT FROM A MENU SELECTIONIf you have added machines but chosen not to deploy the agents at that time, you can deploy them later by first selecting the desired target machine(s) in the machine list and then selecting Deploy Agent . . . either from the Machine menu or from the right-click context menu. The Agent Activity dialog will display the progress as the deployment proceeds on each target machine.

DEPLOYING THE AGENT FROM A SECURE MANUAL DEPLOYMENT (SMD) F ILEIt is not possible to deploy the WinINSTALL Agent to all machines from the Console. For example, deployment to Windows 95 and Windows 98 machines must be done manually, from the target machines themselves. Once the WinINSTALL Agent has been deployed, such machines can be controlled from the Console, but in these and some other instances, the initial agent deployment may have to be done manually.

The first step in manual deployment is to create the Secure Manual Deployment (SMD) file. This file contains the initial settings which the WinINSTALL agent will use when it is first run.

Once you have created an SMD file, you can then use it as a parameter to the WIDeploy.exe utility (found in the \bin directory of the WinINSTALL share) in order to deploy the WinINSTALL Agent to any workstation for which the settings in the SMD file are suitable.

H O W T O U S E S E C U R E M A N U A L D E P L O Y M E N T T O D E P L O Y T H E A G E N T

1 To create an SMD file, select All Machines in the Console tree view, and select Secure Manual Deployment from the Machine menu.

2 The Secure Manual Deployment dialog will appear, allowing you to specify the required deployment settings: machine role (workstation or server), assigned share, and User name and password.

In addition, the Secure Manual Deployment dialog includes two additional settings: SMD file to create (path and file name for the output SMD file) and a checkbox labeled Run in user mode. This last setting is required for Windows 95 and Windows 98 operating systems, where the WinINSTALL Agent cannot run as a system service.

NOTE: The WinINSTALL Agent must be deployed manually to Windows 9x machines.

. . .

. .C O N F I G U R I N G T H E E N V I R O N M E N TDeploy the WinINSTALL Agent


3 To deploy the WinINSTALL Agent using an SMD file, you must run the WIDeploy.exe utility from the target machine and provide the desired SMD file as a command line parameter. This deployment can be done by means of a script, through a WinINSTALL package, or simply by opening a command prompt window on the target machine and entering the correct command line, such as the following:

\\<server>\WinINSTALL\Bin\WIDeploy.exe \\<server>\WinINSTALL\Packages\win9x.smd

In this example, \\<server>\WinINSTALL represents the WinINSTALL share, and win9x.smd represents the filename of the SMD file you must have already created for deployment to the target workstation.

In addition to installing the WinINSTALL Agent, WIDeploy.exe will automatically install the Windows Installer if it is not already installed, or upgrade it if it is not at least v2.0.

Once the WinINSTALL Agent starts running, it begins producing log files. After running for two minutes, the agent copies these log files to the share. After a maximum of two minutes, the server agent assigned to that share will merge these log files into the database. At this point, if the workstation is not found in the database, the server agent will create a machine entry in the database - entering the machine name and machine ID, leaving the name of the machine group blank, assigning the default role of workstation to the machine, and indicating that the agent is deployed. You can add the machine group later and change the role, if desired, on the Machine Properties dialog.

C O N F I G U R I N G T H E E N V I R O N M E N TDeploy the WinINSTALL Agent


4

Documents

WinINSTALL 8.7 Desktop Management Suite and Desktop ...docs.attachmate.com/wininstall/8.70.0400/enu/dms-das/DMS...Such a setup would also require a PXE server at each site. Client