The Java dependency test AdminStudio provides is about finding apps that use old versions of Java, which introduce risk. As a result, the Java testing is under the Windows Desktop Risk Assessment testing in the overall suite of tests. Within AdminStudio Professional or Enterprise (including the evaluation version): 1.) Within the Analyze tab, on the group of applications in question, click on the Summary / Detail View switcher to get the detail table view: 2.) The application in question would show as white-x-on-red-circle icon under the Risk Assessment column, this indicating an Error with this application in this category of tests: 3.) Click into this Error and you’ll see the Supportability Risks tab; scroll to the bottom to see the Risk Assessment > Windows Desktop Risk Assessment test. Click into this Error icon: 4.) You’ll be presented with the test(s) with the error message; click on the plus button to expand and get further details similar to these test results: AdminStudio Enterprise provides a Reports tab that includes a Java Dependency report: 1.) Click on Reports > Dependencies > Java Runtime Dependency: 2.) You can drill into the test results on either pie chart and see applications that not only use unsupported versions of Java, but any version of Java including currently supported ones: (All links were to the current version of AdminStudio at the time of this posting.) ... View more

AdminStudio supports importing several installation package formats, including .EXE and .MSI, into its Application Catalog.  For complex installers, AdminStudio will show the breakout of multiple MSI installers contained within that package. In general, you can import the output from the Autodesk utility if it falls into one of the formats that is supported. Typically importing an application package into the Application Catalog is done for testing, customization (including wrapping, creating transforms, and repackaging), and publishing to a distribution system. Since Autodesk has provided a utility to prepare their complex installation, it's recommended to use their tool to prepare the application and follow their instructions for publishing to a distribution system. They've made their installer complex and they have provided the solution to deploy that complex software, so that's the best and fastest way to go. For the >95% applications out there that have no utility to prepare their installers, then AdminStudio is your "multi-tool pocketknife" solution! (All links provided go to product documentation for the current AdminStudio version at the time of this reply.) ... View more

There are two challenges to overcome with regard to this specific package, though is fairly common among many application installations: Getting the installation to install and be completely configured while completely silent (no user interaction) Getting the product to automatically activate after installation (no user interaction) With a bit of research and added effort, I am fairly confident that AdminStudio could solve for Challenge #1. However, Challenge #2 is completely in the realm of the software vendor. AdminStudio would be limited to only support what their license activation process supports; it could run a custom action after the installation is completed but that activation program would have to support silent running as well. If it does not, then there is no workaround that would provide this automation and this could not be 100% silently driven installation and activation. ... View more

Please refer to the below article for detailed explanation on how to set up connection between AdminStudio and Microsoft Intune: https://community.flexera.com/t5/AdminStudio-Blog/Setting-up-connection-between-AdminStudio-and-Microsoft-Intune/ba-p/163603 Thanks ... View more

If you have several InstallScript-based packages that you want to move to MSI, the Repackager in AdminStudio would allow you to migrate them to this format. You run each of your InstallScript EXE installers on a clean virtual machine and the Repackager captures the result of that installer (including the files and folders it put down, the registry keys and entries it created, shortcuts, and INI file changes). You can automate the spin up of VMs and copying files in and out of them through the use of the Automated Application Converter: https://docs.flexera.com/adminstudio2019r2sp1/adminstudio.htm#helplibrary/Vam_RootTopic.htm We don't typically recommend the use of InstallScript after this repackaging process, as an InstallScript MSI adds complexity back into the package MSI that we removed when Repackaging was done. Our recommendation would be to keep it as a Basic MSI installer utilizing all of the MSI standard actions. Using the InstallShield Editor included with AdminStudio, you can augment these Standard actions with build-in Custom Actions to perform other takes not available with the MSI format (e.g. create and write to XML and Text files, connect to a SQL database, install a website to IIS, etc.). A list of these Custom Actions that InstallShield can optionally include are found here: https://docs.flexera.com/installshield25helplib/installshield25helplib.htm#helplibrary/Ref-ISCustomActions.htm If you also need to do pre/post-installation tasks outside of the MSI, I'd suggest you look at the wrapping functionality in AdminStudio Professional/Enterprise: https://docs.flexera.com/adminstudio2019r2sp1/adminstudio.htm#helplibrary/Wrap_MSI_EXE_Packages_Using_the_Wrap_Package_Wizard.htm Most users don't know InstallScript and while its very powerful, there is an upfront learning curve.  However, its ultimately up to you to decide what's best for your environment. (These are the latest links at the time of this post; please check https://docs.flexera.com/ for the current product documentation) ... View more