ReadMe
WinINSTALL 9.0
MSI Packager Professional

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 2007 by Attachmate Corporation. All Rights Reserved.
Migration Engine Copyright 1998-2006 by Tranxition Corporation. All Rights Reserved.

 


This file contains the latest basic startup information, a brief explanation of the major new features, and the latest listing of known issues.


 

Table of Contents

Startup Tips

Installation Requirements

Starting the Console for the first time

Conflict Assessment

Upgrading from an Evaluation Copy to a Permanent License

Support Forum

 

New Features and Enhancements

Remote Control

Two-Phase Distribution

New Patch Management Facility

Job Creation Wizard

IPC File Transfer

PXE Client Reset Enhancements

Enhanced Checkpoint Restart in Server to Server Replication

 

Limitations and Known Issues

Setup

MSDE DBMS Setup

MSDE DBMS Removal

Evaluation Limitations

Upgrading from an Evaluation Copy

Initializing the WinINSTALL Database

Console

Database

Oracle DBMS Issues

On XP Pro SP2 RC2 the Database server name does not appear in Database Wizard with local MSDE installed

Cannot uninstall and successfully re-install the product on the same machine.

Discover

MSI Validation

Validation on Japanese Systems

Packaging

 

Startup Tips 

Installation Requirements

Please consult the WinINSTALL Installation Guide for specific installation requirements.

Starting the Console for the first time

When you start the console for the first time, you may be prompted by the Default Settings Wizard for the location of your WinINSTALL database and WinINSTALL share.

Please have these items of information available when you start the console.

Conflict Assessment

You create baselines for conflict assessments on the baseline machines themselves. You run the baseline generator program, WIBaselineGen.exe, which will be found in the \bin directory of the WinINSTALL share.

Upgrading from an Evaluation Copy to a Permanent License

If you have an evaluation version of WinINSTALL Software Distribution Suite installed but have purchased a permanent license, you can directly upgrade your installed evaluation version to a fully licensed version. To enter a permanent license key, simply click the Change button on the console Help/About screen and enter the license key on the provided dialog. Doing so will update the product to a permanent license.

Support Forum

Attachmate provides a free forum for support and discussion of all WinINSTALL products at http://support.attachmate.com/solutions.html?prod=wininstall

New Features and Enhancements 

The 9.0 release of the WinINSTALL family of products includes many new and improved features designed to make your job as a network administrator easier. The major new features and enhancements are listed below.

Remote Control

WinINSTALL now allows a console user to remotely control any client machine directly from the Machines list through either of two methods:

  • Windows Remote Desktop Connection (RDC).

  • The remote control product of your choice.

Two-Phase Distribution

WinINSTALL now offers a new option for delivering application packages to managed workstations.  The new Two-Phase Distribution option delivers the package to the workstation in phase one, and then, in phase two,  installs that package from the local drive.  This feature provides a number of new capabilities to WinINSTALL's industry leading software distribution capability:

  • Local execution of the WinINSTALL Installer.

  • Bandwidth throttling during package delivery.

  • Multicast package delivery option.

  • Checkpoint restart (sub-file level) during package delivery.

  • Package delivery without requiring access to a network share.

  • Decoupling of package delivery from package installation.

TIP: This combination of new capabilities makes Two-Phase Distribution an ideal mechanism for delivering large packages to remote or poorly connected users.

New Patch Management Facility

WinINSTALL now provides a comprehensive patch management feature with a number of new capabilities:  

  • Ability to schedule vulnerability scans as well as remediation (patch application) jobs.

  • Ability to view all managed machines with a selected vulnerability.

  • Ability to apply patches (remediations) to all vulnerable machines.

  • Remediation jobs use the new Two-Phase Distribution feature, enabling all the associated advantages and options of that feature.

  • Vulnerability scans and remediation jobs employ the Microsoft Windows Update Agent for maximum reliability and minimum system reboots.

  • The vulnerability database and remediation patches can be automatically downloaded to all WinINSTALL servers, enabling all vulnerability scans and remediation operations to be carried out with no required workstation internet access.

  • Legacy patch delivery through WinINSTALL .nai packages remains an available option.

Job Creation Wizard

WinINSTALL now provides a Wizard for job creation.  This Wizard is a new, unified facility for creating both scheduled and immediate jobs, making running tasks on managed workstations easier and more intuitive than ever.

IPC File Transfer

