mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-05-12 05:17:22 +00:00
move lockdown-features-windows-10.md to previous-versions
This commit is contained in:
Paolo Matarazzo
parent
ef6cafb67a
commit
4069d91e55
@ -1,5 +1,5 @@
|
||||
---
|
||||
title: More kiosk methods and reference information (Windows 10/11)
|
||||
title: More kiosk methods and reference information
|
||||
description: Find more information for configuring, validating, and troubleshooting kiosk configuration.
|
||||
ms.topic: reference
|
||||
ms.date: 12/31/2017
|
||||
|
||||
@ -1,5 +1,5 @@
|
||||
---
|
||||
title: Policies enforced on kiosk devices (Windows 10/11)
|
||||
title: Policies enforced on kiosk devices
|
||||
description: Learn about the policies enforced on a device when you configure it as a kiosk.
|
||||
ms.topic: article
|
||||
ms.date: 12/31/2017
|
||||
|
||||
@ -1,5 +1,5 @@
|
||||
---
|
||||
title: Validate kiosk configuration (Windows 10/11)
|
||||
title: Validate kiosk configuration
|
||||
description: In this article, learn what to expect on a multi-app kiosk in Windows 10/11 Pro, Enterprise, and Education.
|
||||
|
||||
ms.topic: article
|
||||
|
||||
@ -1,5 +1,5 @@
|
||||
---
|
||||
title: Assigned Access configuration kiosk XML reference (Windows 10/11)
|
||||
title: Assigned Access configuration kiosk XML reference
|
||||
description: Learn about the assigned access configuration (kiosk) for XML and XSD for kiosk device configuration in Windows 10/11.
|
||||
|
||||
ms.topic: article
|
||||
|
||||
@ -1,7 +1,6 @@
|
||||
---
|
||||
title: Configuration service providers for IT pros (Windows 10/11)
|
||||
title: Configuration service providers for IT pros
|
||||
description: Describes how IT pros and system administrators can use configuration service providers (CSPs) to configure devices.
|
||||
ms.reviewer: gkomatsu
|
||||
ms.topic: article
|
||||
ms.date: 12/31/2017
|
||||
---
|
||||
|
||||
@ -1,7 +1,6 @@
|
||||
---
|
||||
title: Provision PCs with common settings (Windows 10/11)
|
||||
title: Provision PCs with common settings
|
||||
description: Create a provisioning package to apply common settings to a PC running Windows 10.
|
||||
ms.reviewer: gkomatsu
|
||||
ms.topic: article
|
||||
ms.date: 12/31/2017
|
||||
---
|
||||
|
||||
@ -2,7 +2,6 @@
|
||||
title: Provision PCs with apps
|
||||
description: Learn how to install multiple Universal Windows Platform (UWP) apps and Windows desktop applications (Win32) in a provisioning package.
|
||||
ms.topic: article
|
||||
ms.reviewer: gkomatsu
|
||||
ms.date: 12/31/2017
|
||||
---
|
||||
|
||||
|
||||
@ -1,8 +1,7 @@
|
||||
---
|
||||
title: Apply a provisioning package (Windows 10/11)
|
||||
title: Apply a provisioning package
|
||||
description: Provisioning packages can be applied to a device during initial setup (OOBE) and after (runtime).
|
||||
ms.topic: article
|
||||
ms.reviewer: gkomatsu
|
||||
ms.date: 12/31/2017
|
||||
---
|
||||
|
||||
@ -28,8 +27,8 @@ To apply a provisioning package from a USB drive during initial setup:
|
||||
|
||||
1. Insert the USB drive. If nothing happens when you insert the USB drive, press the Windows key five times.
|
||||
|
||||
- If there is only one provisioning package on the USB drive, the provisioning package is applied. See step 5.
|
||||
- If there is more than one provisioning package on the USB drive, Windows setup will recognize the drive and ask how you want to provision the device. Select **Install provisioning package** and select **Next**.
|
||||
- If there's only one provisioning package on the USB drive, the provisioning package is applied. See step 5.
|
||||
- If there's more than one provisioning package on the USB drive, Windows setup recognizes the drive and ask how you want to provision the device. Select **Install provisioning package** and select **Next**.
|
||||
|
||||
:::image type="content" source="images/provisioning-oobe-choice.png" alt-text="What would you like to do?":::
|
||||
|
||||
@ -45,7 +44,7 @@ To apply a provisioning package from a USB drive during initial setup:
|
||||
|
||||
## After initial setup
|
||||
|
||||
Provisioning packages can be applied after initial setup through Windows settings or by simply double-clicking a provisioning package.
|
||||
Provisioning packages can be applied after initial setup through Windows settings or by double-clicking a provisioning package.
|
||||
|
||||
### Windows Settings
|
||||
|
||||
@ -61,11 +60,11 @@ Provisioning packages can be applied after initial setup through Windows setting
|
||||
|
||||
:::image type="content" source="images/provisioning-runtime-add-package.png" alt-text="Select and add a package.":::
|
||||
|
||||
1. Provisioning packages require administrator privileges as they can modify system policies and run scripts at the system level. Ensure you trust the package you are installing before accepting the UAC prompt. Select **Yes**.
|
||||
1. Provisioning packages require administrator privileges as they can modify system policies and run scripts at the system level. Ensure you trust the package you're installing before accepting the UAC prompt. Select **Yes**.
|
||||
|
||||
:::image type="content" source="images/provisioning-runtime-UAC.png" alt-text="Do you want to allow changes to your device?":::
|
||||
|
||||
1. The provisioning runtime will ask if the package is from a source you trust. Verify that you are applying the correct package and that it is trusted. Select **Yes, add it**.
|
||||
1. The provisioning runtime asks if the package is from a source you trust. Verify that you're applying the correct package and that it's trusted. Select **Yes, add it**.
|
||||
|
||||
:::image type="content" source="images/provisioning-runtime-trust.png" alt-text="Do you trust this package?":::
|
||||
|
||||
@ -77,11 +76,11 @@ To apply a provisioning package directly, such as from a USB drive, folder, netw
|
||||
|
||||
:::image type="content" source="images/provisioning-runtime-click-to-install.png" alt-text="Double-click package to being installation.":::
|
||||
|
||||
1. Provisioning packages require administrator privileges as they can modify system policies and run scripts at the system level. Ensure you trust the package you are installing before accepting the UAC prompt. Select **Yes**.
|
||||
1. Provisioning packages require administrator privileges as they can modify system policies and run scripts at the system level. Ensure you trust the package you're installing before accepting the UAC prompt. Select **Yes**.
|
||||
|
||||
:::image type="content" source="images/provisioning-runtime-UAC.png" alt-text="Do you want to allow changes to your device?":::
|
||||
|
||||
1. The provisioning runtime will ask if the package is from a source you trust. Verify that you are applying the correct package and that it is trusted. Select **Yes, add it**.
|
||||
1. The provisioning runtime asks if the package is from a source you trust. Verify that you're applying the correct package and that it's trusted. Select **Yes, add it**.
|
||||
|
||||
:::image type="content" source="images/provisioning-runtime-trust.png" alt-text="Do you trust this package?":::
|
||||
|
||||
|
||||
@ -1,8 +1,7 @@
|
||||
---
|
||||
title: Windows Configuration Designer command-line interface (Windows 10/11)
|
||||
title: Windows Configuration Designer command-line interface
|
||||
description: Learn more about the ICD syntax, switches, and arguments that you can use in the Windows Configuration Designer command-line interface for Windows10/11 client devices.
|
||||
ms.topic: article
|
||||
ms.reviewer: gkomatsu
|
||||
ms.date: 12/31/2017
|
||||
---
|
||||
|
||||
|
||||
@ -1,8 +1,7 @@
|
||||
---
|
||||
title: Create a provisioning package (Windows 10/11)
|
||||
title: Create a provisioning package
|
||||
description: Learn how to create a provisioning package for Windows 10/11, which lets you quickly configure a device without having to install a new image.
|
||||
ms.topic: article
|
||||
ms.reviewer: gkomatsu
|
||||
ms.date: 12/31/2017
|
||||
---
|
||||
|
||||
|
||||
@ -2,7 +2,6 @@
|
||||
title: How provisioning works in Windows 10/11
|
||||
description: Learn more about how provisioning package work on Windows client devices. A provisioning package (.ppkg) is a container for a collection of configuration settings.
|
||||
ms.topic: article
|
||||
ms.reviewer: gkomatsu
|
||||
ms.date: 12/31/2017
|
||||
---
|
||||
|
||||
|
||||
@ -1,5 +1,5 @@
|
||||
---
|
||||
title: Create a provisioning package with multivariant settings (Windows 10/11)
|
||||
title: Create a provisioning package with multivariant settings
|
||||
description: Create a provisioning package with multivariant settings to customize the provisioned settings for defined conditions.
|
||||
ms.topic: article
|
||||
ms.date: 12/31/2017
|
||||
|
||||
@ -1,9 +1,8 @@
|
||||
---
|
||||
title: PowerShell cmdlets for provisioning Windows 10/11 (Windows 10/11)
|
||||
title: PowerShell cmdlets for provisioning Windows 10/11
|
||||
description: Learn more about the Windows PowerShell cmdlets that you can use with Provisioning packages on Windows10/11 client desktop devices.
|
||||
ms.topic: article
|
||||
|
||||
ms.reviewer: gkomatsu
|
||||
ms.date: 12/31/2017
|
||||
---
|
||||
|
||||
|
||||
@ -1,8 +1,7 @@
|
||||
---
|
||||
title: Use a script to install a desktop app in provisioning packages (Windows 10/11)
|
||||
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.
|
||||
ms.topic: article
|
||||
ms.reviewer: gkomatsu
|
||||
ms.date: 12/31/2017
|
||||
---
|
||||
|
||||
@ -14,7 +13,7 @@ This walkthrough describes how to include scripts in a Windows client provisioni
|
||||
|
||||
1. On the device where you're authoring the package, place all of your assets in a known location. Each asset must have a unique filename, because all files will be copied to the same temp directory on the device. It's common for many apps to have an installer called 'install.exe' or similar, and there may be name overlap because of that. To fix this, you can use the technique described in the next step to include a complete directory structure that is then expanded into the temp directory on the device. The most common use for this would be to include a subdirectory for each application.
|
||||
|
||||
1. If you need to include a directory structure of files, you will need to cab the assets for easy inclusion in the provisioning packages.
|
||||
1. If you need to include a directory structure of files, you'll need to cab the assets for easy inclusion in the provisioning packages.
|
||||
|
||||
## Cab the application assets
|
||||
|
||||
@ -65,7 +64,7 @@ You don't need to create an orchestrator script. You can have one command line p
|
||||
|
||||
### Debugging example
|
||||
|
||||
Granular logging is not built in, so the logging must be built into the script itself. Here is 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 will 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
|
||||
@ -126,7 +125,7 @@ echo result: %ERRORLEVEL% >> %LOGFILE%
|
||||
|
||||
Your provisioning package can include multiple **CommandFiles**.
|
||||
|
||||
You are allowed one **CommandLine** per provisioning package. The batch files shown above are orchestrator scripts that manage the installation and call any other scripts included in the provisioning package. The orchestrator script is what should be invoked from the **CommandLine** specified in the package.
|
||||
You're allowed one **CommandLine** per provisioning package. The batch files shown above are orchestrator scripts that manage the installation and call any other scripts included in the provisioning package. The orchestrator script is what should be invoked from the **CommandLine** specified in the package.
|
||||
|
||||
Here's a table describing this relationship, using the PowerShell example from above:
|
||||
|
||||
@ -134,7 +133,7 @@ Here's a table describing this relationship, using the PowerShell example from a
|
||||
| --- | --- | --- |
|
||||
| ProvisioningCommands/DeviceContext/CommandLine | cmd /c PowerShell_Example.bat | The command line needed to invoke the orchestrator script. |
|
||||
| ProvisioningCommands/DeviceContext/CommandFiles | PowerShell_Example.bat | The single orchestrator script referenced by the command line that handles calling into the required installers or performing any other actions such as expanding cab files. This script must do the required logging. |
|
||||
| ProvisioningCommands/DeviceContext/CommandFiles | my_powershell_script.ps1 | Other assets referenced by the orchestrator script. In this example, there is only one, but there could be many assets referenced here. One common use case is using the orchestrator to call a series of install.exe or setup.exe installers to install several applications. Each of those installers must be included as an asset here. |
|
||||
| ProvisioningCommands/DeviceContext/CommandFiles | my_powershell_script.ps1 | Other assets referenced by the orchestrator script. In this example, there's only one, but there could be many assets referenced here. One common use case is using the orchestrator to call a series of install.exe or setup.exe installers to install several applications. Each of those installers must be included as an asset here. |
|
||||
|
||||
### Add script to provisioning package
|
||||
|
||||
@ -156,11 +155,11 @@ In Windows Configuration Designer, that is done by adding files under the `Provi
|
||||
|
||||
|
||||
|
||||
When you are done, [build the package](provisioning-create-package.md#build-package).
|
||||
When you're done, [build the package](provisioning-create-package.md#build-package).
|
||||
|
||||
### Remarks
|
||||
|
||||
1. No user interaction or console output is supported via ProvisioningCommands. All work needs to be silent. If your script attempts to do any of the following it will cause undefined behavior, and could put the device in an unrecoverable state if executed during setup or the Out of Box Experience:
|
||||
1. No user interaction or console output is supported via ProvisioningCommands. All work needs to be silent. If your script attempts to do any of the following it causes undefined behavior, and could put the device in an unrecoverable state if executed during setup or the Out of Box Experience:
|
||||
|
||||
1. Echo to console
|
||||
1. Display anything on the screen
|
||||
@ -182,7 +181,7 @@ When you are done, [build the package](provisioning-create-package.md#build-pack
|
||||
>[!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 is no notification that provisioning or script execution has completed
|
||||
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
|
||||
|
||||
|
||||
@ -1,8 +1,7 @@
|
||||
---
|
||||
title: Uninstall a provisioning package - reverted settings (Windows 10/11)
|
||||
title: Uninstall a provisioning package - reverted settings
|
||||
description: This article lists the settings that are reverted when you uninstall a provisioning package on Windows 10/11 desktop client devices.
|
||||
ms.topic: article
|
||||
ms.reviewer: gkomatsu
|
||||
ms.date: 12/31/2017
|
||||
---
|
||||
|
||||
|
||||
@ -9,8 +9,6 @@ ms.topic: article
|
||||
|
||||
Microsoft User Experience Virtualization (UE-V) supports the synchronization of Microsoft Office application settings. The combination of UE-V and App-V support for Office enables the same experience on virtualized instances of Office from any UE-V-enabled device or virtualized desktop.
|
||||
|
||||
To synchronize Office applications settings, you can download Office templates from the [User Experience Virtualization (UE-V) Template Gallery](https://gallery.technet.microsoft.com/site/search?f%5B0%5D.Type=RootCategory&f%5B0%5D.Value=UE-V&f%5B0%5D.Text=UE-V). This resource provides Microsoft-authored UE-V settings location templates and community-developed settings location templates.
|
||||
|
||||
## Microsoft Office support in UE-V
|
||||
|
||||
UE-V includes settings location templates for Microsoft Office 2016, 2013, and 201. In previous versions of UE-V, settings location templates for Office 2013 and Office 2010 were distributed and registered when you installed the UE-V agent. Now that UE-V is a feature in Windows 10, version 1607, settings location templates are installed when you install or upgrade to the new operating system.
|
||||
|
||||
@ -102,8 +102,6 @@ To validate a UE-V settings location template with the UE-V template generator:
|
||||
|
||||
## <a href="" id="share"></a>Share settings location templates with the Template Gallery
|
||||
|
||||
The [User Experience Virtualization Template Gallery](https://gallery.technet.microsoft.com/site/search?f%5B0%5D.Type=RootCategory&f%5B0%5D.Value=UE-V&f%5B0%5D.Text=UE-V) enables administrators to share their UE-V settings location templates. Upload your settings location templates to the gallery for other users to use, and download templates that other users have created.
|
||||
|
||||
Before you share a settings location template on the UE-V template gallery, ensure it doesn't contain any personal or company information. You can use any XML viewer to open and view the contents of a settings location template file. The following template values should be reviewed before you share a template with anyone outside your company.
|
||||
|
||||
- Template Author Name - Specify a general, non-identifying name for the template author name or exclude this data from the template.
|
||||
|
||||
Loading…
x
Reference in New Issue
Block a user