### Starting IntuneManagement with App Authentication - PowerShell Source: https://github.com/micke-k/intunemanagement/blob/master/ReleaseNotes.md This command line example shows how to start the IntuneManagement script using Azure App ID and Secret/Certificate for authentication, typically used for batch processes. It requires specifying the tenant ID and can optionally include the App ID and Secret/Certificate via command line arguments. ```PowerShell Start-IntuneManagement.ps1 -tenantId "" -appid "" -secret "" ``` -------------------------------- ### Example Policy Setting OMA-URI Path Source: https://github.com/micke-k/intunemanagement/blob/master/ADMXImport.md A concrete example of the OMA-URI path used to configure the 'ShowHomeButton' policy setting for Chrome, specifying Device scope, Chrome AppID, Policy type, and the category path 'googlechrome~Startup'. ```OMA-URI ./Device/Vendor/MSFT/Policy/Config/Chrome~Policy~googlechrome~Startup/ShowHomeButton ``` -------------------------------- ### Example AdmxInstalled Registry Path Source: https://github.com/micke-k/intunemanagement/blob/master/ADMXImport.md A concrete example of the registry path created for an ingested Chrome ADMX file, showing a specific ProviderGuid, AppID, type, and filename. ```Registry Path \SOFTWARE\Microsoft\PolicyManager\AdmxInstalled\D12FCE57-F71E-4D0D-93EE-35C5E6F8C0D9\Chrome\Policy\ChromeAdmx ``` -------------------------------- ### Example ADMX Ingestion OMA-URI Path Source: https://github.com/micke-k/intunemanagement/blob/master/ADMXImport.md A concrete example of the OMA-URI path used to ingest the Chrome ADMX file, specifying 'Chrome' as the AppID and 'Policy' as the type. ```OMA-URI ./device/Vendor/MSFT/Policy/ConfigOperations/ADMXInstall/Chrome/Policy/ChromeAdmx ``` -------------------------------- ### Start Intune Management Script with JSON Settings (PowerShell) Source: https://github.com/micke-k/intunemanagement/blob/master/README.md This command demonstrates how to start the Intune Management script using settings stored in a JSON file instead of the default registry location. The -JSonSettings flag enables this mode, and the optional -JSonFile parameter allows specifying a custom path to the settings file. ```PowerShell Start-IntuneManagement.ps1 -JSonSettings [-JSonFile ] ``` -------------------------------- ### Example: Silent Batch Import with Settings Authentication (PowerShell) Source: https://github.com/micke-k/intunemanagement/blob/master/README.md This example shows how to run a silent batch import when the authentication details (App ID, Secret/Certificate) are stored within the silent batch settings JSON file itself. It only requires specifying the tenant ID and the path to the settings file on the command line. ```PowerShell Start-IntuneManagement.ps1 -Silent -SilentBatchFile "C:\Temp\BatchImport.json" -TenantId "00000000-0000-0000-0000-000000000000" ``` -------------------------------- ### Example: Silent Batch Import with App Secret (PowerShell) Source: https://github.com/micke-k/intunemanagement/blob/master/README.md This is a concrete example demonstrating how to execute a silent batch import using an Azure App ID and Secret for authentication. It specifies the path to the batch settings file, the tenant ID, the App ID, and the App Secret. ```PowerShell Start-IntuneManagement.ps1 -Silent -SilentBatchFile "C:\Temp\BatchImport.json" -TenantId "00000000-0000-0000-0000-000000000000" -AppId "00000000-0000-0000-0000-000000000001" -Secret "KJ76P~B9###9-.8I####-_MySecret" ``` -------------------------------- ### AdmxInstalled Registry Path Template Source: https://github.com/micke-k/intunemanagement/blob/master/ADMXImport.md Template for the registry path created for each successfully ingested ADMX file, containing metadata such as installation time, status, and the number of policies defined in the ADMX. ```Registry Path \SOFTWARE\Microsoft\PolicyManager\AdmxInstalled\\\\\\[Policy|Preference]\\ ``` -------------------------------- ### Export App Content Encryption Keys (PowerShell) Source: https://github.com/micke-k/intunemanagement/blob/master/ReleaseNotes.md This command demonstrates how to use the Export-EncrytionKeys script to extract encryption key information from existing .intunewin files within a specified root folder and save the output JSON files to an export folder. ```PowerShell Export-EncrytionKeys -RootFolder C:\Intune\Packages -ExportFolder C:\Intune\Download ``` -------------------------------- ### Execute IntuneManagement Silently with App Authentication (PowerShell) Source: https://github.com/micke-k/intunemanagement/blob/master/README.md This command shows the general syntax for running the IntuneManagement script in silent mode. It requires specifying the tenant ID, the path to the silent batch settings file, and optionally provides options for app authentication using either an App ID and Secret or a Certificate Thumbprint. ```PowerShell Start-IntuneManagement.ps1 -Silent -TenantId "<*TenantID*>" -SilentBatchFile <*PathToFile*> [-AppId <*AppId*>] [-Secret <*Secret*> | -Certificate <*CertThumb*>] ``` -------------------------------- ### ADMX Ingestion OMA-URI Path Template Source: https://github.com/micke-k/intunemanagement/blob/master/ADMXImport.md Template for the OMA-URI path used to initiate ADMX file ingestion on a device via the Policy CSP. It specifies the application ID, policy/preference type, and ADMX filename. ```OMA-URI ./device/Vendor/MSFT/Policy/ConfigOperations/ADMXInstall//[Policy|Preference]/ ``` -------------------------------- ### ADMX File Path on Device Template Source: https://github.com/micke-k/intunemanagement/blob/master/ADMXImport.md Template for the file system path where ingested ADMX files are stored on the target device after successful ingestion via the Policy CSP. ```Path %ProgramData%\Microsoft\PolicyManager\ADMXIngestion\\\\\\[Policy|Preference] ``` -------------------------------- ### Policy Setting OMA-URI Path Template Source: https://github.com/micke-k/intunemanagement/blob/master/ADMXImport.md Template for the OMA-URI path used to configure individual policy settings defined within an ingested ADMX file, specifying user/device scope, AppID, category path, and policy name. ```OMA-URI ./[User|Device]/vendor/msft/policy/config/~[Policy|Preference]~/ ``` -------------------------------- ### Current Registry Path Source: https://github.com/micke-k/intunemanagement/blob/master/ADMXImport.md The base registry path under HKLM where the Policy CSP stores the currently applied policy settings, separated by device or user scope (SID). ```Registry Path HKLM\Software\Microsoft\PolicyManager\Current ``` -------------------------------- ### Provider Registry Path Source: https://github.com/micke-k/intunemanagement/blob/master/ADMXImport.md The base registry path under HKLM where the Policy CSP creates subkeys for each configured OMA-URI policy setting, including those derived from ingested ADMX files. ```Registry Path HKLM\Software\Microsoft\PolicyManager\Provider ``` -------------------------------- ### ADMXDefault Registry Path Source: https://github.com/micke-k/intunemanagement/blob/master/ADMXImport.md The registry path under HKLM where the Policy CSP stores information about ingested ADMX files, including category paths, used for mapping OMA-URI settings to ADMX definitions. ```Registry Path HKLM\Software\Microsoft\PolicyManager\ADMXDefault ``` === COMPLETE CONTENT === This response contains all available snippets from this library. No additional content exists. Do not make further requests.