WinINSTALL has long used IPC (Inter-Process Communication) for direct interaction between the WinINSTALL console and managed machines.  Now this facility is used optionally or automatically in several additional WinINSTALL operations:

  • IPC file transfer is available as an optional means of transferring configuration and transaction files between the WinINSTALL agent on each managed machine and the WinINSTALL server.  This new option, configured on the WinINSTALL Agent Settings Advanced tab, allows these operations to make more efficient use of network bandwidth and strengthens network security.

  • The new Two-Phase Distribution feature automatically uses IPC file transfer to move packages to the local drive of the target machine before installation.

  • The new Patch Management facility also uses IPC file transfer to move patches to the local drive of each target machine before the patches are applied.

PXE Client Reset Enhancements

The PXE-based Client Reset feature of the WinINSTALL Desktop Availability Suite installs Windows operating systems directly from network servers, without loading MS-DOS or running MS-DOS applications.  In addition, administrators can use the built-in integration of WinINSTALL software distribution and personality transfer to optionally include in the reset process installation of any number of application packages and/or Microsoft patches, and the restoration of user data and settings as well.

This release introduces a number of significant enhancements to this major WinINSTALL feature:

  • PXE Reset Queues.

  • Improved automatic OS language detection.

  • Automatic OS detection for drivers.

  • SCSI/SATA driver support.

  • Regional language setting (Locale) support.

  • The UI now enables the hiding of unused languages.

  • Support for disabling the administrator account on PXE reset clients.

Enhanced Checkpoint Restart in Server to Server Replication

The server to server replication feature included in  the WinINSTALL Desktop Management Suite and WinINSTALL Desktop Availability Suite has always provided a file-level checkpoint restart capability for interrupted replication jobs.  Now this checkpoint restart capability has been extended to sub-file level, vastly increasing the efficiency of this feature.  For example, if a replication session is interrupted 90% of the way through the transmission of a large file, WinINSTALL will now transfer only the remaining 10% of the file, rather than the entire file, when the session is reestablished.

Note: This enhanced checkpoint restart feature is automatically used in all Two-Phase Distribution jobs as well as in server to server replication and patch management remediation.

 

Limitations and Known Issues

The following list itemizes all known issues with this release, including workarounds, where available. In most cases, subsequent releases are planned to address these issues.

Setup

During setup, you can change the installation directory for the console, but we recommend that you accept the default: [ProgramFilesFolder]OnDemand\WinINSTALL\ .

The WinINSTALL Agent is always installed to [ProgramFilesFolder]OnDemand\WinINSTALL\ and later maintenance of WinINSTALL will be simpler if both the agents and the Console are in the same directory.

 

MSDE DBMS Setup

After installation of the Microsoft SQL Server Desktop Engine (MSDE) database system, the following warning message may appear:

Files that are required for Windows to run properly have been replaced by unrecognized versions. To maintain system stability, Windows must restore the original version of these files. Insert your Windows 2000 Professional CD-ROM now.

The MSDE install, supplied by Microsoft, can replace protected files with other versions of these files. Since Microsoft produces this setup, Attachmate Corporation has no ability or right to change it.

Note that this warning message presents an option to replace the files with the original ones. You can continue the install by simply ignoring the fact that the files have been replaced. WinINSTALL will operate correctly despite these file replacements.

 

MSDE DBMS Removal

If you install WinINSTALL with the MSDE option, and you later want to remove MSDE from your system, be sure that you have first stopped the SQL AD Helper service. Otherwise, you may encounter difficulty removing MSDE.

 

Evaluation Limitations

Evaluation licenses allow you to use the product for a limited number of days. The specific time period varies, depending on the product being evaluated.

Please note that packages built during the evaluation period have evaluation license limitations time restrictions built into them. After the evaluation period expires, installations of these packages will no longer function and will be extremely difficult to repair.

Therefore, we recommend that, during the evaluation period, you limit distribution of these packages to a test environment only. To distribute these packages after the evaluation period expires, you must purchase a copy of WinINSTALL and access each package once from the newly licensed console.

 

Upgrading from an Evaluation Copy

If you have an evaluation version of any of the WinINSTALL 9.0 products installed, you can upgrade to a licensed version of the same product by simply entering the license key into the console on the Help/About screen.

If you have installed the console onto more than one machine during the evaluation, you need to upgrade the console on each of these machines. To do this, from each console machine, simply execute the upgraded WIConsole.msi in the \bin directory of the WinINSTALL share. Setup will start and offer to uninstall the console or to repair it.

You may uninstall it and reinstall it, or you may simply choose Repair. In either case, the console will be upgraded to the fully licensed version. The console should be closed before attempting an upgrade.

 

Cross-product and Evaluation Upgrades

The above procedure may or may not be permitted if you have evaluated one WinINSTALL product but purchased another. In fact, evaluation versions of certain products may not be upgraded to other products at all. For example, if you have evaluated the WinINSTALL MSI Packager Professional but have decided to purchase WinINSTALL Desktop Management Suite , you will have to uninstall the evaluation copy of the MSI Packager product before installing the Desktop Management Suite.

