Forum Discussion
Thanks for the feedback everyone, I have taken the use cases to Central Development for consideration.
I'm not a PS expert but what about something alond the lines of an if statement to check the version and generate an error if it matches the one you are looking for or if it doesn't match the one your looking for - depending what you're trying to find.
Like I say, no expert but I guess it would go something like this (anyone welcome to change it to actually work and correct my mistakes).
$WinVerCheck = $null; $WinVerCheck = (Get-ItemProperty "HKLM:\SOFTWARE\Microsoft\Windows NT\CurrentVersion").ReleaseId If ($WinVerCheck -eq 1909) { <some command that will not generate an error> } Else { <some command to generate an error> }
some simple ideas for a command to make an error and not - a simple "dir" should give no error and maybe trying to delete a fake file would generate an error. e.g. Remove-Item –path c:\nosuchfolder
After this is done, you could check the results for an overview of which failed and succeeded - which ones matched the if statement or not.
- abbeyainscal5 years agoActive Contributor
I have definitely look into some PS scripts but I guess my point is that this can't be that hard for LMI to add lol! My gosh - it's a field for goodness sake that they do have just not in a report friendly way.
- leecronin5 years agoActive Contributor
For sure, it's something that should be so simple to add. My suggestion is more a workaround than a solution. It would be good to have more response from someone at LMI.
- LMkhobar5 years agoNew Contributor
Is there any progress in this report option. This is something we should have it by now. Appreciate the logme in feedback or any timeline.