About chiranjeevi

chiranjeevi · ‎Sep 18, 2020

Patch for AdminStudio 2019 R2 Summary A patch for AdminStudio 2019 R2 is made available to address a couple of product bugs identified by the AdminStudio product team. This article explains those bugs and how to apply the patch on the affected version of AdminStudio to fix the bugs. Symptoms Every package imported from the Package Feed Module into AdminStudio’s application catalog was missing the setup file name in the command line value set in ‘Install Command Line’ property. So, there was a need to manually update the value in this property with the setup file name. The following error is seen while building MSIX projects in AdminStudio Edition of InstallShield (Editor): Error Description: The specified provider is unknown ‘ISMSIX’ Error Code: -9009 Resolution The patch will fix both the issues mentioned above. Please go to the below link to download the patch: https://flexerasoftware.flexnetoperations.com/control/inst/AnonymousDownload?dkey=15101737 How to Apply the Patches: The downloaded AS2019R2_Patch.zip includes two patch installers: Patch#1 AS2019R2_Patch.exe Patch#2 IS2019_Patch.exe To Apply Patch #1: Copy the AS2019R2_Patch.zip to the machine where AdminStudio 2019 R2 is installed Close all the instances of AdminStudio, AdminStudio tools opened. Kill the AdminStudioHost.exe (if it is already running) from the tray icon area on the taskbar. Extract the AS2019R2_Patch.zip Double click on the AS2019R2_Patch.exe | Wait until the patch installation wizard appears | Continue the wizard to apply the patch To Apply Patch #2: Copy the AS2019R2_Patch.zip to the machine where AdminStudio 2019 R2 is installed Close all the instances of AdminStudio, AdminStudio tools opened. Kill the AdminStudioHost.exe (if it is already running) from the tray icon area on the taskbar. Extract the AS2019R2_Patch.zip Double click on the IS2019_Patch.exe | Wait until the patch installation wizard appears | Continue the wizard to apply the patch Note: These patches can be applied in any order to fix the issues.

chiranjeevi · ‎Feb 05, 2020

@madhupn Thank you for your reply. We'll take a look at the attached script and get back with the observations.

chiranjeevi · ‎Feb 03, 2020

@madhupn I tried to run Invoke-ASImportPackage, Remove-ASApplication cmdlets on a test catalog. If a package gets imported successfully "Invoke-ASImportPackage" cmdlet returns the package object as shown in the attached screenshot " Invoke-ASImportPackage.JPG " which can be used to validate the import. If an application is removed using the "Remove-ASApplication" cmdlet, it returns "The delete operation completed successfully." string as shown in the screenshot " Remove-ASApplication.JPG " which can be used to validate the success or failure. Hope this helps.

chiranjeevi · ‎Jan 27, 2020

Automated Application converter uses TCP Ports# 135 and 443 for external communication and will be using a random remote port within the machine to establish this communication via those standard TCP ports. AdminStudio Application Manager and AdminStudio Host processes use default port #1433 to connect to the SQL server. To see the ports which are used by Automated Application Converter - Launch Automated Application Converter tool alone and launch Resource Monitor Tool - Network Tab - TCP Connections.

chiranjeevi · ‎Jan 24, 2020

Thank you for your reply. Currently, I am working with our engineering team to get the requested details. As soon as I have them, I'll update.

chiranjeevi · ‎Jan 23, 2020

Hi @cliffordhull, I believe, that you are trying to configure the infrastructure required to work with the Automated Application converter to carry out conversions. Are you looking for automating the whole conversion process or just would like to know the technical aspects of the tool? Could you please help me understand the use case to provide you with the required details.

chiranjeevi · ‎Jan 10, 2020

In local environment, one can host the VMs and the AdminStudio server on the same Hyper-V server to carry out the conversions. As far as I know, it should work if the VMs are hosted in a Hyper-V server enabled VM which is hosted in Azure wherein the AdminStudio server also stays on the same Hyper-V server.

chiranjeevi · ‎Jan 10, 2020

