

Once synchronized you will want to check for arrival date, as new packages are added from as far back as April. Help and Support ).īe sure to update the subscriptions on the Subscriptions tab to include the new selections as well. Using the links that joeuser99 provided above, I added the three new catalogs from Adobe to my Patch Manager server ( Expand the products and catalogs list - SolarWinds Worldwide, LLC. Then create a collection like below - having a check for Acrobat being installed prevents false negatives as described in Chuck's entry.Tracking down Adobe updates is never easy in my opinion, but here's some information that will hopefully help: New-ItemProperty -Path $registryPath -Name InstalledVersion -Value $Version -PropertyType String -ForceĪfter the registry has an entry, set up a Scan Profile in PDQ for "SOFTWARE\Adobe\Adobe Acrobat\2017\InstalledVersion". $registryPath = "HKLM:\SOFTWARE\Adobe\Adobe Acrobat\2017\" If you have a different Acrobat product the file path and name may be different. I just wrote a quick script to take the Adobe SWID serial number and translate it to Pro/Standard. This thread just reminded me I was going to get around to this problem. If I don't see Acrobat DC installed, I go back and deleted the swidtag file. In my case, I just look at the installed apps on a suspicious computer. Thus, you may get some false positives in your dynamic group. when Acrobat is uninstalled on a pc it does not appear the files in the folder are removed . You should see them roll right on into your dynamic groups.įilenames or paths listed above may change on future Acrobat version but this works as of today 4/4/18. Test by scanning a few computers you have Pro or Std installed on. > Name > Equals > _AcrobatPro-AS1-Win-GM-MUL.swidtagĬ:\ProgramData\\_AcrobatStd-AS1-Win-GM-MUL.swidtagĬ:\ProgramData\\_AcrobatPro-AS1-Win-GM-MUL.swidtag

In each dynamic group, add two value filters.įile > Path > equals > c:\ProgramData\įile > Name > Equals > _AcrobatStd-AS1-Win-GM-MUL.swidtagįile > Path > Equals > C:\ProgramData\įile. Star by creating a dynamic group for each. std) installed but I found they have added that info to the swidtag filename which makes it much easier to break them out into dynamic groups, pro or standard. The Adobe Acrobat Admin Guide says you have to find the serial number in the swidtag file to determine the version (pro vs. We have a volume license and need to be sure we are in compliance. We really need ot break out the DC installs by Pro or Standard so we can keep track of our licenses. I know this post is kind of old but I encountered the same issue and found a way to resolve it so I figured I'd share.
