none
Blank Application Reports in ERROR Tab RRS feed

  • Question

  • Hello,

    Since I've upgraded to 1906 I've been getting some weird reporting errors, in the case of the application deployment below, it is deployed to a system collection but installed for one single user at the time.

    The detection parameter used is "HKCU\Software\Microsoft\Windows\CurrentVersion\Uninstall\Anaconda2 2019.03 (Python 2.7.16 64-bit)" and that as always worked in the past.

    But since the SCCM and CCM client upgrade to the latest, a lot of user-based deployment are reporting errors, however the said error is blank in the monitoring segment.

    For the example below, 13 systems and or users are reporting errors, however there's no way of telling whom?

    



    Friday, October 18, 2019 12:24 PM

Answers

  • Well it looks like it was a weird system bug, it's reporting correctly now.

    I've ran a redistribute of the sources.

    

    The trick for making user detection is when you make a package choose Install For User and then you run the detection through the registry in HKCU.

    Sometimes, if the package doesn't write any entries, I'll create a custom one using REG and make sure it gets deleted at the uninstallation time.




    Friday, October 18, 2019 1:35 PM

All replies

  • So HKCU will only see the Local system account and NOT the login user detail. As such, you should use the HKLM key or some other method to detect this product. 

    Garth Jones

    Blog: https://www.enhansoft.com/blog Old Blog: https://sccmug.ca/

    Twitter: @GarthMJ Book: System Center Configuration Manager Reporting Unleashed

    Friday, October 18, 2019 12:31 PM
  • So HKCU will only see the Local system account and NOT the login user detail. As such, you should use the HKLM key or some other method to detect this product. 

    Garth Jones

    Blog: https://www.enhansoft.com/blog Old Blog: https://sccmug.ca/

    Twitter: @GarthMJ Book: System Center Configuration Manager Reporting Unleashed

    Not entirely true sir, I've been using this for YEARS, it all depends on the deployment parameters ;)

    If you run the installer in this mode SCCM is able to read the current user's registry value

     As you can see below:

    

    What it does usually fail at detecting is %AppData% paths... works just fine with registry if you run the installation for the user.

    Try it, I've been doing this for about 3yrs to make user-based installation, the limitation is that when the installer runs it's limited to the user's current system permissions and for detection it doesn't read drive paths but works perfectly fine with the HKCU key. I usually use the method of deployment in tendem with AppLocker so not everything is allowed to be ran by users...

    I deploy pycharm, jetbrains, MS teams, slack and much more, this way certain apps are installed per-user profile and not system wide.





    Friday, October 18, 2019 1:10 PM
  • Well it looks like it was a weird system bug, it's reporting correctly now.

    I've ran a redistribute of the sources.

    

    The trick for making user detection is when you make a package choose Install For User and then you run the detection through the registry in HKCU.

    Sometimes, if the package doesn't write any entries, I'll create a custom one using REG and make sure it gets deleted at the uninstallation time.




    Friday, October 18, 2019 1:35 PM
  • So my OCD is satisfied....

    100% compliance (except that one remediation because not everyone has VLC)


    Friday, October 18, 2019 2:15 PM
  • As I have time this weekend, I will double check this. It will not be the first time I wrong and it will be the last either. 

    Garth Jones

    Blog: https://www.enhansoft.com/blog Old Blog: https://sccmug.ca/

    Twitter: @GarthMJ Book: System Center Configuration Manager Reporting Unleashed

    Friday, October 18, 2019 9:14 PM
  • Hi,
     
    Thank you very much for sharing! Here's a short summary for the problem.
     
    Problem/Symptom:
    ===================
    since the SCCM and client agent upgrade to the latest, a lot of user-based deployment are reporting errors but The error message is blank.

    Possible Cause:
    ===================
    the client actually completed the deployment but didn't show the correct results
     
    Solution:
    ===================
    Run a Redistribute of the source content file


    Best regards,
    Larry

    Please remember to mark the replies as answers if they help. If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Tuesday, October 22, 2019 9:06 AM
  • As I have time this weekend, I will double check this. It will not be the first time I wrong and it will be the last either. 

    Garth Jones

    Blog: https://www.enhansoft.com/blog Old Blog: https://sccmug.ca/

    Twitter: @GarthMJ Book: System Center Configuration Manager Reporting Unleashed

    indeed... It was a pretty  interesting discovery back in the days, which I found inconsistent since I could detect HKCU paths but not local paths when using that deployment approach.

    Wednesday, October 23, 2019 12:58 PM
  • Hi,
     
    Thank you very much for sharing! Here's a short summary for the problem.
     
    Problem/Symptom:
    ===================
    since the SCCM and client agent upgrade to the latest, a lot of user-based deployment are reporting errors but The error message is blank.

    Possible Cause:
    ===================
    the client actually completed the deployment but didn't show the correct results
     
    Solution:
    ===================
    Run a Redistribute of the source content file


    Best regards,
    Larry

    Please remember to mark the replies as answers if they help. If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    That was essentially the fix... It's usually the fix in many other situations, including Windows Updates.

    I've also seen this condition when a package has a dependency, where the dependency package get's updated.

    Users are in a situation where the core software is installed but the dependency software is newer and not upgraded yet, so when you look at the core package linked to that dependency it appears as if some systems have "in progress" activity but then looking at the activity tab it's blank...

    In the case of this current thread it wasn't so but yeah, I've seen other type-situation where in package view it reports "in progress" or "non compliant" but the actual deployment report tabs are empty :/




    Wednesday, October 23, 2019 1:03 PM
  • Hi,

    Thanks for your posting and sharing here, and I'm glad the problem is solved.
    Have a nice day!


    Best regards,
    Larry

    Please remember to mark the replies as answers if they help. If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Thursday, October 24, 2019 8:18 AM