Long time no see, huh? Now I’m back with a new post about removing the Windows.old folder after a feature Upgrade.
Recently I seen this on twitter, a commented it with: Why don’t you let the automation from Windows 10 let it do. But since then, I was in a project, where the removal of this folder was required, and within the Upgrade Task Sequence. I thought, this is easy, starting the Scheduled Task should do the job…
Continue reading
Updates Management
ConfigMgr – Windows 10 Servicing – Step by Step
Today I would like to show you, how you can implement an Upgrade of a Windows 10 Installation through the Servicing Option.
I always think of two things, when I have to decide to use an Upgrade Task Sequence or the Servicing Model, and those are:
But for this blog post, I would like to show my setup for the servicing model.
First of all, I have already written a post about the Update process in a slightly overview manner, you will find this post here: My old post
The first step would be to determine which packages you would like to implement for the upgrade. Based on the fact, that I use English as base language, I will add the Feature on Demand (FoD) packages, and I will also add the feature package NetFx3. My Setup does also contain the German Langauge, which requires me to add the corresponding Language Pack and FoD Packages. The following picture shows the folder of my Packages which I want to include within the Windows 10 Installation:
Continue reading
ConfigMgr – Windows 10 Feature Update without a Task Sequence
Today I would like to talk about the upcoming update cycles you have to do, when you are using Windows 10 Current Branch or Current Branch for Business. This means, if you have started to install Windows 10 1507 (which represents the first Windows 10 Release, some may call it also RTM) in spring of last year, you will be soon required to upgrade to a newer version of Windows 10. Also if you are using Windows 10 1511, with the upcoming creators update, the 1511 version of Windows 10 will be soon unsupported, following the official guidelines.
Continue reading
Office365 – Manage Updates through Configuration Manager
Today I had the problem that some clients were failing to install the Client 365 Package from our System Center Configuration Manager (1602). I have set up the configuration for the Office 365 installation through GPO, this process is outlined on the following TechNet Article: Manage Office 365 client updates with System Center Configuration Manager
But the client did not even start to download the update:
Continue reading
ConfigMgr 1602 – Windows 10 Servicing Plans create continuous Software Update Groups
I was running the Service Plan for the Windows 10 enrollment within System Center Configuration Manager 1602 (Current Branch).
Unfortunately the option the use the same Software Update Group over and over again is missing:
Continue reading
ConfigMgr 1602 – Windows 10 Servicing “Error 3”
Today I solved my Problem with the Service Plan of my Environment, it always ended up with the following Error in the Patchdownloader.log, this Log usually reside in “C:\Program Files\SMS_CCM\Logs”:
Failed to move C:\Windows\TEMP\CABD212.tmp to \\deheim.hosebei.ch\hosebeiDFSroot\Deployment\Packages\_UpdatePackages\20160116 - Win10x64\9a30f732-4d40-4b56-b86b-8253f80868a1.1\10586.0.160212-2000.th2_refresh_CLIENTENTERPRISE_VOL_x64fre_en-us.esd, error 3 Software Updates Patch Downloader 26.03.2016 19:16:01 7780 (0x1E64)
Will retry in 5000ms Software Updates Patch Downloader 26.03.2016 19:16:01 7780 (0x1E64)
Failed to move C:\Windows\TEMP\CABD212.tmp to \\deheim.hosebei.ch\hosebeiDFSroot\Deployment\Packages\_UpdatePackages\20160116 - Win10x64\9a30f732-4d40-4b56-b86b-8253f80868a1.1\10586.0.160212-2000.th2_refresh_CLIENTENTERPRISE_VOL_x64fre_en-us.esd, error 3 Software Updates Patch Downloader 26.03.2016 19:16:06 7780 (0x1E64)
Will retry in 5000ms Software Updates Patch Downloader 26.03.2016 19:16:06 7780 (0x1E64)
Failed to move C:\Windows\TEMP\CABD212.tmp to \\deheim.hosebei.ch\hosebeiDFSroot\Deployment\Packages\_UpdatePackages\20160116 - Win10x64\9a30f732-4d40-4b56-b86b-8253f80868a1.1\10586.0.160212-2000.th2_refresh_CLIENTENTERPRISE_VOL_x64fre_en-us.esd, error 3 Software Updates Patch Downloader 26.03.2016 19:16:11 7780 (0x1E64)
ERROR: DownloadContentFiles() failed with hr=0x80070003 Software Updates Patch Downloader 26.03.2016 19:16:11 2800 (0x0AF0)
Continue reading
ConfigMgr – Create Device Collections based on Windows 10 Build
Hey,
You might come to the same spot, where you would like to split your Windows 10 devices into different collections based on the Windows 10 Version. I will show to you, how easy you can achieve that, but let me say first, that this could be implemented from Microsoft Out-Of-The-Box.
If you are using System Center Configuration Manager Current Branch (CB) and Windows 10, you will have a nice Windows 10 Servicing Dashboard within your Software Library, to open it, just click on “Windows 10 Servicing” within the Software Library:
Continue reading
ConfigMgr 1511 – Run WSUS cleanup wizard automatically
Another new check box with the new System Center Configuration Manager release will help you massively to have a functional WSUS Infrastructure for your SCCM Environment:
If you activate this checkbox, a WSUS Server cleanup will be started after the next software update synchronization is done. Continue reading
SCCM 2012 – Reboot after Installation in Maintenance Window
When you patch your Server automatically, and also want to reboot the machines when a maintenance window is active, that is quite easy. Modify the Settings of the specific collection, I would recommend to use collections created for the use of maintenance window only, in this example, we have a short window of 45 minutes: Continue reading
SCCM 2012 – Automatic Deployment Rules
For how long we was waiting for this feature? 🙂
First, let’s take a look back: In SCCM 2007 we had the choice between make Deployments over and over again, or to use the WSUS Console and make an Automatic Approval. In SCCM 2012 there’s no need to use the WSUS Console, when you want to deploy Updates automatically, and the best: You’ve got control over the Updates, because everthing is handled within SCCM.
blog.hosebei.ch 