You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 7, 2024. It is now read-only.
Compliance is working as expected, detects 67 settings aren't compliant, the remediation script runs and echos Remediation in Progress in the WS1 Sensor, however remediation doesn't do anything.
I've logged a call with VMware support but they don't seem familiar with these baselines, wondering if this is a known issue?
Reproduction steps
Create sensors and assign to devices
Expected behavior
Remediation makes devices compliant
Additional context
No response
The text was updated successfully, but these errors were encountered:
Hi Matt, this issue seems to be that once the baseline remediation runs we can no longer elevate/ use sudo (wont accept password / root account . So unable to run the compliance script, I have a feeling one of the settings the baseline applying is locking down root but no luck in finding which one
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Describe the bug
Have followed the documentaiton for macOS Baselines https://github.com/vmware-samples/euc-samples/tree/master/UEM-Samples/Utilities%20and%20Tools/macOS/Baselines
We've generated the NIST 800-53 low
Created all 3 sensors as required.
Compliance is working as expected, detects 67 settings aren't compliant, the remediation script runs and echos Remediation in Progress in the WS1 Sensor, however remediation doesn't do anything.
I've logged a call with VMware support but they don't seem familiar with these baselines, wondering if this is a known issue?
Reproduction steps
Expected behavior
Remediation makes devices compliant
Additional context
No response
The text was updated successfully, but these errors were encountered: