The information contained in this publication is subject to change without notice. Scalable Software 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. Scalable Software 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 © 2015 by Scalable Software, Inc. All Rights Reserved.

Prerequisites

Best Practices

Viewing or Changing License Keys

Known Limitations and Workarounds

Smart Packager runs on the following operating systems:

• Windows XP SP2 or greater¹
• Windows Server 2003 SP1 or greater
• Windows Server 2003 R2
• Windows Vista
• Windows 7
• Windows 8
• Windows 8.1
• Windows 10
• Windows Server 2008
• Windows Server 2008 R2
• Windows Server 2012
• Windows Server 2012 R2

Smart Packager also requires the following Microsoft packages. These requirements are typically pre-installed on all newer versions of Windows.

• Microsoft XML services (MSXML) version 6 [http://www.microsoft.com/download/en/details.aspx?id=3988]

The following are best practices in software repackaging. They yield the best possible results while minimizing the post-capture modification of the package.

• Close all non-essential applications. This helps to ensure the changes added to the new package are only those changes made by the desired application and not other programs that were active on the system at the time of capture.
• Use a clean system. Many applications do not fully uninstall, therefore subsequent reinstallations will not create the full set of files and registry keys associated with the package.
• Stop anti-virus and other similar programs. It is not uncommon for anti-virus software to block applications from making changes to the system which would result in an incomplete repackaging.
• Disable Windows Update and other auto-updating programs.
• Ensure the system is not busy performing other tasks, e.g. search indexing.
• After installation is complete, wait a few seconds before stopping the monitoring process. Some installations continue modifying the system even after the installation program has completed. Non-MSI installations can spawn child processes which can continue to modify the system. Even MSI-based installations can use the Windows Installer Service to perform installation tasks after the initial setup has completed.
• Perform the capture on a system that is very similar to the final target systems. For example, for an organization that uses Windows XP SP3 with .NET 4.0, do not perform the capture on Windows 7 SP1.
• Repackage 32-bit applications on 32-bit Windows. Although 32-bit installations can be repackaged on 64-bit Windows, it is recommended to repackage 32-bit applications on 32-bit Windows. A 32-bit application installed on 64-bit Windows creates up to twice as many registry keys (once in the 64-bit hive and again in the 32-bit hive) which increases the size and complexity of the package and also prevents the new package from being installed on 32-bit Windows.
• Consider the use of a virtual machine as the machine on which the package is captured.
• Repackage on a machine with a unique and complex computer name. Simple computer names run the risk of being turned into variables during the repackage process. For example, if the computer name is "Homer" then the registry key HKLM\Software\AppLocation\HomeReturnPaths would become HKLM\Software\AppLocation\%ComputerName%eturnPaths. Instead a computer name like "PC-A1547B" would prevent this false-positive from occurring.

To view the current license key run Discovery or Smart Packager. Right-click on the title bar and select "Properties." The License dialog will display the current license key, product type, and days remaining until expiration.

To enter a new license key, open the License dialog and click "Change." Enter the and click "Ok" to accept the new license key.

Here is a list of known issues and limitations for Smart Packager as well as workarounds when available.

Issue: The Microsoft Windows Installer format supports installations for a single user or all users, but not both. Repackaging an installation containing both per-user and per-machine files and settings may not work correctly.
Workaround: You can attempt to repackage installations containing both per-user and per-machine files, usually the resulting package still works. Note, the packaging process will log a warning that it detected both per-user and per-machine.

Issue: The Microsoft Windows Installer format cannot support both x86 and x64 architectures in a single package. A package must target either x86 or x64, but not both.
Workaround: The solution is to create two separate packages, one for x86 and a second for x64.

Issue: Packages that install files monitored by the System File Checker (a.k.a. Windows Protected Files) cannot be repackaged. These are operating system critical files that only Microsoft can repackage and distribute. Examples of packages that install SFC files include Windows updates, Microsoft hotfixes, and Internet Explorer.

Issue: Packages that store files or settings remotely may not work. For example, if the package installs files to a network share, or adds settings to Active Directory.
Workaround: You can attempt to repackage these types of installations. Smart Packager can only repackage files and settings installed locally, so the new package may or may not work when installed on other machines. It would depend on the software in question.

Issue: Packages that store machine-specific files or settings may not work. For example, if the application creates a local token based upon the machine's unique SID.
Workaround: You can attempt to repackage these types of installations. Smart Packager will repackage machine specific files and/or settings, but the new package may or may not work when installed on other machines.

Issue: Software that requires unique license keys may not work. If every instance of the software requires a unique license key, repackaging and distributing multiple copies with the same license key may or may not work. Even if it does work, it may be a violation of the original vendors software license agreement. Always read software license agreements carefully.
Workaround: Obtain a common or volume license key for use when repackaging.

Issue: A 32-bit package captured on a 64-bit machine and only be installed on another 64-bit machine. This is because 32-bit installations on 64-bit machines create registry keys into hive locations that do not exist on 32-bit Windows.
Workaround: Capture the package a second time on a 32-bit version of Windows.

Issue: Importing (converting) an App-V version 5.0 package to MSI may result in a files located in the wrong folder. The problem is importing App-V packages on with 32-bit applications on a 64-bit machine may not have the same variable paths defined. The same is true for 64-bit packages imported on a 32-bit machine.
Workaround: Perform the import (conversion) on architecture that match the application in the App-V package. If the package contains a 32-bit application, perform the import and conversion on a 32-bit version of Windows.

Issue: Importing (converting) an MSI package to an App-V package may result in a application that does not install correctly. The problem is Windows Installer packages may contain custom actions and properties that can only be resolved at install time.
Workaround: Instead of importing (converting) the package, use Discovery to repackage the MSI into an App-V package.