Windows Provisioning Errors

Owned by Leigh Jones
Last updated: Nov 19, 2024
1 min read

Microsoft Provisioning portion logs into Applications and Services Logs > Microsoft > Windows > Provisioning-Diagnostics-Provider > Admin

Any errors during the provisioning portion up to and including CleanPC option should log as event since all that happens before ezdeploy EZDService actually starts deploying agents, running scripts or kicking off Windows Update (including Feature Updates)

  1. Error code 0x800700B7 - this error is known to be triggered when the computer already has an existing package.

    1. Remove an existing ppkg by going to Settings>Accounts>Access Work or School>Add or remove a provisioning package

       

  2. Additional potential items to review.

    1. Size of the ppkg - normally will be 650kb up to 1mb on average. If 0k or very small most likely corrupted and you will need to download ppkg fresh copy.

    2. USB Drive - verify FAT32 Format - potentially may need to reformat and save ppkg fresh

    3. Missing network drivers. Example recently a new computer from factory was missing drivers entirely for the NIC so once the driver installed - provisioning worked.

    4. The Windows OS has issues - would need to boot and check eventlogs, perhaps chkdsk and sfc /scannow etc.

       

 

The content of this site is proprietary and confidential information of Stack Advisors, LLC. It is not intended to be distributed to any third party without the written consent of Stack Advisors, LLC.