Assign device to profile
Before you enroll an iOS device under DEP, the device need to be, assigned to a profile. This will build a relationship between a given profile and a device. Please note that with Apple DEP APIs, any change to a exiting profile creates a new UUID and the existing devices must be assigned to the new profile.
...
| Field name | Usage | Description |
|---|---|---|
| Assigned user's username | Username of the user to asign assign the device | Username must be provided without the tenant domain(i.e not the fully qualified username). If Login required is checked, this field must be empty |
| Login required | If the end user need to provide login credentials | If username is provided, this must be unchecked |
| Agent install required | If the agent must be installed after the device startup |
...
- If DEP related policies must be applied to the device, the "is Supervised" check is ticked during profile creation.
- If this is a first testing rounds, keep "is Mandotory Mandatory" uncheked untill until it is confimed the configurations are correctly made.
- If profile edit is made, the device must be removed from existing profile assignment and reassigned to the new UUID.
- A profile is assigned to the device being enrolled.
- Either "Assigned user's username " is filled or "Login required" check is ticked.
- If Agent install is checked, the agent is published and agent app ID related configurations are made. Note that the agent version must be IoT server 3.3.1 or upwards compatible.
- Factory reset is mandotory if an existing device is being reused/tested. Apple devices purched through DEP program and has not beed setup before, does not need to be factory resetting.