> For the complete documentation index, see [llms.txt](https://www.osdcloud.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.osdcloud.com/osdcloud-v1/osdcloud-automate/provisioning/msi-application-ppkg.md). # MSI Application PPKG OSD 23.5.23.1+ Updated May 23, 2023 I'll walk you through how to create a Provisioning Package for OS Deployment. In this example, I'll be working with Google Chrome Enterprise. Start by downloading the MSI from this link {% embed url="" %} On that link, you can select the Google Chrome you want to download. I'm following these options 1. Stable 2. MSI (not bundle) 3. 64 bit Architecture 4. Make a note of the version, in my case it is 113.0.5672.127 5. Download the file to your Downloads directory

## Windows Configuration Designer You should have Windows Configuration Designer installed. Open it and select Advanced provisioning

Enter the details of your Project. The Name field doesn't take periods well, so keep that in mind. Pres Next

(1) Enter project details (2) Press Next

(1) All Windows desktop editions (2) Press Next

## Runtime settings Complete the following steps 1. Expand Runtime settings 2. Expand to ProvisoiningCommands, Primary Context, Command 3. Add a Name for the install. I chose Install 4. Press the Add button

Complete the following steps 1. Select the Name that you selected for step 3 in the last screenshot. For me, this is Install 2. CommandFile: Browse to the Google Chrome Enterprise that was downloaded earlier 3. Commands 1. CommandLine: msiexec /i "googlechromestandaloneenterprise64.msi" /passive /norestart 2. ContinueInstall: TRUE. You don't want this to kill your deployment if the installation fails 3. RestartRequired: FALSE. 4. Export Provisioning Package

(1) Describe the provisioning package (2) Press Next

--- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://www.osdcloud.com/osdcloud-v1/osdcloud-automate/provisioning/msi-application-ppkg.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.