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 more

Question: What are the Different methods using which we can Activate Adminstudio? Answer: There are 4 methods using which we can activate Adminstudio (Refer Attached screenshot"Activation Wizard" for more details) 1. Activate or Purchase Adminstudio. In this method, we need to provide an Activation code which will be in the (4 sets of 4 characters) in the below format: XXXX-XXXX-XXXX-XXXX  This is the method that the majority of the customers use. (Refer Attached screenshot"Activation Code" for more details) 2. Continue to Evaluate Adminstudio : We can use this method to evaluate Adminstudio for 21 days without Activation. 3. Configure Adminstudio to get license information from a license server. In this method, we provide license server details IP/Server Name and Port(27000) (Refer Attached screenshot"License Server" for more details) 4. Configure Adminstudio to get license information from a license file. In this method, we use a license file to activate Adminstudio. Please have a look at the following link which will provide you more details: https://docs.flexera.com/adminstudio2020/Content/helplibrary/VerificationOverview.htm#asverification_416060839_1061278 ... View more

Question:  Why do we receive an error message "SSL Security Error" while connecting to the SQL database after enabling TLS 1.2 and disabling TLS 1.0 and TLS 1.1 in the server machine? Please refer attached screenshot "SSL Security Error.JPG" for more details. Answer:  SQL Server OLE DB provider does not support TLS 1.2 so AdminStudio will not be able to connect to a SQL server in a TLS 1.2 only environment. Adminstudio started supporting TLS 1.2 from the 2018 R3 version and above. So if you are using the Adminstudio version less than 2018R3 and below, you will not be able to connect to the SQL server where TLS 1.2 is enabled. However, it connects successfully to the SQL server if TLS 1.0 and TLS 1.1 are enabled. Navigate to the following path in the SQL server machine and modify the value accordingly: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.2 Please refer attached screenshot "TLS Registry path.JPG" for more details.   We can set programmatically TLS 1.2 Client and Server using the following PowerShell script attached Powershell script to enable TLS 1.2 on Client and Server   $protocols = @{ 'SSL 2.0'= @{ 'Server-Enabled' = $false 'Client-Enabled' = $false } 'SSL 3.0'= @{ 'Server-Enabled' = $false 'Client-Enabled' = $false } 'TLS 1.0'= @{ 'Server-Enabled' = $false 'Client-Enabled' = $false } 'TLS 1.1'= @{ 'Server-Enabled' = $false 'Client-Enabled' = $false } 'TLS 1.2'= @{ 'Server-Enabled' = $true 'Client-Enabled' = $true } } $protocols.Keys | ForEach-Object { Write-Output "Configuring '$_'" # create registry entries if they don't exist $rootPath = "HKLM:\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\$_" if(-not (Test-Path $rootPath)) { New-Item $rootPath } $serverPath = "HKLM:\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\$_\Server" if(-not (Test-Path $serverPath)) { New-Item $serverPath New-ItemProperty -Path $serverPath -Name 'Enabled' -Value '1' -PropertyType 'DWord' New-ItemProperty -Path $serverPath -Name 'DisabledByDefault' -Value '0' -PropertyType 'DWord' } $clientPath = "HKLM:\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\$_\Client" if(-not (Test-Path $clientPath)) { New-Item $clientPath New-ItemProperty -Path $clientPath -Name 'Enabled' -Value '1' -PropertyType 'DWord' New-ItemProperty -Path $clientPath -Name 'DisabledByDefault' -Value '0' -PropertyType 'DWord' } # set server settings if($protocols[$_]['Server-Enabled']) { Set-ItemProperty -Path $serverPath -Name 'Enabled' -Value '1' Set-ItemProperty -Path $serverPath -Name 'DisabledByDefault' -Value '0' } else { Set-ItemProperty -Path $serverPath -Name 'Enabled' -Value '0' Set-ItemProperty -Path $serverPath -Name 'DisabledByDefault' -Value '1' } # set client settings if($protocols[$_]['Client-Enabled']) { Set-ItemProperty -Path $clientPath -Name 'Enabled' -Value '1' Set-ItemProperty -Path $clientPath -Name 'DisabledByDefault' -Value '0' } else { Set-ItemProperty -Path $clientPath -Name 'Enabled' -Value '0' Set-ItemProperty -Path $clientPath -Name 'DisabledByDefault' -Value '1' } }       ... View more

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 more