Microsoft states that everything that you can do through the Azure portal, is possible to accomplish with PowerShell as well. This becomes possible because Microsoft has built the new portal on top of what called Microsoft Graph API.
If you were to add a new Device Profile, add an App or create a Compliance Policy, all the actions you take within the portal, is actually being processed by the Microsoft Graph API that communicates with the Microsoft Intune.
With this knowledge in mind, it’s now possible to start exploring all the possibilities available through the Microsoft Graph API and how it can be used with PowerShell.
With this knowledge in mind, it’s now possible to start exploring all the possibilities available through the Microsoft Graph API and how it can be used with PowerShell.
The Intune management extension lets you upload PowerShell scripts in Intune to run on Windows 10 devices. The management extension supplements Windows 10 mobile device management (MDM) capabilities and makes it easier for you to move to modern management.
이 페이지는 기업 IT 부서를 위해 작성되었습니다. 최종 사용자가 Acrobat이나 Reader를 업데이트하는 가장 쉬운 방법은 도움말 업데이트 확인을 선택하는 것입니다. 9.x 이전 버전 제품에 대한 IT 관련 중요 정보는 업데이트, 패치 Acrobat, Reader 7.x - 9.x Windows를 참조하십시오. Adobe Reader 7.0.5 - A PDF reader for Linux and other Unices. Adobe Reader 7.0.5 About: The free Adobe Reader (formerly Adobe Acrobat Reader) allows you to view, navigate, and print PDF files across all major computing platforms. Adobe Reader is the free viewing companion to Adobe Acrobat and to Acrobat Capture software.
When a PowerShell script is assigned to a group, The Intune will install the Intune Management Extension. This Intune Management Extension responsible for deploying your PowerShell scripts and it will install the service “Microsoft Intune Management Extension” and setup a scheduled task Intune Management Extension Health.
Intune Management Extension check for scripts every 60 minutes, and the health check will run once a day to see if the agent is functioning correctly.
Prerequisites
- Devices must be joined to Azure AD or Hybrid Azure AD.
- Devices must run Windows 10, version 1607 or later.
- Automatic MDM enrollment must be enabled in Azure AD, and devices must be auto-enrolled to Intune
Deploy Acrobat Reader via Intune
Create PowerShell script for Acrobat Reader and make sure to work or change with the specific parameters:
- Installdir – Local installation folder with dedicated folder
- source – Remote files
Go to PowerShell script and add the Acrobat Reader PowerShell file.
Next, make sure to assign the relevant group that will received the Acrobat Reader
Note: once finished lets speed up the process and synchronize one of the workstation.
The PowerShell script for Deploy
# Check if Acrobat Reader installed already in registry.
$CheckADCReg = Get-ItemProperty HKLM:SoftwareWow6432NodeMicrosoftWindowsCurrentVersionUninstall* | where {$_.DisplayName -like “Adobe Acrobat Reader DC*”}
# If Adobe Reader is not installed continue with script. If it’s installed already script will exit.
If ($CheckADCReg -eq $null) {
$CheckADCReg = Get-ItemProperty HKLM:SoftwareWow6432NodeMicrosoftWindowsCurrentVersionUninstall* | where {$_.DisplayName -like “Adobe Acrobat Reader DC*”}
# If Adobe Reader is not installed continue with script. If it’s installed already script will exit.
If ($CheckADCReg -eq $null) {
# Path for the temporary download folder.
$Installdir = “C:Intuneinstall_adobe”
New-Item -Path $Installdir -ItemType directory
$Installdir = “C:Intuneinstall_adobe”
New-Item -Path $Installdir -ItemType directory
# Download the installer from the Adobe website.
$source = “ftp://ftp.adobe.com/pub/adobe/reader/win/AcrobatDC/1800920044/AcroRdrDC1800920044_en_US.exe”
$destination = “$InstalldirAcroRdrDC1800920044_en_US.exe”
Invoke-WebRequest $source -OutFile $destination
$source = “ftp://ftp.adobe.com/pub/adobe/reader/win/AcrobatDC/1800920044/AcroRdrDC1800920044_en_US.exe”
$destination = “$InstalldirAcroRdrDC1800920044_en_US.exe”
Invoke-WebRequest $source -OutFile $destination
# Start the installation when download is finished
Start-Process -FilePath “$InstalldirAcroRdrDC1800920044_en_US.exe” -ArgumentList “/sAll /rs /rps /msi /norestart /quiet EULA_ACCEPT=YES”
Start-Process -FilePath “$InstalldirAcroRdrDC1800920044_en_US.exe” -ArgumentList “/sAll /rs /rps /msi /norestart /quiet EULA_ACCEPT=YES”
# Wait for the installation to finish.
Start-Sleep -s 240
Start-Sleep -s 240
# Finish by cleaning up the download.
rm -Force $InstalldirAcroRdrDC*
}
rm -Force $InstalldirAcroRdrDC*
}
Continuous or Classic track?¶
The Acrobat product family provides two tracks for both Acrobat and Reader:
- The Continuous track provides service-based tools as well as new features, security and platform enhancements, and bug fixes as part of frequent (and most often) silent updates. Over time, the Continuous track’s update cadence will be more frequent than the Classic track. Classic license program customers do not have access to this track for Acrobat.
- The Classic track is similar to the 11.x model and provides few (if any) new features in updates. Free services are available, but optional. Like previous releases, a quarterly update cadence delivers security and platform enhancements as well as bug fixes.
Note
For up-to-date details about what features exist in each track, see https://helpx.adobe.com/acrobat/using/whats-new.html.
Example release schedules:
Which track should I use?¶
Continuous track¶
Choose this track if you:
- Use named-user deployments; that is, you want to manage entitlements through enterprise IDs. In service-centric environments, it’s beneficial to have a single identity of the user across the desktop, mobile & cloud. DC products support federated and enterprise IDs for identity-based licensing.
- Want new features delivered in updates as soon as they become available.
- Use DC web services.
- Would like to take advantage of frequent updates for security and functionality reasons (you can leverage the silent and automatic update mode, but it is not required).
- Can automatically update or push controlled updates on a 60 day schedule. Since web and desktop updates are released in tandem, keeping the desktop updated ensures features and functionality remain synchronized with Document Cloud services.
- For the Continuous track, only the latest base release and last update will be available for download.
Adobe Ftp Server
Classic track¶
Choose this track if you:
- Use serialized deployments; that is, you don’t need identity-based licensing and deployment and the ability to manage users via the Admin Console.
- Want to limit the feature set to those included in major releases.
- Have not purchased services.
- Want to manage updates like previous 11.x releases.
- Manage a locked environment and need to control the frequency and nature of updates. All updates remain available for download.
License types¶
Licenses are associated with a particular track. A Continuous track license cannot be used with a Classic installer and vice versa.
License programs¶
License program | Plan names | Tracks |
---|---|---|
ETLA | Adobe Document Cloud for enterprise: Premium 1, Premium 2, Pro w/ services, Std w/ services | Continuous |
ETLA | Adobe Document Cloud for enterprise: Pro or Std | Continuous |
ELA, CLP, TLP | Adobe Acrobat Pro Document Cloud and Standard Document Cloud | Classic |
VIP | Adobe Acrobat Pro Document Cloud and Standard Document Cloud | Continuous |
Can I switch tracks?¶
With the right license, yes. Installing a different track requires uninstalling the existing product first.
Acrobat Professional vs. Standard¶
Acrobat Professional and Standard DC are delivered as a single installer. Product behavior and features become enabled based on the entitlements granted by the licensing methodology (a user ID or serial number).
Licensing (provisioning)¶
Http://ftp.adobe.com/pub/adobe/reader/win/acrobatdc/
DC products support named users deployments in addition to traditional, serialized deployments. Named user deployments provide the following advantages:
- Management of usage rights for users and groups via the Admin Console.
- Streamlined license management and compliance.
- Provisioning mobile devices for Document Cloud services.
- Leveraging existing systems so that users can fully participate in more efficient e-sign workflows.
Item | Named user deployment | Serialized deployment |
---|---|---|
License access | Licensing website (LWS) | |
License association | Assigned users and groups | Specific machines |
License programs | ETLA, VIP | ELA, CLP, TLP |
Entitlement granted to | each user | each machine |
Entitlement management | Admin Console | Pre-deployment configuration |
Internet connection | Required: Users must log in and signing out deactivates product. * | Only required pre-deployment for activation |
Activation | Occurs on user log-in | Admin pre-activates for all users |
Services ID | Adobe ID | |
Integrated mobile provisioning | Yes | No |
Services access | Yes (optional) | Yes (optional) |
Virtualization support | App-V (Jan 2017: Citrix, VMWare) (Nov 2017: WTS) | Citrix, WTS, App-V |
SCCM, AIP/GPO, ARD | Yes | Yes |
Track support | Classic, Continuous | Classic only after Dec. 2018 |
*
For the VIP program, the product performs an online activation check every 24 hours. Users can be offline for 30 days on the monthly plan and 99 days on an annual plan.Installer bit locations¶
The requisite installers are available from the following locations:
Location | Continuous | Classic |
---|---|---|
What’s available? | Base installer and last update | Base installer and all updates |
Base installer | None | |
Base installer | Base installer | |
Download pages (Acrobat 2017, Acrobat 2020) | Last update only | All updates |
DC dir: Last update only | All updates |
Location | Continuous | Classic |
---|---|---|
What’s available? | Base installer and last update | Base installer and all updates |
Admin Console | None | None |
Download pages | Base installer and last update | Base installer and all updates |
DC dir: Base installer and last update | All updates | |
get.adobe.com | Latest full installer | None |
Ftp Ftp Adobe Com Pub Adobe Reader Windows 8
Continuous vs. Classic comparison¶
Acrobat product tracks¶
Feature | Continuous | Classic |
---|---|---|
Updates | Frequent | Planned quarterlies |
Update order | Base + last update | Base + last update |
Update UI | Auto or off | Auto or off |
Update registry controls | Auto or off | Win: Same as 11.x |
Services integration | All tools enabled * | Free tools only * |
Upsell enabled? | Standard only | N/A |
Languages | MUI only: licenses are language specific | MUI only: licenses are language specific |
File and preference paths | Versionless: always under DC | Versioned: Under major version, 2015|2017|2020, etc. |
Windows installer | Acrobat_DC_Web_WWMUI.exe | Acrobat_2015|2017|2020_Web_WWMUI.exe |
Windows install paths | C:ProgramFilesAdobeAcrobatDC | C:ProgramFilesAdobeAcrobat2015|2017|2020 |
Registry paths | HKCUSoftwareAdobeAdobeAcrobatDC | HKCUSoftwareAdobeAdobeAcrobat2015|2017|2020 |
Application data path | %Appdata%RoamingAdobeAcrobatDC | %Appdata%RoamingAdobeAcrobat2015|2017|2020 |
FTP download locations | ftp://ftp.adobe.com/pub/adobe/acrobat/win/DC/ | ftp://ftp.adobe.com/pub/adobe/acrobat/win/2015|2017|2020 |
*
What services are visible in the user interface varies by the purchased track and license type. Use the Customization Wizard or registry/plist configuration to remove unwanted items from the user interface.- For the Continuous track, all services are visible and functional. Note that some features, such as Create PDF and Export PDF, are part of the desktop offering and don’t use a DC service.
- For the Classic track, paid for service-based tools are unavailable. Features such as Export PDF are part of the desktop product and don’t require a service to function. Free services which don’t duplicate existing functionality are on by default.
Reader DC tracks¶
Feature | Continuous | Classic |
---|---|---|
Updates | frequent; often silent | Planned quarterlies |
Update order | Base + last update | Base + last update |
Update UI | None (no UI but registry settings can still be used) | Auto or off |
Update registry controls | Auto or off | Auto or off |
Services integration | All tools visible * | Free tools visible * |
Upsell enabled? | On by default | On by default |
Spelling pack | Add on | Bundled |
Font pack | Add on | Bundled |
Languages | Win: single language or MUI | MUI only |
File and preference paths | Versionless: always under DC | Versioned: Under major version, 2015|2017|2020, etc. |
Windows installer Paragon 12 ntfs for mac serial. | AcroRdrDC<version>_<langID>.exe | AcroRdr2015|2017|2020_MUI.exe |
Windows install paths | C:ProgramFilesAdobeAcrobatReaderDC | C:ProgramFilesAdobeAcrobatReader2015|2017|2020 |
Registry/plist paths | HKCUSoftwareAdobeAcrobatReaderDC | HKCUSoftwareAdobeAcrobatReader2015|2017|2020 |
Application data path | %Appdata%RoamingAdobeAcrobatDC | %Appdata%RoamingAdobeAcrobat2015|2017|2020 |
*
What services are visible in the user interface varies by the purchased track and license type. Use the Customization Wizard or registry/plist configuration to remove unwanted items from the user interface.Ftp://ftp.adobe.com/pub/adobe/reader/win/acrobatdc/
- For the Continuous track, all services are visible. Free services are functional by default, and paid-for services require an upgrade or purchase to access.
- For the Classic track, most service-based tools are hidden. Basic, paid-for services such as Create PDF and Export PDF are visible but must be enabled with a purchase.
Product versioning¶
Track release schedules and their respective versions will be different, but both the Continuous and Classic tracks share an identical methodology. The new strategy is designed to provide better granularity, support more frequent releases, and aid in troubleshooting by providing build information. In it’s generic form, the version number will appear as
major.minor.minor_minor
.Ftp Ftp Adobe Com Pub Adobe Reader Win 8
Version | Range | Notes |
---|---|---|
major | 1-255 | The last two digits of the release year.* |
minor | 1-255 | An internal number indicating when code moves from Trunk to Beta. |
minor_minor | 1-65535 | The first two digits indicate the track. 20 = Continuous. 30 = Classic. |
Hidden 4th field | Changelist number | Only visible if user clicks on the version number in the About box. |
*
The year-based version number is not the same as the Classic track name. While the Classic track versioning contains a year-number (2015|2017|2020
), the track name only changes at each major release–not every year. The version number increments every year.