PENDING Application couldn't found in logs

[mcdy]

Hey folks,

I created a script installation - because I need to add a reg file too - for system and couldn't find an entry in my logs.
There is a installation for the user too and this will be recorgnized by the AppDiscovery log.
Both are deployed to the same collection.

Did the user installation block the system installation?

Entering ExecQueryAsync for query "select * from CCM_AppDeliveryType where (AppDeliveryTypeId = "ScopeId_3A46DE8B-0A9F-4E7F-AB25-CBEAAAA6B5F8/DeploymentType_900d5d69-3fdb-4222-bf66-3c8817b37371" AND Revision = 3)"    AppDiscovery    11.03.2022 16:33:10    15984 (0x3E70)
    Performing detection of app deployment type XXXXXXXX 18c (User Part)(ScopeId_3A46DE8B-0A9F-4E7F-AB25-CBEAAAA6B5F8/DeploymentType_900d5d69-3fdb-4222-bf66-3c8817b37371, revision 3) for user.    AppDiscovery    11.03.2022 16:33:10    15984 (0x3E70)
+++ Application not discovered with script detection. [AppDT Id: ScopeId_3A46DE8B-0A9F-4E7F-AB25-CBEAAAA6B5F8/DeploymentType_900d5d69-3fdb-4222-bf66-3c8817b37371, Revision: 3]    AppDiscovery    11.03.2022 16:33:10    15984 (0x3E70)
+++ Did not detect app deployment type XXXXXXXX 18c (User Part)(ScopeId_3A46DE8B-0A9F-4E7F-AB25-CBEAAAA6B5F8/DeploymentType_900d5d69-3fdb-4222-bf66-3c8817b37371, revision 3) for S-1-5-21-13620034-1472260336-3426108985-1335.    AppDiscovery    11.03.2022 16:33:10    15984 (0x3E70)

Hope somebody could help.
THX mcdy

 

[Garth]

without your script everyone will be guessing at answers.

 

[mcdy]

Hey Garth,

why should a wrong script lead to the application not being found by the CM in general?

But anyway, here is the script:

@echo off
rem ----------------------------------------------------------------------
::    INSTALL
rem ----------------------------------------------------------------------

rem Installation startet
    echo XXXXXXXX 18c wird installiert...
msiexec.exe /I "XXXXXXXX.msi" /qn /norestart
regedit.exe /S "SA218692_063.reg"

THX mcdy

 

[Garth]

Hey Garth,

why should a wrong script lead to the application not being found by the CM in general?

But anyway, here is the script:

@echo off
rem ----------------------------------------------------------------------
::    INSTALL
rem ----------------------------------------------------------------------

rem Installation startet
    echo XXXXXXXX 18c wird installiert...
msiexec.exe /I "XXXXXXXX.msi" /qn /norestart
regedit.exe /S "SA218692_063.reg"

THX mcdy

What is your detection methods? It doesn't look like you are waiting for the MSI install to complete BEFORE doing the import. This would throw off the the detection method.

 

[mcdy]

Hey Garth,

I thought I'm very clever and use the MSI guid for the detection methode, but if I have understood you correctly, then this will not work?
Until now I thought that the detection method only checks after the installation whether it was really successful and otherwise tries the installation again.
Apparently, however, an incorrect detection method can cause no installation to start at all?

THX mcdy

 

[Garth]

Hey Garth,

I thought I'm very clever and use the MSI guid for the detection methode, but if I have understood you correctly, then this will not work?
Until now I thought that the detection method only checks after the installation whether it was really successful and otherwise tries the installation again.
Apparently, however, an incorrect detection method can cause no installation to start at all?

THX mcdy

Using the MSI guid is a good idea, assuming it is the right guid. What I'm not sure about (with an unknown MSI) and it might be a "it depends" answer, but does the batch file wait for the FULL MSI to be installed or are their "tasks/treads" that get spun out from the MSI setup, which the detection method is checking for.

You can tell if this is the case if the detection method see is later. aka 24hours later.

 

[mcdy]

Hello Garth,

so in principle it's a good idea to use the MSI GUID as detection method even if it's a script installation?

Which detection method do you usually use for a script (.bat) installation?

Thanks!
mcdy

 

[Garth]

If I'm using a batch file I don't. I use a program / package.

 

[mcdy]

Hey Garth,

first of all please excuse my late feedback, I was very busy the last days.

So let me summarize:

* if possible I use the MSI ( like I already did ) and as part of that I can also rely on this detection method.
* if I need additional steps besides the MSI, then I can install and uninstall via MSI in the script, but have to use an alternative detection method
* if there is only an EXE anyway, I have to work with a script and parameterization anyway and also choose the detection method accordingly.

Can / may I use C:\temp\progam.txt as a detection method for a test installation and then switch to a real one when I finally installed it on the system?

Thanks!
mcdy

 

[Garth]

You can use C:\temp for a detection method but I would never do it. As soon as the file is delete, the app will try to re-install. use a Reg key instead.