Cleaning up after conversion

This commit is contained in:
LizRoss
2016-04-06 10:30:03 -07:00
parent 2ca2ed6892
commit 5cafdca2a4
2 changed files with 15 additions and 54 deletions

View File

@ -9,15 +9,11 @@ author: CFaw
--- ---
# Sideload LOB apps in Windows 10 # Sideload LOB apps in Windows 10
**Applies to** **Applies to**
- Windows 10 - Windows 10
- Windows 10 Mobile - Windows 10 Mobile
Sideload line-of-business apps in Windows 10.
"Line-of-Business" (LOB) apps are present in a wide range of businesses and organizations. Organizations value these apps because they solve problems unique to each business. "Line-of-Business" (LOB) apps are present in a wide range of businesses and organizations. Organizations value these apps because they solve problems unique to each business.
When you sideload an app, you deploy a signed app package to a device. You maintain the signing, hosting, and deployment of these apps. Sideloading was also available with Windows 8 and Windows 8.1 When you sideload an app, you deploy a signed app package to a device. You maintain the signing, hosting, and deployment of these apps. Sideloading was also available with Windows 8 and Windows 8.1
@ -31,8 +27,6 @@ In Windows 10, sideloading is different than in earlier versions of Windows:
- Devices do not have to be joined to a domain - Devices do not have to be joined to a domain
## Requirements ## Requirements
Here's what you'll need to have: Here's what you'll need to have:
- Devices need to be unlocked for sideloading (unlock policy enabled) - Devices need to be unlocked for sideloading (unlock policy enabled)
@ -50,8 +44,6 @@ And here's what you'll need to do:
- Install the app - use PowerShell to install the app package. - Install the app - use PowerShell to install the app package.
## How do I sideload an app on desktop ## How do I sideload an app on desktop
You can sideload apps on managed or unmanaged devices. You can sideload apps on managed or unmanaged devices.
**To turn on sideloading for managed devices** **To turn on sideloading for managed devices**
@ -74,17 +66,14 @@ You can sideload apps on managed or unmanaged devices.
3. Import the certificate to the **Trusted Root Certification Authorities** folder. 3. Import the certificate to the **Trusted Root Certification Authorities** folder.
-Or- -OR-
You can use a runtime provisioning package to import a security certificate. For information about applying a provisioning package to a Windows 10 device, see runtime instructions on [Build and apply a provisioning package]( http://go.microsoft.com/fwlink/p/?LinkId=619162). You can use a runtime provisioning package to import a security certificate. For information about applying a provisioning package to a Windows 10 device, see runtime instructions on [Build and apply a provisioning package]( http://go.microsoft.com/fwlink/p/?LinkId=619162).
**To install the app** **To install the app**
- From the folder with the appx package, run the PowerShell `Add-AppxPackage` command to install the appx package. - From the folder with the appx package, run the PowerShell `Add-AppxPackage` command to install the appx package.
## How do I sideload an app on mobile ## How do I sideload an app on mobile
You can sideload apps on managed or unmanaged devices. You can sideload apps on managed or unmanaged devices.
**To turn on sideloading for a managed device** **To turn on sideloading for a managed device**
@ -115,7 +104,7 @@ You can sideload apps on managed or unmanaged devices.
- From an email, tap a xap, appx, or appx bundle package. - From an email, tap a xap, appx, or appx bundle package.
-Or- -OR-
With your mobile device tethered to a desktop, click a xap, appx, or appx bundle package from the files system to install the app. With your mobile device tethered to a desktop, click a xap, appx, or appx bundle package from the files system to install the app.

View File

@ -10,8 +10,6 @@ author: CFaw
--- ---
# Update Windows 10 images with provisioning packages # Update Windows 10 images with provisioning packages
**Applies to** **Applies to**
- Windows 10 - Windows 10
@ -30,8 +28,6 @@ Rather than wiping a device and applying a new system image when you need to cha
For details about the settings you can customize in provisioning packages, see [Windows Provisioning settings reference]( http://go.microsoft.com/fwlink/p/?LinkId=619012). For details about the settings you can customize in provisioning packages, see [Windows Provisioning settings reference]( http://go.microsoft.com/fwlink/p/?LinkId=619012).
## Advantages ## Advantages
- You can configure new devices without reimaging. - You can configure new devices without reimaging.
- Works on both mobile and desktop devices. - Works on both mobile and desktop devices.
@ -43,11 +39,9 @@ For details about the settings you can customize in provisioning packages, see [
- Ensure compliance and security before a device is enrolled in MDM. - Ensure compliance and security before a device is enrolled in MDM.
## Create package ## Create package
Use the Windows Imaging and Configuration Designer (ICD) tool included in the Windows Assessment and Deployment Kit (ADK) for Windows 10 to create a runtime provisioning package. [Install the ADK.](http://go.microsoft.com/fwlink/p/?LinkId=526740) Use the Windows Imaging and Configuration Designer (ICD) tool included in the Windows Assessment and Deployment Kit (ADK) for Windows 10 to create a runtime provisioning package. [Install the ADK.](http://go.microsoft.com/fwlink/p/?LinkId=526740)
1. Open Windows ICD (by default, %windir%\\Program Files (x86)\\Windows Kits\\10\\Assessment and Deployment Kit\\Imaging and Configuration Designer\\x86\\ICD.exe). 1. Open Windows ICD (by default, `%windir%\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Imaging and Configuration Designer\x86\ICD.exe`).
2. Choose **New provisioning package**. 2. Choose **New provisioning package**.
@ -70,8 +64,6 @@ Use the Windows Imaging and Configuration Designer (ICD) tool included in the Wi
**Tip**   **Tip**  
You can make changes to existing packages and change the version number to update previously applied packages. You can make changes to existing packages and change the version number to update previously applied packages.
 
11. Optional. In the **Provisioning package security** window, you can choose to encrypt the package and enable package signing. 11. Optional. In the **Provisioning package security** window, you can choose to encrypt the package and enable package signing.
- **Enable package encryption** - If you select this option, an auto-generated password will be shown on the screen. - **Enable package encryption** - If you select this option, an auto-generated password will be shown on the screen.
@ -79,25 +71,21 @@ Use the Windows Imaging and Configuration Designer (ICD) tool included in the Wi
- **Enable package signing** - If you select this option, you must select a valid certificate to use for signing the package. You can specify the certificate by clicking **Select...** and choosing the certificate you want to use to sign the package. - **Enable package signing** - If you select this option, you must select a valid certificate to use for signing the package. You can specify the certificate by clicking **Select...** and choosing the certificate you want to use to sign the package.
**Important**   **Important**  
We recommend that you include a trusted provisioning certificate in your provisioning package. When the package is applied to a device, the certificate is added to the system store and any package signed with that certificate thereafter can be applied silently. We recommend that you include a trusted provisioning certificate in your provisioning package. When the package is applied to a device, the certificate is added to the system store and any package signed with that certificate thereafter can be applied silently. 
  12. Click **Next** to specify the output location where you want the provisioning package to go once it's built. By default, Windows ICD uses the project folder as the output location.<p>
Optionally, you can click **Browse** to change the default output location.
12. Click **Next** to specify the output location where you want the provisioning package to go once it's built. By default, Windows ICD uses the project folder as the output location.
Optionally, you can click **Browse** to change the default output location.
13. Click **Next**. 13. Click **Next**.
14. Click **Build** to start building the package. The project information is displayed in the build page and the progress bar indicates the build status. 14. Click **Build** to start building the package. The project information is displayed in the build page and the progress bar indicates the build status.<p>
If you need to cancel the build, click **Cancel**. This cancels the current build process, closes the wizard, and takes you back to the **Customizations Page**.
If you need to cancel the build, click **Cancel**. This cancels the current build process, closes the wizard, and takes you back to the **Customizations Page**. 15. If your build fails, an error message will show up that includes a link to the project folder. You can scan the logs to determine what caused the error. Once you fix the issue, try building the package again.<p>
If your build is successful, the name of the provisioning package, output directory, and project directory will be shown.
15. If your build fails, an error message will show up that includes a link to the project folder. You can scan the logs to determine what caused the error. Once you fix the issue, try building the package again.
If your build is successful, the name of the provisioning package, output directory, and project directory will be shown.
- If you choose, you can build the provisioning package again and pick a different path for the output package. To do this, click **Back** to change the output package name and path, and then click **Next** to start another build. - If you choose, you can build the provisioning package again and pick a different path for the output package. To do this, click **Back** to change the output package name and path, and then click **Next** to start another build.
- If you are done, click **Finish** to close the wizard and go back to the **Customizations Page**. - If you are done, click **Finish** to close the wizard and go back to the **Customizations Page**.
16. Select the **output location** link to go to the location of the package. You can provide that .ppkg to others through any of the following methods: 16. Select the **output location** link to go to the location of the package. You can provide that .ppkg to others through any of the following methods:
@ -115,21 +103,16 @@ Use the Windows Imaging and Configuration Designer (ICD) tool included in the Wi
- NFC (mobile only) - NFC (mobile only)
## Add package to image ## Add package to image
**To add a provisioning package to Windows 10 for desktop editions (Home, Pro, Enterprise, and Education)** **To add a provisioning package to Windows 10 for desktop editions (Home, Pro, Enterprise, and Education)**
- Follow the steps in the "To build an image for Windows 10 for desktop editions" section in [Use the Windows ICD command-line interface]( http://go.microsoft.com/fwlink/p/?LinkId=617371). - Follow the steps in the "To build an image for Windows 10 for desktop editions" section in [Use the Windows ICD command-line interface]( http://go.microsoft.com/fwlink/p/?LinkId=617371).
**To add a provisioning package to a Windows 10 Mobile image** **To add a provisioning package to a Windows 10 Mobile image**
- Follow the steps in the "To build an image for Windows 10 Mobile or Windows 10 IoT Core (IoT Core)" section in [Use the Windows ICD command-line interface]( http://go.microsoft.com/fwlink/p/?LinkId=617371). - Follow the steps in the "To build an image for Windows 10 Mobile or Windows 10 IoT Core (IoT Core)" section in [Use the Windows ICD command-line interface]( http://go.microsoft.com/fwlink/p/?LinkId=617371).<p>
The provisioning package is placed in the FFU image and is flashed or sector written to the device. During device setup time, the provisioning engine starts and consumes the packages.
The provisioning package is placed in the FFU image and is flashed or sector written to the device. During device setup time, the provisioning engine starts and consumes the packages.
## Learn more ## Learn more
- [Build and apply a provisioning package]( http://go.microsoft.com/fwlink/p/?LinkId=629651) - [Build and apply a provisioning package]( http://go.microsoft.com/fwlink/p/?LinkId=629651)
- [Provisioning Windows 10 Devices with New Tools](http://go.microsoft.com/fwlink/p/?LinkId=615921) - [Provisioning Windows 10 Devices with New Tools](http://go.microsoft.com/fwlink/p/?LinkId=615921)
@ -137,15 +120,4 @@ Use the Windows Imaging and Configuration Designer (ICD) tool included in the Wi
- [Windows 10 for Mobile Devices: Provisioning Is Not Imaging](http://go.microsoft.com/fwlink/p/?LinkId=615922) - [Windows 10 for Mobile Devices: Provisioning Is Not Imaging](http://go.microsoft.com/fwlink/p/?LinkId=615922)
## Related topics ## Related topics
- [Configure devices without MDM](../manage/configure-devices-without-mdm.md)
[Configure devices without MDM](../manage/configure-devices-without-mdm.md)