Testing

Sort by:

Skip Feed

SonnyLee (Flexera) asked a question.
February 26, 2025 at 4:07 PM
-For the operating system application compatibility testing, some areas have the green/yellow/red status but some areas are greyed out. What is the reason for this?
-For the ICEs tests, some have a wrench icon to fix the problem but some don't. Why?
Hi,
My prospecting is going through the AdminStudio & Package Feed Module evaluation. One of the areas they are evaluating is the various testing the solution can preform to help with ConfigMgr deployments
Thanks,
Sonny
Expand Post
AdminStudio
Testing
Evaluation
Share
1 answer
164 views
moconn likes this.
- SonnyLee (Flexera)
  a year ago
  In the Analyze tab of the Application Manager, you can select which tests to run against your applications. These tests include OS Compatibility for the latest builds of Windows, against Internal Consistency Evaluator (or ICE) rules, Application Virtualization Compatibility, Java Dependency, and more.
  
  AdminStudio uses a “traffic light” coloring scheme to classify the test results as No Issue (green), Warming (yellow), or Error/Major issue (red). Grey means that rule has not been run for that application.
  
  You may choose to run certain rules and not run others; those that are not run will remain grey. If you are adding new application packages via wrapping into PowerShell App Deploy Toolkit (PsADT), converting from EXE to MSI via Repackaging, or convert an application to MSIX, the testing does not automatically run for those new applications by default. You would either select a give deployment type after its been created an imported into the Application Catalog, then choose Execute Test on the Analyze tab ribbon (or right-click on a given package and choose Execute Tests). You can also have AdminStudio automatically run the relevant tests on every application package that gets imported, including wrapped and converted applications. More info on these and other import configuration can be found under the Help Library topic Import Options / General Tab, online version found here. Note this will increase the import wizard processing time, as the testing is done as part of the import process when Execute Tests as import is enabled.
  
  Some compatibility rules have an associated fix for that specific issue. That fix comes from AdminStudio, which is in the form of an automatically generated transform file (.MST) for that specific MSI installer, which will alter the original MSI installer at install time for that application to remediate the issue in question. These fixes are tied to the application being remediate and do not affect other applications installed and running on a given deployed Windows machine.
  
  Other compatibility issues cannot be resolved through the use of a Transform file as they likely require a rewriting of the application itself. In the past, Compatibility Fixes (aka “shims”) were used to resolve certain compatibility issues, but these affect all applications running on a Windows machine and should only be used as a stop-gap measure while more permanent options are reviewed. For example, a legacy program should be upgraded to a version that supports the latest Windows build rather than using an older, unsupported version.
  
  Regardless, with all rules AdminStudio includes for testing, every rule has a Manual Fix with a suggestion on how to address the issue is provided, even if AdminStudio cannot automatically resolve it.
  
  The rules that have fixes for them and what the fix entails can be found on each rule in the Select Tests to Execute page accessible on the Analyze tab in the Application Manager when selecting a rule, as well as in the built-in and online Help Library under the main contents chapter “Analyze Tests” (attached is a screenshot)
  
  If the test in question supports fixing the issue via a transform file, then details for a (1) Basic Auto Fix, an (2) Advanced Auto Fix, or both are listed, along with the (1) Manual Fix. In the Select Tests to Execute, you can also choose to tell AdminStudio on a going-forward basis how you want to remediate these issues as they are found via the setting under (4) Default Fix (if either fix is available for a given issue).
  
  More information about the Analyze section of the Application Manager and how to select and run tests as well as resolve issues can be found in the Help Library, online version of this found here:
  https://docs.flexera.com/?product=AdminStudio
  
  Thank you Mike O'Connor
  Expand Post
allisonlow asked a question.
February 24, 2025 at 4:07 AM
What is the easiest way to replicate data from Flexera One PROD instance to UAT?
I'm a Flexera One newbie and hoping to test Business Adapters in UAT. Would like some "real" data to test against. Is there a replication facility? If not, what is the best way to export/ingest from PROD to UAT. I understand there is the ability to test adapters in Prod without committing the changes. Is that the fallback option here?
Expand Post
Flexera One
Testing
Share
1 answer
173 views
- allisonlow
  a year ago
  Meanwhile, found an answer - use the Business Adapter functionality to import exported data from PROD. However, this is piecemeal. Would still be interested if there is a more comprehensive way to do this.
  For example: a push button replicate PROD to UAT, would be a great means to refresh UAT. If this is not available, I suppose UAT is not meant to be a DEV environment?
  Expand Post
JYARBROUGH asked a question.
July 11, 2017 at 7:00 AM
Another Powershell Question
The Powershell below works great when I run it straight from Powershell and prompt for the inputs. However when I run inside of the App Store I get the following error.
Failed to run expression: . 'C:\Program Files\Snow Software\Snow Automation Platform\Activities\migrategroupmembership\2\migrategroupmembership.ps1' -identity 'CNCLCFZLHC2' -target 'STLVDBUS029'. Row number: 110. Error: Cannot validate argument on parameter 'MemberOf'. The argument is or empty. Provide an argument that is not or empty, and then try the command again.
It appears to be passing the parameter but from some reason the MemborOf is but I don't get that error when I run manually.
Thanks for you help!
Jerry
Param(

$identity,

$target

)

Function Get-MyModule

{

Param([string]$name)

if(-not(Get-Module -name $name))

{

if(Get-Module -ListAvailable |

Where-Object { $_.name -eq $name })

{

Import-Module -Name $name

$true

} #end if module available then import

else { $false } #module not available

} # end if not module

else { $true } #module already loaded

} #end function get-MyModule

Function Get-GroupsToMigrate

{

Param($identity)

$array = @()

$groups = Get-AdComputer -Identity $identity -property “MemberOf”

Foreach($group in $groups.memberOf)

{

#$reply = Read-Host -Prompt “add group $($group) `r`ny / n”

#if($reply -match “y”) {$array +=$group}

} #end foreach

Return $array

} #end Get-GroupsToMigrate

# *** ENTRY POINT TO SCRIPT ***

If(-not (Get-MyModule -name “ActiveDirectory”)) { exit }

$array = Get-GroupsToMigrate -identity $identity

Get-ADComputer -Identity $target | Add-ADPrincipalGroupMembership -MemberOf $array
#testing making a change
Expand Post
If
Module
End
+3 more
Share
11 answers
189 views
- Community Manager (Flexera Software)
  9 years ago
  Hi! I would try running the script logged in as the workflowengine account (or runas). It could be that your own account has permissions to read the memberOf property but the service account does not. //Joakim
  Expand Post

End of Feed

3 Chatter Feed Items

3 Posts

Testing

Related Topics