Sccm client not updating

22-Nov-2017 05:26 by 8 Comments

Sccm client not updating

Our help desk could get flooded with calls.” But then I realized that if this really were a wide spread issue with this service disabled, we’d have a lot more issues in previous months with Office 2003 updates.But nonetheless, I was curious, so I made a query in SCCM to look for all machines with the Office Source Engine disabled.

By doing a search, I found that 0x80070643 relates to an issue with the Office Source Engine being disabled.

The query syntax is as follows: select distinct SMS_R_System.

Netbios Name from SMS_R_System inner join SMS_G_System_SERVICE on SMS_G_System_SERVICE.

I suggest: In addition, this handy tool – https://gallery.technet.microsoft.com/Config Mgr-Driver-Injector-aae7d17d is available, which can grab the drivers off of a machine and import them into SCCM.

Handle it with a little bit of care, as just importing all drivers can again lead to driver bloat and different versions of things such as chipset or network drivers.

The handler tells me that WUA passed this on to MSI and MSI returned exit code 0x80070643.

Windows Update (which is the Handler in this case) is saying its exit code is 0x8024200b.I don’t love any of the major OEM’s, they all have their faults…..but some of the more fringe players make some junk that’s hard to manage deployment for.It is very important that the driver type is correctly identified.Many drivers come in an format, but can be extracted to expose the inf/sys/cat files.1) Under your package source, create a directory called “DRVSource” (or similar) 2) Copy all your original drivers into a folder structure under this directory such as 3) Import your drivers into the database, one model/OS combo at a time – creating a category for them as part of the process. Import everything from DRVSource\Dell Opti Plex.745\Win7.x64 and create a category called “Dell. Win7.x64” 4) Create the package in your package source location, using your naming convention… say anywhere under 50, you can probably just use “auto apply drivers” in your task sequence 7b) if you have a large number of makes and models or you run into conflicts, you can apply the driver package based on category or apply a specific package For places that do have large numbers of makes and models – the most important thing is to avoid driver bloat – it will make your driver database difficult to manage….