AdminStudio Knowledge Base

Knowledge Base Categories
Application Version General Availability End of Standard Lifecycle End of Limited Lifecycle Lifecycle as of Today AdminStudio 2019 R2 2019-08-13 2022-08-13 2023-08-13 Standard Life Cycle AdminStudio 2019 2019-03-07 2022-03-07 2023-03-07 Standard Life Cycle AdminStudio 2018 2018-04-27 2021-04-27 2022-04-27 Standard Life Cycle AdminStudio 2016 2016-06-23 2019-06-23 2020-06-23 No Support AdminStudio 2015 2015-07-28 2018-07-28 2019-07-28 No Support AdminStudio Inventory and Rationalization 2015 2015-07-21 2018-07-21 2019-07-21 No Support AdminStudio 2014 2014-07-24 2017-07-31 2018-07-31 No Support AdminStudio 2013 R2 2013-11-22 2016-11-22 2017-11-22 No Support AdminStudio 2013 2013-07-16 2016-07-31 2017-07-31 No Support AdminStudio 11.5 2012-07-16 2015-07-31 2016-07-31 No Support AdminStudio for Symantec 11.5 2012-07-16 2015-07-31 2016-07-31 No Support AdminStudio 11.0 2012-01-26 2015-01-31 2016-01-31 No Support AdminStudio for Symantec 11.0 2012-01-26 2015-01-31 2016-01-31 No Support The date format used is YYYY-MM-DD Versions not listed should be assumed as past extended lifecycle   Read a complete description of the   Flexera lifecycle and end-of-life policy
View full article
Question: Why and how to Enable the DebugLogLevel to 5 in Adminstudio Registry entry: Answer: The DebugLogLevel will be set to 0 by default. The reason for enabling the DebugLogLevel to 5 in the Registry is, this setting will provide a detailed entry of all the tasks that are performed on Adminstudio in the log files ISCMIDE.log and AdminStudio Host.log which will help in debugging the issue. Steps to be followed to set debug log level to 5: 1. Login to the machine where Adminstudio is installed. 2. Open Regedit and navigate to Regedit>HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\InstallShield\AdminStudio>DebugLogLevel. By default, the DebugLogLevel is set to 0. 3. Double click on DebugLogLevel and set the value to 5 and click on the OK button.   4. Stop and then Restart the Adminstudio Host process. 5. By default, the log files 'ISCMIDE.log' and 'AdminStudio Host.log' will be present in the following path: C:\Program Files (x86)\AdminStudio\2019\Common.  
View full article
Summary: This article helps you to retrieve information on SLA time taken for a particular Step/Phase and information on SLA clock stopped time and resumed time through SQL queries. Discussion: --The difference between the minimum (Changedate) of AuditTypeCode '90' and maximum (ChangedDate) of AuditTypeCode '100' gives you the time taken for a particular step in the below query. select ap.ApplicationLName,mn.WFMinorItemID, mn.WFMinorItemDesc, adt.AuditTypeCode,min(adt.ChangedDate) from AMS_AuditTrail adt inner join AMS_ApplicationItem ai on ai.ApplicationItemID= adt.AuditTablePK inner join AMS_WFMinorItemTpl mn on mn.WFMinorItemID = ai.ItemID inner join AMS_Application ap on ap.ApplicationID= adt.ApplicationID where AuditTypeCode in (90 ) and adt.ApplicationID='b75bda5b-a685-480c-b9c7-018054ed379e' group by ap.ApplicationLName,mn.WFMinorItemID, mn.WFMinorItemDesc,adt.AuditTypeCode order by 3 desc select ap.ApplicationLName, mn.WFMinorItemDesc, adt.AuditTypeCode,max(adt.ChangedDate) from AMS_AuditTrail adt inner join AMS_ApplicationItem ai on ai.ApplicationItemID= adt.AuditTablePK inner join AMS_WFMinorItemTpl mn on mn.WFMinorItemID = ai.ItemID inner join AMS_Application ap on ap.ApplicationID= adt.ApplicationID where AuditTypeCode in (100 ) and adt.ApplicationID='b75bda5b-a685-480c-b9c7-018054ed379e' group by ap.ApplicationLName, mn.WFMinorItemDesc,adt.AuditTypeCode order by 2 desc --The difference between the minimum (Changedate) of AuditTypeCode '500 'and maximum (ChangedDate) of AuditTypeCode '501' gives you the time taken for a particular phase in the below query. select ap.ApplicationLName,mj.WFMajorItemName, adt.AuditTypeCode,min(adt.ChangedDate) from AMS_AuditTrail adt inner join AMS_ApplicationItem ai on ai.ApplicationItemID= adt.AuditTablePK inner join AMS_WFMajorItemTpl mj on mj.WFMajorItemID = ai.ItemID inner join AMS_Application ap on ap.ApplicationID= adt.ApplicationID where AuditTypeCode in (500 ) and adt.ApplicationID='b75bda5b-a685-480c-b9c7-018054ed379e' group by ap.ApplicationLName,mj.WFMajorItemName,adt.AuditTypeCode select ap.ApplicationLName, mj.WFMajorItemName, adt.AuditTypeCode,max(adt.ChangedDate) from AMS_AuditTrail adt inner join AMS_ApplicationItem ai on ai.ApplicationItemID= adt.AuditTablePK inner join AMS_WFMajorItemTpl mj on mj.WFMajorItemID = ai.ItemID inner join AMS_Application ap on ap.ApplicationID= adt.ApplicationID where AuditTypeCode in (501) and adt.ApplicationID='b75bda5b-a685-480c-b9c7-018054ed379e' group by ap.ApplicationLName, mj.WFMajorItemName,adt.AuditTypeCode --SQL query to retrieve information on SLA clock stopped time and resumed time select ap.ApplicationLName,mj.WFMajorItemName, adt.AuditTypeCode, adt.ChangedDate from AMS_AuditTrail adt inner join AMS_ApplicationItem ai on ai.ApplicationItemID= adt.AuditTablePK inner join AMS_WFMajorItemTpl mj on mj.WFMajorItemID = ai.ItemID inner join AMS_Application ap on ap.ApplicationID= adt.ApplicationID where AuditTypeCode in (401) and adt.ApplicationID='4a569a1b-4b88-43f8-8bf0-9c914999d614' group by ap.ApplicationLName,adt.AuditTypeCode,mj.WFMajorItemName,adt.ChangedDate select ap.ApplicationLName, mj.WFMajorItemName, adt.AuditTypeCode,adt.ChangedDate from AMS_AuditTrail adt inner join AMS_ApplicationItem ai on ai.ApplicationItemID= adt.AuditTablePK inner join AMS_WFMajorItemTpl mj on mj.WFMajorItemID = ai.ItemID inner join AMS_Application ap on ap.ApplicationID= adt.ApplicationID where AuditTypeCode in (400) and adt.ApplicationID='4a569a1b-4b88-43f8-8bf0-9c914999d614' group by ap.ApplicationLName, mj.WFMajorItemName,adt.AuditTypeCode,adt.ChangedDate  
View full article
Summary: Users may encounter Authentication error when they try to log in to AdminStudio Enterprise server if the IIS settings are not correctly set. Symptoms: When attempting to login to catalog via AdminStudio Enterprise server users may encounter the below error message if Windows Authentication is enabled. Resolution: Ensure the AES\WFM Service Account used must have access to the SQL database. If selecting to connect with "Windows Authentication" then the Website Level Authentication in IIS should be set to "Windows Authentication".           Under AdminStudio Web Components <version> Application select Webservicesroot folder. On the bottom select Content View. Right Click on ‘Authentication.asmx’ and select Switch to Features View. Now the Authentication.asmx page under the Webservicesroot folder shown should be set to "Anonymous and Windows Authentication". Once this is set, users should be able to log in to AdminStudio Enterprise server with Windows Authentication.
View full article
Summary: After a machine reboots/new PowerShell session starts, it is mandatory to execute the PowerShell Snapin's and reinitialize the connection string to utilize the AdminStudio PowerShell cmdlets. Discussion: Since PowerShell does not retain the AdminStudio Snapin's from the earlier session, every time if the session is closed or the machine is rebooted it is mandatory to execute the below snapin's.  Kindly launch the PowerShell (x86) application as ‘Administrator’ and execute the below.  Import-Module  -Name '[AdminStudioInstallDir]\Common\AdminStudio.Utilities.dll'  Import-Module -Name '[AdminStudioInstallDir]\Common\AdminStudio.Platform.PowerShellExtensions.dll'  To initialize the connection string execute- Set-ASConfigPlatform -ConnectionString "PROVIDER=SQLNCLI11;Data Source=**********;Initial Catalog=********;user ID=sa;password=******;" Once the above mentioned steps are executed, you can make use of AdminStudio PowerShell Cmdlets provided in the below link. https://docs.flexera.com/adminstudio2019r2sp1/adminstudio.htm#helplibrary/ASplatform_command_root.htm#platformapi_1062681083_1064690%3FTocPath%3DAdminStudio%2520PowerShell%2520Cmdlets%7CPowerShell%2520Cmdlets%2520Reference%7C_____0
View full article
Summary: Unable to generate Workflow Steps/Phase SLA Report. Symptoms: While generating Workflow Steps/Phase SLA Report users might encounter the below error if the  columns in the SQL view are not upgraded properly. Steps To Reproduce: Launch Workflow manager. Create a Template. Make sure to Track the Workflow phase and Step SLA. Create a Project, submit a Workflow and Complete it. Navigate to Reports -> Workflow Steps SLA Report, Reports -> Workflow Phase SLA Report. You will encounter the above error message if the  columns in the SQL view are not upgraded properly. Resolution: Adding new columns in the view will fix the issue. To do so execute the attached query 'Fix for SLA reports issue.sql' against the database which will fix the issue.
View full article
Summary: This article helps you to understand on how Automated Application Converter functions while converting a package to MSIX. Discussion: The certificate and Publisher name details can be provided in MSIX conversion options under Tools menu or in the Package properties - Referring to the above screenshot,        -  If only the Certificate details (CERT Path , CERT Password) are provided, the publisher name of the converted package (which can be viewed in the AppManifest.xml file) will be overridden by the publisher details provided in certificate.        - If Certificate details are provided along with the Publisher Name details (CERT Path, CERT Password and Publisher Name), then the publisher name of the converted package (which can be viewed in the AppManifest.xml file) will be overridden with the publisher details provided in certificate.        - If only the Publisher name is provided, then the publisher name of the converted package (which can be viewed in the AppManifest.xml file) will be overridden by the Publisher name provided in the MSIX conversion options.
View full article
Synopsis: You may run into issues creating tables with the correct dbo schema when running the SQL Scripts manually.   Description: This can happen if the Default Schema being used is something other than dbo. A symptom of this would be seeing the table created something like nondboschema.ASCMPackageData instead of dbo.ASCMPackageData. This can break the proper execution of scripts manually and if ignored could affect the creation of the database properly.   A solution to this would be to set the user's default schema used to dbo.   Example: This SQL statement can be used and added to the beginning of the adminstudio SQL scripts given to set the schema to dbo: ALTER USER [DOMAIN\USERNAME] WITH DEFAULT_SCHEMA=dbo EXECUTE AS USER='DOMAIN\USERNAME'   This SQL statement can be used to check the schema used: SELECT SCHEMA_NAME()    Additional Information: Here is a link to our documentation on  Creating New Application Catalogs Using Scripts. https://docs.flexera.com/adminstudio2019r2sp1/adminstudio.htm#helplibrary/ASIDETaskCreateUsingScripts.htm#applicationcatalogs_3514464006_1091964%3FTocPath%3DManaging%2520Applications%2520and%2520Application%2520Catalog%2520Databases%7CManaging%2520Application%2520Catalogs%7CCreating%2520New%2520Application%2520Catalogs%7C_____2
View full article
Summary If you have a node-locked licence that is activated by entering your serial number into the software, but have accidentally clicked the 'Configure License Server' option, this article will help to return to the normal activation window. Symptoms If you have accidentally clicked the 'Configure License Server' option on the activation wizard. Then you may be unable to launch AdminStudio or return to the normal activation window. If you try to launch AdminStudio you may see the error below or something similar: This article will only help to return to the normal activation wizard so you can activate your node-locked licence using your serial number. If you have a licence which does use a licence server (concurrent licence) then please see the links below in the related documents section for troubleshooting. If you're having a different problem with the activation after following these steps. Try searching the Knowledge Base for the error you are receiving for help with the problem. Resolution To resolve this issue perform the following steps: 1. Launch Regedit by clicking start and typing 'regedit' in the search box and pushing enter 2. Navigate to HKEY_CURRENT_USER\Software\InstallShield\<Version>\Professional 3. Locate the string entry called LicenseServer, right click on it and click Delete 4. Navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\InstallShield\AdminStudio\<Version> 5. Locate the string entry called LicenseServer, right click on it and click Delete 4. Launch AdminStudio and you should no longer see the license server error AdminStudio 2016 = Version 15.0 AdminStudio 2015 = Version 14.0 AdminStudio 2014 = Version 13.0 AdminStudio 2013 = Version 12.0 Additional Information Download and License Overview for AdminStudio
View full article
Summary This article provides steps regarding how to activate an AdminStudio Node-Locked License Synopsis This article provides steps regarding how to activate an AdminStudio Node-Locked License. Discussion To activate your AdminStudio Node-Locked license: Launch the AdminStudio application. Enter your product serial number in the following format (XXXX-XXXX-XXXX-XXXX). Click the Activate button. If the activation process fails: Select the offline activation option. An offline activation request will be generated. Save the offline activation license.request file. Click the Next button. The next dialog should indicate that an offline transaction is pending. Go to the following website to process your offline activation request: https://flexerasoftware.flexnetoperations.com/control/inst/offlineActivation Click the Choose File button and browse to the license.request file that you recently saved. Click the Process button. Save the activation.xml file. Launch the AdminStudio application, once again. The Offline Activation dialog should be displayed. Click the Load button and browse to the activation.xml file you recently saved. Click the Activate button. Click the Finish button.
View full article
We use a checksum to ensure the download is not modified in transit. We then scan them for viruses. If a setup triggers a virus alert, we will not accept the update and host the file but will instead communicate with the vendor to resolve the issue. Because we are not wrapping or modifying vendor setups, any security signature applied by the vendor remains intact and can be leveraged to confirm it has not been tampered with.
View full article
Summary: Unable to create new Workflow requests in Workflow Manager 2019 Update 2. Symptoms: When we try to create a new request in  Workflow Manager 2019 Update 2 , the “Add” screen briefly flashes and then it re-displays without creating a new request.  Steps To Reproduce: Install a new installation/Upgrade of Workflow Manager 2019 Update 2, along with a brand new database. Log in as “suams”. Create a new company that is a Workflow administrator. (For example : TestCompany) Create an SCAdmin user for that new company.(For example : Test@user.com provided with SCAdmin role) Log out of WFM and log in as the new SCAdmin user. (As per above example its Test@user.com) Browse to Settings -> Company Preferences. Notice that the “Specify Workflow Folder Name” option is not available.  (Some other options are also not available, such as “Role that will be shown in Workflow Lists” and “Custom table pattern to search”.) Resolution: Executing the attached script will add the settings that are missing and users can create new Workflow requests.  Affected Versions: Workflow manager 2019 Update 2.
View full article
Attached are simple, step-by-step instructions for the activation of AdminStudio's Package Feed Module which details the following: Launch AdminStudio Open the Application Manager About Dialog Upgrade the AdminStudio License Activate Your Package Feed Module License Restart AdminStudio Confirm Activation of the Package Feed Module  
View full article
Summary: Duplicate application entries while searching in Package Feed Module Symptoms: While searching for applications in the Package Feed, duplicate entries are seen for some of the applications. Steps To Reproduce: To check the duplicate entries present in the Application catalog: 1. Install the latest build of Adminstudio 2019/2019 R1/2019R2. 2. Launch Application Manager from the start menu 3. Create a new catalog and connect to the created catalog. 4. Click on Package Feed Button from the ribbon and wait till the data is updated. 5. Once the data is updated, enter the product name and click on the Search button. Duplicate entries are displayed as shown below. 6. Run the following SQL query against the Application catalog. Note: The following SQL  Script – Identifies and prints the number of duplicate records (does not delete). ***SQL Script*** DECLARE @duplicateCount int; WITH PacakgeFeedCTE AS ( SELECT *, Row_Number() OVER (PARTITION BY PackageFeedId ORDER BY OID) AS RowNumber FROM ASPackageFeed ) SELECT @duplicateCount = count(*) FROM PacakgeFeedCTE WHERE RowNumber > 1 PRINT 'Duplicate record count: ' + + CAST(@duplicateCount AS VARCHAR) GO Resolution:  Run the following SQL query against the Application catalog. (Refer the attached screenshot "Duplicate records got deleted.JPG" for more details). Note: The following SQL  Script - Identifies and deletes all the duplicate records. ***SQL Script*** WITH PacakgeFeedCTE AS ( SELECT *, Row_Number() OVER (PARTITION BY PackageFeedId ORDER BY OID) AS RowNumber FROM ASPackageFeed ) DELETE FROM PacakgeFeedCTE WHERE RowNumber > 1 GO Affected AdminStudio Versions The following versions of Adminstudio that are affected: AdminStudio 2019 AdminStudio 2019 R1 AdminStudio 2019 R2 Additional Information If there are any additional issues, please contact our Technical Support team
View full article
Summary If you find that it will be necessary to move your license to a new machine, the license must first be returned or deactivated from the previous machine before it can be activated on the new machine. Synopsis AdminStudio and WiseScript Editor node-locked licenses are single-machine, single-user licenses according to the End-User License Agreement (EULA). This means that they can be activated on one machine and accessed by one user. If moving a license to a new machine is required, the license must be returned or deactivated from the machine on which it is currently activated, before attempting to activate the license on a new machine. Please note that there is a return limit for each type of licence: Node Locked Licence If your licence is a node locked licence, then you are allowed to return/deactivate/transfer your licence up to a maximum of four times per year. Concurrent Licence If your licence is a concurrent licence and you would like to return/transfer it from the current licence server to a new/another licence server, then please note that there is a return/transfer limit of 2 returns/transfers per year. Discussion This section included steps for both online and offline activation methods of deactivation. Online Deactivation: 1) Reinstall the software on the previous machine (if it has been uninstalled). 2) From the command-line change directories to the appropriate default path: Version Default Path AdminStudio 8.5 C:\Program Files\Macrovision\AdminStudio\Common AdminStudio 8.6 C:\Program Files\Macrovision\AdminStudio\Common AdminStudio 9 C:\Program Files\AdminStudio\9.0\Common AdminStudio 9.01 C:\Program Files\AdminStudio\9.01\Common AdminStudio 9.5 C:\Program Files\AdminStudio\9.5\Common AdminStudio 10 C:\Program Files\AdminStudio\10.0\Common AdminStudio 11 C:\Program Files\AdminStudio\11.0\Common AdminStudio 11.5 C:\Program Files\AdminStudio\11.5\Common AdminStudio 2013 C:\Program Files\AdminStudio\2013\Common AdminStudio 2014 C:\Program Files\AdminStudio\2014\Common AdminStudio 2015 C:\Program Files\AdminStudio\2015\Common AdminStudio 2016 C:\Program Files\AdminStudio\2016\Common AdminStudio 2018 C:\Program Files\AdminStudio\2018\Common AdminStudio 2019 C:\Program Files\AdminStudio\2019\Common WiseScript Editor C:\Program Files\WiseScript Package Editor\WiseScript Package Editor Note: For 64 bit machines, the default location will be under the (x86) Directory. For example: AdminStudio 11.0 on a 64-bit machine will be located at C:\Program Files (x86)\AdminStudio\11.0\Common WiseScript Editor on a 64-bit machine will be located at C:\Program Files (x86)\WiseScript Package Editor\WiseScript Package Editor 3) Based on the product installed, execute the following Command: For AdminStudio use TPSconfig /return For WiseScript Editor use TSWconfig /return Activation Server URL: activationservice.installshield.com Note: We suggest allowing incoming and outgoing traffic to and from *.flexerasoftware.com and *.installshield.com as well as making sure that ports 80, 443 & 8443 are open. Offline Deactivation: 1) Reinstall the software on the previous machine (if it has been uninstalled) 2) Open up a Command Prompt and CD to the appropriate default path. 3) Execute the following command which will generate a request code: For AdminStudio use TPSconfig /return /no_internet For WiseScript Editor use TSWconfig /return /no_internet 4) For AdminStudio 2014 and later, process the request code at our Product and License Center self-service web page.
View full article
Question: Why a copy of the entire folder is getting created under 'C:\Users\<Username>\Documents\AdminStudio' after Importing an application into the Application Catalog and running the test rules, from where the application has been imported? Answer: During the catalog creation "Enable Software Repository" checkbox was checked and created as a "Software Repository" catalog. So after running the test rules, a copy of the entire folder is created under 'C:\Users\<Username>\Documents\AdminStudio', from where the application has been imported. It is not possible to change the already created "Software Repository catalog" into the Normal catalog. In order to avoid this, uncheck the checkbox "Enable Software Repository" while creating a new catalog.  Note: If we delete the files that were created under 'C:\Users\<Username>\Documents\AdminStudio', there will be no effect at all, while running the test rules or during checking the reports.
View full article
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
View full article
Summary InstallShield digital signing feature uses a timestamp server from Symantec which is being decommissioned (more details   here) and migrated to Digicert. Signing with new DigiCert URL causes breakage in Digital Signing Symptoms When signing an installer with SHA-256 digest, using the new Digicert server (http://timestamp.digicert.com), the resulting installer is signed by SHA-256 digest, but the countersignatures are signed with SHA1 due to an incorrect order in which InstallShield calls the signing APIs Resolution Please refer following InstallShield KB article to download and install  Digital Signing Patch for InstallShield 2015 SP2 and above https://community.flexera.com/t5/InstallShield-Knowledge-Base/Digital-Signing-Patch-for-InstallShield-2015-SP2-and-above/ta-p/121641/jump-to/first-unread-message Affected AdminStudio Versions The patch is applicable only to versions of InstallShield editor available in the following versions of AdminStudio AdminStudio 2016 SP2 AdminStudio 2018 R3 AdminStudio 2018 R4 AdminStudio 2019 R2   Additional Information If there are any additional issues, please contact our  Technical Support   team  
View full article
Question: Why users cannot see workflows created/submitted by other users in the same company? Answer: By default, users in the same company only can see the workflows created or submitted by themselves.  Follow the steps mentioned below to allow all the users in the same company to see the workflows submitted by other users : Navigate to App_Data folder present inside Workflow Manager Installation  Directory              Ex: C:\ AdminStudio Web Components_2019\wwwroot\App_Data\        2.  Locate 'XMLQuery.xml' file and Open it in a Text Editor        3.  Look for the tag <Query id="WFList_Consumer"> and then the <SqlServerVersion> Tag in it.                Remove the text: AND a.uploadBy = ' {0} '        4. Save XMLQuery.xml file        5. Log in as any user in the same company and now will be able to see the workflows submitted by                  other users in the same company.      
View full article
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.  
View full article