What does the video show?
In the video, we present the process of adding an Android device to Essentials MDM in COBO mode. The process begins in the administrative console, where the administrator selects the Android platform and indicates the appropriate deployment mode.

The system then allows the administrator to define the basic parameters of the new device, such as the user, assigned group, and policy that will be applied after registration. In the example shown, the device receives the default policy along with the applications required by the organization.

On the device side, the process is carried out using a QR code. This is a convenient deployment method, especially during the first launch of a new or reset phone.

Adding a device in COBO 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 chooses the platform – in this case, Android.

At this stage, COBO mode is selected, meaning full management of a corporate-owned device.

2. Selecting the registration method and assigning the user
   In the scenario shown, a variant without additional authentication is used. This means that after scanning the QR code, the device will be automatically added to the environment.

The administrator also assigns the appropriate user. This is an important step because it may determine:

• assignment of the device to the appropriate group,
• application of a specific policy,
• the way the device will be managed further within the organization.

3. Preview of the policy that will be assigned
   Before completing the configuration, the system shows which policy will be applied to the device. This is a very useful moment because the administrator can already see at the beginning which settings and applications will be deployed.

The material includes an example of a default policy under which, among other things, the Microsoft Outlook application is installed. This shows that already at the registration stage, the device can be prepared for work in line with the company’s requirements.

4. Selecting Device Owner mode and generating the QR code
   The next step is selecting Device Owner mode and generating the QR code. This is a standard and convenient way to register an Android device in a COBO scenario.

The QR code contains the information needed to connect the device to the management system. Thanks to this, the administrator does not need to manually configure multiple settings directly on the phone.

5. Preparing the device after a factory reset
   On the phone side, we use a device that has previously been restored to factory settings. This is important because deployment in COBO mode usually takes place on a new or wiped device.

On the Android welcome screen, the QR code scanner can be launched by tapping the screen six times. This is a very practical feature because it eliminates the question of where to get a QR scanning app on a device that is only just being configured.

After activating the camera, all that remains is to scan the previously generated QR code.

6. Connecting to the network and starting configuration
   After scanning the code, the device may ask to connect to a Wi-Fi network or use mobile data from the SIM card, if available. Without internet access, the device will not download the configuration and will not register properly in the system.

In the next part of the process, the user goes through the basic device setup wizard. In practice, this comes down to confirming the next steps, such as accepting system prompts or proceeding through the wizard.

7. Automatic addition of the device to the system
   After the QR code is scanned, Essentials MDM recognizes that the device has started the registration process. From that moment on, the phone is added to the system, and the rest of the configuration proceeds automatically.

The video shows that even at this stage, the device is already visible in the console. However, not all policy elements must appear immediately on the device screen. Some settings and applications may be deployed a little later, in the background.

8. Applying the policy and final configuration
   After completing the basic Android setup wizard, the device is ready for further automatic configuration. The system may still perform operations related to:

• application installation,
• downloading settings,
• activation of security policies,
• additional confirmations required by the device manufacturer or system version.

This is a natural stage of deployment. The most important thing is that the device has been correctly added to the environment and is starting to operate in accordance with the policy assigned by the administrator.

Why is this deployment method convenient?
Adding devices using a QR code in COBO mode is convenient because it simplifies the configuration process and reduces the time needed to prepare devices for use. Instead of manually configuring each device separately, the administrator can define policies, applications, and assignment structure in advance.

The main benefits of this approach are:

• faster deployment of new devices,
• repeatable configuration,
• lower risk of errors,
• better control over the mobile environment,
• greater security of corporate data.

In practice, this means that the company can scale device management more easily and maintain consistent standards across all departments.

What should you pay attention to when deploying COBO?
Although the process itself is simple, it is worth remembering a few important points:

• the device should be new or restored to factory settings,
• it must have internet access,
• it is worth preparing the user, group, and policy in advance,
• it is a good idea to check which applications should be installed automatically,
• some policy elements may appear with a delay, which is normal.

Summary
The video shows that adding a device in COBO mode in Essentials MDM can be a quick and structured process. You simply need to prepare the configuration in the console, generate a QR code, scan it on the device after restoring factory settings, and go through the basic setup wizard.

The rest happens largely automatically – the device is added to the system, receives the assigned policy, and begins to be prepared for use in accordance with the organization’s requirements.

For companies that want to maintain full control over corporate devices, COBO mode is one of the most practical deployment models.