New Post: Powershell Application Detection

jguevarajr wrote:

Lipid_Venom wrote:

One thing that I have noticed with the detection method I posted, I occasionally receive reports from users that if they already have the latest version (or higher) the installation will show as "Failed" in SCCM... Is it missing an Exit Code? There is an Exit Code 0 at the end of the script, but I'm thinking I need one right after the Installed = True portion as well?

Lipid how are you deploying this via SCCM? Application or Package? Have you checked the SCCM logs on the workstation when it fails? Suppose you are deploying via an Application, you could check the AppEnforce.log to see why SCCM considers it a failed install.

+++ Application not discovered. [AppDT Id: ScopeId_8829C3AB-A8A5-486A-9846-BA94CAF6EEA6/DeploymentType_a555d5e8-218d-4958-b842-1c4aee0090f6, Revision: 6]   AppEnforce  
    App enforcement environment: Context: Machine Command line: ServiceUI.exe Deploy-Application.exe Install Allow user interaction: No UI mode: 1 User token: null Session Id: 1 Content path: C:\Windows\ccmcache\ct Working directory:   AppEnforce
 Prepared working directory: C:\Windows\ccmcache\ct AppEnforce  
    Prepared command line: "C:\Windows\ccmcache\ct\ServiceUI.exe" Deploy-Application.exe Install    AppEnforce
    Post install behavior is BasedOnExitCode    AppEnforce
    Waiting for process 6320 to finish.  Timeout = 120 minutes. AppEnforce
    Process 6320 terminated with exitcode: 1603 AppEnforce
    Looking for exit code 1603 in exit codes table...   AppEnforce
    Unmatched exit code (1603) is considered an execution failure.  AppEnforce

As I suspected, I should place an Exit-Code 0 = (Successful?) for when the Application is detected via the script. The actual issue is based off a faulty Detection Method within SCCM, the user should not have received this update to begin with.