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

Add periods to alt text

Browse Source 
No other changes
This commit is contained in:
Gary Moore
2021-08-21 13:08:01 -07:00
parent 963086456e
commit 17262985e6
406 changed files with 2100 additions and 2100 deletions
Download Patch File Download Diff File Expand all files Collapse all files

10
windows/configuration/provisioning-packages/how-it-pros-can-use-configuration-service-providers.md
View File

@ -38,7 +38,7 @@ Each CSP provides access to specific settings. For example, the [Wi-Fi CSP](/win
CSPs are behind many of the management tasks and policies for Windows 10, both in Microsoft Intune and in non-Microsoft MDM service providers. For example, in Intune, the policy to allow search suggestions in the Microsoft Edge address bar uses **Browser/AllowSearchSuggestionsinAddressBar** in the [Policy CSP](/windows/client-management/mdm/policy-configuration-service-provider).
![how intune maps to csp](../images/policytocsp.png)
![how intune maps to csp.](../images/policytocsp.png)
CSPs receive configuration policies in the XML-based Synchronization Markup Language (SyncML) format, pushed from an MDM-compliant management server, such as Microsoft Intune. Traditional enterprise management systems, such as Microsoft Endpoint Configuration Manager, can also target CSPs, by using a client-side Windows Management Instrumentation (WMI)-to-CSP Bridge.
@ -66,7 +66,7 @@ You can use Windows Configuration Designer to create [provisioning packages](./p
Many settings in Windows Configuration Designer will display documentation for that setting in the center pane, and will include a reference to the CSP if the setting uses one, as shown in the following image.
![how help content appears in icd](../images/cspinicd.png)
![how help content appears in icd.](../images/cspinicd.png)
[Provisioning packages in Windows 10](provisioning-packages.md) explains how to use the Windows Configuration Designer tool to create a runtime provisioning package.
@ -86,7 +86,7 @@ All CSPs in Windows 10 are documented in the [Configuration service provider ref
The [main CSP topic](/windows/client-management/mdm/configuration-service-provider-reference) tells you which CSPs are supported on each edition of Windows 10, and links to the documentation for each individual CSP.
![csp per windows edition](../images/csptable.png)
![csp per windows edition.](../images/csptable.png)
The documentation for each CSP follows the same structure. After an introduction that explains the purpose of the CSP, a diagram shows the parts of the CSP in tree format.
@ -94,7 +94,7 @@ The full path to a specific configuration setting is represented by its Open Mob
The following example shows the diagram for the [AssignedAccess CSP](/windows/client-management/mdm/assignedaccess-csp). The diagram maps to the XML for that CSP. Notice the different shapes in the diagram: rounded elements are nodes, and rectangular elements are settings or policies for which a value must be supplied.
![assigned access csp tree](../images/provisioning-csp-assignedaccess.png)
![assigned access csp tree.](../images/provisioning-csp-assignedaccess.png)
The element in the tree diagram after the root node tells you the name of the CSP. Knowing this structure, you would recognize in XML the parts of the URI path for that CSP and, if you saw it in XML, you would know which CSP reference to look up. For example, in the following OMS-URI path for the kiosk mode app settings, you can see that it uses the [AssignedAccess CSP](/windows/client-management/mdm/assignedaccess-csp).
@ -104,7 +104,7 @@ The element in the tree diagram after the root node tells you the name of the CS
When an element in the diagram uses _italic_ font, it indicates a placeholder for specific information, such as the tenant ID in the following example.
![placeholder in csp tree](../images/csp-placeholder.png)
![placeholder in csp tree.](../images/csp-placeholder.png)
After the diagram, the documentation describes each element. For each policy or setting, the valid values are listed.

6
windows/configuration/provisioning-packages/provision-pcs-for-initial-deployment.md
View File

@ -58,7 +58,7 @@ Provisioning packages can include management instructions and policies, installa
> [!TIP]
> Use the desktop wizard to create a package with the common settings, then switch to the advanced editor to add other settings, apps, policies, etc.
>
>![open advanced editor](../images/icd-simple-edit.png)
>![open advanced editor.](../images/icd-simple-edit.png)
## Create the provisioning package
@ -68,11 +68,11 @@ Use the Windows Configuration Designer tool to create a provisioning package. [L
2. Click **Provision desktop devices**.
![ICD start options](../images/icd-create-options-1703.png)
![ICD start options.](../images/icd-create-options-1703.png)
3. Name your project and click **Finish**. The pages for desktop provisioning will walk you through the following steps.
![ICD desktop provisioning](../images/icd-desktop-1703.png)
![ICD desktop provisioning.](../images/icd-desktop-1703.png)
> [!IMPORTANT]
> When you build a provisioning package, you may include sensitive information in the project files and in the provisioning package (.ppkg) file. Although you have the option to encrypt the .ppkg file, project files are not encrypted. You should store the project files in a secure location and delete the project files when they are no longer needed.

8
windows/configuration/provisioning-packages/provision-pcs-with-apps-and-certificates.md
View File

@ -46,7 +46,7 @@ Use the Windows Imaging and Configuration Designer (ICD) tool included in the Wi
2. Click **Advanced provisioning**.
![ICD start options](../images/icdstart-option.png)
![ICD start options.](../images/icdstart-option.png)
3. Name your project and click **Next**.
@ -73,19 +73,19 @@ Universal apps that you can distribute in the provisioning package can be line-o
2. For **DeviceContextApp**, specify the **PackageFamilyName** for the app. In Microsoft Store for Business, the package family name is listed in the **Package details** section of the download page.
![details for offline app package](../images/uwp-family.png)
![details for offline app package.](../images/uwp-family.png)
3. For **ApplicationFile**, click **Browse** to find and select the target app (either an \*.appx or \*.appxbundle).
4. For **DependencyAppxFiles**, click **Browse** to find and add any dependencies for the app. In Microsoft Store for Business, any dependencies for the app are listed in the **Required frameworks** section of the download page.
![required frameworks for offline app package](../images/uwp-dependencies.png)
![required frameworks for offline app package.](../images/uwp-dependencies.png)
5. For **DeviceContextAppLicense**, enter the **LicenseProductID**.
- In Microsoft Store for Business, generate the unencoded license for the app on the app's download page, and change the extension of the license file from **.xml** to **.ms-windows-store-license**.
![generate license for offline app](../images/uwp-license.png)
![generate license for offline app.](../images/uwp-license.png)
- Open the license file and search for **LicenseID=** to get the GUID, enter the GUID in the **LicenseProductID** field and click **Add**.

10
windows/configuration/provisioning-packages/provision-pcs-with-apps.md
View File

@ -74,11 +74,11 @@ When you add an app in a Windows Configuration Designer wizard, the appropriate
2. Enter a name for the first app, and then click **Add**.
![enter name for first app](../images/wcd-app-name.png)
![enter name for first app.](../images/wcd-app-name.png)
3. Configure the settings for the appropriate installer type.
![enter settings for first app](../images/wcd-app-commands.png)
![enter settings for first app.](../images/wcd-app-commands.png)
## Add a universal app to your package
@ -88,19 +88,19 @@ Universal apps that you can distribute in the provisioning package can be line-o
2. For **DeviceContextApp**, specify the **PackageFamilyName** for the app. In Microsoft Store for Business, the package family name is listed in the **Package details** section of the download page.
![details for offline app package](../images/uwp-family.png)
![details for offline app package.](../images/uwp-family.png)
3. For **ApplicationFile**, click **Browse** to find and select the target app (either an \*.appx or \*.appxbundle).
4. For **DependencyAppxFiles**, click **Browse** to find and add any dependencies for the app. In Microsoft Store for Business, any dependencies for the app are listed in the **Required frameworks** section of the download page.
![required frameworks for offline app package](../images/uwp-dependencies.png)
![required frameworks for offline app package.](../images/uwp-dependencies.png)
5. For **DeviceContextAppLicense**, enter the **LicenseProductID**.
- In Microsoft Store for Business, generate the unencoded license for the app on the app's download page.
![generate license for offline app](../images/uwp-license.png)
![generate license for offline app.](../images/uwp-license.png)
- Open the license file and search for **LicenseID=** to get the GUID, enter the GUID in the **LicenseProductID** field and click **Add**.

14
windows/configuration/provisioning-packages/provisioning-apply-package.md
View File

@ -35,7 +35,7 @@ Provisioning packages can be applied to a device during the first-run experience
1. Start with a computer on the first-run setup screen. If the PC has gone past this screen, reset the PC to start over. To reset the PC, go to **Settings** > **Update & security** > **Recovery** > **Reset this PC**.
![The first screen to set up a new PC](../images/oobe.jpg)
![The first screen to set up a new PC.](../images/oobe.jpg)
2. Insert the USB drive. Windows Setup will recognize the drive and ask if you want to set up the device. Select **Set up**.
@ -43,11 +43,11 @@ Provisioning packages can be applied to a device during the first-run experience
3. The next screen asks you to select a provisioning source. Select **Removable Media** and tap **Next**.
![Provision this device](../images/prov.jpg)
![Provision this device.](../images/prov.jpg)
4. Select the provisioning package (\*.ppkg) that you want to apply, and tap **Next**.
![Choose a package](../images/choose-package.png)
![Choose a package.](../images/choose-package.png)
5. Select **Yes, add it**.
@ -59,7 +59,7 @@ Provisioning packages can be applied to a device during the first-run experience
Insert the USB drive to a desktop computer, navigate to **Settings** > **Accounts** > **Access work or school** > **Add or remove a provisioning package** > **Add a package**, and select the package to install. For a provisioning package stored on a network folder or on a SharePoint site, navigate to the provisioning package and double-click it to begin installation.
![add a package option](../images/package.png)
![add a package option.](../images/package.png)
## Mobile editions
@ -68,13 +68,13 @@ Insert the USB drive to a desktop computer, navigate to **Settings** > **Account
1. Insert an SD card containing the provisioning package into the device.
2. Navigate to **Settings** > **Accounts** > **Access work or school** > **Add or remove a provisioning package** > **Add a package**, and select the package to install.
![add a package option](../images/packages-mobile.png)
![add a package option.](../images/packages-mobile.png)
3. Click **Add**.
4. On the device, the **Is this package from a source you trust?** message will appear. Tap **Yes, add it**.
![Is this package from a source you trust](../images/package-trust.png)
![Is this package from a source you trust.](../images/package-trust.png)
### Copying the provisioning package to the device
@ -84,7 +84,7 @@ Insert the USB drive to a desktop computer, navigate to **Settings** > **Account
3. On the device, the **Is this package from a source you trust?** message will appear. Tap **Yes, add it**.
![Is this package from a source you trust](../images/package-trust.png)
![Is this package from a source you trust.](../images/package-trust.png)

10
windows/configuration/provisioning-packages/provisioning-create-package.md
View File

@ -39,7 +39,7 @@ You can use Windows Configuration Designer to create a provisioning package (.pp
2. Select your desired option on the **Start** page, which offers multiple options for creating a provisioning package, as shown in the following image:
![Configuration Designer wizards](../images/icd-create-options-1703.png)
![Configuration Designer wizards.](../images/icd-create-options-1703.png)
- The following wizard options provide a simple interface for configuring common settings for desktop, mobile, and kiosk devices:
@ -56,7 +56,7 @@ You can use Windows Configuration Designer to create a provisioning package (.pp
>[!TIP]
> You can start a project in the simple wizard editor and then switch the project to the advanced editor.
>
> ![Switch to advanced editor](../images/icd-switch.png)
> ![Switch to advanced editor.](../images/icd-switch.png)
3. Enter a name for your project, and then select **Next**.
@ -87,7 +87,7 @@ You can use Windows Configuration Designer to create a provisioning package (.pp
For an advanced provisioning project, Windows Configuration Designer opens the **Available customizations** pane. The example in the following image is based on **All Windows desktop editions** settings.
![What the ICD interface looks like](../images/icd-runtime.png)
![What the ICD interface looks like.](../images/icd-runtime.png)
The settings in Windows Configuration Designer are based on Windows 10 configuration service providers (CSPs). To learn more about CSPs, see [Introduction to configuration service providers (CSPs) for IT pros](./how-it-pros-can-use-configuration-service-providers.md).
@ -103,14 +103,14 @@ The process for configuring settings is similar for all settings. The following
For details on each specific setting, see [Windows Provisioning settings reference](../wcd/wcd.md). The reference topic for a setting is also displayed in Windows Configuration Designer when you select the setting, as shown in the following image.
![Windows Configuration Designer opens the reference topic when you select a setting](../images/icd-setting-help.png)
![Windows Configuration Designer opens the reference topic when you select a setting.](../images/icd-setting-help.png)
## Build package
1. After you're done configuring your customizations, select **Export**, and then select **Provisioning Package**.
![Export on top bar](../images/icd-export-menu.png)
![Export on top bar.](../images/icd-export-menu.png)
2. In the **Describe the provisioning package** window, enter the following information, and then select **Next**:
- **Name** - This field is pre-populated with the project name. You can change this value by entering a different name in the **Name** field.

2
windows/configuration/provisioning-packages/provisioning-install-icd.md
View File

@ -66,7 +66,7 @@ On devices running Windows 10, you can install [the Windows Configuration Design
6. On the **Select the features you want to install** page, clear all selections except **Configuration Designer**, and then click **Install**.
![Only Configuration Designer selected for installation](../images/icd-install.png)
![Only Configuration Designer selected for installation.](../images/icd-install.png)
## Current Windows Configuration Designer limitations

2
windows/configuration/provisioning-packages/provisioning-multivariant.md
View File

@ -35,7 +35,7 @@ In the XML file, you provide an **Id**, or friendly name, for each **Target**. E
A **Target** can have more than one **TargetState**, and a **TargetState** can have more than one **Condition**.
![Target with multiple target states and conditions](../images/multi-target.png)
![Target with multiple target states and conditions.](../images/multi-target.png)
The following table describes the logic for the target definition.

2
windows/configuration/provisioning-packages/provisioning-packages.md
View File

@ -124,7 +124,7 @@ For details about the settings you can customize in provisioning packages, see [
Windows ICD for Windows 10, version 1607, simplified common provisioning scenarios.
![Configuration Designer options](../images/icd.png)
![Configuration Designer options.](../images/icd.png)
Windows ICD in Windows 10, version 1607, supported the following scenarios for IT administrators:

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

@ -189,13 +189,13 @@ cmd /c InstallMyApp.bat
In Windows Configuration Designer, this looks like:
![Command line in Selected customizations](../images/icd-script1.png)
![Command line in Selected customizations.](../images/icd-script1.png)
You also need to add the relevant assets for that command line including the orchestrator script and any other assets it references such as installers or .cab files.
In Windows Configuration Designer, that is done by adding files under the `ProvisioningCommands/DeviceContext/CommandFiles` setting.
![Command files in Selected customizations](../images/icd-script2.png)
![Command files in Selected customizations.](../images/icd-script2.png)
When you are done, [build the package](provisioning-create-package.md#build-package).