Skip to main content

Using TAB Completion with CIM Commands

One of the items that my PowerShell class this past week has noticed is that there is some TAB completion capability with Get-CIMInstance.  This is true for both the –NameSpace and –ClassName parameters. To use the TAB completion, just press space after the parameter and press TAB.  The list of Class Libraries are not loaded by default.  This means that the Shell/ISE may pause for loading when it comes to big namespaces like the default Root\CIMv2.  This pause will only be for the first usage in the current namespace.
Notice the ISE is loading after I pressed TAB.









To get a list of CIM cmdlets that support some type of TAB completion:
Function Find-TabCompletion
{
PAram ($String)

    # Set up the search string.
    $S = "*"+"$String"+"*"

    Get-Command -noun "$S" |
        Select-Object -ExpandProperty Name |
        ForEach-Object {
            $Obj = New-Object -TypeName psobject -Property @{
            Cmdlet = $Null
            Parameters = $Null
              }
            $String = $Null
            $Data = (Get-Help -Name $_ -Full).Parameters
            ForEach ($D in $Data.parameter)
            {
                If ($D.Description -match "You can use tab completion to browse")
                {
                    $String = $String + ", " + "$($D.Name)"
                }
            }
           
            # Write to the pipeline only if one of the
            # commands parameters has TAB completion in
            # its description.
            If ($String -ne $Null)
            {
                $Obj.Cmdlet = $_
                $Obj.Parameters = $String.Remove(0,1).Trim()
      
                Write-Output $Obj
            }
        }
}

Here is what it the output looks like when you look for TAB completion being listed in the CIM cmdlets’ help files:
Find-TabCompletion -String "CIM"

Cmdlet                    Parameters         
------                    ----------         
Get-CimAssociatedInstance Namespace          
Get-CimClass              ClassName, Namespace
Get-CimInstance           ClassName, Namespace
Invoke-CimMethod          ClassName, Namespace
New-CimInstance           ClassName, Namespace
Register-CimIndication... ClassName, Namespace
Remove-CimInstance        Namespace          
Set-CimInstance           Namespace          




You will get nothing for WMI. This is just another good reason to switch to the CIM cmdlets.





Comments

Popular posts from this blog

Sticky Key problem between Windows Server 2012 and LogMeIn

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 .

Where did a User’s Account Get Locked Out?

Updated: May 15, 2015 When this article was originally published, two extra carriage returns were add causing the code to malfunction.  The code below is correct.   My client for this week’s PowerShell class had a really interesting question. They needed to know where an account is being locked out at. OK, interesting. Apparently users hop around clients and forget to log off, leading to eventual lock out of their accounts. The accounts can be unlocked, but are then relocked after Active Directory replication. This problem is solved in two parts. The first one is to modify the event auditing on the network. The second part is resolved with PowerShell. The first part involves creating a group policy that will encompass your Domain Controllers. In this GPO, make these changes. Expand Computer Configuration \ Policies \ Windows Settings \ Security Settings \ Advanced Audit Policy Configuration \ Audit Policies \ Account Management Double click User Account Management C...

How to run GPResult on a remote client with PowerShell

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.