• Welcome to Support Forum: Get Support for Patch My PC Products and Services.
 

Adobe Flash Player 32-bit/64-bit Plugin (Firefox - MSI) 32.0.0.223 - Detection Issue

Started by MrRobot13, August 06, 2019, 10:01:33 AM

Previous topic - Next topic

MrRobot13

The application created for "Adobe Flash Player 32-bit/64-bit Plugin (Firefox - MSI) version 32.0.0.223" appears to have a detection issue.
Copying it's content folder locally to the machine and running the script works fine.

Justin Chalfant (Patch My PC)

Can you email us all the CCM\Logs? https://patchmypc.com/technical-support

Quote from: MrRobot13 on August 06, 2019, 10:01:33 AM
The application created for "Adobe Flash Player 32-bit/64-bit Plugin (Firefox - MSI) version 32.0.0.223" appears to have a detection issue.
Copying it's content folder locally to the machine and running the script works fine.

MrRobot13

I apologize for the delay! I'd prefer to not disclose logs.
If there is a specific log with a block of information you need I'd be fine with that.

Thanks for your time!

Justin Chalfant (Patch My PC)


MrRobot13

Taken from AppDiscovery.log

+++ Application not discovered with script detection. [AppDT Id: ScopeId_32D6837B-F7F8-41E4-AA33-B3D85F0DEB0E/DeploymentType_7df2015e-1d02-411b-8c1d-cbdcca15b625, Revision: 2]

+++ Did not detect app deployment type Adobe Flash Player 32-bit/64-bit Plugin 32.0.0.223 (Firefox - MSI)(ScopeId_32D6837B-F7F8-41E4-AA33-B3D85F0DEB0E/DeploymentType_7df2015e-1d02-411b-8c1d-cbdcca15b625, revision 2) for S-1-5-21-2071095341-785605168-1538882281-18123.



Thanks!

Justin Chalfant (Patch My PC)


MrRobot13

Hmm, ok...
I'm not sure what has changed but it is installing now as well as successfully uninstalling with proper detection.

I appreciate the quick feedback you've provided!

MrRobot13

I spoke too soon I suppose.

I updated a couple of my task sequences to now use the newer applications during deployment. Both test deployments of Adobe Flash Player NPAPI "Firefox" .msi appear to not be present on the machine after the TS completed. The TS specified no issue and exited with error code 0.

Thanks

Justin Chalfant (Patch My PC)

Please let me know if this helps. You probably need to perform this action for the task sequence apps to work

Applications Fail to Install During OSD in SCCM with Error AuthorizationManager check failed 0x87d00327 - https://patchmypc.com/applications-fail-to-install-during-osd-in-sccm-with-error-authorizationmanager-check-failed-0x87d00327

Quote from: MrRobot13 on August 08, 2019, 02:33:05 PM
I spoke too soon I suppose.

I updated a couple of my task sequences to now use the newer applications during deployment. Both test deployments of Adobe Flash Player NPAPI "Firefox" .msi appear to not be present on the machine after the TS completed. The TS specified no issue and exited with error code 0.

Thanks

MrRobot13

This is taken from the recent deployment AppDiscovery.log.
It doesn't appear to be getting error "0x87d00327" anywhere. Is it thinking it's already present on the machine?

Entering ExecQueryAsync for query "select * from CCM_AppDeliveryType where (AppDeliveryTypeId = "ScopeId_32D6837B-F7F8-41E4-AA33-B3D85F0DEB0E/DeploymentType_7df2015e-1d02-411b-8c1d-cbdcca15b625" AND Revision = 2)"   AppDiscovery   8/8/2019 10:10:09 AM   3296 (0x0CE0)
Checking digest for Repair action for appdt ScopeId_32D6837B-F7F8-41E4-AA33-B3D85F0DEB0E/DeploymentType_7df2015e-1d02-411b-8c1d-cbdcca15b625   AppDiscovery   8/8/2019 10:10:09 AM   3296 (0x0CE0)
    Performing detection of app deployment type Adobe Flash Player 32-bit/64-bit Plugin 32.0.0.223 (Firefox - MSI)(ScopeId_32D6837B-F7F8-41E4-AA33-B3D85F0DEB0E/DeploymentType_7df2015e-1d02-411b-8c1d-cbdcca15b625, revision 2) for system.   AppDiscovery   8/8/2019 10:10:09 AM   3296 (0x0CE0)
