The .NET Core Runtime and Hosting Bundle Detection methods need updating I think. After an update, many machines don't detect unless I run a repair install after and then rescan again, though they in fact installed fine the first time.
Here's what I can tell based on the detection methods in SCUP and what's present on the machine:
There are 4 sets of detections in an OR statement, each of which contains 3 detections in an AND group
Set 1 Detection Method:
a) HKLM\SOFTWARE\dotnet\Setup\InstalledVersions\x86\sharedhost\Version exists
b) HKLM\SOFTWARE\dotnet\Setup\InstalledVersions\x86\sharedhost\Version string is >= '2.2.4.0'
c) HKLM\SOFTWARE\Microsoft\Updates\.NET Core exists
Set 2 Detection Method:
a) HKLM\SOFTWARE\WOW6432Node\dotnet\Setup\InstalledVersions\x86\sharedhost\Version exists
b) HKLM\SOFTWARE\WOW6432Node\dotnet\Setup\InstalledVersions\x86\sharedhost\Version string is >= '2.2.4.0'
c) HKLM\SOFTWARE\WOW6432Node\Microsoft\Updates\.NET Core exists
Set 3 Detection Method:
a) HKLM\SOFTWARE\dotnet\Setup\InstalledVersions\x64\sharedhost\Version exists
b) HKLM\SOFTWARE\dotnet\Setup\InstalledVersions\x64\sharedhost\Version string is >= '2.2.4.0'
c) HKLM\SOFTWARE\Microsoft\Updates\.NET Core exists
Set 4 Detection Method:
a) HKLM\SOFTWARE\WOW6432Node\dotnet\Setup\InstalledVersions\x64\sharedhost\Version exists
b) HKLM\SOFTWARE\WOW6432Node\dotnet\Setup\InstalledVersions\x64\sharedhost\Version string is >= '2.2.4.0'
c) HKLM\SOFTWARE\WOW6432Node\Microsoft\Updates\.NET Core exists
Results on machine not detecting (update is installed, but repair not done):
Set 1:
a) Does not exist
b) Does not exist, so comparison no good
c) Does not exist
Set 2:
a) Exists
b) 2.1.5
c) Exists
Set 3:
a) Exists
b) 2.2.4
c) Does not exist
Set 4:
a) Does not exist
b) Does not exist, so comparison no good
c) Exists
Same box after repair install performed:
Set 1:
a) Does not exist
b) Does not exist, so comparison no good
c) Does not exist
Set 2:
a) Exists
b) 2.2.4
c) Exists
Detection occurs because of this set
Set 3:
a) Exists
b) 2.2.4
c) Does not exist
Set 4:
a) Does not exist
b) Does not exist, so comparison no good
c) Exists
These detections seem to work about 85-90% of the time, but not always. The example machine for this is an x64 Server Core 2016 system. Please let me know if I can help provide more information.
I've tried to change them in today's catalog update but I couldn't find better rules than the current ones :(
The only alternative is to use the first 2 rules only BUT this will let Hosting Bundle get detected on machines that has only .NET Core Runtime and vice versa !
Because both has the same exact rules and I can't find anything else to use! Please let me know if you found something we can use.. I will keep looking too in the mean time.
What about reorganizing them just a bit? This should detect better but should still provide exclusivity (using a shorthand to refer to previous posts set, please let me know if this isn't clear):
AND group
OR group
AND Group
Set 1 a
Set 1 b
AND Group
Set 2 a
Set 2 b
AND Group
Set 3 a
Set 3 b
AND Group
Set 4 a
Set 4 b
OR group
Set 1 c
Set 2 c
First I forgot to say thanks for reporting all these good details and sorry to hear that this is bothering you and not working as it should, but we will figure this out together :)
So now to be clear on this, you are talking about only "Hosting Bundle" ? Which already contains .NET Core Runtime
Or you are talking about both separately ("Hosting Bundle" & " .NET Core Runtime") ?
Because the sets of rules you mentioned are the "Installed Rules" of "Hosting Bundle".
Its full name is the ".NET Core Runtime and Hosting Bundle", but if it's easier, we can just call it the Hosting Bundle, for clarity :) This is not about the Runtime standalone
Yeah I know, I started calling it "Hosting Bundle" for clarity :)
Ok good to know, your plan looks good! Will test it and if it worked fine then we will update the rules with these ones and it will be in tomorrow's catalog update :)
Can you submit a technical support request https://patchmypc.com/technical-support. I think it would be easier for us to analyze some device(s) with the product installed, but aren't evaluating the update as required. This would help us figure out root cause in our rules why the machine isn't seeing it.
Support request sent.