Please consult the chart below to determine whether or not you can upgrade your evaluation version. If you cannot upgrade, you will have to uninstall the evaluation before installing the licensed version.

Evaluation Product:

v9.0 Licensed Product (Upgrade Permitted):

LE

MSI

SDS

DMS

DAS

LE 9.0 Eval

YES

NO

NO

NO

NO

MSI 9.0 Eval

NO

YES

NO

NO

NO

SDS 9.0 Eval

NO

NO

YES

NO

NO

DMS 9.0 Eval

NO

NO

NO

YES

YES

DAS 9.0 Eval

NO

NO

NO

YES

YES

SDS 9.0

NO

NO

N/A

NO

NO

DMS 9.0

NO

NO

NO

N/A

YES

 

 

Initializing the WinINSTALL Database

WinINSTALL includes a database setup wizard, WIDBSetup.exe , located in the \bin directory of the WinINSTALL share. WinINSTALL setup offers the option of executing this wizard at the conclusion of setup, but it can also be executed directly at any time. This wizard will create all the needed tables for the WinINSTALL database in MSDE, Microsoft SQL Server, or Oracle.

 

Console

When you have an MSI package open on one console, a second console attempting to view the same package will receive the following message:

Someone else is currently working with this file. Opening for read-only access; changes will not be saved.

The way to release the console locks on an MSI package is to refresh (F5) the parent list, not just to click away from the package. This procedure was designed for performance reasons.

 

Database

Oracle DBMS Issues

Oracle databases are case sensitive by default and can cause problems for certain WinINSTALL features. Example: searches using a default Oracle database can return erroneous results. Reports can also be affected in the same way.

 

Server upgrades from 2000 to 2003 Can render WinINSTALL unable to open the database connection dialogue

When you upgrade a Windows 2000 Server to Server 2003, you cannot open the database connection dialogue in the WinINSTALL console, making the console inoperable.

When WinINSTALL setup installs MDAC, it installs the file OLEDB32.DLL with a version of 2.71.9042 . When Windows 2003 is installed as a standard install (not an upgrade) the version of this file that is installed is 2.80.1022 . Either of these file versions works properly and will allow WinINSTALL to display the connection properties dialogue.

However, an upgrade install of Windows 2003 installs an older version of OLEDB32.DLL, version 2.70.7713 , which will not allow WinINSTALL to operate. This issue should be resolved in SP1 for Windows 2003.

In the event that you encounter this problem, you can work around the issue by simply obtaining either the 2.71 or 2.80 version of OLEDB32.DLL and copying it to the C:\Program Files\Common Files\System\Ole DB\ folder on the upgraded machine.

 

On XP Pro SP2 RC2 the Database server name does not appear in Database Wizard with local MSDE installed

After installing WinINSTALL with MSDE on Windows XP Pro SP2 RC2 the Database Wizard will not show the local machine's name with instance name in the Database server name drop down.

You can manually type in the database server name, and the Database Wizard will find the local database.

To avoid having to manually enter the database server name, open UDP port 1434.

 

Cannot uninstall and successfully re-install the product on the same machine.

If you have a WinINSTALL installation using MSDE and you uninstall it and then try to install (or re-install) v9.0, database creation will fail with the following message:

Msg 5170, Level 16, State 1, Server servername \ONDSQL, Line 1
Cannot create file 'C:\Program Files\Microsoft SQL Server\Data\MSSQL$ONDSQL\Data\WINSTALL8.mdf' because it already exists.

Msg 1802, Level 16, State 4, Server servername \ONDSQL, Line 1
CREATE DATABASE failed. Some file names listed could not be created. Check previous errors.

Cannot open database requested in login 'WINSTALL8'. Login fails."

Because an uninstall of WinINSTALL will never delete user data, the old WinINSTALL database remains. However, MSDE and SQL Server work in such a way that they will not automatically reconnect to the old database when WinINSTALL is reinstalled.

SQL 2000 Server and MSDE both have the notions of the server instance and the database. ( servername\ONDSQL is a server instance, WINSTALL8 is a database name). When you install MSDE, it creates the server instance only; it does not create a new database nor does it attach to existing databases.

Therefore, if you open the console and point it to the local MSDE, it would return an error saying that the database was not found.

In order that procedure to work, you must first attach the database to the server instance.

This problem has 3 possible workarounds:

  1. Delete the old database files (using Explorer) then rerun WIDBSetup.exe.

  2. Use a different name for the database when re-installing WinINSTALL.

  3. Use the Enterprise SQL Manager Console to attach the existing database to the MSDE server.

