Flexera Community Knowledge Base

cancel
Showing results for 
Search instead for 
Did you mean: 
Knowledge Base Categories
Welcome! The Flexera Community is where all of us share knowledge and gain insight on Flexera products. We aim to ensure this is an inclusive and inviting experience. While we encourage lively conversation, we do insist that you follow our guidelines. Postings may be edited or deleted if they violate these guidelines Terms of Use or Privacy Policy. Do… Be respectful and helpful to those with questions Mark an answer as an “accepted solution” if it helps resolve the problem Provide constructive and thoughtful feedback to those with problems to solve Share what worked and what you learned whenever possible Don’t… Post spam, repetitive content, solicitations or links to products or services not offered by Flexera Share copyrighted information without permission unless it is within the fair use standards of posting small excerpts or a link Use the community as a channel for marketing or promotions; links that add value to discussions or help answer questions are permitted Make threats, use hateful language, post harassing messages or launch personal attacks Post time-sensitive requests; contact Flexera Support if you are under a deadline   Reporting violations and addressing grievances Tell us if you believe someone has violated these guidelines by emailing community@flexera.com. Be sure to include as much detail and context as possible.
View full article
As you're exploring Flexera Community, you likely want maximize your experience. Never fear! This is a full roadmap for you from start to success.
View full article
Symptoms: When normalizing a data Mashup using a SCCM database, the process completes successfully but the mashup fields do not appear in Flexera Data Platform Analyze Report.  Solution: Mashup normalize process works fine with .zip or .csv data source type. The below is a workaround and we will do a permanent fix in further release. 1. Zip the mashup data source from data source database: a. Open "..\BDNA\Data Platform\Bin\Extractor.exe" b. Upload the mashup extract config file. c. Complete the sccm connection fields d. Click "Test" button to make sure SCCM database is connected, then click execute button to zip the mashup data source 2. Then normalize the .zip file instead as a mashup data source.  
View full article
What are the correct requirements to integrate SVM 2019 to WSUS for publishing third-party patches? This is what we will explain in this article in detail
View full article
Intel has recently disclosed new 'speculative execution' vulnerabilities   that affect millions of computers with Intel processors. Many tech giants already issued a patch, including Microsoft. Software Vulnerability Manager can detect the security flaws and the missing Microsoft update KB that needs installing. The vulnerabilities are listed in SA89022 and detected on systems that are not obstructed to fetch Windows Update information from the source that has been configured under Configuration > Settings in SVM 2019. (Settings > Assessment > Scan Configuration in SVM Next).  NOTE: If your Windows Update setting in SVM 2019 is set to Managed Server or WMI Check (alone), ensure that KB4499164 (Windows 7) and all other required KBs (for other flavors) are imported to your System Center Configuration Manager database, or imported manually in WSUS and Approved for all hosts. Only then clients can get the data which systems are missing the KBs.  If your Windows Update settings are set to Online servers or CAB file, you should get the KBs directly in any of your SVM editions only on the systems that have unobstructed online access.  Tip: Create new host-based Smart Group and use the Missing KB criteria to track every system being impacted in a separate group for proper visibility. 
View full article
Summary IBM Practice Guide Synopsis How do I configure IBM applications? How do I configure IBM PVU licensing?   Discussion This is a guide to project planning, installation, configuration, and operation of FlexNet Manager® for IBM. The IBM Practice Guide has been created to help answer some of your FlexNet Manger and IBM Software License Optimization questions. This Practice Guide describes strategies for managing IBM licenses while providing IBM licensing knowledge. We've also outlined an iterative approach (using milestones and work streams) to conducting an IBM license reconciliation project. Using this iterative approach, with each milestone and work stream, your IBM licensing position becomes more refined, optimized and mature, delivering faster results.   Additional Information Customers, partners & employees can access the IBM Practice Guide through the Flexera Learning Center which is available from the Flexera Community. If you're not able to access the guide, please contact learning@flexera.com
View full article
All on prem customers who are currently whitelisting 185.109.133.99 will need to whitelist https://sync.secunia.com Discussion Flexera will be rolling out DNS updates to move  https://sync.secunia.com from HSK to AWS on May 24 th . The IP address is for the URL https://sync.secunia.com changing to 34.247.11.96 We recommend that any whitelisting you have in place leverage the URL and not the IP address so that any future IP address changes will not affect you. If you have whitelisted this IP for any specific reason then please update as highlighted above to ensure the product continues to function as expected.  
View full article
Summary Object reference not set to an instance of an object: when importing intermediate data from a Beacon. Symptoms When performing a compliance import this fails with the following error message and the intermediate data from the Beacon that has been uploaded is moved into the 'Bad packages' folder under the default path 'C:\ProgramData\Flexera Software\Beacon\IntermediateData'. No intermediate path specified, using default output path C:\ProgramData\Flexera Software\Beacon\IntermediateData. Performing import ERROR: Loading package file C:\ProgramData\Flexera Software\Beacon\IntermediateData\I[S=<ConnectionName > ]_20140901082122.zip has failed Object reference not set to an instance of an object. Moved bad package I[S= ConnectionName ]_20140901082122.zip to folder C:\ProgramData\Flexera Software\Beacon\IntermediateData\BadPackages Importing from 'ManageSoft' [type: ManageSoft] (primary connection)   Cause This issue is caused by a trailing space in the 'Connection Name' when this was entered in the Beacon User Interface (UI), the space can be seen in the example highlighted below and also in the 'package.xml', '<ConnectionName>' element when you browse the contents on the .zip file. The space in the following example of the package.zip is between the 'e' at the end of connection name and the closing brace ']'. 'I[S=ConnectionName ]_20140901082122.zip'   Resolution This issue is resolved be editing the ?Connection Name? column for the connection in question and ensuring there are no trailing spaces in the name. Once this has been update run the import again on the beacon and when the file has been uploaded to the Intermediate folder perform a compliance import and the data should be imported.   Additional Information Additional information on the compliance import can be located in the FNMP Operations Guide and the System Reference guide for the command line options.
View full article
Description The InstallCognos.ps1 script fails with the following error when the service account is a member of an AD group that doesn't exist. ERROR: The Flexera Analytics install script failed: An error occurred while enumerating through a collection: An error occurred while enumerating the groups. The group could not be found.   Replication Scenario   Workaround Open InstallCognos.ps1 in a text editor  Search for the string "Test-LocalAdministrator"  Comment out the following lines of code like so:  #if ($serviceUser -ne $null -and -not (Test-LocalAdministrator $serviceUser)) {  # throw "The specified service user, $serviceUser must exist and be a member of the local administrators group. The user's domain must also exist and be contactable.";  #}  Execute InstallCognos.ps1 again Version Fix Target   Resolution This issue is being tracked under  IOJ-1913873.
View full article
While running the user console config wizard , on the "Connect to BDNA Data Platform" screen the error message received is : Connect attempt to BDNA Data Platform service failed Things to check: 1. Ensure your data platform and user console server can communicate with each other over the specified port (http/https). 2. Try using hostname/IP in the User Console config wizard. 3. If the network/port connectivity between the servers is fine but you still cannot get through this page, validate the user console logs. If you see the below error in setup.log ERROR UI: System.Xml.XmlException: Data at the root level is invalid. Line 1, position 1. OR below error in UX.log The remote server returned an error: (500) Internal Server Error. you can use below workaround: In <Data Platform Install directory>/Conf/Norm.configuration.config file: Update the value of <BI_CONFIG_NORMALIZE_BI_SERVER_URL> to the IP of the User Console server. Restart Data Platform service and then try to re run the User Console config wizard. This should work.
View full article
How to use the tpsconfig executable file to activate the AdminStudio product . Discussion Launching the tpsconfig.exe would display the AdminStudio Product Activation dialog where a serial number can be entered for node locked licenses to activate the product. This dialog also has a link to configure the License server information for concurrent licenses. The tsconfig.exe accepts the following parameters when using a commandline prompt:   /repair Repair license /return Return license to account /activate Activate license /info Show license information /helpShow help information /h Show help information /? Show help information /no_internet Perform offline transaction only /serial_number Serial Number /verbose Log Verbose Information /silent Perform silent transaction /set_license_server Set license server /feature Feature Enum /uninstall_service Uninstall licensing service
View full article
This article discusses how to setup a clean machine for repackaging applications with AdminStudio. Discussion It's recommended to repackage applications on clean machines as it ensures that all necessary changes that are made by the installation are picked up through the repackaging process since they will not already exist on the machine. A clean system typically consists of a computer that has only the operating system and its service packs installed. T he repackaging developer must consider the minimum set of files ALL computers will initially possess. This set of files is the base case, or lowest common denominator. This base case or LCD is a computer image EVERY user will be guaranteed to have ? almost like a template for a systems administrator. A good channel of communication with your company's Systems Administrator before creating the initial repackaging snapshot will be time well spent. Ask them about their current set of default user images for various departments, and identify what applications are guaranteed to exist for all images. Always repackage using the image you define to be your base case or many wasted hours can be spent trying to understand dependencies and prerequisites, attempting to make some application function as intended. If the base image is properly defined, repackaging will generate a robust installation. Each computer will always be capable of running the repackaged program(s). A good definition of a base image will cut down on time spent debugging or reinstalling broken applications. The Repackager can be configured on a clean machine by either:   Launching Repackager Remotely If you have network connectivity from a clean machine to the computer that contains the AdminStudio Repackager tool, you can launch the repackager remotely by following the steps described in the link.   Installing Repackager on a clean machine If you do not have network connectivity from a clean machine to the computer that contains the AdminStudio Repackager tool, you can install the standalone repackager on the clean machine by following the steps described in the link.     Related Documents About Repackaging on Clean Systems
View full article
In order to support Three Server Redundancy, there are elements of a license file which are required to be configured for a successful triad license server set up. These elements are specific to the environment in which the servers are being deployed and are therefore left to be configured by the end user rather than through the Product and Licensing Center. This article discusses these elements and how to configure them in order to set up a successful triad license server set up which supports Three Server Redundancy. Discussion The license file generated by the Product and Licensing Center for a triad license server configuration will look similar to the following (The serial number and signature have been removed): SERVER this_host 00137238bb88 SERVER this_host 002186948BF2 SERVER this_host 000d56289d8d VENDOR mvsn USE_SERVER INCREMENT IAEE mvsn 12.00000 permanent 1 VENDOR_STRING=REAL \ DUP_GROUP=NONE ISSUER="Flexera Software, Inc." \ ISSUED=11-may-2011 SN=XXXXXXX-XXX-XXXXXXXXXX TS_OK SIGN="XXXX \ XXXX XXXX XXXX XXXX XXXX XXXX XXXX XXXX XXXX XXXX XXXX XXXX \ XXXX XXXX XXXX XXXX XXXX XXXX XXXX XXXX XXXX XXXX XXXX XXXX \ XXXX XXXX XXXX XXXX XXXXX In this state, this license file will not support a triad license server configuration. The file must be modified prior to using it in a triad license server configuration. First, the hostname of each individual server needs to replace the ?this_host? placeholder that is generated in the license. Each hostname needs to correspond to the HostID on the SERVER line. In the above example, assume the first HostID, 00137238bb88, corresponds to the hostname LS1.flexerasoftware.com, the second HostID, 002186948BF2, corresponds to the hostname LS2.flexerasoftware.com, and the third HostID, 00d56289d8d, corresponds to the hostname LS3.flexerasoftware.com. After replacing each ?this_host? placeholder with the correct hostname, the file would look like: SERVER LS1.flexerasoftware.com 00137238bb88 SERVER LS2.flexerasoftware.com 002186948BF2 SERVER LS3.flexerasoftware.com 000d56289d8d VENDOR mvsn USE_SERVER INCREMENT IAEE mvsn 12.00000 permanent 1 VENDOR_STRING=REAL \ DUP_GROUP=NONE ISSUER="Flexera Software, Inc." \ ISSUED=11-may-2011 SN=XXXXXXX-XXX-XXXXXXXXXX TS_OK SIGN="XXXX \ XXXX XXXX XXXX XXXX XXXX XXXX XXXX XXXX XXXX XXXX XXXX XXXX \ XXXX XXXX XXXX XXXX XXXX XXXX XXXX XXXX XXXX XXXX XXXX XXXX \ XXXX XXXX XXXX XXXX XXXX" In addition to specifying the hostname for each license server, the port on which the license server should communicate needs to be defined as well. This port can be any port between 1024 and 64000 that is not in use by another process on the system. It is strongly advised that the same port be specified for all three servers, as this makes administration much simpler. In this example, port 12345 has been selected and the file would now look like: SERVER LS1.flexerasoftware.com 00137238bb88 12345 SERVER LS2.flexerasoftware.com 002186948BF2 12345 SERVER LS3.flexerasoftware.com 000d56289d8d 12345 VENDOR mvsn USE_SERVER INCREMENT IAEE mvsn 12.00000 permanent 1 VENDOR_STRING=REAL \ DUP_GROUP=NONE ISSUER="Flexera Software, Inc." \ ISSUED=11-may-2011 SN=XXXXXXX-XXX-XXXXXXXXXX TS_OK SIGN="XXXX \ XXXX XXXX XXXX XXXX XXXX XXXX XXXX XXXX XXXX XXXX XXXX XXXX \ XXXX XXXX XXXX XXXX XXXX XXXX XXXX XXXX XXXX XXXX XXXX XXXX \ XXXX XXXX XXXX XXXX XXXX" Optionally, the PRIMARY_IS_MASTER keyword can be used to specify that the first server in the list always be the primary server when it is up and running and communicating with at least one other server in the triad. After adding the PRIMARY_IS_MASTER keyword, the license file now looks like: SERVER LS1.flexerasoftware.com 00137238bb88 12345 PRIMARY_IS_MASTER SERVER LS2.flexerasoftware.com 002186948BF2 12345 SERVER LS3.flexerasoftware.com 000d56289d8d 12345 VENDOR mvsn USE_SERVER INCREMENT IAEE mvsn 12.00000 permanent 1 VENDOR_STRING=REAL \ DUP_GROUP=NONE ISSUER="Flexera Software, Inc." \ ISSUED=11-may-2011 SN=XXXXXXX-XXX-XXXXXXXXXX TS_OK SIGN="XXXX \ XXXX XXXX XXXX XXXX XXXX XXXX XXXX XXXX XXXX XXXX XXXX XXXX \ XXXX XXXX XXXX XXXX XXXX XXXX XXXX XXXX XXXX XXXX XXXX XXXX \ XXXX XXXX XXXX XXXX XXXX" That is the extent of the required changes that must be made to the generated license file in order to support Three Server Redundancy through a triad license server configuration. At this point, the license can be copied to all three servers and the license manager started on each, starting with the Primary, to establish a quorum and begin serving licenses. Oftentimes, the ports used by the license manager need to be opened in the corporate firewall in order to allow clients to check out licenses from the license manager. If this is a necessity, the license file should be modified to specify the port which the vendor daemon runs on as well. This is then specified on the VENDOR line using the PORT=<PORT> notation. In this example, the mvsn vendor daemon is going to be configured to run on port 1234. The license file now looks like: SERVER LS1.flexerasoftware.com 00137238bb88 12345 PRIMARY_IS_MASTER SERVER LS2.flexerasoftware.com 002186948BF2 12345 SERVER LS3.flexerasoftware.com 000d56289d8d 12345 VENDOR mvsn PORT=1234 USE_SERVER INCREMENT IAEE mvsn 12.00000 permanent 1 VENDOR_STRING=REAL \ DUP_GROUP=NONE ISSUER="Flexera Software, Inc." \ ISSUED=11-may-2011 SN=XXXXXXX-XXX-XXXXXXXXXX TS_OK SIGN="XXXX \ XXXX XXXX XXXX XXXX XXXX XXXX XXXX XXXX XXXX XXXX XXXX XXXX \ XXXX XXXX XXXX XXXX XXXX XXXX XXXX XXXX XXXX XXXX XXXX XXXX \ XXXX XXXX XXXX XXXX XXXX" After configuring the license as above, the ports 12345 and 1234 must be opened in the firewall to ensure that clients are able to check out licenses.
View full article
This article details steps to take to resolve AdminStudio error 13003 reverting virtual machine to snapshot AutoRepack_Base. Symptoms While using Automated Application Converter (AAC) to automatically repackage setup packages in Adminstudio, one may see the error message -> 'Error 13003 reverting virtual machine to snapshot AutoRepack_Base'. Cause The error message 13003 is returned by the VMware VIX api calls. This error means that file by that name could not be found.   Resolution The possible cause of this error could be using a different VMWare machine than the one mentioned while configuring AAC. Please follow the steps below to check this - Launch AAC and open the project you are working on Browse to the 'Machine' tab Check the 'Path' column value for the machine you are trying to use for the repackaging process Make sure that the Path is valid and points to the right VMWare image Launch the Application Conversion Process again.   Additional Information For more information on Automated Application Converter, please refer to the User Guide in the attachments   For more information about the VMWare VIX Api calls, please refer to this article:http://vmware.ie/support/developer/vix-api/vix16_reference/errors/errors.html
View full article
While using AdminStudio, you may receive an error locating AdminUIFramework.dll when attempting to run the Remote Repackager. Please activate the product to resolve this error. Symptoms You may receive an error locating AdminUIFramework.dll when attempting to run the AdminStudio.  This is caused by not having correctly activated the copy of AdminStudio from which you're sharing the Remote Repackager folder. Since the Remote Repackager is not intended to function in Evaluation mode, the licensing library (AdminUIFramework.dll) gets dynamically generated by the activation process. Resolution To resolve this error, please activate your copy of AdminStudio. If activating AdminStudio does not resolve this error, please contact Flexera Software Technical Support.
View full article
In order to operate some AdminStudio tools, AdminStudio users require specific database  permissions. Depending upon the type of user, you may wish to be more selective in the permissions you assign to these users. Synopsis In order to operate some AdminStudio tools, AdminStudio users require specific database permissions.Depending upon the type of user, you may wish to be more selective in the permissions you assign to these users. Every AdminStudio user will need at a minimum read privilege to every table in the Application Catalog. The minimum permissions are described below, based upon the type of operation you want the user to perform. General User Process General administrative processes cover a range of activities such as adding groups, moving packages around, adding comments, updating extending attributes, etc. For example, these tables include cstblPackage, cstblGroups, and cstblGroupPackages Any Application Catalog table which is not referenced explicitly in the discussion for the other AdminStudio processes should be considered a general user administrative table. Most AdminStudio users should have write access to these tables. Import Process The user importing MSI packages, merge modules, or just about anything will require write access to a significant set of Application Catalog tables depending on the type of import. For example: MSI package file For MSI package file import operations, those Application Catalog tables with a csmsi prefix are populated. Merge modules For merge module import operations, the csmsm prefixed tables are used. Patches For patch import operations, the cspch prefix tables are used. OS snapshots For OS snapshot import operations, the osc prefix tables are used. Occasionally, the Import process will need to create new tables in the Application Catalog to support the import of custom table data. Either the necessary server privileges need to be given for these users, or the import of custom table data needs to be disabled within the Application Manager Options dialog box. Validation Process For this process, the user will need to be able to write entries into the cstblValidationResults and cstblValidationConfiguration tables. Dependency Scanning Process For this process, the user will need to be able to write entries into the cstblPackageExeDependencies table. Conflict Detection and Resolution Process For this process, the user will need to be able to write entries into the cstblConflict prefixed table names. Patch Impact Analysis Process For this process, the user will need to be able to write entries into the cstblPatchConflict prefixed table names. This process will create and delete some temporary tables and, as such, the user performing this process should have the necessary server privileges to perform these operations. Package Auto Import Process The Package Auto Import process will ultimately generate a series of Import operations, and so the user performing these operations should have the Import process rights described above. If the user wants to edit these operations in the Wizard, then they will need write accession to the cstblSubscribed prefixed tables. Workflow Operations Process For this process, the user will need to be able to write entries into the wftbl prefixed table names. Tools Properties Operations For this process, the user will need to be able to write entries into the wftblTools table name. Job Manager Process For this process, the user will need to be able to write entries into the As prefixed table names. Pre-Deployment Testing For this process, the user will need to be able to write entries into the pdt prefixed table names. Note: A number of processes within AdminStudio generate data which can subsequently be deleted by the AdminStudio user. Any discussion of the minimum privileges required for a specific AdminStudio process will also imply the privileges to delete this same data. Additional Information If you have AdminStudio Enterprise Edition, you can assign permissions to individual users using the Role functionality in AdminStudio Enterprise Server.
View full article
This article discusses how to enable logging in Workflow Manager. Synopsis This article discusses how to enable logging in Workflow Manager. Discussion Locate the wwwroot folder where Workflow Manager is installed (Example: <AdminStudioEnterpriseServer>\wwwroot). Open web.config in a text editor such as Notepad. Locate the following section in web.config: <!--Web trace module log level: 0,1,2,3,4. 4 is the higest level, log everything--> <system.diagnostics> <switches> <add name="ISTraceSwitch" value="4"/> </switches> </system.diagnostics> Set the ISTraceSwitch value to 4, and save the file. Next, locate the wwwroot\Log folder. You may see logfiles generated in the format of 'aes483b3dd7-a141-4680-92ba-a631c423a2d2.log'. Copy these logs to a separate folder so that you are easily able to identify logs created during the reproduction of the issue. Reproduce the issue, and send the resultant logfiles to technical support. In the case no logs are generated, make sure to notify Support of this behavior. Additional Information When providing the Application Event log to Support, it is extremely important to provide timestamps that correspond to when the issue was observed, and as well take into account differences in timezones between the client and the web server. Making sure to provide this information will ensure that Support is able to address the issue in the quickest and most accurate manner.
View full article
This article details how to set-up the AdminStudio Standalone Repackager Setup. Synopsis In AdminStudio, a Standalone Repackager Setup executable is available to install on clean machines. This article explains how to acquire this utility. Discussion AdminStudio includes a standalone setup for Repackager. This allows you to install Repackager by itself on a clean machine to repackage applications. The repackaged setup can then be transferred to a build machine with AdminStudio installed or copied to a network location. The download is in the form of a setup.exe that should be launched on the clean machine.   The Standalone Repackager is available on the installation DVD in the Tools folder entitled "StandaloneRepackager.exe". It is also available in the Product and License Center. To download the Standalone Repackager: 1. Login to the Product and License Center. 2. If applicable, click the AdminStudio hyperlink from the Product List. 3. Click the AdminStudio (Enterprise, Professional, or Standard) Edition hyperlink from the Product and File Downloads list. 4. Click the StandaloneRepackager.exe   Additional Information For more information on the Repackager, see Help Library topics: Installing Repackager on a Clean Machine Repackaging Wizard Best Practices
View full article
AdminStudio offers two methods of repackaging that can migrate a legacy setup in any format into MSI format. These two methods are the Installation Monitoring and Snapshot methods. Both methods are explained and compared in this article. Synopsis AdminStudio offers two methods of repackaging that can migrate a legacy setup in any format into MSI format. These two methods are the Installation Monitoring and Snapshot methods. Both methods are explained and compared in this article. Discussion Installation Monitoring The Installation Monitoring method of repackaging involves watching a system for any processes that are created during the installation. In this way, Repackager can identify changes being made to the target system. The Installation Monitoring method has advantages and disadvantages in comparison to the Snapshot method. Installation Monitoring Advantages Installation Monitoring is significantly faster than the Snapshot method.   It can detect install "intent." This refers to files or registry entries that were intended to be installed but were not actually installed because the file or registry entry already existed on the target machine. However, this will not detect conditional logic that was present in the installation and was not actually executed. For example, consider the following two cases: Case 1: The setup calls CopyFile and overwrites a.dll with a.dll from the installation. Snapshot will not capture this because the net effect is the same. However, Installation Monitoring will because the CopyFile function is logged. Case 2: The legacy installation uses a call to GetVersionEx to conditionally install the file only if the version to be installed is greater than the installed version of the file. If the function that copies the file is not called due to this conditional logic the install intent is not captured. Installation Monitoring is also less prone to capturing extraneous file and registry data compared to the Snapshot method. Installation Monitoring Disadvantages It cannot detect changes made by processes already running prior to the monitoring session or made via DOS. For more information, see the Additional Information section.   Installation Monitoring also cannot detect manual changes made in Explorer without some steps being taken prior to Repackaging. For more information on this and the steps that need to be taken, see the Additional Information section. Installation Monitoring Output Files The updated.isr and *.spy output files are created by the Installation Monitoring method. For more information on these and other repackaging files, see the Additional Information section. Snapshot The Snapshot method of repackaging involves taking a snapshot of a system setup as a baseline configuration, running an installation, and then taking a second snapshot of the system after the installation. The information provided by comparing the two snapshots is stored in an .inc file and used to convert the installation into .msi format. When using the Snapshot method, it is important to use a clean system for your initial baseline snapshot. If you do not do so, some system files may already be present initially and, therefore, will not be captured during repackaging. The Snapshot method has advantages and disadvantages in comparison to the Installation Monitoring method. Snapshot Advantages Due to the nature of the Snapshot method, all changes made to the target system between the snapshots will be recorded. This includes information Installation Monitoring cannot capture, such as changes made by processes already running prior to the monitoring session or made via DOS. There are also no added steps to allow the Snapshot method to record manual changes made in Explorer. Snapshot Disadvantages The Snapshot method will take longer than Installation Monitoring.   It cannot detect install "intent." For more information on install intent, see the corresponding advantage listed in the Installation Monitoring section of this article. Snapshot Output Files The standard.nir file is created by the Snapshot method. For more information on this and other repackaging files, see the Additional Information section. Output Files Created by Both Repackaging Methods The following files are created by both repackaging methods: Options.ini, <product name>.inc, deleted.isr, Repack.log, *.irp, <ExclusionList>.ini, and Options.ini. For more information on these and other repackaging files, see the Additional Information section. Additional Information For more information on the files created by Repackager, see the Help Library topic Files Associated with Repackager. Snapshot and Installation Monitoring are also documented in the Help Library topic Repackaging Methods.
View full article
This article describes when to use Adminstudio Tuner versus InstallShield. Question When do I use AdminStudio Tuner versus InstallShield? Answer InstallShield is used to make any modifications necessary to the base package. It is also used to create new MSI packages. Additionally, it can also be used to add more complex functionality such as custom actions via a transform. Tuner can be used to create response transforms and make small modifications to a package via a transform. Additional Information For more information on transforms, see InstallShield Help Library topic Creating Transforms
View full article