Windows 10: ADR Deployment Installation Deadline

Hi What does "As soon as possible" in the ADR deployment installation deadline mean:- update installation will be forced immediately? - updates installation starts when update-policy is triggered on the clientThanks

:)

 

ADR for EndPoint Protection SCCM Deployments Failing

I have been experiencing a similar issue in ADR for EndPoint Protection SCCM deployments all week long.

The Security Intelligence Update for Windows Defender Antivirus - KB2267602 (Version 1.303.837.0) fails with error 0X87D00668 (Software update still detected as actionable after apply) every day on about half of our Win 10 v1809 x64
Dell clients.

The same behavior is repeated daily.

Any help would be much appreciated!

 

SCCM version 1602. Is there anything that we are missing that is causing the deployments to not succeed?

My company recently updated to 1602. We've sent out two patches for updates and neither are deploying to the field(One is at 4% after a month and a half, the other is at 0%). We've confirmed that the deployment package settings are identical to previous
patches that we've deployed. To give you the steps that we took to deploy the patches

• Created the software update group and added all the software for the monthly update to group. (the files are on all of our distribution points as of right now).
• Deployed to a group of test PCs using a specific template that has been in action
• Made the type of deployment required with detail levels showing "only success and error messages"
• For schedule I made available time ASAP as well as deadline.
• Under User Experience we hide notifications in software center, allows system restart (if necessary) outside of maintenance windows
• There are no alerts
• Deployment options are "download software updates from DP and install"

Is there anything that we are missing that is causing the deployments to not succeed?

 

Customised Windows 10 deployment on multiple desktops and laptops.

OK, after giving this a thought and thinking how I would do it, here's my suggestion. Please notice that, as I said, this is how I would do it. Other geeks might disagree with parts or all of it.

I tested this scenario using one Hyper-V VM as technician machine (the one to build image) and three virtual machines to test simultaneous deployment in two scenarios:

• Capturing install.wim from technician machine and using DISM to apply / deploy image from a network share
• Capturing install.wim from technician machine, making ISO from it, deploying by clean installing from ISO burned to Flash drive

Based on the fact that ISO method is clearly faster and simpler, it is what I suggest to you. I estimate you would need an hour and half to two hours to customize install image, capture it and make an ISO, then assuming you would make 5 Flash drives for install / deployment you would need about half an hour per five machines, in other words you would deploy to those 25 new machines in less than three hours, almost a full working day to deploy those 50 existing ones.

Two working days, day 1 to make the image and deploy to new machines, day 2 to deploy to old ones.

Chronological workflow based on my suggestion:

Phase 1, Image customization tutorial, parts One through Six:

• Install Windows 10 on a technician machine (I recommend Hyper-V VM but any capable PC is OK)
• Boot to Audit Mode
• Update Windows, install software, customize & personalize Windows
• Sysprep

Phase 2:

• Capture the install.wim from technician machine as told in this tutorial, Part Four steps 4.1 through 4.5 (physical PC as technician machine) or Part Four steps 4.6 through 4.13 (Hyper-V VM as technician machine)
• Create ISO as told in same tutorial, Part Five
• Burn / write ISO to as many Flash drives as you want to / need to for simultaneous installs
• Boot production machines from Flash drive, install Windows 10

The above is how I would do this. If you choose the DISM method instead, applying install.wim from a network share, see this Microsoft support article: https://technet.microsoft.com/en-us/.../hh824910.aspx

For more advanced deployment using MDT see this article: https://technet.microsoft.com/en-us/.../dn475741.aspx