Acrobat Version information Pro Vs Standard

Forum|Forum|8 years ago
December 7, 2017
4 replies
3240 views

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

This topic has been closed for replies.

Correct answer h29145771

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..

T

Test Screen Name

Legend

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

H

h29145771Author

Inspiring

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

H

h29145771AuthorCorrect answer

Inspiring

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..

T

Test Screen Name

Legend

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

H

h29145771Author

Inspiring

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!

T

Test Screen Name

Legend

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?