Yes, to convert MSI/EXE packages to MSIX format, one would need a VM to carry out the conversion process using the Automated Application Converter. Today, AdminStudio's Automated Application Converter tool supports only Microsoft Hyper-V Server, VMWare ESX or ESXi Server, Local machines to perform conversions to convert the target packages to different formats such as MSIX. Adding VMs from Azure in the Automated Application Converter tool is not supported as of now, but I had a discussion with our product management regarding this requirement and submitted an enhancement request for the same with master issue # IOJ-2090503.

chiranjeevi · ‎Dec 27, 2019

Self-signed digital certificates can be used in InstallShield to sign the packages. This issue needs to be analyzed in-depth in a screen sharing session to figure out the root cause. Feel free to submit a new support ticket for the same, if you have an active maintenance plan for support.

chiranjeevi · ‎Dec 25, 2019

Is the self-sign digital certificate installed into the trusted store? If not, please try installing the same to the trusted store(Trusted Root Certification) and try to sign the package.

chiranjeevi · ‎Dec 23, 2019

@john_burke There is no bat file contents in the post. Please attach the same to look into the issue.

chiranjeevi · ‎Dec 23, 2019

Unfortunately, today there are no InstallShield automation APIs for creating MSIX packages. The good news is that implementing the same is on the cards and is expected to be available in the upcoming release of InstallShield which is planned for Q1 2020.

chiranjeevi · ‎Dec 20, 2019

Have you tried with any other executable which has a shortcut icon embedded into the binary? Please let us know the exact InstallShield version you are using to help resolve the issue.

chiranjeevi · ‎Nov 28, 2019

Summary How to get back hidden tools in AdminStudio - Application Isolation Wizard, Quality Monitor and Security Console tools under ‘AdminStudio Tools’ Menu? Symptoms Starting from AdminStudio 2018 and later, Application Isolation Wizard, Quality Monitor and Security Console tools are not listed under the ‘AdminStudio Tools’ menu. Cause The usage of some of the tools in AdminStudio was very low. In order to keep AdminStudio relevant and simple, some of such tools were hidden in the product. Steps to Reproduce Install AdminStudio 2018 or later Launch the AdminStudio and Connect to an application catalog. On the ‘Home’ tab, click ‘AdminStudio Tools’ and observe Resolution Close all the open instances of AdminStudio Execute the attached 'Unhide_AS_Tools.sql' SQL file in SQL Server Management Studio against the Application catalog connected. Launch AdminStudio and connect to the Application Catalog to get back the hidden tools - Application Isolation Wizard, Quality Monitor, and Security under ‘AdminStudio Tools’ Menu

chiranjeevi · ‎Nov 22, 2019

@chris_glum Have you tried adding a new driver in the ODBC resources section in which you can choose the sqlncli11.dll present in 'C:\Windows\System32' if SQL Server Native Client 11.0 is installed. Please see the attached screenshot. Hope this helps.

Online Status	Offline
Date Last Visited	‎Feb 11, 2020 11:26 AM

Patch for AdminStudio 2019 R2

Re: Issues with AdminStudio PowerShell Cmdlets

Re: Issues with AdminStudio PowerShell Cmdlets

Re: Adminstudio auto conversion

Re: Adminstudio auto conversion

Re: Adminstudio auto conversion

Re: Adminstudio automation

Re: Adminstudio automation

Re: MSIX BUILD ERROR 9008 & 9009

Re: MSIX BUILD ERROR 9008 & 9009

Re: Wise Script Editor - Calling a Bat file RM /S /Q Repository returns "System cannot find the File...

Re: MSIX API using install shield

Re: MSIX BUILD ERROR 9008 & 9009

How to get back the hidden tools in AdminStudio - Application Isolation Wizard, Quality Monitor, and...

Re: SQL Server Native Client 11.0 not in ODBC Resources

Patch for AdminStudio 2019 R2

Re: Issues with AdminStudio PowerShell Cmdlets

Re: Issues with AdminStudio PowerShell Cmdlets

Re: Adminstudio auto conversion

Re: Adminstudio auto conversion

Re: Adminstudio auto conversion

Re: Adminstudio automation

Re: Adminstudio automation

Re: MSIX BUILD ERROR 9008 & 9009

Re: MSIX BUILD ERROR 9008 & 9009

Suggested Actions

Suggest an improvement

Open a support case