Configure devices

August 13, 2015

The way you configure a Windows Embedded 8.1 Handheld-powered device depends on the state that the device is in:

  • OEM-built condition (factory state)
    This is the state in which the device leaves the factory floor. Although not typical, you can work with your OEM to pre-configure devices in this state by putting organization-specific settings in the provisioning file. During startup, the device reads the provisioning file and applies the configurations to the device. The resulting devices will be in the provisioned state and ready to use.

  • Pre-provisioned enterprise state
    This is the state in which you typically would put your organization-specific settings in a provisioning file. You can create your own provisioning file to configure Wi-Fi settings, enroll in mobile device management (MDM), install apps, and configure lockdown settings. You can then load your provisioning file on a device by using the following methods:

    • SD card - The provisioning file must be named Prov.xml and be located in the root path.

    • NFC tag or OEM plug-in - The provisioning file can have any name.

    During startup - The device reads the provisioning file and applies the configurations to the device. The resulting device will be in the provisioned state and ready to use.

  • Provisioned state
    This is the state in which the device is provisioned and ready to use. In this state, when you start the device, the device applies the configurations to the device without user interaction.

    Once the device is in this state, you can wipe the device to return to the provisioned state, or you can manage the device as described in Locking down a device.

The following image shows these device states.

There is a setting in EnterpriseAssignedAccess configuration service provider that indicates whether to save provisioning data to persistent storage on the device. If PersistProvisionedData is not set, the provisioning data is not saved and you will be asked to provide the data during startup. If the PersistProvisionedData setting is set, the provisioning data is saved and used during a device wipe.

The Prov.xml file is only used during startup. It is not used again unless you wipe the device to return to the startup settings. After you deploy your devices, we strongly recommend that you keep the Prov.xml current with the device settings that you require. In this way, if you have to wipe a device, the device can be updated with the correct configurations. For more information about the Prov.xml file, see Provision the device on startup.

After you deploy your devices, if they are enrolled in MDM, you can configure lockdown settings and policies from the MDM server. For a list of settings and policies that you can configure, see Settings that can be locked down.

In this section

  • Best practices for configuring devices
    Provides some tips to help you manage device configuration, particularly with managing conflicts between MDM policies and Prov.xml.

  • Provision the device on startup
    Describes configuration options that you can apply to a device during startup, and describes how to apply Prov.xml to a device during startup.

  • Locking down a device
    Describes the lockdown settings that you can apply to a device after deployment. This section includes an example lockdown XML file for configuring lockdown settings after deployment.

  • Prepare devices for app deployment
    Describes how to configure devices in a way that bypasses Windows Store and publishes and distributes applications directly to employee devices.

See also

Other resources

Administrator Guide for Windows Embedded 8.1 Handheld