-
Notifications
You must be signed in to change notification settings - Fork 8
Add/Modify LTSC Checks #21
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Note: I developed the following inspec commands to check if a system is LTSC or not, however there is likely a cleaner way. Thoughts?
This seems like the fastest to check
|
Why not just use the os resource
?
…On Mon, Apr 5, 2021, 4:51 PM njohnson11 ***@***.***> wrote:
Note: I developed the following inspec commands to check if a system is
LTSC or not, however there is likely a cleaner way. Thoughts?
is_ltsc = command('gwmi win32_operatingsystem | select
OperatingSystemSKU').stdout.split[-1].strip.to_i >= 123
is_ltsc = command('systeminfo | findstr /B /C:"OS
Name"').stdout.include?("LTS")
is_ltsc = os.name.downcase.include?("lts")
is_ltsc = registry_key('HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows
NT\CurrentVersion')["ProductName"].downcase.include?("lts")
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#21 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AALK42FE3H2H5PK567BYPKLTHIPGDANCNFSM42NNCTVQ>
.
|
That one seemed the cleanest. The first one is a better bet for working against IoT versions but the os name one would likely work as well. |
Uh oh!
There was an error while loading. Please reload this page.
A number of controls whose descriptions mention being NA for LTSC/B systems, are either not checking this or are checking in a way that misses new LTSC versions. The following controls need to be addressed.
The text was updated successfully, but these errors were encountered: