The problem:
Our customer informed Atea Global Services that they want to disable as many servers as possible and move to a cloud solution as well as have a digital workplace. The customer also needed to automate as much as possible of the Windows devices enrollment because building and maintaining customized operating system images is a time-consuming process and expensive in our days. The customer has offices and factories all around the world; thus, the purpose was to group them to manage policies, profiles, application, and more, easily. Due to these needs, the customer wanted Atea Global Service to see what solution can be offered to manage the servers and devices jointly and to do the automation process smoothly.
The Atea solution:
Atea Global Services looked into the customer’s inquiry and found solutions for both inquires, based on the best practice, to implement Co-management and Windows Autopilot. The co-management approach is one of the primary ways to attach existing Configuration Manager deployment to the Microsoft 365 cloud. It helps customers to unlock additional cloud-powered capabilities like conditional access. Thus, they can manage servers needed for their factories (using SCCM) on the one hand and on the other manage the rest of their Windows 10 devices around the world (using Microsoft Intune).
Firstly, Atea Global Services started with the project to upgrade the SCCM server to the 1810 version and set up the necessary settings for this in SCCM and Azure. In parallel, we started with another project to move all managed workstations to the latest Windows 10 version 1803, which is required for Microsoft Intune client management and further as a consequence Co-management implementation. Atea Global Services performed many tests while accomplishing all determined projects and Co-management implementation; thus, completing the process with the highest accuracy.
By using co-management, the customer now has the flexibility to use the technology solution that works best for their organization, as well as receiving benefits of both services. By using Intune to manage Autopilot devices, the customer can manage policies, profiles, application, and more, after the needed devices are enrolled. With Microsoft Intune and Autopilot, the customer can provide new devices to their employees (end-users) without the need to build, maintain, and apply custom operating system images to the devices. The customer can control which workloads, if any, may switch the authority from Configuration Manager to Intune. SCCM continues to manage all other workloads, including those workloads that the customer did not decide to switch to Intune for example, and all other features of Configuration Manager that co-management doesn’t support.
The problem:
Our customer informed Atea Global Services that they want to disable as many servers as possible and move to a cloud solution as well as have a digital workplace. The customer also needed to automate as much as possible of the Windows devices enrollment because building and maintaining customized operating system images is a time-consuming process and expensive in our days. The customer has offices and factories all around the world; thus, the purpose was to group them to manage policies, profiles, application, and more, easily. Due to these needs, the customer wanted Atea Global Service to see what solution can be offered to manage the servers and devices jointly and to do the automation process smoothly.
The Atea solution:
Atea Global Services looked into the customer’s inquiry and found solutions for both inquires, based on the best practice, to implement Co-management and Windows Autopilot. The co-management approach is one of the primary ways to attach existing Configuration Manager deployment to the Microsoft 365 cloud. It helps customers to unlock additional cloud-powered capabilities like conditional access. Thus, they can manage servers needed for their factories (using SCCM) on the one hand and on the other manage the rest of their Windows 10 devices around the world (using Microsoft Intune).
Firstly, Atea Global Services started with the project to upgrade the SCCM server to the 1810 version and set up the necessary settings for this in SCCM and Azure. In parallel, we started with another project to move all managed workstations to the latest Windows 10 version 1803, which is required for Microsoft Intune client management and further as a consequence Co-management implementation. Atea Global Services performed many tests while accomplishing all determined projects and Co-management implementation; thus, completing the process with the highest accuracy.
By using co-management, the customer now has the flexibility to use the technology solution that works best for their organization, as well as receiving benefits of both services. By using Intune to manage Autopilot devices, the customer can manage policies, profiles, application, and more, after the needed devices are enrolled. With Microsoft Intune and Autopilot, the customer can provide new devices to their employees (end-users) without the need to build, maintain, and apply custom operating system images to the devices. The customer can control which workloads, if any, may switch the authority from Configuration Manager to Intune. SCCM continues to manage all other workloads, including those workloads that the customer did not decide to switch to Intune for example, and all other features of Configuration Manager that co-management doesn’t support.