This blog will be about “something” old we need to beware of. This blog has something to do with Autopilot and performing a lockdown on the device to make sure the possibility to “set up Windows with a local account” will be disabled Some weeks ago a customer called us that his new device wasn’t working. I am going to explain what happened. I will divide this blog into multiple parts. Locking down the “Change Account” options The Real issue…
This blog will show you how you could make sure you can still pre-provision your devices with Autopilot even when those fancy new devices have Intel Tiger lake chipsets (11th gen). PLEASE NOTE: This fix only works for the Intel Tiger lake Chipset, not for AMD!. When there is a fix for AMD I certainly will post a new blog! If you didn’t read my TPM attestation blogs, please read them first as they could give you a good understanding…
In one of my older blogs, I was talking a lot about how and why you don’t always need to go hybrid (HAADJ). I also showed you the kind of problems you could run into. This blog will show you how to make sure your old legacy apps (which are configured as Remote Apps) can be easily deployed to your AADJ devices, so you won’t need the go Hybrid 😛 Please read my blog about HAADJ / SSO to on-premises…
This time a small blog, this blog will show you when reinstalling an existing device and enrolling it into autopilot white-glove could get you in trouble sometimes. No red screen like you would expect like I was talking about in this previous blog. This week we were asked to reinstall some existing Azure Ad / Intune enrolled devices before they were handed to some new employees, so we did. Before we reinstalled the device, we made sure the device was…