Acrobat Pro vs Standard

Comments

5 comments

  • Mike P.

     ...

    So I'm trying to work this out, and the only thing that I can come up with would be to just create my own registry key during deployment and check that.

    I wonder if I can just modify the DisplayName in the Uninstall section without it causing problems with future patches.

    Does anyone have any better ideas?

    0
    Comment actions Permalink
  • Chuck Dore

    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. We really need ot break out the DC installs by Pro or Standard so we can keep track of our licenses. We have a volume license and need to be sure we are in compliance.

    The Adobe Acrobat Admin Guide says you have to find the serial number in the swidtag file to determine the version (pro vs. 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.

    Star by creating a dynamic group for each. In each dynamic group, add two value filters.

    Acrobat DC Std
    File > Path > equals > c:\ProgramData\regid.198612.com.adobe
    File > Name > Equals > regid.1986-12.com.adobe_AcrobatStd-AS1-Win-GM-MUL.swidtag

    Acrobat DC Pro
    File > Path > Equals > C:\ProgramData\regid.1986-12.com.adobe
    File .> Name > Equals > regid.1986-12.com.adobe_AcrobatPro-AS1-Win-GM-MUL.swidtag

    Now create a Scan Profile for each

    Each scan profile searches for a file.

    Acrobat Std
    C:\ProgramData\regid.1986-12.com.adobe\regid.1986-12.com.adobe_AcrobatStd-AS1-Win-GM-MUL.swidtag

    Acrobat Pro
    C:\ProgramData\regid.1986-12.com.adobe\regid.1986-12.com.adobe_AcrobatPro-AS1-Win-GM-MUL.swidtag

    Test by scanning a few computers you have Pro or Std installed on. You should see them roll right on into your dynamic groups.

    Filenames or paths listed above may change on future Acrobat version but this works as of today 4/4/18.

    One note... when Acrobat is uninstalled on a pc it does not appear the files in the regid.1986-12.com.adobe folder are removed . Thus, you may get some false positives in your dynamic group. In my case, I just look at the installed apps on a suspicious computer. If I don't see Acrobat DC installed, I go back and deleted the swidtag file. all without leaving PDQ Inventory.

     

     

    0
    Comment actions Permalink
  • Mike P.

    Thanks for this, and I hope that it does someone else some good.

    Unfortunately though, since we're not using Acrobat DC, this doesn't work. In Acrobat 2017, the file is named "regid.1986-12.com.adobe_V7{}AcrobatESR-17-Win-GM-en_US.swidtag" whether the install is Standard or Pro. The only way to get the difference is to read the XML file itself and get the first four digits of the swid:serial_number, and I don't know how to do that in PDQ or if it's even possible.

    What I've done in the meantime is just created groups based on past deployments of our Acrobat Pro or Standard packages. This will end up being wrong if a computer goes from one to the other, but for now, it seems to be kind of OK.

    0
    Comment actions Permalink
  • Nathan Raymond

    This thread just reminded me I was going to get around to this problem.  I just wrote a quick script to take the Adobe SWID serial number and translate it to Pro/Standard.  If you have a different Acrobat product the file path and name may be different.

     

    $file = 'C:\ProgramData\regid.1986-12.com.adobe\regid.1986-12.com.adobe_V7{}AcrobatESR-17-Win-GM-en_US.swidtag'

    #Test file presence
    if (!(Test-Path $file)){Write-Output "File not found"; exit 777}

    #Read and translate SWID license type
    [xml]$swid = Get-Content -Path $file
    $license = $swid.software_identification_tag.serial_number

    if ($license.StartsWith(9101)){$Version = "Standard"}
    elseif ($license.StartsWith(9707)){$Version = "Pro"}

    #Write Acrobat license type to registry
    $registryPath = "HKLM:\SOFTWARE\Adobe\Adobe Acrobat\2017\"

    New-ItemProperty -Path $registryPath -Name InstalledVersion -Value $Version -PropertyType String -Force

     

    After the registry has an entry, set up a Scan Profile in PDQ for "SOFTWARE\Adobe\Adobe Acrobat\2017\InstalledVersion".  Then create a collection like below - having a check for Acrobat being installed prevents false negatives as described in Chuck's entry.

     

    0
    Comment actions Permalink
  • Mike Chapman

    This thread would be an excellent basis for scripting a test for Acrobat Standard or Pro using the new Powershell scanner being added in PDQ Inventory 19 - I wish my PS was good enough to tackle it myself but it just isn't yet. If anyone else fancies having a go then the information you need is still, as the OP states, at::

    https://www.adobe.com/devnet-docs/acrobatetk/tools/AdminGuide/identify.html

     

    0
    Comment actions Permalink

Please sign in to leave a comment.