.NET Framework 4.6.1 detection method SCCM
Hello,
Rule 1:
Looking for exit code 3010 in exit codes table...]LOG]!>
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; >>>
https://www.deploymentmadscientist.com/2016/01/25/deploying-microsoft-net-framework-4-6-1-with-system-center-configuration-manager/
>>> 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]!>
[+++ Application not discovered. [AppDT Id: ScopeId_/DeploymentType_, Revision: 19]]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!
Greetings,
Mark
Greetings,
Mark
0 Comments
[ + ] Show comments
Answers (3)
Answer Summary:
Please log in to answer
Posted by:
itolutions
7 years ago
Look for version for following file: C:\Windows\Microsoft.NET\Framework64\v4.0.30319\System.Core.dll
Didn't check it - just assumtion
Comments:
-
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... ? - Markje678 7 years ago-
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 - itolutions 7 years ago
-
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:
https://www.mupload.nl/img/3b2idnwwg9y7p.%20dll.png
Thx. - Markje678 7 years ago -
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:
http://www.mediafire.com/file/emrxuuqzn0s6c2y/REGSHOT+NET+installation.htm - Markje678 7 years ago -
I found something!
KB3102467 is found under "Installed Updates". Now i need to make a script to detect it :) - Markje678 7 years ago
Posted by:
Markje678
7 years ago
Top Answer
Solution:
Detection Method > Powershell:
get-hotfix | Where-Object {$_.HotFixID -match "KB3102467"}
Comments:
-
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. - suprnova74 5 years ago
Posted by:
EdT
7 years ago
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.