The detection and remediation scripts are the same, the script is smart enough to detect if it is running in detection or remediation mode. The only difference with LAPS config is that the script should run in user context:
To use it, follow the steps in my previous article using proactive remediations (LAPS). You can find the Proactive Remediation script on Gitlab: This can be adjusted to your local needs easily. When Paused or Disabled are detected, there is no remediation as this is not technically an error but something the user manually set.
However, there is no remediation option, so I am sharing a framework based on previous work in Proactive Remediations that can report on the Onedrive client status and trigger a remediation, which looks like this:Ĭurrently, the only remediation method is to restart the Onedrive client, but the script is easily adjusted for additional remediation actions or conditions the community deems useful. With the introduction of Onedrive Sync Heath in the Office portal, we have a much improved view on sync errors of our users. If you have been installing the new OneDrive Sync Client with the /AllUsers switch AFTER the user has logged in, perhaps with a user targeted deployment from SCCM, the HKEYUSERSDefaultHiveSoftwareMicrosoftWindowsCurrentVersionRun /v OneDriveSetup key would have already initiated the binaries to be installed in the users.
0 kommentar(er)
