What is WPC mode?

WPC, or Work Profile on Company Owned, is a model designed for company-owned devices on which a separate work profile is created. This makes it possible for two areas to coexist on one phone:

• the user’s personal space,
• the work space managed by the organization.

This solution works well when a company wants to provide the user with more flexibility than in the COBO model, while still needing control over corporate data, applications, and security policies.

In practice, this means that the organization manages the work profile, while the user can also use the device outside of work duties, without mixing personal data with corporate data.

What does the video show?

In the video, we present the process of manually adding an Android device to Essentials MDM in WPC mode. The entire process begins in the administrative console, where the administrator selects the Android platform and the WPC scenario.

Next, the device group is selected, which makes it possible to define immediately which policy will be assigned to the newly added phone. In the example shown, the device is assigned to a policy prepared for WPC mode, containing the applications that are to be deployed in the work profile.

On the device side, the process is carried out using a QR code and leads to the automatic creation of the work profile and registration of the device in the system.

Adding a device in WPC mode – step by step

1. Starting the device addition process in the Essentials MDM console
   The process begins by creating a new device in the system. The administrator selects the option to add a device and then indicates:

• the Android platform,
• WPC mode.

It is at this stage that the deployment scenario is defined, which will affect the registration method and later device management.

2. Selecting the group and policy
   The next step is assigning the device to the appropriate group. This is important because the group determines which policy will be applied after deployment.

The video shows a policy prepared specifically for WPC devices. It includes the applications that should be deployed in the work container. This means that already at the registration stage, the administrator has influence over what the work profile will look like once configuration is complete.

3. Selecting the appropriate deployment scenario
   In Essentials MDM, different deployment paths can be selected depending on the condition of the device and the Android version. In the material shown, the device used is:

• restored to factory settings,
• running Android 10 or later.

This is an important difference, because WPC mode can be deployed not only on new devices, but also on hardware that has already been used. In this particular scenario, however, the video focuses on a wiped device prepared for initial setup.

4. Generating the QR code
   After selecting the appropriate scenario, the system generates a QR code. This is the most convenient way to start device registration, because it allows the phone to be quickly connected to the previously prepared configuration in Essentials MDM.

The QR code contains the information needed to start the deployment process and automatically create the appropriate work environment on the device.

5. Launching the QR code reader on the device
   On the phone side, a device restored to factory settings is used. On the Android welcome screen, the QR code reader can be launched by tapping the screen six times.

After activating the reader, all that is needed is to scan the code generated earlier. This is the point at which the device begins the process of connecting to the management system.

6. Connecting to the network and starting configuration
   After scanning the QR code, the device may ask to connect to a Wi-Fi network if this has not already been configured. Internet access is needed to download the settings and start the actual deployment.

After entering the network details, the device automatically moves to the next stages of configuration. From that moment on, the user mainly performs the standard steps known from the initial startup of Android – confirming prompts, accepting the required permissions, and going through the basic setup wizard.

7. Automatic detection of the device by Essentials MDM
   The video shows that the system very quickly recognizes that the generated QR code has been scanned. This means that the device has started the registration process and Essentials MDM can already associate it with the appropriate configuration.

The administrator can go to the device details in the console and see that the system is already performing the first operations and that logs are beginning to appear. This is a good sign that the process is proceeding correctly.

8. Creating the work profile
   One of the most important moments in the entire process is the automatic creation of the work profile. This is what distinguishes WPC mode from scenarios in which the entire device is managed as an exclusively corporate environment.

In practice, the work profile creates a separate space for corporate applications and data. Thanks to this:

• work applications are separated from personal ones,
• the organization can manage only the selected part of the device,
• the user has a clear separation between work and personal use.

9. Finalizing the configuration and containerizing the device
   After a short while, the device is handed over to the user as hardware with an active work profile. The video clearly shows the separation between the personal part and the work part.

Application icons in the work profile have the appropriate markings, allowing the user to immediately see which applications belong to the work container. The system may still perform some actions in the background, but this does not change the fact that the device is already managed and ready for further use.

Why is WPC a practical deployment model?

WPC mode gives the organization a good balance between security and user convenience. The company retains control over the work profile, while not having to lock down the entire device in the way that is typical for the COBO scenario.

The main benefits of this approach are:

• separation of personal and corporate data,
• greater convenience for the employee,
• better protection of corporate data,
• the ability to centrally deploy applications and settings,
• clear management of the work profile without interfering with the entire personal space.

This is an especially good solution wherever the device belongs to the company but is meant to be used in a more flexible way.

What should you pay attention to when deploying WPC?

Although the whole process is simple, it is worth remembering a few important points:

• the appropriate deployment scenario should be selected according to the Android version and device condition,
• the device must have internet access,
• it is worth preparing the appropriate group and policy in advance,
• applications assigned to the policy should be planned with the work profile in mind,
• some configuration steps may still continue in the background even after the wizard is complete.

This ensures that deployment runs smoothly and that the user immediately receives a ready-to-use work environment.

Summary

The video shows that adding a device in WPC mode in Essentials MDM is a structured and convenient process. The administrator prepares the configuration in the console, selects the appropriate group and policy, generates a QR code, and then starts deployment on the device.

After scanning the code and going through the basic Android configuration steps, Android automatically creates the work profile, and Essentials MDM begins managing the corporate part of the device.

This is a practical solution for organizations that want to combine the security of corporate data with the convenience of using one device for both work and personal purposes.