One of the best ways to access your Windows 365 Cloud PC is by using the Remote Desktop application which you can either download from the Microsoft website or deploy from Microsoft Intune if you are using a managed client.
This post was inspired by a blog post from Microsoft that seems to have disappeared.
To simplify the “adding your Cloud PC/Azure Virtual Desktop to Remote Desktop” process for your users, you can actually create a configuration profile in Microsoft Endpoint Manager which automatically adds the signed-in user to the Remote Desktop with the correct subscription URL.
Please be aware that depending on which version of AVD (Azure Virtual Desktop) you are using, the URL might vary so check the documentation beforehand!
Let’s start by adding Remote Desktop to MEM.
Adding Remote Desktop as an application
The first step is to download the Remote Desktop application, which can be found here.
When you have downloaded the MSI, you will need to use the Microsoft Win32 Content Prep Tool to create a .intunewin file of the MSI.
Download the tool from GitHub and run the tool in PowerShell.
When the tool has successfully created the intunewin-file, you will find the .intunewin file in the output folder you specified.
Head over to Microsoft Endpoint Manager and navigate to Apps > Windows and select “+ Add” and then Windows app (Win32) as App type.
On the first page, find your .intunewin file created in the earlier step and upload it. Update any information about the application as needed add press next.
Leave all settings to default on the next tab.
On the Requirements tab, update Operating System Architecture to correlate to the version of Remote Desktop you downloaded and add which the minimum OS version needs to be. In this case, I’m using a 64-bit version of the app and I require Windows 10 21h1 or newer.
On the next tab, Detection rule, add a custom detection rule using MSI as rule type and leaving all values to default.
Leave Dependencies and Supersedence empty and add a group on which you wish to deploy the application. In this example, I’m deploying it to all users but filtering out that it needs to be a Windows 11 computer.
Review your settings and then create your application. It takes a few minutes for the application to upload.
Automatically adding virtual machines to remote desktop
The next step is to create a new configuration profile, based on a setting from Settings Catalog.
Navigate to Devices > Windows > Configuration Profiles and create a new profile by clicking “+ Create profile” and then select “Windows 10 and later” as a platform and “Settings catalog” as Profile type.
On the first page, give your profile a good name and press next.
On the next page, click “+ Add setting“, find and click Remote Desktop in the list, then check the box next to “Auto-subscription (user)“. Then close the flyout using the X in the upper right corner.
Add the subscription URL to the settings. The one used in this example works for Windows 365 and Azure Virtual Desktops.
Press next and assign your profile to a group, in this example I’m using the same settings as for the Remote Desktop app (All users and a filter for Windows 11).
Click next and skip the Scope section. Review and create your profile.
User experience
When the user opens the Remote Desktop the first time, they will see all Cloud PCs and AVD that they are assigned to.
If they are not assigned to any virtual clients, they will get a message saying that no machines are assigned.
So you have decided to get going with Windows 365 Enterprise? There are a few steps we need to take care of before you can start consuming the future!
What you will need:
Windows 365 licenses
Microsoft Endpoint Manager
Microsoft 365 licenses of some sort
An Azure subscription if you want to use an Azure V-net and not the Microsoft hosted network – optional
Windows 365 is a great way to get started with virtual clients, and it’s actually pretty simple to get going and administrate compared to Azure Virtual Desktop.
Windows 365 licenses
The first thing you need to take care of is obtaining Windows 365 licenses through your licensing partner or where you usually get your licenses. I will leave that one up to you!
There are several different licenses for Windows 365, and there is also a business version that I will not cover in this blog post.
Windows 365 licensing is based on what “size” of a machine you want, basically how many CPUs, the amount of RAM memory, and disk size. As I’m writing this, there are 3 different SKUs of CPUs you can select from (2, 4, and 8). In each SKU of CPUs, there are a few different options in RAM memory and disk size as you can see in the picture below. There is also actually a 1 vCPU version, but that one does not support Windows 11 so I wouldn’t recommend getting that one.
Selecting the correct size of the machine might be a little bit tricky, but Microsoft has actually created a simple cheat sheet you can use to get a feeling of what license to buy which you can find here Windows 365 size recommendations | Microsoft Docs. It’s actually a great guide to get a sense of what size to choose.
One great thing with Windows 365 is that you can upgrade the machines by upgrading the license assigned to the user. However, this does not work if you are using group-based licensing to assign licenses.
Licenses are assigned the same way you assign other Microsoft 365 licenses, either through the Microsoft 365 Admin center or the Azure AD, I will cover this further down
Microsoft Endpoint Manager setup
In Microsoft Endpoint Manager, navigate to Devices > Windows 365 which has now been enabled for you since you have purchased licenses.
To get going with a really basic setup using Azure AD joined and Microsoft hosted network, you only need to create a Provisioning policy and then you are ready.
Click on the Provisioning policies tab and select “+ Create policy”.
On the General step, give your policy a name and select which join type you want, in this example, I will use the Azure AD join and use a Microsoft Hosted network in Western Europe. Please do notice that Azure AD join is still in preview.
When you press next, you will get to select what image you will use. You can either use a gallery image or a custom image, and I will in this example use a gallery image by selecting Gallery image in the drop-down menu and then pressing select. I then get a list of all the available images in the gallery, and also the recommended size/license for each image. I select the image I want, in this case, the Windows 11 image, and press select followed by next.
The next step is to select the region and language for your machine. The default selection is English (United States). In this example, we will leave that to English and press next.
The next step is to assign this to a group of users. I’ve created an Azure AD group which I will assign this to called Windows 365 user, which I will use for my users located in Western Europe since my provisioning policy is creating a Cloud PC in the Western Europe Azure region.
After pressing next we can now review our settings and press Create.
Assigning licenses
There are a few ways of assigning licenses to a user, but in this instance, I will do this from within Microsoft Endpoint Manager.
Search and find the user you want to assign a license to by going to Users > All users on the left side navigation three.
When you have found your user, click on their name then select Licenses to see what licenses they have assigned.
By selecting “+ Assignments” we can add or remove licenses from the user. In this case, we want to add our Windows 365 license which you do by checking the checkbox next to the license, then pressing Save.
You have now successfully assigned a Windows 365 license to your user!
Make sure your user is a member of your provisioning policy group which we selected earlier. When you head back to Devices > Windows 365 and select the All Cloud PCs tab you can see that the provisioning process has started.
Assign configuration profiles and compliance policies
While we are waiting for our Cloud PCs to be provisioned, this usually takes a while, we can go ahead and make sure that we are assigning our configuration policies towards the Cloud PCs. We can either create new ones, specifically for the Cloud PCs, or reuse our existing ones. Since in this case, I’m treating a Cloud PC as any other PC, I will reuse the profiles I already have created for my physical PCs.
If you are assigning configuration profiles and compliance policies towards “All devices” you do not need to do anything. If you are using filters, you need to update your filters to also include Windows 365.
The first thing we need to do is to create a device group that dynamically adds our Cloud PCs by going to Groups in the left side menu and creating a new dynamic group.
We want to add a query looking for devices where the Device model contains “Cloud PC Enterprise”.
The query could look like this:
(device.deviceModel -contains "Cloud PC Enterprise")
When you have added your rule. Save the group and let’s head over to Devices > Windows and add that group to our configuration profiles and compliance policies where we target devices. We can also assign any applications which we deploy to devices using this group.
You can either connect to your VDI directly from the browser, which is a pretty cool experience, by clicking “Open in browser” on the Cloud PC.
You can also download the Remote Desktop app and add the Cloud PC in there. There is a link in the Windows 365 portal to download the application and how to add the Cloud PC.
Windows Autopilot is a really nice thing, I think you all are familiar with this by now. But the process to add devices, and adding devices without being an administrator, isn’t really that straightforward with exporting CSV’s and such. The way I usually import the hardware IDs is by using the Get-WindowsAutopilotInfo.ps1 PowerShell script.
The built-in roles in Microsoft Endpoint Manager do not give you rights to add or remove devices, you need to create a custom role for this.
There are two options here, you could either duplicate an existing role such as the Help Desk Operator role and add the Enrollment Programs rights which you will need, or you can create a new custom role.
Creating a custom role for this could be very useful if you want to provide the possibility for your e.g. deskside support personal or a hardware coordinator to upload hardware IDs if this was not done by your hardware vendor.
In this example, I’ve created a new role called “Windows Autopilot Operator”.
Create a new role
Head to the Microsoft Endpoint Manager portal and navigate to Tenant Administration > Roles and click “+ Create” (or mark the role you want to duplicate and click the duplicate button).
Give your new role a name such as “Windows Autopilot Operator”.
Click next and find the heading “Enrollment programs” and enable:
Sync device
Delete device
Create device
Read device
Click through the wizard and create the new role.
We now need to assign this to a group of users. When the role is created, click on the role and go to Assignments.
Click “+ Assign” and give your assignment a name, such as Deskside Support or something describing what kind of users will be in this assignment.
Click next and add a group containing your users.
On “Scope groups”, add all users and all devices.
Complete the wizard and you have now created an assignment. If you wish to add more assignments, you can just click the “+ Assign” button again and repeat the steps.
Importing the hardware ID
We can now get started with importing the hardware ID into our tenant! You can do this either from the Out of Box Experiance (OOBE) process or in runtime. Since I think we all know how it works in run time, let’s have a look at what it looks like during OOBE.
In this example I’m using a virtual machine, but you need to have passed the Wi-Fi selection part if you are doing this on Wi-Fi since we need internet connectivity.
During the OOBE process, press SHIFT + F10 (don’t forget FN if you have such keyboard). Type powershell and hit enter.
You have now launched PowerShell in your terminal, and we can get going with executing the following three lines. You will during the have to confirm that you want to install the script, just press “y” and enter when asked to.
Set-ExecutionPolicy -Scope Process -ExecutionPolicy Unrestricted
Install-Script -Name Get-WindowsAutoPilotInfo
Get-WindowsAutoPilotInfo.ps1 -online
When you run the third line of PowerShell code, you will be prompted to sign in with you account. If this is the first time you are running the online version, you will need to consent the sign in first (it will show up on the screen).
Once signed in, the process will start and the Hardware ID will be harvested and uploaded to your tenant.
This process usually takes a few minutes. Once completed, turn off the computer.
If you have a look in your Windows Autopilot devices list in the Microsoft Endpoint Manager by going to Devices > Windows > Windows Enrollment > Devices you can see that the devices has been uploaded.
Depending on how you are assigning deployment profiles, this will usually be assigned within 15 minutes. Once the profile has been assigned, you can start the computer again and enroll it!
Bonus tip
If you are using group tags to assign profiles like I do in my lab, you can actually do this while running the script by adding “-GroupTag ‘[YourTag]’” at the end of the script.
This will automatically add the group tag to the device entry, and if your automated profiles assignment is depending on this everything will happen automatically!
When you are in a Teams meeting and using video, it can be pretty distracting with your own video. You tend to glans at it quite a lot to look at yourself instead of the other people you have a meeting with.
There is a new feature in Teams that allows you to hide your camera in a meeting, letting you focus more on the people you have a meeting with.
To hide your camera you have to click on the three dots on your camera feed.
Then select “Hide for me” in the menu.
This will push your camera out to the side, hiding your picture for you. All the participants in the meetings can still see you.
To get the camera back, click the little arrow on where your picture is, and the video feed will re-appear for you!
We have all been there. You are in a meeting, saying something smart, and everyone is just silent. Until someone says those dreadful words:
“Hey Ola, I think you are on mute”
I think you all know that feeling and you have to repeat yourself again, maybe losing your flow a little bit.
Staying on mute while not talking in a Teams meeting is (or should be) the common practice for everyone to avoid unwanted background noises in meetings. But this also creates the need to remember to unmute when it’s your turn to speak. And we all know that “finding” the unmute button is sometimes hard…
During January, a new shortcut was added which gives you the possibility to push down Ctrl + Spacebar (Windows) or Option + Spacebar (Mac) when you talk, and when you release the keys you will go back on mute again! To be honest, this might be my new favorite feature in Teams!
This feature is on by default in Teams, but you can turn it of if you like by going to Teams Settings > Privacy and unchecking the Keyboard shortcut to unmute.
One question I get a lot from people that are fairly new to Microsoft Endpoint Manager is “which function should I use to reset a Windows device?” and what the different buttons actually do.
So here is a little cheat sheet what the different type of reset of a Windows device does. Some also applies for other platforms, which I will mention below.
One thing you will notice when clicking these options in the portal, you will always have to confirm your selection.
Retire
This is the first option you will glance at when looking at the remote actions available in the ribbon.
Retire is not a Windows unique feature and is maybe mostly used in a BYOD scenario, but could be applicable for some corporate scenarios as well.
Retire means that you will remove the connection to Microsoft Endpoint Manager and at the same time remove all data YOU put there through MEM, such as apps, profiles, policies etc. You could basically call this an “unenrollment” of the device.
A usefull scenario would be when a user is leaving the comapny and is keeping their iPhone which has been been enrolled through a more BYOD scenario. You will only remove corporate data, but leave all the users personal data.
This feature is maybe not that commonly used for Windows since these devices would typically be “locked” to the tenant using Autopilot. But for BYOD scenarios, this could be applicable.
Wipe
Wipe is just what it sounds like. You will wipe all data from the device and put it back to factory defaults. This feature can be used on other platforms too. This is the feature I most frequently use, especially when testing things and needing to enroll things. This is equal to doing a factory reset from within the operating system. This is perfect for when a device is being decomissioned.
For Windows you get a few more options when triggering the option:
Wipe device, but keep enrollment state and associated user
Wipe decice and continue wipe even if device loses power
Typically, you dont need to select any of these but there are some cases where it could be usefull.
The wipe will also remove the device from Microsoft Endpoint Manager, IF not the first option is selected. The Azure AD object will remain and also the Windows Autopilot object, if you are using Windows Autopilot.
The “Wipe device, but keep enrollment state and associated user” will reset wipes all policies, but keeps user accounts and data, but not user files. It will reset user settings back to default. and resets the operating system to its default state and settings. This basically means that the device will be put back into the same state it was when it was first enrolled. If you are using Autopilot, use Autopilot reset instead.
The “Wipe decice and continue wipe even if device loses power” means that the device will continue to try to wipe untill its successfull. This is great for instance if the device is lost and you really want to make sure that the device is wiped for corporate data. This could in worse case leave the device unbootable if something happens. So use it with causion!
Delete
The delete option is exactly what it sounds like, you will delete the device form Microsoft Endpoint Manager. However, this will only remove the link and all data on the device will remain. However, the next time the device connects to Microsoft Endpoint Manager, corporate data will be removed.
This is mostly usefull when cleaning up any stale objects. Cleaning up stale object could with ease however we automated by using the automated clean-up rules in Microsoft Endpoint Manager found in Devices > Device clean-up rules.
Fresh start
Fresh start is a farily unknown feature in Windows which was introduced back in 2017.
What fresh start does is to remove any pre-installed software by the manufacturer (OEM) which is usally there. The computer will then run a more “Vanilla” version of Windows after the Fresh start.
When triggering this reset, there is an option to retain the user data, including enrollment, which would have little to no impact for the user. If this option is not selected, the device will be reseted and start up on the OOBE screen.
This could be usefull for cleaning out devices which has been delivered with an OEM image instead of a pure Windows image, or if the device is not purchased through your regular channels and getting the “wrong” image which includes pre-installed software.
Autopilot reset
Last out is the Autopilot reset, which is a really useful option if you are repurposing a computer from one user to another.
What Autopilot reset does is that it will restore the device back to a business ready state, meaning that all personal data is removed but all corporate settings are re-applied. All management information about the device is kept and so is the Azure AD object with all its device group memeberships. Doing this will also remove the primary user associated with the device.
When the device is handed to a new user, all they need to do is to sign in and the computer will finilize the setup for them. Users will not be able to use the device until the user enrollment parts are finilized, just like with any other Autopilot enrolled device.
Update: Got this pointed out to me by several people so I thought I would add this here as well. Autopilot Reset is NOT supported on Hybrid Azure AD Joined devices.
Key take aways
I hope this brings some clarity to the different remote actions and that you can figure out which to use when.
The ones I most commonly use are:
Wipe when testing things in my lab or completly changing what the device is used for, e.g. assigning a different Deployment Profile to the device.
Delete when I for some reason have ghost/stale objects
Autopilot reset when a device is being repurposed or changing user
The other ones are ofcourse useful, but maybe not something I frequently use.
This is somewhat of a forgotten post that got left behind in 2021, but I thought I would share this with you.
Since 2021 has been somewhat of a semi-weird year, where we started seeing a way back to the offices but also faced new trends and buzzwords. My favorite ones during 2021 were “hybrid work” and “digital fabric”, both heavily used in the Microsoft world.
I’m coming at this from a millennial’s perspective, maybe going back to my posts about being a millennial in the workplace.
1. Hybrid meetings are here to stay
Since we are seeing more people going back to offices, but in a more flexible way, hybrid meetings are here to stay! Hybrid means you will have people remote and in the room.
This comes with a lot of new challenges and a “do’s and don’ts” worthy of a blog post of its own. But it´s clear that some things will be challenging in this and I would say it comes down to culture and good meeting manners. But also the fact that you need a Teams-link in every meeting and you most likely can’t do an old school whiteboard session like you are used to, because most of our conference rooms are that fancy yet.
Having people remotely connected means that if there is a lot of people in the room, you can’t whisper things to your college since this will most likely be picked up by the mics in the room and you won’t hear the person actually speaking.
Another thing that might be on the list of things you didn’t think of is if someone brought “fika”/pastry to the meeting for those in the room. This is fairly common in Sweden and is usually delivered in some kind of paper bag made for bread. So it makes A LOT of noise. This is a BIG problem if you join through Teams since all you will hear is that bag.
Do have your pastry, even though I will be jealous, but please get rid of the bag before the meeting!
2. Being at an office
I’ve felt this before, but the pandemic and “the return to offices” has confirmed this and made my belief even stronger. If I’m going to an office I’m going there with a purpose. Not just because “that’s where I go to work”. This is a very personal thing, and I know a lot of people who prefer working from an office. But we are now seeing a shift in the “standard approach” and you are no longer the weird exception wanting to work remotely. If I look at the people I interact with daily, they are not based in the same part of Sweden as me anyway, so I won’t meet them at an office.
There is a point of showing up and having social interaction, but if I want to get stuff done I’m way more productive at home. However, going in for meetings and workshops is extremely valuable, but then again I’m going to the office with a purpose.
I keep coming back to this, some of my first posts touched upon this. During my time at Microsoft the phrase “work is not a place, it’s something you do” was something that was really pushed out. I think this is still relevant, and the pandemic has shown this.
However, I’ve picked up kind of a new take on that quote which is “The endpoint is the new workplace, and the workplace is hybrid”. I will come back to this in 2022!
3. Corporate life revolves around an office
One thing I think was pretty clear when we were seeing the light at the end of the tunnel of the pandemic was that everyone got REALLY excited about going back to offices again. I was excited too, this meant that you could meet people again and do things face to face, which is important and meaningful. However, as I stated in the second point, this whole thing “business as usual” at the office and going there every day is not for me but I respect that people feel the need for this.
The standard has always been that you show up at an office to work, working remotely has always been the exception. If you are the kind of person who thrives at an office, that’s great! But if you are the kind of person like me, whose stress is reduced significantly by not having to show up at an office every day, that should be okay going forward.
The two years we have spent working remotely show that we can be just as productive and creative in a remote setup. Since not everyone is the same, we should in the future embrace that we are all different with different needs. Not everyone feels great about being at an office 5 days a week.
Also, the coffee is usually better at home and the line to the microwave is a lot shorter.
4. Hangout on Teams
In my world, I’m really bad at small talk in general and I have always preferred chat over talk. I’m the generation that if I call you, it’s probably urgent (or I’m driving).
However, working from home missing daily social interaction from others other than my girlfriend and dog have actually gotten me to value to call people or just connect to social team hangouts. I’m not always the person driving the discussion in larger groups, but I enjoy the company and listening in.
I’ve actually increased the number of 1:1 calls I have with colleges discussing work and other stuff. I usually call people with a purpose, but I’ve caught myself calling people just to small talk. Big learning for Ola!
5. I miss traveling for work
I had a really intense period in a previous role traveling A LOT. I actually never counted the number of travel days I had per year, but I easily spent 3-4 days traveling per week during some periods.
I was so done with traveling for work, and I wanted to settle for something more predictable being more in the same place all the time.
Now I’ve reached a point where I actually miss traveling for work. Maybe not 4 days per week, but the occasional longer trip to see a customer or just attend a conference.
I really miss that and I want to do more of that when we get more into a controlled Covid situation.
6. I’m not used to people anymore
I don’t consider myself as an introverted person, my conclusion is that I’m somewhere in between introvert and extrovert.
But this whole thing with only meeting people through Teams has made meeting people IRL something that I get really exhausted by. It really drains my energy.
We had a 1,5-day gathering with all the people who work at Advania Knowledge Factory and I basically needed a day to recover from just meeting people.
Getting back to not being exhausted after meeting people several days in a row will take some time getting used to.
7. Learn to stop working
This is probably what I’m really bad at during the weekdays, but I try really hard NOT to be in front of the computer on the weekends.
My typical day starts at around 9:00 am, most meetings tend to start then. I work until about 12:00 where I have lunch and take my dog for a walk, hopefully being back until 13:00 where after lunch meetings usually start.
Then I’m stuck behind the computer until about 18:00 or something like that when it’s time to start cooking dinner. I might not do actually work that late, it usually involves catching up on tech news and community stuff.
There is always one more email to reply to, one more blog post to read, and one more tweet to re-tweet. But learning when to stop is key and this is something I need to improve in 2022 to actually keep me sane. One thing that I’ve promised myself to actually start using is the virtual commute in Viva Insights. This is a really cool feature and the days when I’ve used it I’m more disconnected from work and can focus on other stuff. If you haven’t tried it yet, I really recommend you do!
We have all done this. Showing something in the webcam in Teams and pointing in the wrong direction or mixing up left and right, since the camera is mirrored by default in Teams. It’s always been like this, but it’s still a tricky thing.
However, this might not be a problem for most users, but it could actually be usefull when for example showing physical things. Or it might just be that you want to see what your video feed looks like for everyone else.
This settings is set in the Device Settings panel in the meetings, click More actions (the three dots) and select Device settings. At the bottom you will find “Mirror my video” which is enabled. By disabling this, your video preview will not be mirrored anymore.
So before changing this, my camera is mirrored in my preview box like this.
When I disable the “Mirror my video” feature, it looks like this.
Like you can see, my preview is not mirrored anymore!
HoloLens got to be one of the cooler devices out there, but probably also one of the lesser-known devices how to manage.
What is a HoloLens really?
HoloLens is Microsoft’s device aimed for Mixed Reality, but at heart, it’s actually a Windows-based device but done in a more modern way. This means that the support for legacy protocols is limited, but also that the level of built-in security is maybe a bit higher than on your Windows-based PC. You can read more about the HoloLens as a platform here.
Given that it’s a Windows device, we can manage it using basically the same policies in Microsoft Endpoint Manager (MEM) as you would for the rest of your Windows devices. A lot of baseline profiles could be re-used (or duplicated) with ease which simplifies the configuration a bit.
There are a few things to keep in mind when it comes to Microsoft HoloLens 2, which has had an impact on the designs and implementations in my experience.
It doesn’t support EPP/EDR software of any kind
You can only run UWP based applications
You will need additional licenses to run e.g. Remote Assistance
HoloLens 2 as a kiosk
There are a lot of different applications and ways to implement and use a HoloLens 2. In this post, I’ll focus on how to set up the HoloLens 2 as a multi-app kiosk, but with user sign-in, using Microsoft Endpoint Manager.
Importing the device into Windows Autopilot
If your vendor or retailer didn’t import the HoloLens hardware ID for you, you can do this by following these four simple steps:
While the HoloLens 2 device is powered on, press and release the Power and Volume down buttons together to trigger the hardware ID and diagnostic log collection process.
Connect the HoloLens 2 device to a PC using a USB cable so that it shows up in File Explorer.
Browse to Internal Storage > Documents and extract AutopilotDiagnostics.zip. This file/folder will contain a CSV file with a a file name that begins “DeviceHash…”.
Upload the CSV file to the Windows Autopilot service
In order to simplify our management a bit and be able to create a dynamic device group with only HoloLens devices, assign a GroupTag to the device such as “Hololens”.
Creating a device group for HoloLens
Like all things in device management, we are really dependent on groups. In this case, we will use a device group to target only our HoloLens devices.
You can create a new Azure AD group by selecting Groups in the left hand side menu in the MEM portal. Then select “New group“.
Give your group a good name and select “Dynamic Device” as Membership type.
Next, click “Add dynamic query” at the bottom and add the following rule syntax, but replace the word Hololens used here with the name of your GroupTag.
Click Save followed by Create to finish the creating of the group.
Setting up enrollment
First off, we need to create a new Deployment Profile for the HoloLens platform.
You will find the Deployment Profiles by navigating to Devices > Windows > Windows Enrollment and selecting Deployment Profile.
When you have selected the Deployment Profiles card, select “+ Create Profile” and choose HoloLens as the platform.
Give your profile a name in the Basic tab and press next. On the “Out-of-box experience (OOBE)”, you can really only have to change the name template if you are looking to use custom names for your HoloLenses. In my example, I’ve left all values to default. Press next to move to the next tab.
On the Assignment tab, select your HoloLens device group and press next.
Review your settings and hit Create to finish the creating of the deployment profile.
Creating a Filter for HoloLens
To make sure that we only target settings deployed towards users to their HoloLens devices, we need to create a filter we will use later on.
Navigate to Tenant administration > Filter. Create a new filter by clicking “+ Create” in the top ribbon. Give your filter a name, such as HoloLens, and select Windows 10 and later as the platform.
Since filters are kind of like dynamic groups, we need to add a syntax. The easiest way I’ve found to include HoloLens devices is to use our Deployment profile name, the attribute is called EnrollmentProfileName on the device. Enter the name of your Deployment Profile in the Value field.
Click next, then review and create the filter.
Configuring kiosk mode
You could basically already enroll your devices now and be done, but it will be like an unconfigured PC, your end-user will miss vital settings and applications.
Since this is a Windows-based platform, you can reuse or duplicate profiles you already have for Wi-Fi, certificates, and such. Not all profiles make a whole lot of sense to use on the HoloLens (such as settings for the Office suite or Chrome browser to give some examples).
The profile we need to create to set up the Kiosk-mode on HoloLens is a profile based on the Kiosk template.
Go to Devices > Windows > Configuration profiles and create a new profile by pressing “+ Create profile” in the top ribbon. Select Windows 10 and later as platform and Templates as Profile type. Scroll down and find the Kiosk template and click create.
As always, give your profile a name based on your naming convention on the basic tab and press next.
Based on your scenario, select either “Single app, full screen” or “Multi app kiosk” as kiosk mode and select “No” on the question if device is running S mode.
In my scenario, I will configure that users will use the device using their Azure AD accounts. Since I have to specify a group with eligible users, I’ve in my setup used a group containing most of my users meaning that all my users are allowed to sign in to the HoloLens. You can easily assign this to either a group of users or even a specific user. You can also add additional groups and/or users. Depending on your scenario, you can make different choices here.
Next up is to select what applications we will run on the device. This can be done by either selecting built-in applications or applications distributed through MEM. Keep in mind that Win32 applications DO NOT WORK on the HoloLens when selecting applications.
If you want to add built-in or system applications, this is done by adding the AUMID of the application. You can find all the HoloLens 2 applications AUMID on this MSFT Docs site.
In this example, I will add one built-in application and one store app. You add apps by pressing the “Add…” button under the Browser and application section.
When adding a app by using AUMID, you give the application a name (preferably what it’s called in the reference document) and the AUMID for the application.
When adding a store app, MEM will list the apps you have available for distribution. Also, keep in mind that you will need to make sure to target the application distribution towards the HoloLens group.
Leave the rest of the settings to the default value and click Next.
In order for the Kiosk mode to function properly when requiring Azure AD users to sign in, the profile needs to be targeted toward users otherwise nothing will happen in my experience. If you are notdoing personal logins, you can target this towards a device group.
In order to not assign the Kiosk-mode to all the user’s devices, we will need to use a filter to limit what devices the profile is assigned to.
On the Assignment tab, select your group of users who will be allowed to use the HoloLens and then press “Edit filter” next to the group.
Select “Include filtered devices in assignment” and choose your filter then press Select.
Press next and leave the Application Rules to blank and review and create your profile.
Enroll and sign in!
Now it’s time to enroll your device, simply start the device and follow the on-screen instructions.
What I’ve seen is that sometimes, the kiosk mode does not kick in on the first login after enrollment. If this happens, simply sign in and out of the device, this has done the trick for me!
One feature I really like in Teams on the desktop is the possibility to use different backgrounds in a meeting, to have your video background blurred or replaced by a picture. I think we all are familiar with this feature.
Now, this feature has finally reached mobile devices, which in my world could be really useful since you tend to be out and about while on your mobile device.
It’s really easy to get started with and to me, it’s really useful. I tend to connect through my phone when I’m out and about which then can remove any messy background since it’s not a controlled environment like my home office.
How to enable it?
When you connect to a meeting, you will get a new option at the top of the screen called “Background effects”.
When you click that, you will get the option to select a blurred background, a Teams standard background, or a custom background.
My personal favorite to use is the blurred background since it doesn’t take any attention from me so to speak. It makes it easier to focus.
But you could just as easily upload a picture from your camera roll and use that. Like faking you are out on the golf course.
We use cookies on our website to give you the most relevant experience by remembering your preferences and repeat visits. By clicking “Accept”, you consent to the use of ALL the cookies.
This website uses cookies to improve your experience while you navigate through the website. Out of these, the cookies that are categorized as necessary are stored on your browser as they are essential for the working of basic functionalities of the website. We also use third-party cookies that help us analyze and understand how you use this website. These cookies will be stored in your browser only with your consent. You also have the option to opt-out of these cookies. But opting out of some of these cookies may affect your browsing experience.
Necessary cookies are absolutely essential for the website to function properly. These cookies ensure basic functionalities and security features of the website, anonymously.
Cookie
Duration
Description
cookielawinfo-checkbox-analytics
11 months
This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Analytics".
cookielawinfo-checkbox-functional
11 months
The cookie is set by GDPR cookie consent to record the user consent for the cookies in the category "Functional".
cookielawinfo-checkbox-necessary
11 months
This cookie is set by GDPR Cookie Consent plugin. The cookies is used to store the user consent for the cookies in the category "Necessary".
cookielawinfo-checkbox-others
11 months
This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Other.
cookielawinfo-checkbox-performance
11 months
This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Performance".
viewed_cookie_policy
11 months
The cookie is set by the GDPR Cookie Consent plugin and is used to store whether or not user has consented to the use of cookies. It does not store any personal data.
Functional cookies help to perform certain functionalities like sharing the content of the website on social media platforms, collect feedbacks, and other third-party features.
Performance cookies are used to understand and analyze the key performance indexes of the website which helps in delivering a better user experience for the visitors.
Analytical cookies are used to understand how visitors interact with the website. These cookies help provide information on metrics the number of visitors, bounce rate, traffic source, etc.
Advertisement cookies are used to provide visitors with relevant ads and marketing campaigns. These cookies track visitors across websites and collect information to provide customized ads.
