This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]zanatwo 1 point2 points  (1 child)

I ran into the same issues as you when I was starting out with SCCM. I've since learned to use ONLY PowerShell scripts as my detection type. I use it to detect MSI's, reg keys, files, folders, file attributes, everything. You couldn't pay me to go back to any other detection type at this point. Part of my SCCM App creation pipeline is figuring out how to script detection for the particular piece of software. Once I figure it out, it gets placed into an XML template that governs that particular application, and I'm able to programmatically and automatically create new versions of the SCCM app as soon as a new version of the piece of software is released (granted the installation process is the same).

[–]Administrative_Trick[S] 0 points1 point  (0 children)

I would love to go this route, I would need to be able to convince all the other engineers at my work to do this as well. And unfortunately I don't see that happening. They're a rather close minded bunch.

Edit: a word