Acrobat Version information Pro Vs Standard

[h29145771]

As we deploy Acrobat 2017 via SCCM, is there any possibility (except the License Informations in the c:\ProgramData\regid.1986-12.adobe\ Swidtag File)

SCCM cannot read the informations of this file, and after isntallation we cannot find any other difference.

Is there any registry key to detect the pro vs the Standard Installation?

Thanks for the reply

[EnterpriseHelp]

No. ID methods are here: Identifying Existing Installs — Enterprise Administration Guide

[h29145771]

As i have written: SCCM is not able to detect informations in a file, which is described in the article!

the only difference i can see is in the swidtag File as described in the article.

we use the same installer with different Serials, which are only detectable in the swidtag file as far as i have found.

are there really no other differences? Does Acrobat use this file everytime at Startup to detect if it is an Pro or Standard Installation?

is it not hold in any registry Key?

the link to the Enterprise guide is known before....

Regards

[Test Screen Name]

It is the same software. Acrobat must recheck the license. If there was a registry key checked instead, people could use it to get a free upgrade...

[h29145771]

so there is no possibility to check the installed Software, which Version is installed without checking this ... File?

this means manual at 70 Clients???

[Test Screen Name]

I'm curious why SCCM needs to know, since presumably the patches and installs are the same. Your license management needs to know but presumably tracked this already?

[h29145771]

our license Management Needs to know and they ask for SCCM Reports... so SCCM has to know...

[Test Screen Name]

Does DCM work? Check if a File Exists using the Desired Configuration Monitoring Solution – The All TECHNICAL Blog

[h29145771]

if i had known bevor the rollout, that there is no chance i would have made a manual reg Key to find out which Version is installed (or a Txt File), but now there is the only Chance to find out via CIs and baselines, and then manually shift the Pro Clients to a Collection.

i have found out that ithere is a reg key, which Points to the installer Files, where i can find out which mst is used to install. therewith it is possible to manage this for me.

I hoped it would be easier...

Bad Luck!

[Test Screen Name]

Questions on using SCCM to check  on a file's existence were recommended to use DCM. Report to SCCM if a file exists

[h29145771]

therefore i should find a different file, or define a file Prior the Installation---

[h29145771 · Accepted solution]

i have found something new...

in C:\WINDOWS\Installer\{AC76BA86-1033-FFFF-7760-0E1108756300}\ is the .mst file found which is used to install.

as i use the same Installation with different .mst files, this can be an indocator for the Installation..

[Greg20973069oxeh]

no go, no such path location given the install method used.