Error 0xc1036501 while Self-Service at AutoPilot

Hi all.

Last time I was playing with Self-Service AutoPilot, where device is deploying automatically without any interaction from end user / administrator.

After creating profile on Intune, assigning to proper group and started deploying I received message that was problem while deploying etc.. Please contact with your administrator with error code:

0xc1036501

Everything what I was able to find on Internet was providing to More than just ConfigMgr site – direct link to post here But on that site wasn’t provide much information how to fix that issue.

So I decided to find more information about that.

I was started with collecting logs from enrollment to USB drive and check logs from my computer:

Looks similar? Nope, for me too isn’t look similar. So how to fix that issue?

You need to check Azure AD > Mobility (MDM and MAM) and check if you have more than ONE provider. On my case I have two: Microsoft Intune and the second version of Intune which I didn’t remember that i’m adding.

After removing that one what you can see on screen, self-service deployment was started without any issues.

Deploy Start Menu using Intune

Start menu on fresh installation of Windows is ugly. Is very ugly, just see on my screen:

Why I should work with that kind of menu?

Maybe better idea will be deploy start menu looks this same on every device in our company?

For example on that blog post we will deploy start menu looks like on below screen:

It’s quite looks better, right?

Firstly, we need to prepare Start menu on another computer and export that menu to XML file using PowerShell command:

Export-StartLayout -path menu.xml

When export is completed we can start with creating Device Profile like on below screen:


  • Platform: Windows 10 and later (1)
  • Profile type: Device Restriction (2)
  • Scope: Start (3)
  • On fourth point we need to upload created XML file

When the policy is created, need to be assigned to proper group. On end device you can click: Sync.

After couple minutes you will see new Start Menu on screen.

Have fun!

Deploying Wi-Fi profile connection using Intune

On that post I want to show you how to deploy Wi-Fi profile using Intune. That means – user don’t need to know what is a password for our small Wi-Fi network.

Let’s start!

First we should create new Device Profile with settings:

  • Platform: Windows 10 and later
  • Profile type: Wi-Fi

When we select proper option, we can start with configure our settings. On 3 you need to insert SSID and Connection Name, on 4 you need insert password to your network.

It will works only when you have WPA(2) WiFi connection. If you have Enterprise network – select Enterprise instead of Basic on Wi-Fi type.

After assignment policy should deploy without any issues. When user disconnect LAN cable – Wi-Fi connection will connect automatically.

From end-user there is not exist any requirements.

Have fun!

Azure Nested Virtualization – Internet connection

Yesterday I created new machine on Azure with Windows on board –
Standard D8s v3 (8 vcpus, 32 GB memory). It’s something big for me – previous I was used smaller machines. So, main target of that machine is virtualization. I’m preparing posts about Remote Desktop Services, so I needed one host where I install Hyper-V role, and on that Hyper-V I install 5 x Windows Server 2019.

Sharing network on Azure is not easy like in our home environment and we need to create second switch, create network and set up NAT. It’s easy to do with my post.

First, we need to create virtual switch named NATSwitch using that PowerShell command:

New-VMSwitch –SwitchName “NATSwitch” –SwitchType Internal

After that we need to create new address with that command ( I will use space 192.168.0.0/24) and assign it to previously created Switch

New-NetIPAddress –IPAddress 192.168.0.1 -PrefixLength 24 -InterfaceAlias „vEthernet (NATSwitch)”

On the end we need to create NAT on our switch which we created:

New-NetNat –Name NatNetworkRDS –InternalIPInterfaceAddressPrefix 192.168.0.0/24

Now, you need use that NATSwitch and assign manually IP address like on below screen. After that you should have Internet connection.

You can see that I have IPv4 address from 192.168.0.0/24, but as DNS server i’m using Google servers. Why? Because on host machine I don’t have installed dns role.

Hello world! ;)

Yep, it’s my first blog on the English version of my personal blog. Everything what I wrote on the Polish version of blog – https://dzejzibloguje.pl will be published here too.

About what I will write on future? Especially about Intune – its future of New Device Management.

I would like to write about Azure AD / Office 365, Powershell, MDT, Windows Server, Windows Client etc…

First – sorry for my English. If you found any mistake, please ping me here in the comments sections or on my Twitter for example. Or just send email with information. I’m still learning, but I think after publishing couple posts will be much better.

I don’t have any timetable for my posts. When I will write – it will be published.

So, if you have any questions – please ask on below comments, do not hesitate add my blog to yours RSS reader and read all my posts. Good luck! 🙂