Survey
* Your assessment is very important for improving the workof artificial intelligence, which forms the content of this project
* Your assessment is very important for improving the workof artificial intelligence, which forms the content of this project
Microsoft Access wikipedia , lookup
Oracle Database wikipedia , lookup
Concurrency control wikipedia , lookup
Relational model wikipedia , lookup
Open Database Connectivity wikipedia , lookup
Team Foundation Server wikipedia , lookup
Database model wikipedia , lookup
Microsoft SQL Server wikipedia , lookup
Microsoft Jet Database Engine wikipedia , lookup
..... WinINSTALL 8.70.03 MSI Packager Professional Release Notes .................................................................... ..... 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 2006 by Attachmate Corporation. All Rights Reserved. Migration Engine © Copyright 1998-2006 by Tranxition Corporation. All Rights Reserved. ..... TABLE OF C ONTENTS Chapter 1: Installation Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1 WinINSTALL Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 Hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 Display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 WinINSTALL Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 Hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 Reference Machine (clean machine on which packages are discovered) . . . . . . . . . . . . . . . . . . . 2 Hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 WinINSTALL Administrator Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 Chapter 2: New Features and Enhancements . . . . . . . . . . . . . . . . . . . . . . . . . . .5 PXE-Based Client Reset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 Machine Ping from the Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 Ability to Suspend Scheduled Jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 WinINSTALL Software Distribution Suite (SDS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 MSI Packaging Improvements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 Wake on LAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 Improved support for Workgroup Environments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 Improved Agent Deployment and Monitoring Capabilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 Configurable Share Selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 Multiple Patch Download Capability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 License Management Improvements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 Improved CD Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 Job Scheduling to User Accounts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 Global Jobs and Defaults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 Client Reset Improvements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 New Release of the Personality Transfer Engine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 SQL Server 2005 Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 April, 2006 Release Notes iii Chapter 3: Problems Resolved . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13 Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 Discover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 Help and Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 Chapter 4: Limitations and Known Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15 Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 MSDE DBMS Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 MSDE DBMS Removal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 Evaluation Limitations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 Upgrading from an Evaluation Copy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16 Initializing the WinINSTALL Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 Oracle DBMS Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 Server upgrades from 2000 to 2003 Can render wininstall unable to open the database connection dialogue . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 On XP Pro SP2 RC2 the Database server name does not appear in Database Wizard with local MSDE installed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 Cannot uninstall and successfully re-install the product on the same machine. . . . . . . . . 19 Discover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 MSI Validation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 Packaging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21 NLS (Non-English) Operating Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 iv WinINSTALL MSI Packager Professional I NSTALLATION R EQUIREMENTS T ..... ................................... 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. .................................................... WININSTALL CONSOLE The 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, plus sufficient additional space to store application packages built and edited in the Console. 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 RESOLUTION • 1024 X 768 or higher. April, 2006 Release Notes 1 1 INSTALLATION REQUIREMENTS WinINSTALL Database COLOR • 16-bit or better. .................................................... WININSTALL DATABASE The WinINSTALL database holds all of the information used internally by WinINSTALL and displayed in the console. 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. HARDWARE • Adequate disk space for database. 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. REFERENCE MACHINE (CLEAN MACHINE ON WHICH PACKAGES ARE DISCOVERED) .................................................... 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 2 WinINSTALL MSI Packager Professional WinINSTALL Administrator Requirements ..... INSTALLATION REQUIREMENTS 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. SOFTWARE • Operating System. Windows 2003/XP/2000/ • Microsoft Windows Installer 2.0 or greater. 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. WININSTALL ADMINISTRATOR REQUIREMENTS .................................................... An 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. • 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. April, 2006 Release Notes 3 1 INSTALLATION REQUIREMENTS WinINSTALL Administrator Requirements 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. Scripting in Windows Installer packages is accomplished through custom actions. 4 WinINSTALL MSI Packager Professional N EW F EATURES AND E NHANCEMENTS T ..... ................................... 2 he 8.70 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. .................................................... PXE-BASED CLIENT RESET The WinINSTALL Desktop Availability Suite (DAS) now includes an exciting new client reset facility based on PXE (Preboot eXecution Environment). This facility is extremely easy to configure and use, and it does not use DOS or any other operating system other than the one being installed on the target machine. PXE reset server files, including operating system files, drivers, and post-install utilities, are available to be replicated from one PXE server to another using WinINSTALL’s built-in replication feature. The PXE-based Client Reset feature of the WinINSTALL Desktop Availability Suite installs Windows operating systems directly from network servers, without loading MSDOS 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. WinINSTALL PXE Client Reset installs Windows operating systems using the original setup programs supplied by Microsoft, driven by a configuration file so as to streamline the process and make it operate entirely unattended. Using the vendor setup program to install the operating system enables use of a single set of operating system files for many configurations, while avoiding having to create and maintain separate images for each desired configuration. In addition, the PXE reset process has been optimized to the point where install times are very fast. The seamless integration of PXE Client Reset with WinINSTALL’s powerful personality transfer and software distribution capabilities provides unmatched power and simplicity to desktop management. The full integration of these features makes it a simple matter to right-click on a machine, or group of machines, in the WinINSTALL Console, and with a single command, back up the user data and settings, reboot the PC, format the hard disk, install a new copy of Windows 2000, XP, or 2003, followed by a series of patches and application packages, and conclude with a restoration of the user data and settings. WinINSTALL PXE Client Reset provides an easy, efficient, and convenient method of April, 2006 Release Notes 5 NEW FEATURES AND ENHANCEMENTS 2 Machine Ping from the Console rebuilding any PC or group of PCs on your network—remotely, while the PCs are unattended. WinINSTALL PXE Client Reset allows you to reset a client in any of three ways: 1 You can select the desired client and invoke an immediate reset. 2 You can configure a reset to occur on a machine’s next reboot. 3 You can schedule PXE Client Resets to occur at a set time in the future, or even on a regular, recurring basis! When you invoke an immediate reset or schedule a reset (methods 1 and 3, above), WinINSTALL's PXE Client Reset feature will automatically employ Wake-on-LAN to execute the reset, if needed. .................................................... MACHINE PING FROM THE CONSOLE With WinINSTALL Software Distribution Suite, Desktop Management Suite, and Desktop Availability Suite, the WinINSTALL console now provides a built-in ping capability which allows you to test connectivity between the console and any machine or selected group of machines. The WinINSTALL ping feature can test single or multiple machines at once and is completely configurable to assure effective operation in your environment. To use the WinINSTALL ping feature, you simply select the desired machine(s) in the machine list, and then select Ping... from the Machines menu or the right click context menu. The WinINSTALL ping feature can test single or multiple machines at once and is completely configurable to assure effective operation in your environment. .................................................... ABILITY TO SUSPEND SCHEDULED JOBS You can now temporarily halt execution of any scheduled task. Suspending a scheduled task does not cancel the task, nor does it delete it from the WinINSTALL database. Instead, it simply suspends, temporarily, the execution of the task. Execution can then be resumed at any time, without having to re-create the scheduled task. 6 WinINSTALL MSI Packager Professional WinINSTALL Software Distribution Suite (SDS) ..... NEW FEATURES AND ENHANCEMENTS WININSTALL SOFTWARE DISTRIBUTION SUITE (SDS) .................................................... WinINSTALL is now available in a version providing software packaging and distribution capabilities only, for those environments where inventory, replication, operating system deployment, and other advanced capabilities are not needed. The new WinINSTALL SDS product is a perfect fit for those environments which require the power and simplicity of WinINSTALL packaging and distribution but are not ready for the advanced feature set of the full WinINSTALL Desktop Management Suite or WinINSTALL Desktop Availability Suite products. WinINSTALL SDS is designed for those organizations in need of complete, flexible software packaging and distribution but not requiring inventory, license and asset management, operating system deployment, package replication, or personality transfer capabilities. .................................................... MSI PACKAGING IMPROVEMENTS WinINSTALL's MSI packaging capabilities have been enhanced in numerous ways, including the addition of the following features: • WinINSTALL now provides the ability to store within the MSI file itself a history of modifications made to it in the WinINSTALL console. • WinINSTALL now provides the ability to easily prompt a user for the value of a Windows Installer property. Simply enter a name for the dialog to be presented, the prompt to present to the user, and the property in which to place the text entered by the user. • WinINSTALL now allows the creation of transforms by simply comparing two MSI files. The difference between the two is automatically converted into a transform. When this transform is applied to an installation of the first MSI file, it matches an installation of the second. .................................................... WAKE ON LAN WinINSTALL Software Distribution Suite, WinINSTALL Desktop Management Suite, and WinINSTALL Desktop Availability Suite now provide the ability to wake machines from a sleep state through Wake-On-LAN functionality. You can issue a Wake-On-LAN command immediately or schedule it for a specified time in the future. April, 2006 Release Notes 7 2 NEW FEATURES AND ENHANCEMENTS Improved support for Workgroup Environments If you are using either the WinINSTALL Desktop Management Suite or the WinINSTALL Desktop Availability Suite, you have the additional option of adding the Wake function to any scheduled job. IMPROVED SUPPORT FOR WORKGROUP ENVIRONMENTS .................................................... WinINSTALL Software Distribution Suite, WinINSTALL Desktop Management Suite, and WinINSTALL Desktop Availability Suite all offer improved workgroup networking support, including the addition of a new Console setting to enable seamless browsing of non-Active Directory, non-Domain environments. IMPROVED AGENT DEPLOYMENT AND MONITORING CAPABILITIES .................................................... This release of the WinINSTALL suite products introduces automatic network deployment of the WinINSTALL Agent, plus a number of additional enhancements to the agent deployment and monitoring capabilities: • Account credentials can now be securely re-used for multiple deployment operations without having to re-enter them for each operation. • The Agent Activity window displays the progress of deployment and other machine operations in real time, and roll-over tool tips provide extra status information. • Agent status now includes additional states and diagnostic information. • The Machine/General tab now shows the current status and activity of each WinINSTALL sub-agent. • The Machine/General tab now provides the ability to configure the behavior of the agent status refresh feature. • Secure Manual Deployment (SMD) deployment has been enhanced to permit the contents of the SMD file to be overridden in some circumstances. The primary purpose is to enable the deployment share to be specified at the time of deployment, which can allows a single SMD file to be used enterprise-wide. 8 WinINSTALL MSI Packager Professional Configurable Share Selection ..... NEW FEATURES AND ENHANCEMENTS .................................................... CONFIGURABLE SHARE SELECTION WinINSTALL now provides the ability for each workstation to determine on boot up which WinINSTALL share, among a pre-defined group, is the optimal share to use. The advanced operations provided in DMS and DAS are particularly helpful for laptop users who visit multiple locations within the organization. In this situation, this feature enables such users to automatically attach to the nearest WinINSTALL share at whatever location they find themselves, rather than always pointing back to a “home” share. Of course, administrators can configure the order in which shares are considered and the criteria by which the nearest share is determined. .................................................... MULTIPLE PATCH DOWNLOAD CAPABILITY The WinINSTALL suite products now permits easier management of Microsoft patches, including the ability to download and automatically create packages for multiple patches at once, and (via a special WinINSTALL utility), access to patches in all Microsoft-supported languages. .................................................... LICENSE MANAGEMENT IMPROVEMENTS The WinINSTALL DMS and DAS License Management capability has been expanded and improved in a number of ways. For example, you can now see at a glance how many licenses you have, how many are in use, and how many remain available. .................................................... IMPROVED CD WIZARD The WinINSTALL CD Wizard (available in WinINSTALL Software Distribution Suite, Desktop Management Suite, and Desktop Availability Suite) enables an administrator to very quickly and easily stage applications and lists of applications for burning onto a CD or DVD. It's also very simple to include one or both WinINSTALL Installers and to create an AutoRun file to execute on insertion of the media. In this release, the CD Wizard has been streamlined and simplified for quicker, easier, and more trouble-free creation of application package CDs and DVDs. April, 2006 Release Notes 9 2 NEW FEATURES AND ENHANCEMENTS Job Scheduling to User Accounts .................................................... JOB SCHEDULING TO USER ACCOUNTS When scheduling jobs to specific users and/or user groups, the WinINSTALL suite products now check each target machine to determine whether or not any specified target user has an existing account profile on the machine. If so, the job is executed. This behavior is a change from previous versions, where the only account evaluated was the account under which the WinINSTALL Agent was operating. .................................................... GLOBAL JOBS AND DEFAULTS WinINSTALL now provides an easy method to schedule a job to execute on all workstations, including workstations which have not yet joined the network. In addition, this release makes it easy to change settings on all workstations and to change the default settings for all machines in your network. .................................................... CLIENT RESET IMPROVEMENTS The Client Reset feature available in the WinINSTALL Desktop Availability Suite now includes enhanced capabilities extending beyond installing or restoring operating systems on workstations. • Machine names are now automatically preserved across reset operations. • Dynamic List Files, automatically created after an inventory, enable the automatic restoration of the entire set of pre-reset installed applications. • Advanced operations include application mapping (substitution of new post-reset applications for specified pre-reset applications). This feature enables automatic application upgrades as part of the reset process. • Personality backup and restore can easily be included into an automated reset process, enabling a full client reset in a single operation: backup, followed by a reboot, hard drive reformat, OS install and application set install, and concluding with user data and settings restoration. • Virtual floppy packages enable drag and drop or scheduled resetting of single workstations or groups of workstations. 10 WinINSTALL MSI Packager Professional New Release of the Personality Transfer Engine ..... NEW FEATURES AND ENHANCEMENTS NEW RELEASE OF THE PERSONALITY TRANSFER ENGINE .................................................... WinINSTALL Desktop Availability Suite now includes the Tranxition Personality Transfer Pro™ 4.60 engine, with improved performance and full extraction and injection capabilities for a large number of common applications and Windows settings. .................................................... SQL SERVER 2005 SUPPORT WinINSTALL now supports Microsoft SQL Server 2005, including all available editions. WinINSTALL database support now includes the following database management systems: • Microsoft SQL Server 2000 Desktop Engine (MSDE 2000) • Microsoft SQL Server 2000 • Microsoft SQL Server 2005 • Oracle 9i and later April, 2006 Release Notes 11 2 12 NEW FEATURES AND ENHANCEMENTS SQL Server 2005 Support WinINSTALL MSI Packager Professional 3 P ROBLEMS R ESOLVED T ..... ................................... he WinINSTALL 8.70.03 release includes resolutions to a number of issues uncovered in prior versions. The most important of these fixes are listed below, according to the main area of the product affected. Note that some of these issues were originally provided in the 8.70, 8.70.0100, 8.70.0200 or 8.70.0201 releases. Those fixes which are new in the 8.70.03 release are explicitly identified as such below. .................................................... CONSOLE • As of version 8.70.03, the user is now able to copy information from the Description field of the console log. • When adding a service to a package, if the "Import NT Service" button was used but the "Add Service" dialog was canceled, the console would terminate. This problem has been resolved in 8.70.03. • Version 8.70.03 resolves seveal potential problems in merging third-party (e.g. Microsoft) merge modules into Discover-created MSI packages. Symptoms could have included missing Directory table entries after merging-in a merge module during conversion to MSI, or even a console crash. • The stability of the Custom Action Wizard has been improved. • The AppSearch CompLocator dialog now displays GUIDs instead of component IDs. • MSI packages containing an AppSearch CompLocator entry now install properly. • The Console title bar now displays the path of the current WinINSTALL share. • WinINSTALL now provides the ability to copy all or selected list items to the clipboard or to export them to a tab-delimited text file. This capability has been added to the Console log pages. .................................................... DISCOVER When Discovering an ODBC DSN, the machine-specific MAC address is also captured. Distributing the resulting package to multiple machines results in all connections to the data source appearing to come from the same machine. 8.70.03 Discover’s default registry exclusions have been modified to prevent this information from being included. April, 2006 Release Notes 13 3 PROBLEMS RESOLVED Help and Documentation .................................................... HELP AND DOCUMENTATION The product help and documentation include a number of corrections and improvements to both correct inaccuracies and improve clarity. 14 WinINSTALL MSI Packager Professional L IMITATIONS AND K NOWN I SSUES T ..... ................................... 4 he 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 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 LIMI TATI ONS 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. April, 2006 Release Notes 15 4 LIMITATIONS AND KNOWN ISSUES Setup 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 8.7 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. 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: • v8.7 Licensed Product (Upgrade Permitted): MSI SDS LE 8.7 Eval • YES • NO • NO • NO • NO MSI 8.7 Eval • NO • YES • NO • NO • NO SDS 8.7 Eval • NO • NO • YES • YES* • YES* WinINSTALL 8.60 Eval • NO • NO • NO • YES • YES WinINSTALL 8.60.01 Eval • NO • NO • NO • YES • YES NO • NO • NO • YES • YES DAS 8.60 Eval • NO • NO • NO • YES • YES DAS 8.60.01 Eval • No • NO • NO • YES • YES DAS 8.7 Eval • NO • NO • NO • YES • YES SDS 8.7 • NO • NO • N/A • YES* • YES* LE DMS 8.7 Eval • 16 WinINSTALL MSI Packager Professional DMS DAS Console WinINSTALL 8.60 • NO • NO • NO • YES • YES WinINSTALL 8.60.01 • NO • NO • NO • YES • YES DMS 8.7 • NO • NO • NO • N/A • YES DAS 8.60 • NO • NO • NO • NO • YES DAS 8.60.01 • NO • NO • NO • YES • YES ..... LIMITATIONS AND KNOWN ISSUES * Upgrading the Software Distribution Suite to the Desktop Management Suite or the Desktop Availability Suite requires following a special procedure to accommodate the changes in database configuration between SDS and the other products. NOTE: Upgrading to 8.70.03 from 8.70.0000, 8.70.0100, 8.70.0200, or 8.70.0201 is accomplished by executing the appropriate product-specific patch. If you want to move from an evaluation version of 8.70.0000, 8.70.0100, 8.70.0200, or 8.70.0201 to a licensed version of 8.70.03, you must perform two operations: license the product and upgrade the version. These two operations can be performed in any order. INITIALIZI NG 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. If you have an earlier version of WinINSTALL 8.x installed, when you first start the console after applying the upgrade patch, you will be prompted to allow WinINSTALL to automatically update the database schema. If you would prefer to update the schema manually, please see the release notes to the patch for instructions on how to run the script to update the database schema to 8.70.03. .................................................... 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. April, 2006 Release Notes 17 4 LIMITATIONS AND KNOWN ISSUES Database 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: Machine 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 WI TH 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. 18 WinINSTALL MSI Packager Professional Database ..... LIMITATIONS AND KNOWN ISSUES CANNOT UNINSTALL AND SUCCESSFULLY RE-I NSTALL 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) v8.7, 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'" April, 2006 Release Notes 19 4 LIMITATIONS AND KNOWN ISSUES Discover 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). • 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. .................................................... 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: 20 ICE02 • Circular File/Registry/Component relationships ICE05 • Required property validation ICE08 • Duplicate component GUID ICE09 • Permanent component validation ICE10 • Child/parent feature advertising validation WinINSTALL MSI Packager Professional Packaging 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) ..... LIMITATIONS AND KNOWN ISSUES 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. .................................................... 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. April, 2006 Release Notes 21 LIMITATIONS AND KNOWN ISSUES 4 Packaging NLS (NON-ENGLISH) OPERATING SYSTEMS While WinINSTALL PXE Client Reset can install most non-English operating systems as simply and easily as it can English operating systems, we have identified technical challenges posed by the following language/operating system combinations. WINDOWS 2003 STANDARD/ENTERPRISE SERVER FRENCH Installing French versions of Windows 2003 Server (either Standard or Enterprise) may result in a failure to copy the file channels.scf. There are two workarounds if you encounter this problem: 1 You can choose to skip this file; setup will then continue uninterrupted. NOTE: This workaround will require user intervention at the target machine during the reset process. 2 On the WinINSTALL share, edit the appropriate file, as specified in the following table: OPERATING SYSTEM FILE TO MODIFY Windows 2003 Enterprise Server Volume License • ClientReset\1036\Win2K3eV\i386\txtsetup.sif Windows 2003 Enterprise Server • ClientReset\1036\Win2K3e\i386\txtsetup.sif Windows 2003 Standard Server Volume License • ClientReset\1036\Win2K3sV\i386\txtsetup.sif Windows 2003 Standard Server • ClientReset\1036\Win2K3s\i386\txtsetup.sif • Locate the [Strings] section in the txtsetup.sif file. • Find the key entry ViewChannelsSCF. • Replace the single character in the value entry as specified below: Before: [Strings] ViewChannelsSCF = Cha?nes.scf • Note: ? is hexadecimal 0x3F. After: [Strings] ViewChannelsSCF = ChaŒnes.scf 22 WinINSTALL MSI Packager Professional • Note: Œ is hexadecimal 0x8C. Reports ..... LIMITATIONS AND KNOWN ISSUES .................................................... REPORTS The MSI Packager Professional reports on Console Log Entries and Console Log Entries for a Specified User return no results. This is a known issue and will be addressed as soon as possible in a subsequent release. In the meantime, the workaround is to look at the reports on Console Log Entries for Packages Added, Console Log Entries for Packages Updated, and Console Log Entries for Packages Removed, all of which work as intended. April, 2006 Release Notes 23 4 24 LIMITATIONS AND KNOWN ISSUES Reports WinINSTALL MSI Packager Professional