AdminStudio 2016
Release Notes
23 June 2016
Introduction
AdminStudio Suite powers an enterprise's daily application readiness process for inventory, rationalization, packaging, and compatibility testing of physical, virtual, and mobile applications, ensuring faster service delivery and predictable deployment.
AdminStudio’s automation, integration with leading software distribution tools, and workflow capabilities help companies streamline day-to-day application packaging operations and reduce the time and cost of application virtualization, Windows migrations and mobile application deployment.
Trusted by more than 10,000 organizations, AdminStudio Suite eliminates the need for multiple standalone tools and provides an integrated solution that is adaptive and scalable to changing business priorities.
New Features in AdminStudio 2016
This section lists the new features that are included in AdminStudio 2016:
• | Import and Test Mac OS X Desktop Applications |
• | Ability to Inspect and Test Complex Installer Executables |
• | Improved FlexNet Manager Suite Integration |
• | Enhanced Automation Capabilities to Streamline Application Import and Testing |
• | Automated Application Converter Enhancements |
• | New Wizard to Install and Launch Windows Installer Packages on a Virtual Machine for Testing |
• | Productivity Shortcuts |
• | New System Center Configuration Manager Settings View |
Import and Test Mac OS X Desktop Applications
In its 2016 release, AdminStudio is extending its application readiness capabilities to Mac OS X desktop applications. You can now import Mac OS X applications into the Application Catalog for testing and distribution to a JAMF Casper Suite server. Additionally, because App Portal also supports Casper, when you publish DMG and PKG files to Casper, you can choose to automatically generate App Portal catalog items for those packages.
• | Import Mac OS X Desktop Applications (DMG and PKG Files) |
• | Import Links to OS X Desktop Applications in the Mac App Store |
• | Test Mac OS X Desktop Applications |
• | Publish Mac OS X Desktop Applications to Casper With Integration to App Portal |
Import Mac OS X Desktop Applications (DMG and PKG Files)
In AdminStudio 2016, you can import Apple disk images (.dmg) and Mac OS X installer packages (.pkg) into the Application Catalog for inspection, customization, testing, and distribution to Casper.
The Package Type Selection panel of the Import Wizard now includes two new selections to support the import of Mac OS X desktop applications into the Application Catalog.
New Apple Installer Packages on Package Type Selection Panel
The following are the two new package types that were added to the Package Type Selection panel to support Mac OS X desktop applications:
• | Apple Disk Image package (.dmg)—When you double-click a .dmg file, an Apple disk image is “mounted” as a volume within the Finder. To install the application, you usually drag the application icon from the disk image into the Applications folder. |
• | Apple installer package (.pkg)—Double-clicking a .pkg file launches the Apple installer application, where the package is installed by proceeding through an installation wizard. |
You can import these newly supported package types as single applications, part of a batch import of applications in a selected folder, or as part of a monitored directory using the Package Auto Import feature. You can also publish these package types to a JAMF Casper Suite server.
Inspecting Bundled Packages
Both .dmg and .pkg files can contain child .dmg or .pkg files bundled within the file. These bundled packages can be viewed on the imported package’s Bundled Packages tab of the Catalog Deployment Type View. For more information, see Inspect Bundled Applications in DMG and PKG Installers.
Customizing Installer Settings
The installer settings of a .pkg file can be modified on the Pkg Installer Choices tab of the Catalog Deployment Type View. For more information, see Customize Apple Installer Package PKG Installer Settings.
Inspect Bundled Applications in DMG and PKG Installers
If an Apple disk image package (.dmg) or Apple installer package (.pkg) contains child packages bundled within it, those child packages will be listed on the new Bundled Packages tab of the Catalog Deployment Type view.
Bundled Packages Tab of Catalog Deployment Type View for Apple Installer Package (.pkg)
When the imported .dmg or .pkg file is tested, each of these child packages is also tested, and the combined test results are listed in Test Center, as described in Combined Testing of Child Applications of DMG and PKG Files.
Note • AdminStudio will only inspect Mac OS X package files one level deep. If a .dmg or .pkg package contains another .dmg or .pkg package bundled within it, that child package will not be inspected.
Customize Apple Installer Package PKG Installer Settings
Just as a Windows Installer package can be customized by adding a transform file, an Apple installer package (.pkg) can be customized by editing an XML file that is embedded within it. In AdminStudio 2016, the settings defined in a .pkg file’s embedded XML file are displayed on the new PKG Installer Choices tab of the package’s Catalog Deployment Type view.
New PKG Installer Choices Tab of Catalog Deployment Type View for Mac PKG Installer
The PKG Installer Choices tab lists all settings that have been defined in that .pkg file’s embedded XML settings file by the application manufacturer. To customize this installer (such as to prepare it for silent installation by Casper), you can make changes to the settings on this tab and then click Update Installer Choices. AdminStudio will then save your changes in the package’s embedded settings file.
For each installer Choice listed on the PKG Installer Choices tab, the following options are available:
Option |
Description |
||||||
Visible |
This option can be either selected or not selected:
|
||||||
Selected |
This option can be either selected or not selected:
|
||||||
Enabled |
This option can be either selected or not selected:
|
||||||
Custom Location |
If this choice setting explicitly permits the user to specify a user-defined installation path, the path entered in this field would populate the user-defined installation path when it is displayed in the installer. |
Note • Modifying the installer choices of an Apple installer package does not affect the digital signature of the package.
Import Links to OS X Desktop Applications in the Mac App Store
In previous releases, you could import links to iOS mobile apps in the iTunes App Store. To do this, you selected, Apple Store on the Public Store Selection panel of the Import Wizard.
In AdminStudio 2016, in addition to being able to import links to iOS mobile apps in the iTunes App Store, you can now also import links to Mac OS X desktop applications in the Mac App Store. On the Public Store Selection panel of the Import Wizard, you now have two different Apple public store options:
• | Apple iOS App Store (for iOS mobile apps) |
• | Apple Mac App Store (for OS X desktop apps) |
Apple Mac App Store Option on Public Store Selection Panel
After you have imported a Mac OS X desktop application into the Application Catalog, you can test it and distribute it to a Casper server. For more information, see:
• | Test Mac OS X Desktop Applications |
• | Publish Mac OS X Desktop Applications to Casper With Integration to App Portal |
New Field That Identifies Genre of Mac Public Store Apps (Both iOS and OS X)
For Apple public store apps imported into the Application Catalog (both iOS and OS X apps), a new Genre(s) field is listed on the Package Information tab of the Catalog Deployment Type View, which lists the category that the application belongs to in the public store.
Genre(s) Field on Package Information Tab
Test Mac OS X Desktop Applications
You can use Test Center to test all three types of supported Mac OS X desktop applications: DMG files, PKG files, and Mac App Store apps. Tests are available in the Operating System Compatibility and Best Practices and Risk Assessment test categories.
Test Results for Mac OS X Desktop App
In AdminStudio 2016, the following new tests for Mac OS X desktop applications have been added:
Category |
Test Name |
Description |
Supported Package Types |
Operating System Compatibility |
MAC001 |
Deprecated Property List Keys |
DMG, PKG |
MAC002 |
Deprecated Frameworks |
DMG, PKG |
|
MAC003 |
Application Requires Specific Minimum OS Version |
DMG, PKG, Mac App Store |
|
MAC004 |
Deprecated APIs |
DMG, PKG |
|
MAC005 |
Application Requires 64-bit Processor |
Mac App Store |
|
MAC006 |
Removed Frameworks |
DMG, PKG |
|
MAC007 |
Removed APIs |
DMG, PKG |
|
Apple Best Practices |
MAC701 |
Recommended Property List Keys |
DMG, PKG |
MAC702 |
Code Signature |
DMG, PKG |
|
MAC703 |
Volume Purchase Program |
Mac App Store |
|
MAC704 |
Allows In-App Purchases |
Mac App Store |
Combined Testing of Child Applications of DMG and PKG Files
If an Apple disk image package (.dmg) or Apple installer package (.pkg) contains child packages bundled within it, those child packages are also tested when the parent package is tested. Test results of the parent package and all of its child packages are combined and are displayed in Test Center.
Consolidated Test Results for Apple Installer Package (.pkg)
When you view detailed test results, the name of the child .dmg, .pkg, or .app file that generated the error or warning is listed.
Detailed Consolidated Test Results for Apple Installer Package (.pkg)
Publish Mac OS X Desktop Applications to Casper With Integration to App Portal
In AdminStudio 2016, you can publish Mac OS X desktop applications (DMG, PKG, and Mac App Store apps) to a JAMF Casper Suite server.
Because AdminStudio is also integrated with App Portal (which also supports Casper), you can choose to automatically create App Portal catalog items for DMG and PKG applications in your Application Catalog when you publish them to a Casper server.
• | Setting Up a Connection to a Casper Server |
• | Automatically Creating App Portal Catalog Items for DMG and PKG Applications |
• | Viewing Casper Deployment Data for an Application |
Setting Up a Connection to a Casper Server
On the Server Options > Distribution Options tab of the Application Manager Options dialog box, you can now create a named connection to a Casper server.
Named Connection to a Casper Server
After you select Casper Distribution Plugin from the Deployment Type field, the settings required for connecting to a Casper server are listed.
Note • Casper supports multiple server infrastructures, but AdminStudio only supports the File Share Distribution Points infrastructure, and copies packages to a UNC File Share Distribution Point in Casper. AdminStudio currently does not support copying packages to JDS Instances, Cloud Distribution Points, Software Update Servers, or NetBoot Servers.
Automatically Creating App Portal Catalog Items for DMG and PKG Applications
When you distribute DMG and PKG applications to Casper Suite Server, you can instruct AdminStudio to automatically create App Portal catalog items for each of those applications.
To do this, first set up a named connection to a Casper server and connect to the Flexera Service Gateway. Then, open the App Portal Information tab of the DMG or PKG application’s Application View, and click on the Categories field to open the Categories dialog box. On the Categories dialog box, select the Notify Flexera Software App Portal on publish of current application option and select one or more App Portal categories where the catalog item will be available.
Selecting App Portal Options on Categories Dialog Box
When this application is published to Casper, a catalog item in the selected category will automatically be created, and the Catalog Item field on the App Portal Information view will display the App Portal Catalog ID for that catalog item.
Catalog Item Field on App Portal Information Tab
Note • If an App Portal catalog item has not been created for an application, the Catalog Item field will display Not Published to App Portal.
Viewing Casper Deployment Data for an Application
In AdminStudio 2016, you can view and modify Casper deployment settings for Mac OS X desktop applications on the new Casper Deployment Data tab of the Catalog Deployment Type View.
Casper Deployment Data Tab of Catalog Deployment Type View
The Casper Deployment Data tab can include up to three subtabs that display Casper deployment data: General, Options, and Limitations.
Note • The Options and Limitations subtabs are not displayed for Mac App Store apps.
The Casper Deployment Data tab displays the following properties:
Subtab |
Property |
Description |
|||||
General |
Server Name |
Name of the Casper server. |
|||||
Category |
Category in Casper that the package will be added to. Note • Casper lets you create custom categories. If AdminStudio has matched this application to an entry in the Application Recognition Library (ARL), AdminStudio will use the ARL category when publishing to Casper, creating it if necessary. |
||||||
Info |
Information to display to the administrator when the package is deployed or uninstalled |
||||||
Notes |
Notes to display about the package (such as the name of the person who built it and when it was built). Note • Not displayed for Mac App Store apps. |
||||||
Free |
Indicates whether or not the Mac App Store app is available for free (True) or whether it requires payment (False). Note • Only displayed for Mac App Store apps. |
||||||
Options |
Priority |
Priority to use for deploying or uninstalling the package. For example, a package with a priority of 1 is deployed or uninstalled before other packages. When several applications are deployed together, the one with the highest priority is installed first. Therefore, if one application requires that another application be installed first before it can be successfully installed, you should assign the required application a higher priority (lower number) than the dependent application. |
|||||
Fill user templates (FUT) |
Set this property to True to fill new home directories with the contents of the home directory in the package's Users folder. This setting can be changed when deploying or uninstalling the package using a policy.l Note • Only applicable to DMG packages. |
||||||
Fill existing user home directories (FEU) |
Set this property to True to fill existing home directories with the contents of the home directory in the package's Users folder. This setting can be changed when deploying or uninstalling the package using a policy Note • Only applicable to DMG packages. |
||||||
Requires restart |
Set this property to True to require that computers must be restarted after installing the package. |
||||||
Install on boot drive after imaging |
Set this property to True to ensure that the package is installed on the boot drive after imaging. Note • This setting is only used when deploying a package with an OS image, like with an OSD. It does not affect day-to-day package delivery. |
||||||
Limitations |
Operating System Requirement |
Enter operating system version numbers, separated by commas, to specify that the package only be permitted to be deployed to computers with these operating system versions. To restrict installation to OS X 10.6.8, 10.7.x, or 10.8, you would enter the following: 10.6.8, 10.7.x, 10.8 |
|||||
Install Only if Available in Software Update |
Set to True to require that this package only be installed if it is available in a software update. |
||||||
Limit Architecture Type |
Set to True to require that this package only be installed on machines matching the selectedArchitecture Type Requirement. |
||||||
Architecture Type Requirement |
If Limit Architecture Type is set to True, select the one of the following to specify the architecture type required to deploy the package:
|
||||||
Substitute Package |
If you want to specify a different package to deploy to computers that do not meet the architecture type requirement, click the Browse button in this field to open the Select Substitute Package dialog box, and select a substitute package from either Casper or the Application Catalog. |
Product Name Displayed in Casper Listed on the Catalog Deployment Type View
For DMG and PKG packages imported into the Application Catalog, a Displayed Product Name field is listed on the Package Information tab of the Catalog Deployment Type View, listing the property that is mapped to the File Name property in Casper.
Displayed Product Name Field on Package Information Tab
Ability to Inspect and Test Complex Installer Executables
In previous releases, you could import complex installer executable files (.exe) that contain bundled Windows Installer packages into the Application Catalog, but you could not view the names of those bundled packages and you could not test those packages. You were limited to just viewing general package information and deployment data.
In AdminStudio 2016, you can now view the names of bundled Windows Installer packages and perform operating system compatibility, application virtualization compatibility, and best practices testing on those bundled packages.
• | Bundled Windows Installer Packages Now Listed on New Bundled Packages Tab |
• | Can Perform Testing of Child Windows Installer Packages of Complex Installer Executables |
Bundled Windows Installer Packages Now Listed on New Bundled Packages Tab
There are multiple installation executable types that can contain embedded Windows Installer packages, including the following:
• | InstallShield InstallScript .exe files |
• | InstallShield Basic MSI installers that are compressed into a setup.exe file |
• | InstallShield Suite Installer .exe files |
• | Wise Package Studio .exe files |
• | Other executable file types that can be uncompressed by 7-ZIP |
In AdminStudio 2016, Application Manager can inspect the child .msi packages in these complex installer .exe files, and display a list of those child packages on the new Bundled Packages tab of the Catalog Deployment Type View.
Bundled Packages Tab of Catalog Deployment Type View / Microsoft .NET Framework 4 Suite
When inspecting these child .msi packages, Application Manager extracts the information about each package, such as product name and version number. This makes it much more likely that Application Manager will be able to assign a Flexera Identifier to these applications.
Note • AdminStudio will only inspect complex installer .exe files one level deep. If a complex installer .exe file contains another complex installer .exe file bundled within it, that child .exe file will not be inspected.
Can Perform Testing of Child Windows Installer Packages of Complex Installer Executables
When a complex installer .exe file is tested, its child Windows Installer packages are also tested and the test results are combined and displayed in Test Center.
Consolidated Test Results for Windows Installer Suite Package
When you view detailed test results, the name of the child Windows Installer package that generated the error or warning is listed.
Combined Suite Installer Test Results
Improved FlexNet Manager Suite Integration
In AdminStudio 2016, several new features have been added to improve integration with FlexNet Manager Suite. You can now generate a list of all applications in the Application Catalog that do not have an associated Flexera Identifier, and can create local Application Recognition Library entries for internally developed, repackaged, or unrecognized applications.
• | Ability to Search Application Catalog for Unrecognized Applications |
• | Ability to Create Local Flexera Identifier Entries for Internal or Repackaged Applications |
• | Ability to Enter FlexNet Manager Suite URL |
Ability to Search Application Catalog for Unrecognized Applications
A Flexera Identifier is a unique code, stored in the Application Recognition Library, that is assigned to applications by FlexNet Manager Suite. It is used to link application information from Application Manager with application information in AdminStudio Inventory and Rationalization, FlexNet Manager Suite, and App Portal.
If both Application Manager and FlexNet Manager Suite are connected to the same Flexera Service Gateway, each time you import an application into the Application Catalog, a search for the application’s Flexera Identifier is performed, and if it is found, it is listed on the General Information tab of the Application View.
However, sometimes an application’s Flexera Identifier is not found, such as when:
• | Incorrect information—The value of the information in the application’s Product Name, Version, Edition, or Publisher fields is either incorrect or too specific. |
• | Internally developed applications—The application has been developed internally. |
• | Repackaged applications—The application has been repackaged. |
In previous releases, there was no way to quickly identify all of the applications in your Application Catalog that did not have an assigned Flexera Identifier. You were required to review each application one by one.
In AdminStudio 2016, you can now generate a list of all applications in the Application Catalog that do not have an associated Flexera Identifier, so that you can search for and assign an existing Flexera Identifier to the application or create a new local Flexera Identifier.
To search Application Catalog for unrecognized applications:
1. | Click Unrecognized Applications in the toolbar of the Application Manager Catalog tab. |
The Application Search Results dialog box opens, listing all applications in the Application Catalog that do not have an associated Flexera Identifier.
2. | Select an application in the list and click Assign Flexera ID. The Flexera Identifier dialog box opens. |
3. | Edit the text in the Search Criteria fields to either correct the information or make it less specific, and then click Search. A list of possible matching applications will be generated and will be listed in the Matching Application(s) list. |
4. | Do one of the following: |
• | Matching application found—If the correct matching application is listed, select it from the list and click OK. The selected Flexera Identifier will be saved in the Application Catalog and will be listed on the General Information tab of the Application View for that application. |
• | Matching application not found—If a matching application is not listed, continue with the steps in Ability to Create Local Flexera Identifier Entries for Internal or Repackaged Applications to create a new local Flexera Identifier. |
Ability to Create Local Flexera Identifier Entries for Internal or Repackaged Applications
In AdminStudio 2016, you can create new local Flexera Identifier entries for the FlexNet Manager Suite Application Recognition Library. These may be required for internally developed applications, repackaged applications, and other applications that are not recognized by FlexNet Manager Suite.
To create a local Flexera Identifier for an application:
1. | Open the Application View of the unrecognized application and click the browse button in the empty Flexera Identifier field. The Flexera Identifier dialog box opens. |
2. | Use the search fields to locate and select a Flexera Identifier. |
3. | If no Flexera Identifier is found, click Create New. The Flexera Local Identifier dialog box opens. |
4. | Enter the following information: |
Property |
Description |
|||||||||||||||||||||
Product Name |
The basic name of the application, excluding references to versions or editions, and without mentioning the publisher. |
|||||||||||||||||||||
Version |
The release number (or release identifier) of an application. |
|||||||||||||||||||||
Edition |
Enter the edition of this application. |
|||||||||||||||||||||
Publisher |
The name of the publisher of this software, responsible for its development and distribution. |
|||||||||||||||||||||
Classification |
To indicate how this application is classified, select one of the following options:
|
5. | Click Create. A confirmation message appears stating that a new local Flexera Identifier has been created. |
Ability to Enter FlexNet Manager Suite URL
In AdminStudio 2016, you can now more easily configure your connection to FlexNet Manager Suite by entering the FlexNet Manager Suite URL in the FNMS URL field on the Flexera Service Gateway (FSG) tab of the Application Manager Options dialog box.
FNMS URL Field on Flexera Service Gateway (FSG) Tab of Options Dialog Box
Enhanced Automation Capabilities to Streamline Application Import and Testing
AdminStudio 2016 offers several new automation features that help you to streamline the application import and testing process.
• | Applications Are Automatically Tested Upon Import |
• | Enhancements to Package Auto Import Feature |
• | Enhanced Control When Using Import Wizard to Perform Batch Import from a Directory |
Applications Are Automatically Tested Upon Import
In AdminStudio 2016, Application Manager is now configured to automatically test packages against all selected compatibility, best practices, and risk assessment tests as part of the import process. By default, the Automatically Execute Tests After Import option on the Import Options tab of the Application Manager Options dialog box is selected. In previous releases, this option was not selected by default.
Automatically Execute Tests After Import Option
While having this option selected will mean longer import times for each application, packages will have all testing details populated immediately after import. However, if you are concerned with the length of import time, you may want to clear the selection of this option.
Note • In previous releases of AdminStudio, the Automatically Execute Tests After Import option was not selected by default; in AdminStudio 2016, this option is selected by default. Therefore, for users upgrading from previous releases of AdminStudio, they will inherit the new default selection, which means that, by default, this option will be selected and tests will be run immediately after import. To have the same user experience as you did in previous versions, you need to clear the selection of this option.
Enhancements to Package Auto Import Feature
The Application Manager Package Auto Import feature enables you to automatically import or re-import packages in shared network directories into your Application Catalog. Application Manager periodically checks these directories and imports all new packages it finds, and reimports all updated packages.
In AdminStudio 2016, the following enhancements have been added to this feature to make it even more powerful and useful:
• | Can Monitor Multiple Directories Simultaneously |
• | Can Select File Types to Monitor |
• | Can Perform Batch Auto Import of Microsoft Security Patch Files and iOS Enterprise Policy Files |
Can Monitor Multiple Directories Simultaneously
In previous releases, when setting up the Package Auto Import feature, you could only specify a single directory to scan for new or updated packages to import.
In AdminStudio 2016, you can specify multiple directories to monitor. On the General Options > Import Options > Package Auto Import tab of the Options dialog box, you can add a directory to monitor by clicking the New button. There is no limit to the number of directories you can monitor.
Import Options > Package Auto Import Tab of Options Dialog Box
After the initial auto-import operation, packages will be imported or reimported into the Application Catalog whenever:
• | A new package is added to one of the monitored directories. |
• | An existing package in one of the monitored directories is updated. |
Each time you specify a directory to monitor, you need to provide the following information.
Property |
Description |
Directory |
Enter the directory to monitor. You can either enter a directory path or click the browse button and select a directory. Important • The directory must be in UNC format and it must be a shared directory. |
Target Group |
Specify the group in the Application Manager tree into which the packages will be imported. |
Monitoring Status |
Set this option to True to begin monitoring this directory for new and updated packages. Set it to False to stop monitoring the directory. |
Extensions |
Click the browse button to open the Select Watcher Extensions dialog box, where you will specify the package types to import, as described in Can Select File Types to Monitor. |
The monitoring of the specified Package Auto Import directories is a task that can be distributed among the AdminStudio Host processes of all of the installations of AdminStudio in your network that have access to the specified shared directory.
After you have specified a directory on the Package Auto Import tab and have set the Monitoring Status field to True, the AdminStudio Host processes that are connected to the same Application Catalog will begin to monitor these directories.
Packages in the monitored directories will be imported as soon as one of the AdminStudio Host processes connected to the same Application Catalog is running but is not currently being used. This ensures that if someone is actively using one of AdminStudio’s tools, the import (and subsequent testing) of packages by the Package Auto Import process will not slow down the performance of AdminStudio.
Tip • To make sure that the batch import activities of the Package Auto Import process take place when AdminStudio tools are not in use, you could launch AdminStudioHost.exe as a scheduled task during off peak hours and it will perform the import of packages from the monitored directories at that time.
After a directory’s Monitoring Status has been set to True, the packages (of the selected package type) in that directory are listed on the Package Auto Import tab.
Monitoring the Import of Packages in a Directory on the Package Auto Import Tab
In the Status column, packages will have one of the following statuses:
• | Created—Package will be imported as soon as one of the AdminStudio Host processes connected to this Application Catalog is running but is not currently being used. |
• | Imported—Package has been imported into the Application Catalog. |
• | Canceled—User canceled the import of the package into the Application Catalog. |
• | Error—There was an error during import of the package into the Application Catalog. |
Can Select File Types to Monitor
When setting up a directory to monitor for a Package Auto Import process, you can now specify the specific package types in that directory to import. To do this, you click the browse button in the Extensions field of the Package Auto Import tab of the Options dialog box to open the Select Watcher Extensions dialog box.
Select Watcher Extensions Dialog Box
Only those packages of the package type you select on this dialog box will be imported from the monitored directory.
Can Perform Batch Auto Import of Microsoft Security Patch Files and iOS Enterprise Policy Files
Previously, you could only import Microsoft Security Patch files (.msu) and iOS Enterprise Policy Configuration Files (.mobileconfig or .plist) one at a time using the Import Wizard.
In AdminStudio 2016, you can now perform a batch import of Microsoft Security Patch files and iOS Enterprise Policy Configuration files using the Package Auto Import feature. To do this, select the Microsoft Windows Security Update Patch and/or the Enterprise mobile policy configuration support options on the Select Watcher Extensions dialog box.
Enhanced Control When Using Import Wizard to Perform Batch Import from a Directory
When using the Import Wizard to import a folder of applications, you can now choose to import only the packages that you select rather than all packages of the selected package type in the directory.
After you select the package types that you want to import from the selected directory on the Package Type Selection panel of the Import Wizard, a new panel named Select Applications opens, prompting you to select specific applications to import from the selected directory.
Select Applications Panel of Import Wizard
By default, all packages of the selected package type are selected. You can clear the selection of any packages you do not want to import.
Automated Application Converter Enhancements
AdminStudio 2016 contains several enhancements to the Automated Application Converter tool to expand its functionality.
• | Automated Application Converter for Repackaging Now Included in Professional and Enterprise Editions |
• | Can Set Default Conversion Settings from the Application Manager Options Dialog Box |
• | Can Set Custom Settings When Performing Individual Conversion Using Conversion Wizard |
Automated Application Converter for Repackaging Now Included in Professional and Enterprise Editions
In AdminStudio 2016, the Professional and Enterprise editions now include Automated Application Converter—which you can use to perform automated repackaging on a virtual machine—without requiring you to purchase the Virtualization add-on pack.
• | Professional edition—You can perform automated repackaging one package at a time. |
• | Enterprise edition—You can perform batch automated repackaging of a group of packages. |
Note • In order to use Automated Application Converter to convert packages to virtual formats, you will still be required to purchase the Virtualization add-on pack.
You can choose to perform automated repackaging using either the Automated Application Converter interface or by using the Conversion Wizard, which is launched from Application Manager by right-clicking on a package or group of packages and then selecting Launch Conversion Wizard from the shortcut menu. Previously, the Conversion Wizard feature of Application Manager was only included with AdminStudio if you purchased the Virtualization add-on pack.
Ability to Edit Default Automated Application Converter Settings From Application Manager
In previous releases, you were able to use the Application Manager Conversion Wizard to quickly convert one or multiple Windows Installer packages or legacy installers to virtual packages (of the specified type) using default Automated Application Converter settings. However, to edit those default settings, you were required to launch Automated Application Converter and open the default project file.
In AdminStudio 2016, you can now edit the default settings file by clicking the new Edit Settings button on the Plugin Options > Automated Application Converter Plugin tab of the Options dialog box:
Edit Settings Button on Plugin Options > Automated Application Converter Plugin Tab
When you click Edit Settings, a limited version of Automated Application Converter opens, displaying the Machines tab, where you can quickly edit any of these default conversion settings and save them into this default project file.
Editing the Default Automated Application Converter Settings File
Can Edit Conversion Settings From the Conversion Wizard on a Per-Run Basis
In AdminStudio 2016, you now have to option of modifying the default conversion settings for a single run of the Conversion Wizard.
There is a new panel in the Conversion Wizard entitled Automated Application Converter Settings. On this panel, the virtual machine platforms defined in the settings file are listed in the Virtual Machine Platform list, and you can choose which platform to use for this run of the Conversion Wizard.
Automated Application Converter Settings Panel of Conversion Wizard
If you want to edit additional advanced settings, you can click the Edit Advanced Settings button. A copy of the default conversion settings file (that is specified on the Plugin Options > Automated Application Converter Plugin tab of the Options dialog box) is opened, displaying the Packages tab of Automated Application Converter.
Editing the Default Conversion Settings
You can change any of these settings. When you save this file and exit the Packages tab of Automated Application Converter, you are returned to the Conversion Wizard where you can proceed with the conversion.
New Wizard to Install and Launch Windows Installer Packages on a Virtual Machine for Testing
In AdminStudio 2016, the process of resetting a VM snapshot, powering it on, and copying the application for testing into it can be automated using the new Test on Virtual Machine Wizard, which is available with Professional and Enterprise Editions.
The Test on Virtual Machine Wizard uses the capability of the Automated Application Converter tool to quickly launch a specified virtual machine, install a selected Windows Installer (.msi) or installation executable (.exe) package, and enable you to launch a remote desktop session to that virtual machine so that you can perform testing.
Note • Both legacy installers and complex installer executables (which contain bundled Windows Installer packages) can be tested using the Test on Virtual Machine Wizard.
To use the Test on Virtual Machine Wizard to test a package, perform the following steps.
To use the Test on Virtual Machine Wizard to test a package:
1. | Right click a Windows Installer (.msi) or installer executable (.exe) package (or on an application containing an .msi or .exe package) and select Test on Virtual Machine from the shortcut menu. |
Note • The Test on Virtual Machine selection on the shortcut menu is available on both the Catalog and the Test Center tabs of Application Manager.
The Select Package to Test panel opens. The Application Manager tree is displayed, with the package that was selected when you opened the wizard automatically selected.
2. | Confirm the selection of the package that you want to test and click Next. |
The Automated Application Converter Test Settings panel opens, listing the virtual machines defined in the Automated Application Converter settings file that is selected on the Plugin Options > Automated Application Converter Plugin tab of the Options dialog box:
3. | Select the name of the virtual machine that you want to use for testing and click Next. The Summary panel opens. |
4. | Click Next to launch the package on the specified virtual machine for testing. The Performing the Test Process panel opens, listing progress messages. When the package has been installed and launched on the virtual machine, the Remote Desktop button will become enabled. |
5. | Click Remote Desktop to connect to the virtual machine and perform testing. You may be prompted for login credentials to the virtual machine image. A Remote Desktop session opens displaying the virtual image where this package has been installed. |
6. | Use the installed shortcuts to launch the package and perform the desired testing. |
7. | When you have finished testing the package, click OK to close the Remote Desktop session and shut down the virtual machine. |
8. | Return to the Test on Virtual Machine Wizard and click Finish to close the wizard. |
Productivity Shortcuts
Several productivity shortcuts have been added to AdminStudio in the 2016 release.
• | New Shortcut to Automatically Create Transform for Selected Package in InstallShield |
• | Ability to Browse to Package Location from Application Manager Tree |
New Shortcut to Automatically Create Transform for Selected Package in InstallShield
In previous releases, you were able to select Edit with InstallShield from the shortcut menu to quickly open a Windows Installer package in InstallShield. However, the only option you had was to open the package in Direct Edit Mode, which results in modifying the Windows Installer .msi file itself.
In AdminStudio 2016, you can quickly create a new transform project for a Windows Installer package by right-clicking on the package in the Application Manager tree and then selecting Create Transform with InstallShield from the shortcut menu.
Create Transform with InstallShield
A new transform project (named PackageName_ISTransform.mst) for the selected package opens in InstallShield in Direct MST mode.
Transform File Open in InstallShield Direct MST Mode
After you have finished customizing this transform file in InstallShield and have saved it, you can then reimport the Windows Installer package along with its newly created transform file into the Application Catalog by right-clicking on the Windows Installer package in the Application Manager tree and selecting Reimport Package from the shortcut menu. This lets Application Manager know that you are done editing the transform file.
Reimport Package Command on Shortcut Menu
Ability to Browse to Package Location from Application Manager Tree
In AdminStudio 2016, you can quickly browse to the directory location of your source package files by right-clicking on the package in the Application Manager tree and then selecting Open File Location from the shortcut menu. This new option is available on both the Catalog and the Test Center tabs of Application Manager.
New “Open File Location” Command on Shortcut Menu
A new File Explorer window opens, listing the package’s source files.
File Location of Imported Package’s Source Files
New System Center Configuration Manager Settings View
In previous releases, an application’s System Center Configuration Manager settings were listed on the General Information tab of the Application View. These settings were displayed whether or not you had configured a connection to a System Center Configuration Manager server.
In AdminStudio 2016, a new tab has been added to the Application View entitled SCCM Settings where these System Center Configuration Manager settings are now displayed. The SCCM Settings tab is only displayed if you have set up a connection to a System Center Configuration Manager server.
SCCM Settings Tab of Application View
Components/Editions
AdminStudio 2016 is available in Standard, Professional, and Enterprise Editions. You can also purchase additional Application Virtualization, Application Compatibility, and/or Mac and Mobile add-on packs.
Edition |
Add On |
Tools |
Functionality |
|||||||||||||||||||||||||||||
Standard |
None |
Repackager |
Repackage applications into Windows Installer format Perform basic ISO tagging, including creation of tag files |
|||||||||||||||||||||||||||||
Legacy Distribution Wizard |
Prepare packages for distribution |
|||||||||||||||||||||||||||||||
InstallShield 2015 (Professional Edition) |
Customize Windows Installer packages by either directly editing them or by creating transforms Note • While InstallShield 2015 is being shipped with AdminStudio 2016, you will be required to use an AdminStudio/InstallShield 2016 license to activate InstallShield 2015. InstallShield 2016 will be provided as part of an upcoming service pack release. |
|||||||||||||||||||||||||||||||
Tuner |
Customize Windows Installer packages by creating transforms |
|||||||||||||||||||||||||||||||
Application Isolation Wizard |
Resolve component versioning conflicts |
|||||||||||||||||||||||||||||||
Application Virtualization |
Automated Application Converter (Single Application Version) Conversion Wizard (Single Application Version) |
Convert a package to a virtual application in the following formats:
Convert one package at a time |
||||||||||||||||||||||||||||||
Virtual Package Editor |
Edit App-V packages |
|||||||||||||||||||||||||||||||
Microsoft App-V Assistant ThinApp Assistant Citrix Assistant |
Create a customized virtual package from an InstallShield project |
|||||||||||||||||||||||||||||||
Professional
|
None |
Same as Standard, plus: |
||||||||||||||||||||||||||||||
Application Manager / Catalog |
Manage applications in an Application Catalog database Manage a package’s System Center 2012 Configuration Manager and Symantec Altiris Client Management Suite deployment data View an application’s System Center 2012 Configuration Manager deployment status Perform advanced ISO tag file creation, editing, and storage |
|||||||||||||||||||||||||||||||
Application Manager / Test Center |
Perform tests in the following categories:
Test and fix one package at a time |
|||||||||||||||||||||||||||||||
Distribution Wizard |
Publish applications to System Center 2012 Configuration Manager and Symantec Altiris Management Server. |
|||||||||||||||||||||||||||||||
OS Snapshot Wizard |
Capture basic operating system configuration in an OS Snapshot, which can be imported into the Application Catalog to check for potential OS conflicts |
|||||||||||||||||||||||||||||||
QualityMonitor |
Perform Windows Installer testing, including testing in a locked down environment |
|||||||||||||||||||||||||||||||
Automated Application Converter (Single Application Version) Conversion Wizard (Single Application Version) |
Automatically repackage a legacy package (.exe) into a Windows Installer package (.msi) Repackage one package at a time |
|||||||||||||||||||||||||||||||
Test on Virtual Machine Wizard |
Automatically launch a specified virtual machine and install a selected Windows Installer (.msi) or installation executable (.exe) package for testing. |
|||||||||||||||||||||||||||||||
Application Virtualization |
Same as Standard, plus: |
|||||||||||||||||||||||||||||||
Enhancements to Application Manager / Catalog |
Import virtual packages into Application Catalog View virtual package data in Application Manager Manage System Center 2012 Configuration Manager deployment data for App-V 4.x and 5.1 packages Manage Citrix XenApp Server deployment data for Citrix XenApp profiles and App-V 4.x packages Manage Symantec Altiris Client Management Suite deployment data for Symantec Workspace and VMware ThinApp packages Manage App-V Server deployment data for App-V 4.x and 5.1 packages |
|||||||||||||||||||||||||||||||
Enhancements to Application Manager / Test Center |
Test packages for compatibility to be virtualized to App-V, ThinApp, XenApp, and Symantec Workspace formats Test App-V packages for best practices Test App-V packages for conflicts with other packages |
|||||||||||||||||||||||||||||||
Enhancements to Distribution Wizard |
Publish applications containing App-V 4.x and 5.1 packages to Microsoft App-V Server Publish applications containing App-V packages to System Center Configuration Manager and Citrix XenApp Server Publish applications containing Citrix XenApp profiles and App-V 4.x packages to Citrix XenApp Server Publish applications containing Symantec Workspace and VMware ThinApp packages to Symantec Altiris Client Management Suite Server |
|||||||||||||||||||||||||||||||
Application Compatibility |
Enhancements to Application Manager / Test Center |
Test packages for compatibility with the following operating systems:
On the Operating System Compatibility tab of the Test Center Deployment Type View, you can see detailed data for only the last package tested; for all other packages in the Application Catalog, this tab is blank (even if the package has been previously tested) Ability to display Microsoft Application Compatibility Toolkit (ACT) database test results on ACT Summary tab of the Test Center Deployment Type View |
||||||||||||||||||||||||||||||
Mac and Mobile
|
Enhancements to Application Manager / Catalog
|
|
||||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||||||
Enhancements to Application Manager / Test Center |
|
|||||||||||||||||||||||||||||||
Enhancements to Distribution Wizard |
Ability to publish applications containing the following mobile app formats to System Center 2012 Configuration Manager R2 and AirWatch Server:
Ability to publish applications containing the following mobile app format to System Center 2012 Configuration Manager R2:
Ability to publish applications containing the following package formats to JAMF Casper Suite:
|
|||||||||||||||||||||||||||||||
Enterprise
|
None
|
Same as Professional, plus: |
||||||||||||||||||||||||||||||
InstallShield 2015 (Premier Edition instead of Professional Edition) |
Advanced customization of Windows Installer packages by either directly editing them or by creating transforms Advanced customization of Windows Installer packages by either directly editing them or by creating transforms Note • While InstallShield 2015 is being shipped with AdminStudio 2016, you will be required to use an AdminStudio/InstallShield 2016 license to activate InstallShield 2015. InstallShield 2016 will be provided as part of an upcoming service pack release. |
|||||||||||||||||||||||||||||||
Application Manager / Report Center |
Advanced reports including detailed summary and dashboard reports on Test Center test results, package data, and deployment information |
|||||||||||||||||||||||||||||||
Platform API |
Use to integrate your existing .NET applications or scripting environments like Microsoft PowerShell with AdminStudio |
|||||||||||||||||||||||||||||||
Software Repository |
Secure storage system for AdminStudio package data, including version management |
|||||||||||||||||||||||||||||||
Report Center (Web Tool) |
Generate reports on packages stored in the Application Catalog, including reports using custom SQL queries |
|||||||||||||||||||||||||||||||
Security Console (Web Tool) |
Manage AdminStudio user accounts and directory services Manage AdminStudio roles and permissions |
|||||||||||||||||||||||||||||||
Automated Application Converter (Multiple Application Version) Conversion Wizard (Multiple Application Version) |
Automatically repackage legacy packages (.exe) into Windows Installer packages (.msi) Ability to perform automated repackaging of multiple packages at a time |
|||||||||||||||||||||||||||||||
Application Virtualization |
Same as Professional, plus: |
|||||||||||||||||||||||||||||||
Automated Application Converter (Multiple Application Version) Conversion Wizard (Multiple Application Version) |
Ability to perform automated conversion of multiple packages at a time |
|||||||||||||||||||||||||||||||
Enhancements to Application Manager / Report Center |
Includes the Application Virtualization Compatibility Dashboard report Report Center's Application Readiness Dashboard includes an Application Virtualization Compatibility summary chart and App-V Best Practices and App‑V Conflicts test results summary charts. |
|||||||||||||||||||||||||||||||
Application Compatibility |
Same as Professional, plus: |
|||||||||||||||||||||||||||||||
Enhancements to Application Manager / Test Center |
Ability to test and fix multiple packages or groups of packages simultaneously Ability to view package-level test details for Operating System Compatibility and Browser Compatibility tests for all packages in the Application Catalog, not just the last one tested Import of web applications and web deploy packages into the Application Catalog Test web applications for compatibility with the following browsers:
Test web deploy packages for compatibility with the following platforms:
Test web deploy packages for best practices. Test web deploy packages for browser compatibility. |
|||||||||||||||||||||||||||||||
Enhancements to Application Manager / Report Center |
Display of Microsoft ACT database test results on the Report Center tab |
|||||||||||||||||||||||||||||||
Enhancements to Platform API |
Ability to use the Test-ASPackage and Resolve-ASPackage Platform API commands to perform batch package testing and issue resolution. |
|||||||||||||||||||||||||||||||
Mac and Mobile |
Same as Professional |
|
System Requirements
This section lists the requirements for the AdminStudio machine, Application Catalog database server, Web server, Software Repository server, and virtual machines.
• | Compatibility Summary |
• | AdminStudio Machine |
• | Distribution Systems |
• | Application Catalog Database Server |
• | AdminStudio Enterprise Server / Workflow Manager Server |
• | Software Repository |
• | Automated Application Converter |
Compatibility Summary
AdminStudio 2016 supports the following versions of the listed software.
Category |
Item |
Supported Versions |
|||||||||||||||||||||||||||||||||||||||
Operating System for:
|
Microsoft Windows |
|
|||||||||||||||||||||||||||||||||||||||
AdminStudio Web Server Operating System (AdminStudio Enterprise Server, AdminStudio Inventory and Rationalization, Workflow Manager) |
Microsoft Windows Server |
|
|||||||||||||||||||||||||||||||||||||||
Application Catalog Database |
Microsoft SQL Server |
|
|||||||||||||||||||||||||||||||||||||||
Flexera Software Product Integration |
FlexNet Manager Platform / FlexNet Manager Suite (On Premises) |
9.2 SP1 or later |
|||||||||||||||||||||||||||||||||||||||
FlexNet Manager Suite (Cloud) |
2014 or later |
||||||||||||||||||||||||||||||||||||||||
App Portal |
7.5.3 or later |
||||||||||||||||||||||||||||||||||||||||
Workflow Manager |
2015 |
||||||||||||||||||||||||||||||||||||||||
Flexera Service Gateway |
1.0 |
||||||||||||||||||||||||||||||||||||||||
Virtual Machines for Virtualization |
VMware Workstation |
6.5 or later |
|||||||||||||||||||||||||||||||||||||||
VMware ESXi |
VMware ESX/ESXi Server, Version 3.5 Update 3 or later |
||||||||||||||||||||||||||||||||||||||||
VMware vSphere |
5.5 |
||||||||||||||||||||||||||||||||||||||||
Microsoft Hyper-V Server |
2008 R2 or later |
||||||||||||||||||||||||||||||||||||||||
Virtual Formats |
App-V |
App-V 4.5 through 5.1 |
|||||||||||||||||||||||||||||||||||||||
VMware ThinApp |
4.x and 5x |
||||||||||||||||||||||||||||||||||||||||
Symantec Workspace Virtualization |
7.6 |
||||||||||||||||||||||||||||||||||||||||
Microsoft App-V Sequencer |
App-V Sequencer |
5.1 |
|||||||||||||||||||||||||||||||||||||||
Desktop Distribution (Applications) |
System Center Configuration Manager |
2007, 2012 R2, 2012 R2 SP1 |
|||||||||||||||||||||||||||||||||||||||
Microsoft App-V Server |
5.1 |
||||||||||||||||||||||||||||||||||||||||
Symantec Altiris Client Management Suite |
7.5 |
||||||||||||||||||||||||||||||||||||||||
Citrix XenApp Server |
6.5 |
||||||||||||||||||||||||||||||||||||||||
Desktop Distribution (Packages) |
Novell ZENworks Configuration Management |
10 and 11 |
|||||||||||||||||||||||||||||||||||||||
LANDESK Management Suite |
9 |
||||||||||||||||||||||||||||||||||||||||
System Center Configuration Manager |
2007, 2012 R2, 2012 R2 SP1 |
||||||||||||||||||||||||||||||||||||||||
Altiris Notification Server |
6.5 |
||||||||||||||||||||||||||||||||||||||||
Marimba NCP |
4.7.2 |
||||||||||||||||||||||||||||||||||||||||
Mobile Distribution |
AirWatch Server |
6.5 |
|||||||||||||||||||||||||||||||||||||||
Microsoft App-V Server |
5.1 |
||||||||||||||||||||||||||||||||||||||||
Microsoft System Center Configuration Manager |
2012 R2, 2012 R2 SP1 |
||||||||||||||||||||||||||||||||||||||||
Mobile Operating Systems Supported for compatibility testing |
Apple iOS |
|
|||||||||||||||||||||||||||||||||||||||
Google Android |
|
||||||||||||||||||||||||||||||||||||||||
Windows Phone |
|
||||||||||||||||||||||||||||||||||||||||
Internet Browsers Supported for browser compatibility testing |
Microsoft Internet Explorer |
9, 10, 11 |
|||||||||||||||||||||||||||||||||||||||
Microsoft Edge |
Current version |
||||||||||||||||||||||||||||||||||||||||
Internet Browsers For viewing AdminStudio Enterprise Server, AdminStudio Inventory and Rationalization, and Workflow Manager |
Mozilla Firefox |
Firefox for Windows 25.0 or later |
|||||||||||||||||||||||||||||||||||||||
Google Chrome |
Chrome for Windows 33.0 or later |
||||||||||||||||||||||||||||||||||||||||
Microsoft Internet Explorer |
Microsoft Internet Explorer 9.0 or later |
||||||||||||||||||||||||||||||||||||||||
Microsoft Edge |
Current version |
||||||||||||||||||||||||||||||||||||||||
Apple Safari |
Safari for Mac OS X and iOS |
||||||||||||||||||||||||||||||||||||||||
Mobile Devices |
Apple iOS Devices |
|
|||||||||||||||||||||||||||||||||||||||
Mobile Devices (Continued) |
Google Android Devices |
|
|||||||||||||||||||||||||||||||||||||||
Windows Phone Devices |
|
||||||||||||||||||||||||||||||||||||||||
API |
PowerShell |
4.x |
|||||||||||||||||||||||||||||||||||||||
Application Compatibility |
Microsoft Application Compatibility Toolkit (ACT) |
5.6 |
AdminStudio Machine
The following table lists the recommended system configuration for a machine running AdminStudio.
Item |
Description |
||||||||||||||||||
Processor |
32-bit or 64-bit processor at 2 GHz or greater Note • All of the AdminStudio tools run on 64-bit Windows operating systems. To repackage 64-bit applications or create 64-bit App-V packages, install AdminStudio on a 64-bit Windows operating system. |
||||||||||||||||||
RAM |
4 GB |
||||||||||||||||||
Hard Disk |
4 GB of free space |
||||||||||||||||||
Display |
Designed for XGA at 1024 x 768 resolution or higher |
||||||||||||||||||
MSXML |
MSXML 6.0 Note • MSXML is installed by the AdminStudio installer. |
||||||||||||||||||
Operating Systems |
Note • Support for Windows Vista was removed due to a modification made by Microsoft. For more information, see the following articles:
|
||||||||||||||||||
Browser |
Microsoft Internet Explorer 7.0 or later |
||||||||||||||||||
Privileges |
Administrative privileges on the system |
Distribution Systems
AdminStudio supports distribution of both applications and packages.
Application Distribution
AdminStudio supports the following distribution systems for the distribution of applications.
Distribution System |
Support Version(s) |
System Center Configuration Manager |
2007, 2012 R2, 2012 R2 SP1 |
Symantec Altiris Client Management Suite |
7.5 |
JAMF Casper Suite Server |
9.9 |
Citrix XenApp Server |
6.5 |
AirWatch Server |
6.5 [Mobile applications only] |
Microsoft App-V Server |
5.1 Note • In order for you to distribute packages to a Microsoft App-V Server, the WinRM service must be running, and the App-V Server must be in the list of trusted hosts. Both of these can be accomplished from PowerShell by running the following command: set-item wsman:\localhost\Client\TrustedHosts –value <Machine Name> |
Package Distribution
AdminStudio supports the following distribution systems for the distribution of packages using the Legacy Distribution Wizard.
Distribution System |
Supported Versions |
Altiris Notification Server |
Version 6.5 |
LANDESK Management Suite |
Version 9 |
Novell ZENworks Configuration Management |
Versions 10 and 11 |
Microsoft System Center Configuration Manager |
2007, 2012 R2, and 2012 R2 SP1 |
Application Catalog Database Server
The following table lists the recommended system configuration for a database server to store AdminStudio Application Catalog databases.
Note • While minimum requirements are listed below, the recommended system configuration for a database server is dependent upon the number of users and the number of packages that will be imported into the Application Catalog database.
Item |
Description |
|||||||||||||||
Processor |
32-bit or 64-bit processor at 2 GHz or greater |
|||||||||||||||
RAM |
4 GB or greater (8 GB preferred) |
|||||||||||||||
Hard Disk Space |
80 GB or greater |
|||||||||||||||
Operating System |
Windows Server 2008 R2 or later (Windows Server 2012 preferred) |
|||||||||||||||
Database Software |
SQL Server 2008 R2 or later databases, including SQL Server 2012, SQL Server 2014, and SQL Server 2016.
Latin1-General, case-insensitive, accent-sensitive, kanatype-insensitive, width-insensitive for Unicode Data, SQL Server Sort Order 52 on Code Page 1252 for non-Unicode data
Note • Before attempting to connect to an existing Microsoft SQL Server, open SQL Server Configuration Manager and make sure that the following three protocols are enabled:
|
AdminStudio Enterprise Server / Workflow Manager Server
The following table lists the system requirements for the Web server that hosts the Workflow Manager Data Web service and the actual Workflow Manager Web site and/or AdminStudio Enterprise Server.
Note • While minimum requirements are listed below, the recommended system configuration for this web server is dependent upon the number of users.
Item |
Description |
Processor |
32-bit or 64-bit processor at 2 GHz or greater Note • AdminStudio Enterprise Server / Workflow Manager runs in 32-bit mode on a 64-bit OS. |
RAM |
4 GB or greater (8 GB preferred) |
Hard Disk Space |
100 GB or greater |
Operating System |
Windows Server 2008 R2 or later / English base language (Windows Server 2012 preferred) |
IIS |
IIS 7.0 or later |
.NET |
.NET Framework 4.0 |
MSXML |
MSXML 6.0 Note • MSXML is installed by the AdminStudio Enterprise Server / Workflow Manager installer. |
Software Repository
The following tables lists the recommended system configuration for the machine that stores the Software Repository files.
Item |
Description |
Processor |
1 GHz or greater |
RAM |
2 GB or greater |
Hard Disk Space |
500 GB or greater |
Operating System |
Windows 8, Windows 7, Windows Vista, or Windows Server 2008 or later |
Automated Application Converter
This section lists the requirements for the virtual machines used by Automated Application Converter to perform repackaging. Also, the software requirements for specific virtual technologies are listed.
• | Virtual Machine Requirements |
• | Virtual Technology Requirements |
Virtual Machine Requirements
Edition • Automated Application Converter is included with AdminStudio Application Virtualization.
Automated Application Converter performs automated repackaging on virtual machines. This section lists the virtual machine platform and virtual machine image system requirements.
• | Supported Virtual Machine Platforms |
• | VMware Requirements |
• | Microsoft Hyper-V Server Requirements |
• | Virtual Machine Image Requirements |
Supported Virtual Machine Platforms
The Automated Application Converter supports automated repackaging on virtual machines from the following platforms:
• | VMware ESX/ESXi Server, Version 3.5 Update 3 or later |
• | VMware Workstation 6.5 or later |
• | VMware vSphere 5.5 |
• | Microsoft Hyper-V Server 2008 R2 or later |
VMware Requirements
As described above, Automated Application Converter supports automated repackaging on VMware ESX/ESXi Server and VMware Workstation.
• | VMware VIX API Requirement |
• | VMware ESX/ESXi Server Permission Requirements |
• | vSphere 5.5 Account Requirements |
In order for Automated Application Converter to perform automated repackaging, it needs to communicate with the virtualization technology that you are using. If you are using VMware virtualization technology (VMware ESX or ESXi Server or a local VMware Workstation), the VMware VIX API needs to be installed on the same machine as the Automated Application Converter. You can do this by either installing VMware Workstation on that machine or by downloading and installing the VMware VIX API from the following location:
http://www.vmware.com/support/developer/vix-api
Note • When using VMware Workstation, it is recommended that you install VMware Workstation on the same machine as Automated Application Converter so that Automated Application Converter will use the version of the VIX API that was designed for that specific version of VMware Workstation. Although it is likely that newer versions of the VIX API will also work, it seems that the best approach is for Automated Application Converter to use the version of the VIX API that was bundled with your version of VMware Workstation.
VMware ESX/ESXi Server Permission Requirements
If you plan to use a VMware ESX/ESXi Server in conjunction with Automated Application Converter, make sure that the account that you use to log in to this server has the permissions/roles needed to automatically open a VM using VMware VIX API. The account needs to either have an administrator role assigned or, at least, have the following three roles assigned:
• | All Privileges/Virtual Machine/State/Create Snapshot |
• | All Privileges/Virtual Machine/State/Delete Snapshot |
• | All Privileges/Virtual Machine/Interaction/Console Interaction |
If the login account does not have these permissions/roles, Automated Application Converter will be unable to automatically boot up a virtual machine on that server.
vSphere 5.5 Account Requirements
In order to make Automated Application Converter (AAC) work with VMware virtual machines residing under vSphere 5.5, there are certain minimum permissions required for the vSphere user account. To assign these permissions to a vSphere user account, perform the following steps:
To configure a vSphere 5.5 account to be used with Automated Application Converter:
1. | In vSphere 5.5, open the Assign Permissions dialog box and assign a user the Virtual machine power user (sample) role, which consists of the following permissions: |
Category |
Permission |
|||||||||||||||||||||||||||||||||||||||||||
Datastore |
|
|
||||||||||||||||||||||||||||||||||||||||||
Global |
|
|
||||||||||||||||||||||||||||||||||||||||||
Scheduled task |
|
|
||||||||||||||||||||||||||||||||||||||||||
Virtual machine > Configuration |
|
|
||||||||||||||||||||||||||||||||||||||||||
Virtual machine > Interaction |
|
|
||||||||||||||||||||||||||||||||||||||||||
Virtual machine > Snapshot management |
|
|
2. | Also give the user account read-only access to the rest of the server. |
Microsoft Hyper-V Server Requirements
As described above, Automated Application Converter supports automated repackaging on Microsoft Hyper-V Server. When preparing a Hyper-V Server for use with Automated Application Converter, make sure that the following conditions are met:
• | Configuration tools—Verify that the Hyper-V configuration tools are installed on the Hyper-V server machine. These tools can be installed using the Microsoft Hyper-V Management Console. |
• | Connection—Verify that you can successfully connect to the Hyper-V Server from the machine where AdminStudio Automated Application Converter is installed. |
• | Permissions—Make sure that the Hyper-V Server user has the following permissions to perform operations on the Hyper-V machines: |
• | Permission to create/restore/delete VM snapshots |
• | Permission to start and stop virtual machines |
• | Permission to access console sessions |
• | Configuration settings—Connecting to a WMI namespace on a remote computer running Windows Vista or Windows Server 2008 may require changes to configuration settings. Check the following configuration settings on the AdminStudio machine as well as on the Hyper-V Server machine: |
• | Windows Firewall Settings |
• | User Account Control (UAC) Settings |
• | DCOM Settings |
• | Common Information Model Object Manager (CIMOM) Settings |
For detailed information, see Connecting to WMI Remotely at:
http://msdn.microsoft.com/en-us/library/aa822854(VS.85).aspx
Virtual Machine Image Requirements
Automated Application Converter uses virtual machines to perform automated repackaging. These virtual machines have the following requirements:
Virtual Machine System Requirements
When creating a virtual machine image that will be hosted on one of the virtual machine platforms listed above, the recommended minimum requirements should meet those required by the applications you are trying to repackage. Since you repackage on the target deployment platform, the virtual machine image should closely resemble the target deployment environment.
Preparing Your Virtual Machines for Use With the Automated Application Converter
You need to prepare each virtual machine that you are going to use with the Automated Application Converter to perform automated repackaging by running the Virtual Machine Preparation setup and by creating a snapshot. For instructions, see Preparing Your Virtual Machines for Use With the Automated Application Converter.
Virtual Technology Requirements
In order to convert to some virtual formats, there are some software requirements:
Virtual Format |
Requirement |
|||||||||
App-V 5.1 |
|
|||||||||
VMware ThinApp |
To convert a package to VMware ThinApp format, VMware ThinApp must be installed on the same machine as AdminStudio, and all license agreements must have been accepted. |
|||||||||
Symantec Workspace |
To convert a package to a Symantec Workspace virtual package, the Symantec Workspace Virtualization Agent must be installed on the same machine as AdminStudio. |
Downloading AdminStudio Installers
You can download the installers for AdminStudio, AdminStudio Service Packs, Standalone Repackager, Standalone Quality Monitor, and the FlexNet Licensing Server from the Flexera Software Product and License Center:
https://flexerasoftware.flexnetoperations.com
For information on using the Flexera Software Product and License Center, see the Download and License Overview for AdminStudio:
http://www.flexerasoftware.com/downloads/instructions/productlicensing/en/adminstudio.htm
AdminStudio 2016 Evaluation Restrictions
When you run AdminStudio in trial/evaluation mode, all of the features in the AdminStudio Enterprise Edition tools are fully available, with the following restrictions:
• | Can create only one Application Catalog—You are permitted to create only one Application Catalog, and it must be named AdminStudio Evaluation Catalog. |
• | Ten package import limit—Only 10 total packages (of one or more deployment types) can be imported into the Application Catalog. |
• | Package deletion not permitted—After you import a package into the Application Catalog, you are not permitted to delete it. |
• | AdminStudio Platform API support is disabled—All platform support is disabled. |
Resolved Issues
The following table lists the customer issues that were resolved in AdminStudio 2016.
Issue Number |
Issue Summary |
IOJ-1724747 |
Dependencies are not listed in the Dependencies node view of the package after Patch Impact Analysis is run. |
IOJ-1727335 |
When repackaging using the Installation Monitoring method, the InstallScript/MSI installer hangs. |
IOJ-1736087 |
Request to improve the resolution of runtime value for ProgramFilesFolder when converting to App-V format. |
IOJ-1737236 |
When importing using the Import Wizard, the Package Type Selection panel does not list package types. |
IOJ-1738631 |
When using the legacy Distribution Wizard to distribute a package to System Center Configuration Manager, the package name is truncated. |
IOJ-1742085 |
Request to clean up extracted files after an MSI with a patch is imported. |
IOJ-1742220 |
File/folder permissions on repackaged application are not set correctly. After the MSI is built, the ISLockPermissions table is not present in the MSI, and you are not able to set permissions on files/folders. |
IOJ-1743436 |
The content location specified in AdminStudio during distribution is ignored for certain packages. |
IOJ-1743438 |
Request to provide more logging during distribution. The verbose logging created during AdminStudio distribution does not capture anything specific to the content location. |
IOJ-1744011 |
During repackaging, application is crashing during installation when using the Installation Monitoring method. |
IOJ-1744365 |
InstallShield Editor is missing from the tools list in AdminStudio interface after upgrading to AdminStudio 2015 SP1. The InstallShield shortcut can still be launched from the Start Menu but this initiates a self-repair install. |
IOJ-1744441 |
When you attempt to import a security patch and you are using non US English operating system settings, the package fails to import. |
IOJ-1744443 |
Unable to import or test Web Deploy packages due to licensing issue. |
IOJ-1744464 |
The OS Snapshot Wizard can capture and create a Windows 10 image, but when it is imported into the Application Catalog, AdminStudio recognizes it as a Windows 8 machine. |
IOJ-1744823 |
When repackaging certain packages, the Repackaging Wizard will not progress past the “Running the setup program(s)” dialog box. |
IOJ-1749194 |
Request for a way to mitigate or suppress reboots during a silent installation. |
IOJ-1749216 |
On iOS and Android Feature Use reports, the mobile app is listed multiple times, once for each feature, instead of showing all features on one line. |
IOJ-1749414 |
Request to optimize file copy when republishing a package in Altiris (and other distribution systems. Instead of copying all files, just copy the files that have changed. |
IOJ-1751224 |
Distribution from AdminStudio to Altiris fails. |
IOJ-1751231 |
If you load a Custom ACE rule file, the custom rules are not be displayed properly on the General Options > ACE Tests tab of the Options dialog box. |
IOJ-1753385 |
AdminStudio Host can cause files to be held in use causing issues with “Content Location” during distribution to System Center Configuration Manager. |
IOJ-1753930 |
Database created manually are missing table entries, which prevents plugins from functioning properly. |
IOJ-1754786 |
When trying to repackage an application that contains a file named rnuninst.dll using the Snapshot method, Repackager will not capture the file. |
IOJ-1755267 |
Certain tests results are not being displayed if the database was upgraded or created with a certain build of AdminStudio 2015 SP1. |
IOJ-1755270 |
On Windows 7 SP1, if KB2922229 is not installed on the system, AdminStudio will not be able to create a database or upgrade a database. |
IOJ-1756714 |
When using the Software Repository, the wrong error message is displayed when an error is encountered during test execution in Test Center. |
IOJ-1756810 |
When Adminstudio is activated with an “Enterprise with Application Compatibility” License, Windows Server operating system results are not shown when viewing the “Overall Package Testing Results” report. |
Known Issues
For a complete list of known issues that pertain to the AdminStudio 2016 release, see the AdminStudio Support Knowledge Base article at:
https://flexeracommunity.force.com/customer/articles/en_US/INFO/AdminStudio-2016-Known-Issues
Legal Information
Copyright Notice
Copyright © 2016 Flexera Software LLC. All Rights Reserved.
This publication contains proprietary and confidential information and creative works owned by Flexera Software LLC and its licensors, if any. Any use, copying, publication, distribution, display, modification, or transmission of such publication in whole or in part in any form or by any means without the prior express written permission of Flexera Software LLC is strictly prohibited. Except where expressly provided by Flexera Software LLC in writing, possession of this publication shall not be construed to confer any license or rights under any Flexera Software LLC intellectual property rights, whether by estoppel, implication, or otherwise.
All copies of the technology and related information, if allowed by Flexera Software LLC, must display this notice of copyright and ownership in full.
Intellectual Property
For a list of trademarks and patents that are owned by Flexera Software, see http://www.flexerasoftware.com/intellectual-property. All other brand and product names mentioned in Flexera Software products, product documentation, and marketing materials are the trademarks and registered trademarks of their respective owners.
Restricted Rights Legend
The Software is commercial computer software. If the user or licensee of the Software is an agency, department, or other entity of the United States Government, the use, duplication, reproduction, release, modification, disclosure, or transfer of the Software, or any related documentation of any kind, including technical data and manuals, is restricted by a license agreement or by the terms of this Agreement in accordance with Federal Acquisition Regulation 12.212 for civilian purposes and Defense Federal Acquisition Regulation Supplement 227.7202 for military purposes. The Software was developed fully at private expense. All other use is prohibited.