Skip to main content

Send code to machines based on their OU and Model number with PowerShell

By

This was the final project of my March PowerShell class in Portland Maine.  This is the “Real World” task that the class brought in.  They needed to be able to specify OU in which code would be sent to each client based on the model number of that client.  Below is the code.

 

To run it, dot source it into your PowerShell session and to a Get-Help Send-Code –Full command to learn how to use it.  I left a final challenge in the NOTES filed for the class.




Function Get-ComputerList
{
    Param
    (
        [Parameter(Mandatory=$True)]$OUName
    )
    
    # Get the target OU Object from AD.
    $OUName = "*" + $OUName + "*"
    $TargetOU = Get-ADObject -filter 'Name -like $OUName'
    
    # Build a list of clients to target.
    $TargetObject = @()
    
    $Computers = Get-ADComputer -filter * -SearchBase $TargetOU
    
    ForEach ($Computer in $Computers)
    {
        $Obj = New-Object PSObject
        $Obj | Add-Member NoteProperty -Name "ComputerName" -Value $Computer.Name
        
        $TargetObject += $Obj
    
    } # End: ForEach ($Computer in $Computers)
    
    Write-Output $TargetObject
}


Function Get-WMIInfo
{
    Param
    (
        $ComputerList
    
    )
    
    $Object = @()
    
    ForEach ($Computer in $ComputerList)
    {
        Write-Host "Attempting to connect to "$Computer.ComputerName -ForegroundColor Green
        # Test to make sure the computer is online.
         
        If (Test-Connection $Computer.ComputerName -Count 1 -ea "SilentlyContinue")
        {
            Write-Host "Collection Data" `
            -ForegroundColor Cyan
            $Obj = New-Object PSObject
            $obj | Add-Member NoteProperty -Name "ComputerName" -Value $Computer.ComputerName
            $obj | Add-Member NoteProperty -Name "Model" -Value (Get-WmiObject Win32_ComputerSystem -ComputerName $Computer.ComputerName).Model
            $Object += $Obj
            
        }
        
        Else
        {
            Write-Host "$Computer.ComputerName is Offline" -ForegroundColor White -BackgroundColor Red
        } 
    } # End: ForEach ($Computer in $ComputerList)

    Write-Output $Object
} # End: Function Get-WMIInfo


Function Invoke-ScriptCommands
{
    param
    (
        $ComputerInfo
    )
    
    # List the block of codes that you wish to execute here.
    # Be sure to label the variables something that will help
    # you associate the code with the model number.
    
    $VM = {
            $Services = Get-Service
            ForEach ($Service in $Services)
            {
                Write-host $Service.name "    " $Service.Status
            
            
            }
           } # End: $VM ScriptBlock
            
            
    # Here is where you execute the code against multiple computers.
    ForEach ($Computer in $ComputerInfo)
    {
        Write-Host "Sending code to " $Computer.ComputerName $Computer.Model

        Switch ($Computer.Model)
        {
            "Virtual Machine" {Invoke-Command -ComputerName $Computer.ComputerName -ScriptBlock $VM}
        
        
        } # End: Switch ($ComputerInfo.Model)    
    } # End: ForEach ($Computer in $ComputerInfo)
} # End:Function Invoke-ScriptCommands



<#
.SYNOPSIS
Sends code to machine base on their OU and model number.

.DESCRIPTION
Sends different code to client in an Organizational Unit.  The code sent is based on
the model number of the client.

.PARAMETER OU
The display name of the Organizational Unit that contains the clients that you want to send code to.

.EXAMPLE
Send-Code clients

Extracts the clients in the organizational unit "clients".  If code is present for th
model of client, then that code is send and executed.

.NOTES
I left a challenge for you guys.  In a large OU, a client may go offline before the code is sent.
See if you can modify this code so that it executes against each client as they are
found to be online.
#>

Function Send-Code
{
Param ([Parameter(Position=0,Mandatory=$True)]$OU)

# Import the Active Directory module.
Import-Module ActiveDirectory

# Get a list of computer names from a specific OU.   
# Store an object that in $ComputerList that contains the client name.
$ComputerList = Get-ComputerList $OU

# Get the WMI information and store it in an object with the client name.
# Save this object in $ComputerInfo.
$ComputerInfo = Get-WMIInfo $ComputerList

# Code to send to clients of different model numbers.
Invoke-ScriptCommands $ComputerInfo

} # End: Function Send-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

Where did a User’s Account Get Locked Out?

By
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...
18 comments
Read more

Backup and Restore AD LDS with DSDBUTIL.exe

By
Active Directory Lightweight Directory Services allow you to create a directory service that allows applications to have access to user accounts, groups, and authentication similar to Active Directory Domain Services.  The big advantage here is that the schema of the directory service will not be bound by the rules of an Active Directory database.  Exchange 2007/2010, for example, use an instance of AD LDS on the Edge Transport Server to provide for user authentication from the internet.  Because your Active Directory database is not exposed to the internet, this is more secure. Applications will handle most of the dirty work should they require AD LDS.  You may want to make sure the database is being backed up and also have a restore plan in place.  Should the database become corrupt, the application that uses that database will fail.  This document will walk you through backing up and restoring an instance of AD LDS using the dsdbutil.exe command. Fi...
6 comments
Read more