add barcode

This commit is contained in:
jdeckerMS
2017-03-13 12:29:04 -07:00
parent 0c5401d974
commit 95b7fdc9a2
3 changed files with 15 additions and 9 deletions

View File

@ -11,7 +11,7 @@
### [Set up a kiosk on Windows 10 Mobile or Windows 10 Mobile Enterprise](set-up-a-kiosk-for-windows-10-for-mobile-edition.md)
### [Use Windows Configuration Designer to configure Windows 10 Mobile devices](provisioning-configure-mobile.md)
#### [NFC-based device provisioning](provisioning-nfc.md)
#### [Use the package splitter tool](provisioning-package-splitter.md)
#### [Barcode provisioning and the package splitter tool](provisioning-package-splitter.md)
### [Use the Lockdown Designer app to configure Windows 10 Mobile devices](mobile-lockdown-designer.md)
### [Configure Windows 10 Mobile using Lockdown XML](lockdown-xml.md)
### [Settings and quick actions that can be locked down in Windows 10 Mobile](settings-that-can-be-locked-down.md)

View File

@ -17,7 +17,7 @@ localizationpriority: high
Near field communication (NFC) enables Windows 10 Mobile Enterprise and Windows 10 Mobile devices to communicate with an NFC tag or another NFC-enabled transmitting device. Enterprises that do bulk provisioning can use NFC-based device provisioning to provide a provisioning package to the device that's being provisioned. NFC provisioning is simple and convenient and it can easily store an entire provisioning package.
The NFC provisioning option enables the administrator to provide a provisioning package during initial device setup or the out-of-box experience (OOBE) phase. Administrators can use the NFC provisioning option to transfer provisioning information to persistent storage by tapping an unprovisioned mobile device to an NFC tag or NFC-enabled device. To use NFC for pre-provisioning a device, you must either prepare your own NFC tags by storing your provisioning package to a tag as described in this section, or build the infrastructure needed to transmit a provisioning package between an NFC-enabled device and a mobile device during OOBE.
The NFC provisioning option enables the administrator to provide a provisioning package during initial device setup (the out-of-box experience or OOBE phase). Administrators can use the NFC provisioning option to transfer provisioning information to persistent storage by tapping an unprovisioned mobile device to an NFC tag or NFC-enabled device. To use NFC for pre-provisioning a device, you must either prepare your own NFC tags by storing your provisioning package to a tag as described in this section, or build the infrastructure needed to transmit a provisioning package between an NFC-enabled device and a mobile device during OOBE.
## Provisioning OOBE UI
@ -131,7 +131,9 @@ For detailed information and code samples on how to implement an NFC-enabled dev
## Related topics
- [Use Windows Configuration Designer to configure Windows 10 Mobile devices](provisioning-configure-mobile.md)
- [Barcode provisioning and the package splitter tool](provisioning-package-splitter.md)
 
 

View File

@ -1,5 +1,5 @@
---
title: Use the package splitter tool (Windows 10)
title: Barcode provisioning and the package splitter tool (Windows 10)
description:
ms.prod: w10
ms.mktglfcycl: deploy
@ -8,25 +8,29 @@ author: jdeckerMS
localizationpriority: high
---
# Use the package splitter tool
# Barcode provisioning and the package splitter tool
**Applies to**
- Windows 10 Mobile
Enterprise IT professionals who want to use a barcode to provision mobile devices during OOBE can use the package splitter tool, ppkgtobase64.exe, which is a command-line tool to split the provisioning package into smaller files.
Enterprises that do bulk provisioning can use barcode-based device provisioning to provide a provisioning package to the device that's being provisioned.
The barcode provisioning option enables the administrator to provide a provisioning package during initial device setup (the out-of-box experience or OOBE phase). To use barcodes to provision a device, your devices must have an integrated barcode scanner. You can get the barcode format that the scanner supports from your OEM or device provider, and use your existing tools and processes to convert a provisioning package into barcodes.
Enterprise IT professionals who want to use a barcode to provision mobile devices during OOBE can use the package splitter tool, **ppkgtobase64.exe**, which is a command-line tool to split the provisioning package into smaller files.
The smallest provisioning package is typically 5-6 KB, which cannot fit into one single barcode. The package splitter tool allows partners to split the original provisioning package into multiple smaller sized chunks that are encoded with Base64 so that enterprises can leverage their existing tools to convert these files into barcodes.
Ppkgtobase64.exe is automatically installed when you install Windows Configuration Designer.
When you [install Windows Configuration Designer](provisioning-install-icd.md), **ppkgtobase64.exe** is installed to the same folder.
## Prerequisites
Before you can use the tool, you must have a built provisioning package. The package file is the input to the package splitter tool.
- To build a provisioning package using the Windows Configuration Designer UI, see Build and apply a provisioning package.
- To build a provisioning package using the Windows Configuration Designer CLI, see Use the Windows ICD command-line interface.
- To build a provisioning package using the Windows Configuration Designer UI, see [Use Windows Configuration Designer to configure Windows 10 Mobile devices](provisioning-configure-mobile.md).
- To build a provisioning package using the Windows Configuration Designer CLI, see [Windows Configuration Designer command-line interface](provisioning-command-line.md).
## To use the package splitter tool (ppkgtobase64.exe)
@ -48,7 +52,7 @@ Before you can use the tool, you must have a built provisioning package. The pac
cd C:\Program Files\Windows Kits\10\Assessment and Deployment Kit\Imaging and Configuration Designer\x86
```
3. Run the tool by calling "ppkgtobase64.exe". See the next section in this topic for more information.
3. Run `ppkgtobase64.exe`. The [syntax](#syntax) and [switches and arguments](#switches-and-arguments) sections provide details for the command.
### Syntax