deepblue/windows-itpro-docs
1
0
Fork 0
mirror of https://github.com/MicrosoftDocs/windows-itpro-docs.git synced 2025-06-18 03:43:39 +00:00
Code Issues Actions 3 Packages Projects Releases Wiki Activity

better draft

Browse Source
This commit is contained in:
Liz Long
2023-01-19 12:47:49 -05:00
parent eaced9a320
commit cffb6df30f
2 changed files with 43 additions and 54 deletions
Download Patch File Download Diff File Expand all files Collapse all files

54
windows/client-management/mdm/diagnose-provisioning-packages.md
View File

@ -1,54 +0,0 @@
---
title: Diagnose Provisioning Packages
description: Diagnose general failures in provisioning.
ms.reviewer:
manager: aaroncz
ms.author: lizlong
ms.topic: article
ms.prod: windows-client
ms.technology: itpro-manage
author: lizgt2000
ms.date: 01/18/2023
ms.collection: highpri
---
# Diagnose Provisioning Packages
## Unable to apply Power Settings
When applying certain provisioning packages containing [power settings](../windows-hardware/customize/power-settings/configure-power-settings?view=windows-11) they require elevated permissions which are not applied when applying PPKGs [after the initial setup](/windows/configuration/provisioning-packages/provisioning-apply-package#after-initial-setup). An error of STATUS_PRIVILEGE_NOT_HELD (HRESULT=0xc0000061) is given when applying these packages with the incorrect security context.
Simply placing the PPKG into %WINDIR%/Provisioning/Packages and rebooting the machine will apply the packages with the [correct security context](../windows/win32/services/localsystem-account) as stated in [Configure power settings](../windows-hardware/customize/power-settings/configure-power-settings?view=windows-11)
## Unable to perform Bulk Enrollment in Azure AD
See [allow enrollment into Azure AD for provisioning packages](https://techcommunity.microsoft.com/t5/intune-customer-success/bulk-join-a-windows-device-to-azure-ad-and-microsoft-endpoint/ba-p/2381400).
<!--
TODO: @Harrison Chotzen
-->
## Unable to apply a multivariant provisioning package
If creating a [multivariant package](../windows/configuration/provisioning-packages/provisioning-multivariant). It may be difficult to diagnose why a certain target did not get applied. There may be conditions improperly authored which when applied to the target device may not be evaluated as expected.
<!--
fix below
I think that now that the information is combined there is overlap and confusion
-->
Tooling has been included to surface these conditions in the event a certain target did not get applied.
## Diagnosing general failures in provisioning
To help diagnose common problems, you can run the [MdmDiagnosticsTool](../windows/client-management/diagnose-mdm-failures-in-windows-10) and capture multivariant condition values.
## Diagnosing multivariant problems
When applying multivariant packages it may be difficult to see why a target was not applied. The [MdmDiagnosticsTool](../windows/client-management/diagnose-mdm-failures-in-windows-10) includes the multivariant condition values on the target system.
<!--
this also needs to be fixed
-->
(Zinc semester addition - Deliverable 41742231: [Hydra] [Tooling] Add MultiVariant handler values to MdmdiagnosticsTool diagnostics) which can be helpful when diagnosing why the PPKG was not applied in the target system.
The MDMDiagReport.xml will contain the Multivariant Conditions in the report. Using powershell, we can get the values like so:
([XML](Get-Content MDMDiagReport.xml)).SelectNodes('//Multivariant') | Select -ExpandProperty Condition