SCCM Intune Hybrid to Standalone Guide Pt 2

Dujon Walsham • 14 June 2019

Prepare Intune for User Migration

The next part focuses on how to prepare the users for using the Intune Standalone

Through the Intune Hybrid setup collections and devices would be imported into Intune alongside the AD account assigned to them by user/device affinity.

But the devices itself would have the licenses but not the users so these have to be added.


Assign Users the Intune Standalone License

1.Open Microsoft 365 Device Management

2.Go to Users

3.Select a user and choose “Licenses”

4.Click Assign

5.Select the “Enterprise Mobility + Security E3” license and click assign to accept it for the user.

Assigning Imported Policies

With the profiles and policies which we had imported earlier now within the Device Configuration - Profiles section of your Device Management 365 view, they will need to be assigned very similar to how the Intune Hybrid was working where the MDM User Device collection is assigned to the Intune Policy.

If your user accounts and groups are not fully synchronized using Azure AD Connect then these would need to be created manually.


Create AD Group

( Note: You can skip this step if your User Accounts and AD Groups are fully synchronized)

First we will create a new group in Azure AD. This can also be done in the Microsoft 365 Device Management.

1.Open Microsoft 365 Device Management

2.Go to Groups – All Groups

3.Click New Group

4.Type the name of the new group and ensure it’s a “Security” group type and membership type is “Assigned”. Add the users to the group you need in “Members” then click the Create button.

Assigning Policies to the AD Group

Now we will need to assign the profiles/policies which we had imported earlier to the AD group which we have created

1.Open the Microsoft 365 Device Management

2.Go to Device Configuration – Profiles

3.Click on the profile you need and select Assignments

4.Select the “Select groups to include” box and add the AD group which you have created and click Save.

by D Walsham 13 December 2021
Looking through the current SQL Server topology and how it affects our decision
by D Walsham 7 October 2021
Introduction
by D Walsham 6 October 2021
Introduction
by D Walsham 12 August 2021
All the parts of the series we went into great detail about how we analyse an end to end solution and how we would design a solution in which would allow us to build endpoints without SCCM being a dependency. Whilst we did this, there is another scenario which we have not touched on yet, which is the hybrid scenarios. In a perfect world ideally you would have your Azure Active Directory within the cloud, every machine meets the recommended requirements for Windows 10, everything is imported into Intune/Autopilot and everyone is happy. But we know this isn't realistic in all cases. Many organisations cannot just simply up and go from on-premise into the cloud therefore the checkpoint here is of course getting into hybrid solutions such as; Co-Management Between Intune and SCCM Hybrid AD with Azure AD and On-Premise AD syncing together These things can play a very interesting part in how you would tackle this if you envisage the next step in the blueprint is to be in a position in which you can build and manage endpoints soley within Intune. With this final part of the series we will go in-depth in how the common hybrid setups look like and how we go about moving into the next step of being able to manage and build devices without SCCM.
by D Walsham 29 July 2021
In continuation from the previous part where we had discussed how we create the "on site" piece of the solution, this was the part which would allow us to get our endpoints into a state in which they would essentially be ready to go through the Autopilot process. Which leaves our next piece of the puzzle, to begin the configuration of the actual backend side that resides within our Endpoint Management console. And you will see how everything ties up together to satisfy the full end to end process of getting an unknown (or known) device to proceed thorough the whole workflow to be finally managed by Intune without the aid of SCCM taking part in any of the prerequisites or preparation at hand.
by D Walsham 15 July 2021
In this part we are now going to look into the technical step by step points on how we put everything together. In the previous part we spoke about the structure of how we would asses whether a machine was actually ready to be built with Autopilot or not with a build checklist process which would step through all areas which would cover an endpoints eligibility. Now with everything planned out we finally want to step into making things reality by putting everything together.
by D Walsham 2 July 2021
When it comes to managing your endpoints in endpoint manager, one of the things you may be looking to do is to get all of your Intune registered machines to also be enrolled as Autopilot devices. Now we can of course just have the deployment profile deployed to all machines and then hit the "Convert targeted machines to autopilot" but this might not necessarily be feasible for every client. We may want to perform some due diligence first so we can at least understand what devices in Intune are not in Autopilot.
Show More