Test-Path PowerShell Issue

Question

I am trying to search several servers to see if a specific Registry key exists.

It looks like the code below is working, but as I start to add the final part of the key, it stops "finding" stuff. I can start to add a*, then ab* as the last key, but as soon as I get to the third character or even the full string that I know is there, it comes back False saying it did not find it.

$servers = Get-Content c:\input.txt | `
   Select-Object @{l='ComputerName';e={$_}},@{l='KeyExist';e={Test-Path "HKLM:\System\CurrentControlSet\services\*abcdefg*" }}
$servers | Format-Table -AutoSize

You are not check remote registries. Just you own computer every time. The double *'s are redundant. — Matt
– Matt, Commented Feb 23, 2017 at 16:23
Are you perhaps intending to test the registry path on different computers? Your current command just checks the registry on your local computer, for each server name you pipe in from the file — Mathias R. Jessen
– Mathias R. Jessen, Commented Feb 23, 2017 at 16:23
For remote registry , you should do something like this: $reg = [Microsoft.Win32.RegistryKey]::OpenRemoteBaseKey("LocalMachine", $_.machinename); $key = $reg.OpenSubkey($keyname); $value = $key.GetValue('AutoAdminLogon') — Ranadip Dutta
– Ranadip Dutta, Commented Feb 23, 2017 at 16:29

Mathias R. Jessen · Accepted Answer · 2017-02-23 17:28:05Z

1

Your problem is that you run Test-Path against the local computer for each remote server name. Unfortunately Test-Path doesn't support querying remote registries.

You could use WMI:

$RegProv = [wmiclass]"\\$servername\root\default:StdRegProv"
if($RegProv.EnumKey(2147483650,"System\CurrentControlSet\services").sNames -like 'abc*'){
    # key starting with abc exists
}

Wrap it in your calculated property like this:

@{Name='KeyExists';Expression={[bool](([wmiclass]"\\$_\root\default:StdRegProv").EnumKey(2147483650,"System\CurrentControlSet\services").sNames -like 'abc*')}}

answered Feb 23, 2017 at 17:28

Mathias R. Jessen

178k13 gold badges175 silver badges234 bronze badges

Sign up to request clarification or add additional context in comments.

Comments

Ranadip Dutta · Accepted Answer · 2017-02-23 16:36:23Z

0

You can check the remote registry like this :

So for each server it will get the registry value and it will store the value in the arraylist and will display the final result.

Presently in your code, you are basically checking locally only.

   #####Get Registry Value #### 
$main = "LocalMachine"
$path= "registry key path"
$servers = Get-Content c:\input.txt #-- Get all the servers
$arr=New-Object System.Collections.ArrayList

foreach ($Server in $servers)  
{ 

$reg = [Microsoft.Win32.RegistryKey]::OpenRemoteBaseKey($main, $Server) 
$regKey= $reg.OpenSubKey($path) 
$Value = $regkey.GetValue($key) 
$arr.Add($Value)
}
$arr

Note: Change the placeholders accordingly

answered Feb 23, 2017 at 16:36

Ranadip Dutta

9,5493 gold badges33 silver badges48 bronze badges

4 Comments

Mathias R. Jessen Over a year ago

With this approach you lose the correlation between value and machine name

Ranadip Dutta Over a year ago

Then what should be the best way . Could you please let me know. I do not want to use get-itemproperty or get-itempropertyvalue

Mathias R. Jessen Over a year ago

Instead of using an ArrayList, you should output an object with both properties (using the [pscustomobject] type accelerator, or New-Object psobject), then assign the entire foreach(){} loop to a variable

Ranadip Dutta Over a year ago

Yes, that would be much more better.

Collectives™ on Stack Overflow

Test-Path PowerShell Issue

2 Answers 2

Comments

4 Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

2 Answers 2

Comments

4 Comments

Your Answer

Sign up or log in

Post as a guest

Related