Skip to content
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

Windows 2008 Still not detected correctly #453

Closed
username-is-already-taken2 opened this issue Feb 12, 2016 · 3 comments
Closed

Windows 2008 Still not detected correctly #453

username-is-already-taken2 opened this issue Feb 12, 2016 · 3 comments
Labels
Type: Bug Feature not working as expected
Milestone

Comments

@username-is-already-taken2
Copy link
Contributor

Hi there

Sorry to reopen this issue but I just wanted to confirm the status, for windows 2008 support do I need to install the windows management framework 3+ on my boxes?
My local machine detects fine
PS C:\WINDOWS\system32> inspec version
0.9.11
PS C:\WINDOWS\system32> inspec detect
{"name":null,"family":"windows","release":"10","arch":null}

but when I winrm to 2008 r2 box I get unknown

PS C:\WINDOWS\system32> inspec shell -t winrm://***.***.com --user *** --password *** --ssl --self-signed
Welcome to the interactive InSpec Shell
To find out how to use it, type: help
inspec> help
Available commands:
[resource]` - run resource on target machine` help resources - show all available resources that can be used as commands
help [resource]` - information about a specific resource` exit - exit the InSpec shell
You can use resources in this environment to test the target machine. For example:
command('uname -a').stdout
file('/proc/cpuinfo').content => "value",

You are currently running on:
OS family: unknown
OS release: unknown
inspec>

My server is Windows 2008 R2
C:\Windows\system32>ver
Microsoft Windows [Version 6.1.7601]

@chris-rock
Copy link
Contributor

@username-is-already-taken2 Your are right, this is not yet fix unless you updated the Windows Management Framework on Windows 2008. This is addressed here: inspec/train#70

Even if the detection has been fixed and do not require powershell, the most windows resources will still require an up-to-date WMF, since we rely on Convert-ToJson a lot. command, file and script will still work though.

@chris-rock
Copy link
Contributor

brings up again #346

@chris-rock chris-rock added the Type: Bug Feature not working as expected label Feb 17, 2016
@chris-rock
Copy link
Contributor

This is solved with inspec/train#70 now

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Type: Bug Feature not working as expected
Projects
None yet
Development

No branches or pull requests

2 participants