If you have just gotten a license for Microsoft Intune, the question that always arises is how do I get started? Microsoft provides a guided scenario that creates a series of configuration profiles, applications, and enrollment for devices to allow organizations to start managing devices quickly and efficiently. Today we are going to review the scenario Deploy Windows 10 and later in cloud configuration.
To access the Guided Scenario, log into your tenant and select Troubleshooting + support from the left navigation pane:
Select Guided Scenarios (preview) from the navigation pane:
Microsoft provides four scenarios: Secure Office apps for mobile, Deploy Edge for mobile, Setup a test device to try out cloud management, and Deploy Windows 10 and later in cloud configuration.
As mentioned above we are going to focus on Deploy Windows 10 and later in cloud configuration. To get started select the Start option under Deploy Windows 10 and later in cloud configuration. This will start the workflow for Microsoft to build all the necessary components to enroll, deploy, and manage devices.
Additionally, more information about the Guided Scenario can be found using the following link: Windows in cloud configuration (microsoft.com)
Select Next at the bottom of the window to continue:
In the Basic screen, we have a few choices we can make: Apply a Device Name Template, decide on a Prefix name, and the option to select the Default file format for Office. The First option to apply a device name template sets the naming convention to be used within the Autopilot profile. All devices enrolled in Autopilot and using the created profile use the convention.
For this walk through, I am going to select not to apply a naming convention.
To continue with the scenario, we must enter in a resource prefix name:
This prefix name is applied to every configuration profile and application deployment created by the scenario to allow the administrator to easily distinguish those created manually, and those created using this process.
I have selected the use the following prefix: GS_Demo
We must also choose at this time a default file format for Microsoft Office :
Following the three choices we need to make, is a list of the items that Microsoft creates on our behalf. This includes the device configuration profiles, enrollment profiles (status enrollment page and Autopilot profile) . along with two application deployments (Office 365 and Edge). You will also notice that all of these use the prefix we entered above and ending with the current date and time:
Selecting Next will advance us to the App Configuration page:
Within this page, we can configure the Office 365 installation to either include or exclude individual Office apps, apart from Teams. For this demonstration, I have selected to include all apps except Skype for Business:
The other application installation that is also created is for the latest version of Microsoft Edge for Windows 10 and later.
Select next to continue to the assignments page.
On the Assignments page, we have the option to either create a new Azure group, or use and existing group to assign all profiles and deployment to. In my case, am going to create a new group:
Select Next to continue to the Review + Deploy page:
On the final page, of the scenario setup, we can review all of the configuration options to make sure they align with our needs. Microsoft also provides links to each of the resources its creates under the configuration to be made section:
I highly recommend taking a screenshot of the entire page, as it can serve as a configuration record of the items created and the naming conventions used.
If everything is acceptable, click the deploy button at the bottom. If everything completes successfully the following is shown:
Again, I highly recommend capturing this information.
Now we have a complete set of enrollments, configuration profiles, and app deployments for testing and as a reference when building new profiles.
Comments