In this post, we will deploy the recently released Windows 2019 with SCCM 1810. We will describe how to create a SCCM Windows 2019 deployment task sequence and deploy it to your servers. If you are already deploying Windows 10 in your environment, or even Windows Server 2016, chances are that you won’t need to change anything in your environment. This task sequence will help you deploy a “vanilla” Windows Server 2019 Standard edition using the default Install.wim from the Windows 2019 media. This means that you’ll end up with a basic Windows 2019 with the SCCM client and nothing else. You will be able to edit this task sequence later to customize it to your environment. PREPARE YOUR Windows 2019 OPERATING SYSTEMS We will now import the Windows Server 2019 WIM file before deployment. We will start by importing the default Install.Wim from the Windows Server 2019 media. You could also import a WIM file that you’ve created through a build and capture process. Mount … Read More
Installing an SCCM DP/MP/SUP in an untrusted domain
There may come a time in your SCCM administration days where some special needs may arise. I had such a case recently. Long story short, in our company, we have a windows domain where no trusts exist with our primary domain where SCCM resides. The problem with that is since there is no visibility in between the two domains, how do you get the servers or workstations managed? This post will describe Installing SCCM DP MP SUP in Untrusted Domain. Default settings? Such as a default Windows Update setup. Nah, I like to have some degree of control over who does what and when. Install a standalone WSUS server? Yes, this is a viable option where you can set and forget it. But it probably doesn’t fit with your SCCM setup. Install a completely separate SCCM infrastructure? Sure this works. But… Do you like doubling all your work? I surely … Read More
Inject Software Updates in your WIM using SCCM Offline Servicing
Offline Servicing in SCCM is the process through which you can inject software updates in your operating system WIM files. This process can alleviate your build and capture yearly/bi-yearly WIM updates that you most likely run in your enterprise. However, as much as this process is great to shorten your gold image updates, it’s still not perfect. Why? The answer is quite simple. Even if your gold image contains products such as Microsoft Office, offline servicing will not apply Office patches even though these are downloaded to your Software Update Point. Only core Windows applications can get patched through this process. What are the type of core applications that you can apply patches to? Obviously, Windows, Internet Explorer, .Net Framework and so on and so forth. (also called CBS, for Component Based Servicing) SCCM Offline Servicing Overview Here’s what happens in the background when you start the SCCM Offline servicing process : SMS_Executive … Read More