This may be a stupid question but I am trying to determine how to test WMI Queries in SCCM. Example: I want to target Driver Packages for Make/Model in OSD Task Sequences I read several forums on how to set them in a TS but I would like to confirm the query is correct by pulling results from the SCCM DB if that is possible. Perhaps I need to run it on the machines themselves in WBEMTEST.exe   Could anyone point me in the right direction on how to accomplish? I greatly appreci

Here's what I have in place currently. Dedicated WSUS server that only downloads updates for servers. AD Groups labeled "SRVGRP1-8" which are tied to Group Policies for each that determine when or if the machines are rebooted automatically. Maintenance windows seem to be a confusing issue and I know that "Server Groups" which was released as a pre-release feature in 1606 was supposed to help with that but I'd rather not tie myself to a pre-release feature. I'm on 1610 and wary of upgra

hello! On some machines I'm having problems with the installation of 2017-05 Cumulative Update for Windows 10 Version 1607 for x86-based Systems (KB4019472)  and Cumulative Update for Windows 10 Version 1511 for x64-based Systems (KB4019473) error descriptio in the colsole is "access denied" and the UpdatesHandler.log says WSUS update (970dc0b3-07a2-4434-8df0-9008dcdc9f36) installation result = 0x80070005, Reboot State = NoReboot Update execution failed. maybe this is

Running 1610, I stumbled across something yesterday, and I'm wondering if anyone else has seen this: changing just the name of a query used to populate a collection breaks the collection. Steps to replicate: Change the name of the query being used as a membership rule for a collection. Collection's icon gets an hourglass, even though nothing about its membership actually changed. Hourglass doesn't go away, and collection membership no longer updates. The first time

We're running current branch SCCM and I've pulled a few Windows 7 machines as a test lab to be upgraded to Windows 10. I've run through all the steps in the guide and set up the Upgrade Task Sequence. The upgrade shows up as available on the lab machines and I can begin the upgrade install, however the upgrade fails with error 0xC1900208 which indicates an incompatible app is blocking the upgrade. I have about 100 of these machines that need to be upgraded and I need to be able to identify

Hi all,   I am having an issue with clients contacting the SCCM SUP. This is a fresh install of SCCM 1702 on a server 2012 R2 and Windows 10 environment. All is working as expected, except even the Software Update Point. WSUS is on its own Server and SCCM talks to it and pulls in all the updates. I can create SU groups and used scheduled updates to inject the patches into my wim. BUT clients are not talking to SCCM SUP, all the updates have "0" required\installed against them. The

Hey guys   Got a new machine, to image. Imported all the drivers as usual, and the network driver was already in the boot image from an earlier model that uses the exacy same network driver. ( already double checked this to ) Turned off secure boot in the Bios, and attempted to pxe boot into the Task Sequence window. The machine reboots right before it manages to bring up the task sequence window. Looking at the smsts.log it display the error in the subject of this post Did a

Hi everyone, I wonder if someone could help me. In my corporate environment, we have collections setup for deployments that our Service Desk use to build machines. The idea is that machines are created or added into that Collection, and the Task Sequence is also deployed to the Collection. We have upgraded to SCCM 1702 in recent times and ntoiced that we cannot always import machines to the collection - we get an error code, like 2152205056. I just looked at:  So will