. Fri, Dec 7 2012. Thu, Nov 8 2012.
I'm trying to get a computer to report into SCCM, I can find it in devices but the client isn't reporting. I uninstalled the client rebooted and tried to reinstall, but get the error CcmSetup failed with error code 0x80070424. Any suggestions? The device is windows 7 64 bit. Microsoft Windows 7Review it: (156). Oct 10, 2016. The System Center Configuration Manager (SCCM) client policy can be used to install System Center Endpoint Protection (SCEP) in supported OSes prior. For which this client policy applies to install the SCEP client (Windows 7/8/8.1 endpoints), or to configure Windows Defender (Windows 10 endpoints).
Unable To Install Sccm 2012 Client On Windows 7
Thu, May 3 2012I’ve used this great tool for some time now in many different environments, and I can’t say how useful it has been in troubleshooting client computers. You can remotely find out the clients cache location, size, and what's in it, and also find out what packages are advertised to a computer and rerun the advertisement if needed. The list goes on of what you can do with this free tool. The latest version released is version 2.0.4 which was released back on 2011-10-06.
SCCM Client CenterAs you can see the tool is broken down into four major group functions Running Executions, Event Monitor, Inventory Agents, Advertisements, and Agent Actions. I’ll break down each of these as we go.
Running ExecutionsThe Running Executions function group is broken down into three sub tabs SMS/SCCM Jobs, Processes, and Services. Once you have connected to an SCCM Client you can use these tabs to display, start, and stop all current running SCCM jobs, running services, or processes.
You can also view all jobs that are in queue and see what might be holding up that job like a file download for example. I know what you’re thinking; well I can do all that with the SCCM Console, and that is true but, the problem is that SCCM won’t put it all together in package like SCCM Client Center does.
SCCM Client Center - Running Executions Event MonitorWhen troubleshooting SCCM clients, it might be necessary to get deep into the weeds. That is what makes having the Event Monitor function group readily accessible in one all encompassing application such huge time saver.
It allows you to access the multiple client logs from one easy to use interface.SCCM Client Center - Event Monitor InventoryWhat SCCM tool would be complete without an effective inventory function, and SCCM Client Center delivers. You can either view an interactive inventory of a client's installed applications by querying its WMI classes, or you can choose to pull that application list from the SCCM database. Since it leverages WMI on the client there is almost nothing that we can’t pull from the client that we might need to troubleshoot or report on. If you are troubleshooting patch compliance issues and believe me you will at some point.
You can use the inventory function to see what patches have been installed or which ones still need to be installed. Plus you can also open up the WindowsUpdate.log file directly from SCCM Client Center saving you time and desktop clutter.SCCM Client Center - Inventory AdvertisementsHere you can view all of the applied advertisement policies and even rerun advertisements on the selected client.
You can also view when a package was last ran and whether or not it ran successfully, and if available you can extract failure codes to help diagnose installation failures. Some SCCM environments can get really complicated as different departments roles and functions vary over time. Thus it becomes of upmost importance that Maintenance Windows are adhered and managed as needed. SCCM Client Center allows you to do that by letting you view all applicable Maintenance Windows. If necessary, you can even delete or create new Maintenance Windows from the Advertisements function group as well.SCCM Client Center - Advertisements Agent ActionsFinally we get to the Agent Actions function group. In my experience most SCCM client issues can be fixed by either reinstalling or repairing the SCCM client, and you can do that right from the SCCM Client Center console.
If that doesn’t do the trick then you might have to repair or recreate the WMI repository. That can also be done from this same function group.SCCM Client Center - Agent Actions Configuration Manager 2012The only down side I can see with SCCM Client Center is the fact that I doesn’t support Configuration Manager 2012. However, Roger has since been spending his time revamping SCCM Client Center to support Configuration Manager 2012.
That new version will be titled Client Center for Configuration Manager12, and the Alpha version was just recently released on Oct. It can be downloaded. Here is a sneak peak of what the new version will look like.
This is the most effective way I've found of clearing up client side issues. If my use it's about 95%. If this doesn't get it something is seriously broke on the system and I generally PXE boot and apply a new image at that point.I'll put my batch file that I use to kick this off in another post, but the way this works is that I copy it over to a local system's temp folder, then I kick it off with PSExec. This ensures it runs local and eliminates a lot of issues caused by remoting.
For example, if you were trying to run remotely with RM or WMI calls, maybe PSEXEC, and you shut down the WMI repository then you gotta go remote into the machine and start it back up before you can move on. Running this locally lets it mess with WMI and disregard if you're remote or not.This script will1) Cleanly uninstall the SCCM client2) Rebuild the repository (yes I know not a best practice, but it beats rebuilding the machine)3) Run WMIRepair (you'll have to get this from Robert Zander's tools, it's not mine to distrubute)4) Reinstall the SCCM client.NOTE.: Windows 7 safe.
In my environment XP still has issues. But only about 2% of our systems are still on XP so I've never worked through those bugs, nor have I added in checking for those systems. NOTE.0.: Search for '.' w/o the quotes.
Those items are unique per environment and have to be configured locally. There are 3 of them.