Failed to read script execution time-out from policy. Use default 60 seconds.   AppDiscovery   8/8/2019 10:10:09 AM   3296 (0x0CE0)
script parameters:  -NoLogo -Noninteractive -NoProfile  -ExecutionPolicy Bypass    AppDiscovery   8/8/2019 10:10:09 AM   3296 (0x0CE0)
Redirected system temp folder to 'C:\WINDOWS\CcmTemp'   AppDiscovery   8/8/2019 10:10:09 AM   3296 (0x0CE0)
+++ Discovered application [AppDT Id: ScopeId_32D6837B-F7F8-41E4-AA33-B3D85F0DEB0E/DeploymentType_7df2015e-1d02-411b-8c1d-cbdcca15b625, Revision: 2]   AppDiscovery   8/8/2019 10:10:13 AM   3296 (0x0CE0)
+++ Detected app deployment type Adobe Flash Player 32-bit/64-bit Plugin 32.0.0.223 (Firefox - MSI)(ScopeId_32D6837B-F7F8-41E4-AA33-B3D85F0DEB0E/DeploymentType_7df2015e-1d02-411b-8c1d-cbdcca15b625, revision 2) for system.   AppDiscovery   8/8/2019 10:10:13 AM   3296 (0x0CE0)
Entering ExecQueryAsync for query "select * from CCM_AppDeliveryType where (AppDeliveryTypeId = "ScopeId_32D6837B-F7F8-41E4-AA33-B3D85F0DEB0E/DeploymentType_7df2015e-1d02-411b-8c1d-cbdcca15b625" AND Revision = 2)"   AppDiscovery   8/8/2019 10:10:14 AM   3296 (0x0CE0)
    Performing detection of app deployment type Adobe Flash Player 32-bit/64-bit Plugin 32.0.0.223 (Firefox - MSI)(ScopeId_32D6837B-F7F8-41E4-AA33-B3D85F0DEB0E/DeploymentType_7df2015e-1d02-411b-8c1d-cbdcca15b625, revision 2) for system.   AppDiscovery   8/8/2019 10:10:14 AM   3296 (0x0CE0)
Failed to read script execution time-out from policy. Use default 60 seconds.   AppDiscovery   8/8/2019 10:10:14 AM   3296 (0x0CE0)
script parameters:  -NoLogo -Noninteractive -NoProfile  -ExecutionPolicy Bypass    AppDiscovery   8/8/2019 10:10:14 AM   3296 (0x0CE0)
Redirected system temp folder to 'C:\WINDOWS\CcmTemp'   AppDiscovery   8/8/2019 10:10:14 AM   3296 (0x0CE0)
+++ Discovered application [AppDT Id: ScopeId_32D6837B-F7F8-41E4-AA33-B3D85F0DEB0E/DeploymentType_7df2015e-1d02-411b-8c1d-cbdcca15b625, Revision: 2]   AppDiscovery   8/8/2019 10:10:17 AM   3296 (0x0CE0)
+++ Detected app deployment type Adobe Flash Player 32-bit/64-bit Plugin 32.0.0.223 (Firefox - MSI)(ScopeId_32D6837B-F7F8-41E4-AA33-B3D85F0DEB0E/DeploymentType_7df2015e-1d02-411b-8c1d-cbdcca15b625, revision 2) for system.   AppDiscovery   8/8/2019 10:10:17 AM   3296 (0x0CE0)




Thanks!

MrRobot13

I wanted to follow up the status of this.

After the release of a new version "32.0.0.238" I decided to remove the current application completely from within SCCM including the source files and have it recreated by the Publishing service. I performed those actions then made this app available for install in Software Center. When attempting an install it acts as if it's already on the machine when it's not. The action will change to an uninstall option. If you attempt the uninstall action you will get a failure.

I am resorting back to a package install for the time being.

Please inspect this further so a may use this within TS deployments.

Thanks!

Justin Chalfant (Patch My PC)

Can you email us the application logs https://patchmypc.com/faq-scup-catalog#log-files using our technical support page https://patchmypc.com/technical-support

Quote from: MrRobot13 on August 23, 2019, 09:08:14 AM
I wanted to follow up the status of this.

After the release of a new version "32.0.0.238" I decided to remove the current application completely from within SCCM including the source files and have it recreated by the Publishing service. I performed those actions then made this app available for install in Software Center. When attempting an install it acts as if it's already on the machine when it's not. The action will change to an uninstall option. If you attempt the uninstall action you will get a failure.

I am resorting back to a package install for the time being.

Please inspect this further so a may use this within TS deployments.

Thanks!

cmacnichol

Quote from: Justin Chalfant on August 23, 2019, 09:13:14 AM
Can you email us the application logs https://patchmypc.com/faq-scup-catalog#log-files using our technical support page https://patchmypc.com/technical-support

Hi Justin,

I wanted to chime in on this as I am currently in the process of testing your Service during the trial period.  We came across the issue with Flash not being detected properly and did a little digging into the issue.

From what I can tell, this all comes down to the detection script.  For example, in my case, it is detecting as already installed for Flash PPAPI when NPAPI is already installed.

