Hi guys,

I'm new to SCCM 2012 R2 and i'm getting know my way around it. We are a high school with about 350 clients in total, spread among different classrooms. Now the problem is:

We are deploying Adobe CC through SCCM to all clients, but in one classrooms there are some problems with Adobe CC now, which i can't figure out: on random clients, Software Center says Adobe CC is installed on the machine, except it isn't. When you look on the local hard disk it just isn't there. And it happens randomly. One day i fix a number of clients, and then the other day there is Adobe CC missing on different clients. Can't get my head around it. I think i need to look in the direction of the detection method. Currently, that's set to the MSI Product code.

Can someone help me out here? Thanks so much in advance!
Answer Summary:
Cancel
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Answer Chosen by the Author

1
Hi,
 I personally always have two detection methods per software package, in the case of MSI based installations ProductCode + Branding, or with Legacy / Scripts Branding + Custom. This way you can be really sure that:

1. The software detection is really working correctly
2. You get to see if something has been manually installed

Cheers
Phil
Answered 11/25/2017 by: Pressanykey
Red Belt

Please log in to comment

Community Chosen Answer

1
Detection is where to look, for sure.
Answered 11/23/2017 by: VBScab
Red Belt

Please log in to comment

Answers

This content is currently hidden from public view.
Reason: Spam
For more information, visit our FAQ's.

0
Adobe products are tricky to detect. The main .exe files do not have any version numbers and often they allow even non admin users to update it. That changes the file size and even the size detection logic would not work.
Answered 11/28/2017 by: nagendrasingh
Third Degree Blue Belt

Please log in to comment
0
The main .exe files do not have any version numbers
Errr...I just picked 5 at random from our selection of Adobe products and every one of them has version information.

I take the point, however, but it's simple enough to work around: for each deployment, create a registry key in HKLM which is unique to that deployment. I use a GUID generator script to create a GUID and use that.
Answered 11/29/2017 by: VBScab
Red Belt

  • We do the same in our environment. Every script and installer is assigned registry entry GUID that we can query. Works great!
Please log in to comment
Answer this question or Comment on this question for clarity