"Everything can be done automatically, as long as you configure it manually"
Good news everyone! The feature was introduced at Ignite earlier this year and now it’s finally here. Windows AutoPilot now allows you to join your Windows 10 v1809 devices to your on-premises Active Directory (Hybrid Azure AD Join). All the magic lies in a new Intune connector for Active Directory. Sounds exciting, right? This will be everything you need to know, on how to get started with this new amazing feature.
Removing the built-in apps in Windows 10 is often a hot topic and in same regard, it’s often discussed if and how they are removed. There are several excellent Powershell scripts for the same purpose made by the community, and they possibly satisfy most needs already.
But maybe you don’t fancy maintaining a Powershell script and maybe you don’t want to deal with specific apps coming back after an in-place upgrade. Or perhaps you just want an alternative. Then this might be of interest. This is solely based on using Microsoft Store for Business integrated with SCCM (System Center Configuration Manager), to uninstall some of the unwanted built-in apps in Windows 10 (and keep them uninstalled shall they ever return)
WOW! Three days ago (November 1, 2018) I was completely and utterly taken by surprise. And one of the good ones indeed. I received one of the most anticipated e-mails to date, the e-mail stating that I was awarded the Microsoft Most Valuable Professional award in Enterprise Mobility for 2019-2020.
Not only was I surprised, but I instantly felt extremely proud, honored and humbled. I was literally speechless. I was in the middle of a technical conversation with some coworkers when the e-mail ticked in and highlighted my phone. Just then everything changed. I remember that I froze and had to re-check the content and sender of the e-mail several times.
This is the beginning of something great I’m sure, and there is a lot of hard work waiting for me ahead.
There’s a bunch of people I obviously owe a lot of gratitude and thank you:
Niall Brady – for believing in me. For motivating me and for just being a good guy. Thank you!
My employer and coworkers – for letting me work so dedicated with my favorite Microsoft products. For giving me space and everything I needed to accomplish this amazing goal.
My family – also for giving me time and space to spend that many hours (usually after-hours) with my laptop fighting the good fight.
Microsoft – for giving us this amazing opportunity and obviously for awarding me. I am EXTREMELY honored and I will do my very best to continue to give back.
Again, thank you everybody. Thank you so much.
/Martin
More info about being an Microsoft MVP:Â https://mvp.microsoft.com/
Last week I blogged about how to get properly started with Windows AutoPilot. This week I’m continuing on the topic, and going into details on how you can deploy the SCCMÂ (System Center Configuration Manager) client as a part of the Windows AutoPilot enrollment and thus achieve Co-management with SCCM and Microsoft Intune.
I have previously blogged a lot about Co-management. Focus here has been enrolling devices already managed by SCCM into Intune MDM.
This post is the opposite. This time we are deploying a device through Windows AutoPilot, enrolling it into Microsoft Intune and then deploying the SCCM client through the Cloud Management Gateway. Sounds interesting? Read on 🙂
Short and sweet: A new Update Rollup is available for download and installation for System Center Configuration Manager Current Branch 1806. More about the rollup itself and it’s fixes here:Â https://support.microsoft.com/en-us/help/4462978/system-center-configuration-manager-version-1806-update-rollup
This is a quick walk trough of the installation for those who’s interested 🙂
It’s time for me to take on a new topic on the blog. I have been experimenting, working and blogging a lot about SCCM, Intune and Co-management, but never really touched base with Windows AutoPilot. Time is due and this will be the first in a series of posts about Windows AutoPilot and how to eventually reach Co-management with SCCM and Microsoft Intune through Windows AutoPilot.
First things first though. This post will give you everything you need to know on how to properly get started with Windows AutoPilot. Curious? Read on 🙂
In line with traditional practice on my blog, I’m kicking off my posts with an introduction – this time is no different.
The topic is something new however, and that’s even though I have been a frequent SCUG.DK attendee the past many years. I don’t dare to make a promise about making this an habit either, but I do think this event in particular deserves a written summary. So here goes my very first of it’s kind; the summary of SCUG.DK Fall Edition starring David James also known as @djammmer on Twitter.
And by the way, I’m not used to doing summaries – so please bare with me if I missed something obvious. I took notes and did a lot of pictures while tweeting live from the event, so there’s a slight chance I missed out on a thing or two. Apologies in advance.
Also, during this event there was a dedicated request to do tweets with the #MMSMOA hashtag for the chance of winning a trip to MMS 2018 Desert Edition, so if browsing Twitter for interesting Tweets, you will find some of them located on both #SCUGDK and #MMSMOA. 🙂
More good news! Microsoft Intune now provides us with an even easier way to pre-configure an e-mail account for Outlook on iOS (and android). This is done with the use of an App Configuration Policy and the additions to the configuration designer when configuring the Outlook app. Let’s walk through the process.
No real introduction is needed here. Long story short is, if you installed the new Windows 10 ADK v1809 and the new Windows PE add-on, chances are that you have issues with WPF forms in Powershell in Windows PE.
Luckily we have Twitter and the community is darn fast in sharing workarounds and what not – and this time is no different. More specifically these two conversations on Twitter by @AdamGrossTX and @ferozekhan267oa are interesting.
@ferozekhan267oa mentioned that replacing ‘UIAutomationCore.dll’ in Windows PE was fixing the problem in his end, so I decided to give it a go as well.
I’m using NickolajA‘s ConfigMgr front end, both in production and in labs, so when I updated to the new v1809 ADK and Windows PE, I immediately spotted that something was wrong; no frontend was ever being launched and SMSTS.log was indicating issues as well.
Continuing on the Windows 10 1809 journey from wednesday! As something completely new, RSAT (Remote Server Administration Tools) is now included as a set of “Features on Demand” in Windows 10 itself and is no longer something you download and install separately.
You can obviously install the tools manually in Windows (this is done from the settings menu and from there select to Manage Optional Features), but as always, we don’t like to do stuff manually. Therefore I created a complete Powershell script which can be used in SCCM (System Center Configuration Manager) in an unattended and automated deployment.
