Skip to main content

How to search the registry in PowerShell

By
Searching the registry in PowerShell for a specific string value is very easy.  Just change the value of $SearchString to reflect the string value you are searching the local registry for.

<#
===========================================================
Script Name: SearchReg.ps1
Author: Jason A. Yoder, MCT
Website: www.MCTExpert.com
Blog: www.MCTExpert.Blogspot.com
===========================================================
===========================================================
Script Purpose:
Searches the local registry for a specified string value.
===========================================================
===========================================================
Requirements:
PowerShell V2
===========================================================
#>
# ===========================================================
# Global Varibles
# == End of Global Variables ================================
#Enter the string value to search for in the variable below.
$SearchString = "Testing"
# ===========================================================
# Functions
# == End of Functions =======================================
# ===========================================================
# Main Code:
# Write a message to the user to let them know the scrip
# has started.
Write-Host "Searching: HKCU" -ForegroundColor White `
-BackgroundColor DarkBlue
# Search the registery for the string value.  Display the
# registry key each time the value is located.
Get-ChildItem HKCU:\ -Recurse -ErrorAction SilentlyContinue |  
       ForEach-Object {  
      if((get-itemproperty -Path $_.PsPath) -match $searchString) 
      {  
         $_.PsPath 
      }  
}
# Write a message to let the user know the script completed.
Write-Host "SearchReg.ps1 has completed." -ForegroundColor Yellow `
-BackgroundColor DarkBlue
# == End of Main Code =======================================
Labels:

Comments

Post a Comment

Popular posts from this blog

Sticky Key problem between Windows Server 2012 and LogMeIn

By
This week I instructed my first class using Windows Server 2012 accessed via LogMeIn and discovered a Sticky Key problem every time you press the Shift key. Here is my solution to resolve this.  First off, in the Preferences of LogMeIn for the connection to the Windows Server, click General . Change the Keyboard and mouse priority to Host side user and click Apply at the bottom. On the Windows 2012 server, open the Control Panel – Ease of Access – Change how your keyboard works . Uncheck Turn on Sticky Keys . Click Set up Sticky Keys . Uncheck Turn on Sticky Keys when SHIFT is pressed five times . Click OK twice. If you are using Windows Server 2012 as a Hyper-V host, you will need to redo the Easy of Use settings on each guest operating system in order to avoid the Sticky Key Problem. Updated Information: March 20, 2013 If you continue to have problems, Uncheck Turn on Filter Keys .
6 comments
Read more

How to list all the AD LDS instances on a server

By
AD LDS allows you to provide directory services to applications that are free of the confines of Active Directory.  To list all the AD LDS instances on a server, follow this procedure: Log into the server in question Open a command prompt. Type dsdbutil and press Enter Type List Instances and press Enter . You will receive a list of the instance name, both the LDAP and SSL port numbers, the location of the database, and its status.
Post a Comment
Read more

How to run GPResult on a remote client with PowerShell

By
In the past, to run the GPResult command, you would need to either physically visit this client, have the user do it, or use and RDP connection.  In all cases, this will disrupt the user.  First, you need PowerShell remoting enabled on the target machine.  You can do this via Group Policy . Open PowerShell and type this command. Invoke-Command –ScriptBlock {GPResult /r} –ComputerName <ComputerName> Replace <ComputerName> with the name of the target.  Remember, the target needs to be online and accessible to you.
Post a Comment
Read more