Note that the last option would be accomplished by running the Enterprise SQL Manager with the following command line:

osql.exe -S DBInstance -E -Q "exec sp_attach_db @dbname = N'DBName', @filename1 = N'db_path', @filename2 = N'log_path'"

DBInstance and DBName will be known by WIDBSetup.exe, but db_path and log_path are the canonical paths to the database and log files respectively--which must be explicitly provided here.

 

Discover

  • Discover does not support creation of transforms with unsupported schemas (0.3, 1.0).

  • Before you can create or use Discover's Archive Before snapshots, the operating system for which you want to do this must have the file cabinet.dll installed (usually in the system folder). Some operating systems (Win95) do not have this DLL. If you copy it from a Win98 system to the system folder of your Win95 system, Discover's Archive Before snapshots will work again. If you're missing this DLL, Discover will continue to work, but this feature will be disabled.

  • Discover fails to create a package with Chinese characters for .msi file name and .lst file name. NetBIOS requires the share code page to match the locale of the operating system on the machine running Discover. If the code pages do not match, the following error message will be displayed at the After Snapshot:

Severity 1
Return Code 110
Message:
Failed to Open Database.

  • When F1 is selected while running the Discover utility, the help may not display or may not display properly. This problem is caused by Internet Explorer security settings which prevent the display of HTML help files launched from a remote location such as the WinINSTALL share. See the following Microsoft KnowledgeBase article for details on the problem and possible solutions: http://support.microsoft.com/kb/896054.

    A workaround is to copy the file Discowiz.chm to a local folder and execute the local copy of this file directly, rather than by pressing F1 within Discover.

  • On a Vista machine with the Sidebar running, Discover fails in the after snapshot section with a message that states "A sharing violation occurred while accessing \path\WindowsSidebar\Settings.ini."  With the Sidebar turned off (i.e., "Exited"), Discover will complete.

 

MSI Validation

When you browse to the .cub file that you want to use for MSI validation, the Open dialog does not default to the \bin directory where .cub files are located, but instead opens to the last working directory.

The product currently supports the following ICE (Internal Consistency Error) repairs:

ICE02

Circular File/Registry/Component relationships

ICE05

Required property validation

ICE08

Duplicate component GUID

ICE09

Permanent component validation

ICE10

Child/parent feature advertising validation

ICE14

Child/parent feature relationship validation

ICE15

MIME/Extension circular relationship validation

ICE16

ProductName length <= 63 characters

ICE18

Null component keypath validation

ICE21

Component/FeatureComponents validation

ICE36

Icon bloat

ICE42

Class Inproc/Local server validation

ICE49

Registry default value type validation ( see note 1 )

ICE54

Keypath file version indirection validation

ICE55

LockPermissions validation

ICE73

Reserved GUID validation

ICE74

UpgradeCode/FASTOEM property validation ( see note 2 )

Note 1: WinINSTALL will repair the issue raised by ICE49 by making the component conditional as recommended by Microsoft. However, ICE49 does not check to see if the component is conditional, so it will continue to raise the warning, even if the component is conditional. Also, since WinINSTALL checks to see if the component is conditional first and will not modify any existing conditions, it may be that the component should still be reviewed manually to make sure that the condition is sufficient to not have the component install on Win95.

Note 2: There is currently an issue with how Validation works, such that if the FASTOEM property is in the property table, validation will fail to run because MSI fails to open the package. This will be addressed in the next version such that packages that author the FASTOEM property in error won't fail Validation and can then be repaired. The other repairs related to ICE74 are functional, as is the repair for FASTOEM, but the FASTOEM repair cannot be demonstrated due to the Validation issue.

Validation on Japanese Systems

MSI Validation messages show up in English instead of Japanese.  These messages are derived from the selected cub file, and these files are supplied by Microsoft.  Unfortunately, Microsoft does not provide Japanese-translated .cub files.

 

Packaging

  • When attempting to add an INI file to the Edits|INI Files|Remove Tab for MSI files, you must specify a value before the INI file can be written to the table. MSI files require a value to be specified. INI files and INI file sections cannot exist independently in an MSI package. If an entire section is to be deleted - each value must be present in the Remove side.

  • If you add package restrictions to an .msi file and then decline to save the changes, the UI may behave as though the group restriction has, in fact, been saved. This is a display anomaly only--the data has not been saved.

    If you leave the Software Distribution area of the product, for example, and then return and select the same package, you may see the restriction you declined to save. Although it looks as though this change has been saved, in fact it has not been written to the package file. If you restart the console or select View/Refresh (F5) and then look at the same package, you will find that the restrictions are not present.