Software Deployment Question

.NET Framework 4.6.1 detection method SCCM

01/25/2017 13830 views

I'm creating a application for Camtasia, but it requires .NET 4.6 or greater.

I got a worked application for .NET 4.6.1, but i have a problem with the Detection Method defined in the Deployment Type. It only detects the application after a reboot..

We used the following manual to create the package; >>>
>>> Windows 8.1 & Windows Server 2012 R2

We removed Rule 2 & 3 because it's already present while installing Windows 8.1. So these rules are useless. The only defined rule is; 

Rule 1:
Hive/Key: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\NET Framework Setup\NDP\v4\Full
Value: Release
Data type: Integer
Greater than or equal to 394271

Point is; we don't want to reboot the device after the .NET installation. Without a reboot it says:
Looking for exit code 3010 in exit codes table...]LOG]!>
No action needed after successful enforcement]LOG]!>
Performing detection of app deployment type Offline Installer/Windows Update Uninstaller – Windows 8.1 and Server 2012 R2/DeploymentType_, revision 19) for system.]LOG]!>"12:03:06.268-60" date="01-23-2017" component="AppEnforce" context="" type="1" thread="3360" file="appprovider.cpp:2148">
[+++ Application not discovered. [AppDT Id: ScopeId_/DeploymentType_, Revision: 19]]LOG]!>
[++++++ App enforcement completed (197 seconds) for App DT "Offline Installer/Windows Update Uninstaller – Windows 8.1 and Server 2012 R2" [ScopeId], Revision: 19, User SID: ] ++++++]LOG]!>

With a reboot the application is detected....

My question; which detection method can be used to detect a successful installation without rebooting? Is there a file created somewhere? Or a regkey before rebooting? 

Thx in advance!


Answer Summary:
0 Comments   [ + ] Show comments


Answer Chosen by the Author


Detection Method > Powershell: 

get-hotfix | Where-Object {$_.HotFixID -match "KB3102467"}
Answered 01/26/2017 by: Markje678
Senior White Belt

  • Be careful with this for a detection logic. On older/underpowered systems, this can cause a significant performance hit while it searches all installed hotfixes. SCCM Detection logic will timeout after 60 seconds IIRC, but this command has taken up to 10 minutes on some resource-constrainted system. Depending on how aggressive your Application detection cycle is, this can cause quite the recurring performance hit.

All Answers

Look for version for following file: C:\Windows\Microsoft.NET\Framework64\v4.0.30319\System.Core.dll

Didn't check it - just assumtion
Answered 01/25/2017 by: itolutions
Purple Belt

  • Hi, thx for your reply.

    I only have these folders under C:\Windows\Microsoft.NET\Framework:

    - 1043
    - v1.0.3705
    - v1.1.4322
    - v2.0.50727
    - v3.0
    - v3.5
    - v4.0.30319

    Under C:\Windows\Microsoft.NET\Framework64:
    - 1043
    - v2.0.50727
    - v3.0
    - v3.5
    - v4.0.30319

    I don't see any specific folder for 4.6.1... ?
    • This is expected. MS don't release new folder for each update of .net. You need v4.0.30319 folder. But check for version for following file System.Core.dll it should be 4.6.1.XXXX for your case. You can use this to build detection method
      • Hmm it seems nothing change (this screenshot is made AFTER installation, WITHOUT reboot.

        https://www.mupload.nl/img/3b2idnwwg9y7p. dll.png

        If the link doesnt work:

      • I also made a REGSHOT before installation of .NET and a REGSHOT after installation, NO reboot.

        There are several things changed, but nothing usefull (i think). You can download the report here if you want:
      • I found something!

        KB3102467 is found under "Installed Updates". Now i need to make a script to detect it :)
Did you check for the PendingFileRenameOperations registry key?  This key lists any files that are in use and need to be replaced at the next reboot.  
Answered 01/28/2017 by: EdT
Red Belt

This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