Share via

Repairing broken clients using group policy

My9to5 261 Reputation points
2021-01-13T18:36:26.373+00:00

We some devices that have the client, but it is broken. We are trying to implement an automated solution that fixes broken clients via group policy because of how our environment is currently set up.

  1. We did not extend the AD schema, but if we did, could they possibly fix themselves that way?
  2. I came across an article a while ago that would export a collection to GP and then run the reinstallation from there. Do any of you know where there is a guide to this or something?

Thanks!

Microsoft Configuration Manager
0 comments
Accepted answer
  1. Sherry Kissinger 4,211 Reputation points
    2021-01-13T19:47:51.233+00:00

    Are you open to a GPO Computer Startup Script?

    https://home.memftw.com/configmgr-client-startup-script/

    We ourselves use a variant of a GPO computer startup script. The one at this link is the one I've heard the most about; but others may comment with different ones or newer ones; I haven't been keeping track. But it's certainly a place to start.

    I wonder if someone has a powershell version that I've forgotten about.

    These gpo computer startup scripts have been part of the cm world for years; and a lot of fixes have been added to them over the years, to keep client installs clean and happy.

1 additional answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. AllenLiu-MSFT 43,061 Reputation points Microsoft Vendor
    2021-01-14T06:20:03.097+00:00

    @My9to5
    Thank you for posting in Microsoft Q&A forum.
    You may try to use below PowerShell script that detects and automatically fixes broken SCCM clients, you may test it in your test environment first:
    https://gallery.technet.microsoft.com/ConfigMgr-Client-Health-ccd00bd7

    If the response is helpful, please click "Accept Answer" and upvote it.
    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

    0 comments