(imported topic written by Rob_Swalley91)
Hey all,
Adobe Flash has been displaying on some of our users an auto-update / install prompt. They cannot do this as we do not give our user base admin rights unless they are system admins.
A custom mms.cfg file can be placed in the root of “C:\WINDOWS\system32\Macromed\Flash” that will stop this. Apparently at some point in the past, a previous admin here had pushed this file out to systems but to a folder that was named "C:\WINDOWS\system32\Macromed\Flash ". That’s right…there’s a space after Flash.
I have created two different analyses to help get me the correct number of systems I need to push this task to. I am writing two different relevancy checks for each version of the folder but am getting some weird returns.
Here are my two checks:
exists both folder “C:\WINDOWS\system32\Macromed\Flash” and not exists file “C:\WINDOWS\system32\Macromed\Flash\mms.cfg”
exists both folder "C:\WINDOWS\system32\Macromed\Flash " and not exists file “C:\WINDOWS\system32\Macromed\Flash \mms.cfg”
Both of these should separately take account of the “Flash” and "Flash " but in my previous attempts to do this I wrote my checks WITHOUT the “both” clause and had some conflicting data as a result. These were the checks:
exists folder “C:\WINDOWS\system32\Macromed\Flash” and not exists file “C:\WINDOWS\system32\Macromed\Flash\mms.cfg”
exists folder "C:\WINDOWS\system32\Macromed\Flash " and not exists file “C:\WINDOWS\system32\Macromed\Flash \mms.cfg”
I want to know all of the folders that exist that meet the criteria for having that specific folder name in the decribed paths but have not yet been pushed the mms.cfg file that my predecessor pushed. Am I on the right path with my thinking with these checks?
Thanks for any & all feedback on this.
Rob
