This is a quick and short post on one of the new and welcomed additions to application management in System Center Configuration Manager 1810 (SCCM). Starting with 1810, we now have the ability to let the end users quickly repair installed applications through the Software Center.
This will come handy in self-service scenarios or when support-personal are trying to solve application specific issues. A common and well known troubleshooting scenario, is to try and repair a broken application. Curious? Read on 🙂
The repair function at display in the Software Center
Good news everyone! System Center Configuration Manager Current Branch 1810 was released today, and similar to previous releases, I’m going to walk you through the process on how I updated my production environment.
Not much has changed, but I know someone will fancy to have an A-Z guide as inspiration, and as of such, I here give you the exact steps I went through to update SCCM to the very latest and greatest version.
The 1810 update ready for installation in the console
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)
Some of the apps I tend to remove and keep removed using this method 🙂
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 🙂
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 🙂
A peek into my AutoPilot devices in my test tenant 🙂
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. 🙂
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.
Good news everyone! Windows 10 1809 was released today and among other awesome things, that also brings us an updated version of the Windows Assessment and Deployment Kit (Windows ADK).
As we all know, the Windows ADK is a requirement for doing OSD (Operating System Deployment) using SCCM (System Center Configuration Manager), so let’s walk through a step-by-step guide on how to install this latest and greatest version.
Sneak peek at the version of the boot images post upgrading to the new ADK
