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

Provisioning packages freshness

Browse Source
This commit is contained in:
Vinay Pamnani (from Dev Box)
2024-07-09 13:29:15 -06:00
parent 732f1f50b7
commit 08b09d9dea
16 changed files with 294 additions and 630 deletions
Download Patch File Download Diff File Expand all files Collapse all files

32
windows/configuration/provisioning-packages/provisioning-script-to-install-app.md
View File

@ -1,8 +1,8 @@
---
title: Use a script to install a desktop app in provisioning packages
description: With Windows 10/11, you can create provisioning packages that let you quickly and efficiently configure a device without having to install a new image.
description: With Windows, you can create provisioning packages that let you quickly and efficiently configure a device without having to install a new image.
ms.topic: how-to
ms.date: 12/31/2017
ms.date: 07/09/2024
---
# Use a script to install a desktop app in provisioning packages
@ -57,14 +57,14 @@ Create a script to perform whatever work is needed to install the application(s)
You don't need to create an orchestrator script. You can have one command line per app. If necessary, you can create a script that logs the output per app, as mentioned below (rather than one orchestrator script for the entire provisioning package).
>[!NOTE]
>All actions performed by the script must happen silently, showing no UI and requiring no user interaction.
> [!NOTE]
>
>The scripts will be run on the device in system context.
> - All actions performed by the script must happen silently, showing no UI and requiring no user interaction.
> - The scripts will be run on the device in system context.
### Debugging example
Granular logging isn't built in, so the logging must be built into the script itself. Here's an example script that logs 'Hello World' to a logfile. When run on the device, the logfile will be available after provisioning is completed. As you'll see in the following examples, it's recommended that you log each action that your script performs.
Granular logging isn't built in, so the logging must be built into the script itself. Here's an example script that logs `Hello World` to a logfile. When run on the device, the logfile will be available after provisioning is completed. As you'll see in the following examples, it's recommended that you log each action that your script performs.
```log
set LOGFILE=%SystemDrive%\HelloWorld.log
@ -178,20 +178,14 @@ When you're done, [build the package](provisioning-create-package.md#build-packa
1. The command line will be executed with the directory the CommandFiles were deployed to as the working directory. This means you do not need to specific the full path to assets in the command line or from within any script.
1. The runtime provisioning component will attempt to run the scripts from the provisioning package at the earliest point possible, depending on the stage when the PPKG was added. For example, if the package was added during the Out-of-Box Experience, it will be run immediately after the package is applied, while the out of box experience is still happening. This is before the user account configuration options are presented to the user. A spinning progress dialog will appear and "please wait" will be displayed on the screen.
>[!NOTE]
>There is a timeout of 30 minutes for the provisioning process at this point. All scripts and installs need to complete within this time.
> [!NOTE]
> There is a timeout of 30 minutes for the provisioning process at this point. All scripts and installs need to complete within this time.
1. The scripts are executed in the background as the rest of provisioning continues to run. For packages added on existing systems using the double-click to install, there's no notification that provisioning or script execution has completed
## Related articles
## Next steps
- [Provisioning packages for Windows client](provisioning-packages.md)
- [How provisioning works in Windows client](provisioning-how-it-works.md)
- [Install Windows Configuration Designer](provisioning-install-icd.md)
- [Create a provisioning package](provisioning-create-package.md)
- [Apply a provisioning package](provisioning-apply-package.md)
- [Settings changed when you uninstall a provisioning package](provisioning-uninstall-package.md)
- [Provision PCs with common settings for initial deployment (simple provisioning)](provision-pcs-for-initial-deployment.md)
- [Windows Configuration Designer command-line interface (reference)](provisioning-command-line.md)
- [PowerShell cmdlets for provisioning Windows client (reference)](provisioning-powershell.md)
- [Create a provisioning package with multivariant settings](provisioning-multivariant.md)
> [!div class="nextstepaction"]
> Learn more about applying a provisioning package:
>
> [Apply a provisioning package](provisioning-apply-package.md)