We currently have over 1000 objects in AD which should all have a healthy SCCM client, but due to the PC's not being turned on all the time the client becomes corrupt for some reason.
I beleive the most efficient way to fix those PC's on the network that have SCCM issues is to have a script read from a computers.txt list, which contains all the corrupted computers, and have the script grab that name from the computers.txt list and let the script run a ccmsetup.exe on that remote PC using PSEXEC.
We currently use site code AP0 and have the ccmsetup.exe file.
We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.
Hi everyone,
We currently have over 1000 objects in AD which should all have a healthy SCCM client, but due to the PC's not being turned on all the time the client becomes corrupt for some reason.
I beleive the most efficient way to fix those PC's on the network that have SCCM issues is to have a script read from a computers.txt list, which contains all the corrupted computers, and have the script grab that name from the computers.txt list and let the script run a ccmsetup.exe on that remote PC using PSEXEC.
We currently use site code AP0 and have the ccmsetup.exe file.
ANY SUGGESTIONS WOULD BE GREATLY APPRECIATED.
Share this post
Link to post
Share on other sites