For this particular problem, if the correct version (32.0.0.238) of NPAPI is already installed when PPAPI attempts to install, the detection script will return an Installed status.  This is due to how to are checking against the application name on line 55-59.

    $InstalledSoftwares = Get-InstalledSoftwares | Where-Object {
        $version = GetVersionFromName $_.DisplayName
        ($_.DisplayName -like $appName -and -not($_.DisplayName -like "*$except*") -and
(($_.DisplayVersion -ne $null -and $_.DisplayVersion.Trim() -ge $appVersion) -or $version -ge $appVersion)) -or
($_.PSChildname -eq $msiCode)


If you check the variables for both NPAPI and PPAPI, the only difference is the MSI Code.

NPAPI
$AppToSearch = 'Adobe Flash Player*'  # A pattern used to search for displayName in the uninstall registry key.
$AppToAvoid = ''                # A pattern used to reject similar applications.
$AppMSICodeToSearch = '{73534489-BFE7-4E2D-9769-FDBA5C886DC2}' # A MSI code used to search for in the uninstall registry key.
$AppVersionToSearch = '32.0.0.238'     # Version >= check to determine if application is installed and greater than or equal to this version.


PPAPI
$AppToSearch = 'Adobe Flash Player*'  # A pattern used to search for displayName in the uninstall registry key.
$AppToAvoid = ''                # A pattern used to reject similar applications.
$AppMSICodeToSearch = '{1ED4AB04-200D-412B-A06A-0B8E7217CCFD}' # A MSI code used to search for in the uninstall registry key.
$AppVersionToSearch = '32.0.0.238'     # Version >= check to determine if application is installed and greater than or equal to this version.


Looking at the detection logic, it will return a True if either the Name OR the MSI match.  Because both names are identical except for the last half, which is covered by the Universal Like operator, it will always come up with a match if the name is the same.

Simplest fix for this is to just add *NPAPI* and *PPAPI* to the respective exception parameter in each detection script.  Might be better in the long run to alter it and confirm that the MSI matches as well though.

Make sense?


Regards,
Chris

Justin Chalfant (Patch My PC)

Hey Chris,

Thanks for the info, we should have an update out this week that will resolve this detection method issue by doing what you mentioned. We will essentially be splitting the Flash Players into three different products (NAPI, PPAPI, and ActiveX) and the detection method will be more specific.

Quote from: cmacnichol on August 26, 2019, 07:18:52 AM
Quote from: Justin Chalfant on August 23, 2019, 09:13:14 AM
Can you email us the application logs https://patchmypc.com/faq-scup-catalog#log-files using our technical support page https://patchmypc.com/technical-support

Hi Justin,

I wanted to chime in on this as I am currently in the process of testing your Service during the trial period.  We came across the issue with Flash not being detected properly and did a little digging into the issue.

From what I can tell, this all comes down to the detection script.  For example, in my case, it is detecting as already installed for Flash PPAPI when NPAPI is already installed.

For this particular problem, if the correct version (32.0.0.238) of NPAPI is already installed when PPAPI attempts to install, the detection script will return an Installed status.  This is due to how to are checking against the application name on line 55-59.

    $InstalledSoftwares = Get-InstalledSoftwares | Where-Object {
        $version = GetVersionFromName $_.DisplayName
        ($_.DisplayName -like $appName -and -not($_.DisplayName -like "*$except*") -and
(($_.DisplayVersion -ne $null -and $_.DisplayVersion.Trim() -ge $appVersion) -or $version -ge $appVersion)) -or
($_.PSChildname -eq $msiCode)


If you check the variables for both NPAPI and PPAPI, the only difference is the MSI Code.

NPAPI
$AppToSearch = 'Adobe Flash Player*'  # A pattern used to search for displayName in the uninstall registry key.
$AppToAvoid = ''                # A pattern used to reject similar applications.
$AppMSICodeToSearch = '{73534489-BFE7-4E2D-9769-FDBA5C886DC2}' # A MSI code used to search for in the uninstall registry key.
$AppVersionToSearch = '32.0.0.238'     # Version >= check to determine if application is installed and greater than or equal to this version.


PPAPI
$AppToSearch = 'Adobe Flash Player*'  # A pattern used to search for displayName in the uninstall registry key.
$AppToAvoid = ''                # A pattern used to reject similar applications.
$AppMSICodeToSearch = '{1ED4AB04-200D-412B-A06A-0B8E7217CCFD}' # A MSI code used to search for in the uninstall registry key.
$AppVersionToSearch = '32.0.0.238'     # Version >= check to determine if application is installed and greater than or equal to this version.


Looking at the detection logic, it will return a True if either the Name OR the MSI match.  Because both names are identical except for the last half, which is covered by the Universal Like operator, it will always come up with a match if the name is the same.

Simplest fix for this is to just add *NPAPI* and *PPAPI* to the respective exception parameter in each detection script.  Might be better in the long run to alter it and confirm that the MSI matches as well though.

Make sense?


Regards,
Chris


MrRobot13

Quote from: Justin Chalfant on August 26, 2019, 07:44:30 AM
We will essentially be splitting the Flash Players into three different products (NAPI, PPAPI, and ActiveX) and the detection method will be more specific.

I have put in place the detection scripts you emailed me and they worked great!

Thanks for fixing this!