Snow Inventory Agent Script - Adobe Acrobat edition 1
Here you can find the release notes for Snow Inventory Agent Script - Adobe Acrobat edition 1.
1.2 latest
Release date: 2023-07-25
COMPATIBLE VERSIONS
| Snow Inventory Agent for Windows | Microsoft PowerShell |
|---|---|
| 5 or later | 3 and later |
INFORMATION
Adobe Acrobat DC licensing details have been located in the Windows Registry user hive since April 2021.
Adobe has started using shared installers for Adobe Reader and Adobe Acrobat in February 2021.
The Scan-AdobeAcrobatReg.snow-ps1 script improves the out-of-the-box functionality of the Snow Inventory Agent for Windows.
The script must be executed as part of the Snow Inventory Agent for Windows, according to the topic Running PowerShell scripts as part of the scanning process on Snow Docs.
In the case that you want to run a manual scan, this script must be executed with appropriate permissions, so execute it using only sc.exe control SnowInventoryAgent5 128, as described in the Windows Agent - Command line topic on Snow Docs.
This script scans for the required values and creates a Reader, Standard, or Professional software row inside the scan result. This line is marked with the word scan_reg as path.
Consult the following Adobe website topic for a description of the license logic used: Appendix A: Identifying Installs.
Consult the following Adobe website topic for a description of the logic used to identify an Adobe Reader installation: How to identify if Acrobat 64-bit or Acrobat Reader 64-bit is installed.
The script also returns other values, stored in the registry for validation purposes. Those are returned as CustomRegKey in the RegKey HKEY_USERS\\\\Software\\Adobe Adobe Acrobat\\DC AVEntitlement.
The results with the Name starting with enc_ includes the ASCII encoded values of the corresponding fields and do not exist in the registry.
The Software Recognition Service process currently takes the highest edition for recognition, so the features of the scan-swid.snow-ps1 script or the agent built-in functions will not collide with the results of this script.
ENHANCEMENTS
- Include the
SCAPackageLevelvalue to enhance Adobe Reader recognition (IDEAS-I-2220).
CURRENT LIMITATIONS
As multiple accounts could use one computer, the current approach would result in all accounts/usage being mapped to the highest edition found. Customers can create a custom query towards the tblcomputerregistry table and evaluate the iEntitlement value manually.
1.1
Release date: 2022-02-18
Information
Adobe Acrobat DC licensing details have been located in the Windows Registry user hive since April 2021.
Therefore, the Scan-AdobeAcrobatReg.snow-ps1 script must be executed as part of the Snow Inventory Agent for Windows, according to the Snow Docs topic Running PowerShell scripts as part of the scanning process.
In the case that you want to run a manual scan, this script must be executed with appropriate permissions, so execute it using only sc.exe control SnowInventoryAgent5 128, as described in the Windows Agent Command line topic on Snow Docs.
This script scans for the required values and creates a Reader, Standard or Professional software row inside the scan result. This line is marked with the word scan_reg as path.
Consult the following Adobe website topic for a description of the license logic used: ”Appendix A: Identifying Installs” (https://www.adobe.com/devnet-docs/acrobatetk/tools/AdminGuide/identify.html ).
The script also returns other values, stored in the registry for validation purposes. Those are returned as CustomRegKey in the RegKey HKEY_USERS\Software\Adobe\Adobe Acrobat\DC\AVEntitlement.
The results with the Name starting with enc_ includes the ASCII encoded values of the corresponding fields and do not exist in the registry.
The Software Recognition Service process currently takes the highest edition for recognition, so the features of the scan-swid script or the agent built-in functions will not collide with the results of this script.
Features
Added recognition for Adobe Reader
Current Limitations
As multiple accounts could use one computer, the current approach would result in all accounts/usage being mapped to the highest edition found. Customers can create a custom query towards the tblcomputerregistry table and evaluate the iEntitlement value manually.ere what is actually delivered in this release. Use only normal text and the typographical conventions described below}
Flexera does not own the third party trademarks, software, products, or tools (collectively, the "Third Party Products") referenced herein. Third Party Product updates, including user interface updates, may not be reflected in this content.