SCCM 2012 Powershell Scripts

Saturday, October 12, 2019

Powershell Script to append environment variable PATH in windows

Powershell Script to append environment variable PATH in windows

#Requires -RunAsAdministrator
<#
.Synopsis
   Script to append environment variable with new path
.DESCRIPTION
   This script will add a required path to path in windows environment variable
   Requires admin powershell prompt
   This script modifies registery, running without understanding might corrupt your windows installation
.EXAMPLE
   .\script.ps1 -PathToAdd "C:\program files\programname\bin"
#>
param(
[Parameter(Mandatory=$True,ValueFromPipeline=$True)]
[ValidateNotNullOrEmpty()]
[string[]]$PathToAdd
)

process{
    foreach($path in $PathToAdd)
    {
        try
        {
           Write-Warning "Path : $path"
           Test-Path (Resolve-Path $path -ErrorAction Stop) | Out-Null

            $currentPathStrings = (Get-ItemProperty -Path 'Registry::HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Session Manager\Environment' -Name PATH).path.split(';')
            $currentPathStrings = $currentPathStrings | ? {$_.trim()}
            $pathToSave = $currentPathStrings + $path
            $pathStringToWrite = $pathToSave -join ';'
            Write-Warning "Writing below paths"
            Write-Output $pathStringToWrite
            try
            {
                Set-ItemProperty -Path 'Registry::HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Session Manager\Environment' -Name PATH -Value $pathStringToWrite -ErrorAction Stop
            }
            catch
            {
                Write-Warning "Error writing to registry"
                Write-Output $_
            }
        }
        catch
        {
            Write-Warning "Above path you are trying to add could not be resolved, please check if it is a plain path and accessible from file explorer"
        }
    }
}

Wednesday, October 9, 2019

Issue: Angular: Datatable data disappears from table on clicking sort or on search

Problem: Upon loading data from http call to a datatable, it disappers on clicking the table header or searching

Possible cause: Data table caches the data as null even before http call occurs and it is not aware that new data has been updated

Solution: Declare a boolean variable in the class as DataLoaded = false and reassign the variable to true inside the http subscribe block.

inside the <TABLE> directive use *ngIf = "DataLoaded" as <TABLE *ngIf = "DataLoaded">

This will ensure that data table initializes only after the data is loaded.

Sunday, January 6, 2019

Powershell script to perform OCR on images present in a folder

This powershell script can perform OCR via tesseract OCR and convert them to text files default supported language is Kannada by script, but you can change it to required language.

Script asks you to choose your source folder and also the output folder to save converted files to.

Requirements to run this script: Tesseract OCR for windows software.
Running powershell script should be enabled by running set-executionpolicy unrestricted in powershell.

Save the below script with convert-ImagestoText.ps1 or any name with .ps1 extension and run it after setting the execution policy.

To run the script, you can right click on it and select run with powershell or run it from the powershell console by typing .\filename.ps1

Please contact me if you need any help related to this

Important note: Please make sure that there is no space in any foldername while providing input and output folders, or else script might fail(I faced this issue today 7/1/2018).

param($SourceFolderPath,$OutputFolderPath,$LanguageCode = "kan")

Function Get-Folder($rootFolder,$DialogBoxTitleMessage)

{

    [System.Reflection.Assembly]::LoadWithPartialName("System.windows.forms") | Out-Null

    $foldername = New-Object System.Windows.Forms.FolderBrowserDialog

    $foldername.Description = $DialogBoxTitleMessage

    $foldername.SelectedPath = $rootFolder

    if($foldername.ShowDialog() -eq "OK")

    {

        $folder += $foldername.SelectedPath

    }

    return $folder

}

if(!($SourceFolderPath -and $OutputFolderPath))

{

    $rootFolderForSelector = "$env:userprofile\desktop"

    $SourceFolderPath = Get-Folder -rootFolder $rootFolderForSelector -DialogBoxTitleMessage "Please select Source folder with images"

    $OutputFolderPath = Get-Folder -rootFolder $rootFolderForSelector -DialogBoxTitleMessage "Please select folder to save the converted files"

}

if($SourceFolderPath -and $OutputFolderPath)

{

    $filterFiles = "*.jp*g","*.png","*.bmp"

    foreach($filterString in $filterFiles)

    {

        Write-Information -MessageData "Getting files of type $filterString" -InformationAction Continue

        $inputFiles += Get-ChildItem $SourceFolderPath -Filter $filterstring

    }

    $totalFiles = $inputfiles.Count

    $count = 0;

    $inputFiles | ForEach-Object{

        $inputFileFullName = $_.FullName

        $outputfileName = Join-Path $OutputFolderPath "$($_.BaseName)"

        try {

            #Write-Information -MessageData "Converting file $inputFileFullName" -InformationAction Continue

            $count++

            $perc = (100*$count)/$totalfiles

            Write-Progress -Activity "OCR conversion" -PercentComplete $perc -Status "$perc %" -currentoperation "Converting $inputfilefullname"

            start-process tesseract.exe -argumentlist  $inputFileFullName,$outputfileName,"-l",$LanguageCode -nonewwindow -wait

        }

        catch {

            Write-Warning "Error while converting $inputFileFullName"

            Write-Warning $_

        }

    } 

}

Screenshots:

Running via commandline with source folder and destination folder as input 

Running without inputs, choosing folders via windows prompt 

Tesseract OCR project page for more options and information:
https://github.com/tesseract-ocr/tesseract

Thursday, January 3, 2019

How to convert djvu to text

I had some djvu documents which had actual text in them, I was able to open them in djvu viewer and select the text and paste them into text files. I wanted to find an easy way to convert all the files into text documents, I had more than 50 files to convert each of them having pages over 500.

I found a commandline tool which can convert/extract the hidden text from djvu files and wrote a powershell script to pass the directories and convert the files.

Please note that if the djvu file does not contain any text this method might not be useful. To confirm that your djvu file has extractable text do the following.

Open djvu file in djvu viewer, click on edit->Select, select the area containing text and copy and paste it into a notepad file, if you see the text pasted, this tutorial should be helpful.

Software Requirements
1. djvulibre package
2. Windows powershell

You need to use the djvutxt.exe tool from djvulibre package in order to extract text from djvu documents.

You can download and install it from following link: http://djvu.sourceforge.net/ select windows download link.
Once the setup file is downloaded double click and install it.

Once you complete the installation add the installation directory to environment variable path.
refer this link for steps

Open windows powershell by searching it in windows search.

Run the following command to check the execution policy(powershell execution policy should be set to allow running scripts on your computer)
Get-ExecutionPolicy
if you get the result as unrestricted then you can continue.
If your policy is restricted, you can execute the following command to enable it
Set-ExecutionPolicy -ExecutionPolicy Unrestricted
(Once you complete the task you can set it to the one whichever was the output of get-executionpolicy command above)

Save the below code in required directory with .ps1 extension, that is when you save the file name it something like DJVU-BulkConvertor.ps1

ps1 is the powershell script extension, in simple terms if you are unfamiliar with powershell, powershell is a new technology implemented by Microsoft which supports scripting and commandline shell similar to DOS but in the back-end it is built with lot of features and strong design which has changed the way system admins used to work on windows.

You need to change the directory paths to your input directory path in below script, first two lines.

The folder structure is like below
FolderName3 -> contains multiple folders, inside each folder I have only djvu files no further directories.
Output will be written to C:\FolderName1\FolderName2 creating folders which were inside foldername3
that is
C:\FolderName1\FolderName2\MyOutput and so on

$source = "C:\FolderName1\FolderName2\FolderName3"

$OutputFolderName = "MyOutput"

$outputDir = Split-Path -Parent $source | ForEach-Object{Join-Path $_ $OutputFolderName}

$directories = Get-ChildItem -Path $source -Directory

foreach($inputDirectory in $directories)

{

    $djvuFiles = Get-ChildItem $inputDirectory.FullName -Filter *.djv*

    $outputPath = join-path $outputDir $inputDirectory.Name

    if(-not(Test-path $outputPath))

    {

        New-Item $outputPath -ItemType Directory

    }

    $djvuFiles | ForEach-Object{

        $inputFileFullName = $_.FullName

        $outputfileName = Join-Path $outputPath "$($_.BaseName).txt"

        try {

            Write-Information -MessageData "Converting file $inputFileFullName" -InformationAction Continue

            djvutxt.exe $inputFileFullName $outputfileName

        }

        catch {

            Write-Warning "Error while converting $inputFileFullName"

            Write-Warning $_

        }

    } 

}

Please feel free to reach me if you have any questions on my email. 

You may need to take help from OCR if you have image files saved in djvu, tesseractOCR can be used via commandline for the same purpose.

Saturday, March 19, 2016

Run powershell on remote machine without enabling powershell remoting !

Here is a tricky way to execute powershell code on remote machine without actually enabling powershell remoting. Enabling powershell remote lets you run powershell commands on a remote machine and get the output on to your computer.

You can either use the -ComputerName parameter available in a command or use the Invoke-Command using the -Computer parameter, or create a psremoting session and run the Invoke-Command on the session.

If PSRemoting is not enabled on your environment you do not have any way to run powershell script on a remote machine.

I was creating a remote software installation tool using powershell which wraps the PsExec tool and lets you install a software on remote machine if you know the silent installation commandlines. With a slight modification same tool can be used for running a script on the remote machine and get the outputs.

PSExec redirects the output onto your screen but if you create an output file on the remote machine you need to figure a way to get it copied onto your local machine from the remote machine, or create a share in your localmachine/server to which you can save the output from the remote machine.

Script uses the cmdkey to cache the credentials and maps the remote machine C drive to copy the setup files.

Creates a folder in C drive on the remote machine, copies the ps1 file you want to run along with a batch file which triggers the powershell script.

Once the script execution is completed on the remote machine, mapped network drive and cached credentials will be deleted.

GUI creation credit to following blog.
Download psexec and save it in the same folder where you have the main script.

The below script can be run using the remote machine name and the ps file source folder name.

Here is how your script folder should look like.

Before running the script, want to show that the remote machine has a restricted powershell execution policy and PSremoting is not enabled(Screenshot1).

Below script would be run on this machine from a different machine.

$process = Get-Process

$process

Write-Host "Also writing output to file on remote machine check C:\temp\lanabhat.txt"

$process | Out-File C:\temp\Lanabhat.txt

How to run the script.

Commandline entered in the installCommand.bat file
powershell -ExecutionPolicy ByPass C:\Software_Install\test-remoteShare.ps1

Running the powershell script.
.\Run-PowershellRemote.ps1 -MachineName PC0001 -installSourceFiles C:\Users\lanabhat\Desktop\Remote-Powershell\test-powershellscript

Credentials to connect to the remote machine, username would default to COMPUTARENAME\Administrator , if you have a service account or a domain admin account, you can modify the code and replace it to default to that value.

Remote machine C drive is mapped to P drive a folder is created to batch file and powershell script is copied to that folder and batch file is executed with system account.

Credential will be cached to connect to run psexec on remote machine. It will be removed at the end.

Output of the script is shown in your machine but the script is running on the remote machine.

Once the execution is completed press enter to do clean-up. Files copied to remote machine will be deleted and shared folder will be unmapped.

Here is the result from the remote machine.

And finally here is the script.

Please share your feedback and send me a message if you find it useful !

<#
.Synopsis
   Run powershell script on remote machine using psexec
.DESCRIPTION
   Copies the setup files specified in the source.
   This script runs the commandline from the installCommand.bat file on remote machine.
   Copies the setup files to remote machine
   Executes the installation.
.EXAMPLE
   .\Run-PowershellScript.ps1 -MachineName "hostname1" -installSourceFiles \\sharename\foldername -Verbose
.EXAMPLE
   .\Run-PowershellScript -MachineName "hostname2" -installSourceFiles \\sharename\foldername -Verbose

#>

[CmdletBinding()]

Param

(

#Machine Name

[Parameter(Mandatory=$true,

ValueFromPipelineByPropertyName=$true,

Position=0)]

$MachineName,

#Shared folder location of setup.

[Parameter(Mandatory=$true,

ValueFromPipelineByPropertyName=$true,

Position=1)]

$installSourceFiles

)

#region functions

Function Get-RandomDriveLetter

{

$drive=ls function:[d-z]: -n|?{!(test-path $_)}|random

$dl=($drive.ToString()).Replace(":","")

$dl

}

Function map-Drive($driveLetter,$networkDrive,$creds)

{

$errorFlag = $false

$net = new-object -ComObject WScript.Network

Write-Verbose "Drive letter $driveLetter"

Write-Verbose "Network share $networkDrive"

$user_cred = $creds #Get-Credential -Message "Enter the admin cred to map C: drive" $userID

if($user_cred -eq $null)

{

"Credentials were not entered, cannot proceed"

return 0

}

$networkCred = $user_cred.GetNetworkCredential()

$password=$networkCred.Password

$userID=$networkCred.Domain + "\" + $networkCred.UserName

$driveLetter += ":"

try

{

$net.MapNetworkDrive($driveLetter,$networkDrive,$false,$userID,$password)

}

catch

{

$errorFlag = $true

$ErrorMessage = $_.Exception.Message

if($ErrorMessage -match "The specified network password is not correct")

{

Write-Host "Invalid credentials" -ForegroundColor Yellow

}

else

{

Write-Host "Invalid credentials" -ForegroundColor Yellow

}

exit 0

}

#Unmap the network drive

Function Unmap-NetworkDrive($driveLet)

{

Remove-PSDrive -Name $driveLet

}

function Cache-Creds($hostname,$username,$password)

{

cmdkey.exe /add:$hostname /user:$userName /pass:$password

}

function Remove-CacheCred($hostname)

{

cmdkey.exe /delete:$hostname

}

#endregion functions

$localSetup = "Software_Install" #Local folder which will be created on C drive on user machine

$batchFile = "$($Script:PSScriptRoot)\installCommand.bat" #Command file which will be copied to user machine

$remoteBatchPath = "C:\$($localSetup)\installCommand.bat"

#create a batch file as per the script argument

Write-Verbose "Commandline used is: $commandLine"

$hostname = $MachineName

$userName = "$($hostname)\administrator"

$credential=Get-Credential $userName -Message "Please center the password to access the remote machine"

$password = $credential.GetNetworkCredential().Password;

#Create a cached credentials for psexec connection

Cache-Creds $hostname $username $password

$remMachinedriveLetter = Get-RandomDriveLetter

$sharePath = "\\$($hostname)\C$"

#Map the remote machine C drive

map-Drive $remMachinedriveLetter $sharePath $credential

#Created SCCM_Install folder on c drive, if it does not exists

if(!(Test-Path "$($remMachinedriveLetter):\$localSetup"))

{

Write-Verbose "Directory not found on remote server, creating the directory: $($remMachinedriveLetter):\$localSetup"

New-Item -path "$($remMachinedriveLetter):\$localSetup" -ItemType Directory

}

#Copy setup files to remote machine

Write-Verbose "Copying setup files from $installSourceFiles"

Copy-Item "$($installSourceFiles)\*" "$($remMachinedriveLetter):\$localSetup\" -Recurse -Verbose -Force -Container

Write-Verbose "Copying batchfile : $batchFile"

Copy-Item $batchFile "$($remMachinedriveLetter):\$localSetup\" -Verbose

#run psexec and launch install

Write-Verbose "Running PSEXEC to trigger the batch"

& .\psexec.exe \\$hostname -h -s $remoteBatchPath

Write-Host "Exitcode:" -ForegroundColor Yellow

$LASTEXITCODE

#Unmap network drive, cleanup

Write-Verbose "Removing Cached Creds"

Remove-CacheCred $hostname

Read-Host "Press enter to do cleanup"

Write-Verbose "Deleting installation files"

Remove-Item "$($remMachinedriveLetter):\$localSetup" -Recurse -Verbose

Write-Verbose "Removing network drive"

Unmap-NetworkDrive -driveLet $remMachinedriveLetter

Coming next -

Remote software installer, merging the power of powershell and psexec....

Friday, March 18, 2016

SCCM Client DP-MP-SUP Port Query tool

A script which can help you to determine if the client machine is able to established connection to DP, MP and SUP on required ports.

A UI will be presented to user to select the site and do the port query.

Change the variable $regionsComboData and add your site names the format should be Sitename-SiteCode , as it is used later in the script .

This script uses the portquery utility to do the port query. It needs to be downloaded and kept in the same folder as the script.

https://www.microsoft.com/en-us/download/details.aspx?id=17148

Place the script inside a folder named logic, script will create the folder named Result and generate the csv file with port query results. Also it consolidate the log created by portqry tool and generate a single log file inside results folder.

Verbose output will be shown in Powershell console.

Screenshot of the UI.

To generate the CSV file which has the server details stored use the second script which is available at the end of this post, this csv file also should be placed along with the script.

#Write-Host "Setting variables" -ForegroundColor Yellow

$regionsComboData = "Site1-SI1","Site2-SI2", "Site3-SI3", "Site4-SI4"

$scriptFolder = split-path -parent $MyInvocation.MyCommand.Definition

#Write-Verbose "Script path: $scriptFolder"

$substringlen = $scriptFolder.LastIndexOf("\")

$resultFolder = "$($scriptFolder.Substring(0,$substringlen))\Result"

$consolidatedLog = "$($resultFolder)\PortQueryLog.log"

$portStatusFile = "$($resultFolder)\PortStatus.csv"

$ServerDetailsFile = "$($scriptFolder)\ServerDetails.csv"

#Write-Verbose "Log file: $consolidatedLog"

#Write-Verbose "Results file: $portStatusFile"

#Write-Verbose "Server Details file: $ServerDetailsFile"

#Write-Host " "

#region GUICode

#ERASE ALL THIS AND PUT XAML BELOW between the @" "@

$inputXML = @"

<Window x:Class="WpfApplication2.MainWindow"

xmlns="http://schemas.microsoft.com/winfx/2006/xaml/presentation"

xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml"

xmlns:d="http://schemas.microsoft.com/expression/blend/2008"

xmlns:mc="http://schemas.openxmlformats.org/markup-compatibility/2006"

xmlns:local="clr-namespace:WpfApplication2"

mc:Ignorable="d"

Title="PortChecker for SCCM Client" Height="386.386" Width="550.99">

<Grid>

<Grid.ColumnDefinitions>

</Grid.ColumnDefinitions>

<ListView.View>

</GridView>

</ListView.View>

</ListView>

</Grid>

</Window>

#Checkbox GUI code

$inputXML = $inputXML -replace 'mc:Ignorable="d"','' -replace "x:N",'N' -replace '^<Win.*', '<Window'

[void][System.Reflection.Assembly]::LoadWithPartialName('presentationframework')

[xml]$XAML = $inputXML

#Read XAML

$reader=(New-Object System.Xml.XmlNodeReader $xaml)

try{$Form=[Windows.Markup.XamlReader]::Load( $reader )}

catch{Write-Host "Unable to load Windows.Markup.XamlReader. Double-check syntax and ensure .net is installed."}

#===========================================================================

# Load XAML Objects In PowerShell

#===========================================================================

$xaml.SelectNodes("//*[@Name]") | %{Set-Variable -Name "WPF$($_.Name)" -Value $Form.FindName($_.Name)}

Function Get-FormVariables{

if ($global:ReadmeDisplay -ne $true){Write-host "If you need to reference this display again, run Get-FormVariables" -ForegroundColor Yellow;$global:ReadmeDisplay=$true}

write-host "Found the following interactable elements from our form" -ForegroundColor Cyan

get-variable WPF*

}

function Write-MessageToGUI($message)

{

$WPFmsgToUser.Text = $message

}

Get-FormVariables

#===========================================================================

# Actually make the objects work

#===========================================================================

#Sample entry of how to add data to a field

#$vmpicklistView.items.Add([pscustomobject]@{'VMName'=($_).Name;Status=$_.Status;Other="Yes"})

#===========================================================================

# Shows the form

#===========================================================================

#write-host "To show the form, run the following" -ForegroundColor Cyan

#$WPFFind.Add_Click({$WPFResult.Text = Get-BoundaryDetails $WPFHostName.Text})

#endregion GUI Code

Function initialize-Settings

{

if(!(Test-Path $resultFolder))

{

Write-Host "Result folder not found, creating the folder" -ForegroundColor Yellow

mkdir $resultFolder

}

if(!(Test-Path $ServerDetailsFile))

{

Write-Host "Unable to find the csv file with server details @ $ServerDetailsFile" -ForegroundColor Yellow

Exit 0

}

Write-Host "Checking if portqry tool is present in the directory" -ForegroundColor Yellow

if(!(Test-Path "$($scriptFolder)\PortQry.exe"))

{

#Get-ChildItem .\

Write-Host "Portquery.exe is not found, aborting" -ForegroundColor Yellow

Exit 0

}

Function Get-PortStatus($serverNameIP,$PortNo,$prtcl)

{

<#$serverNameIP = "C105JWWCMNSDP"

$prtcl = "TCP"

$portNo = 80

Write-Host "Querying....... Server: $serverNameIP, PortNo: $portNo , Protocol: $prtcl" -ForegroundColor Yellow

#Read-Host "test"

$logFile = "$($scriptFolder)\$($serverNameIP)_$($prtcl)_$($portNo)_portRes.log"

& $scriptFolder\PortQry.exe -n $serverNameIP -p $prtcl -e $portNo -l $logFile -q

Write-Host "Writing data to consolidated log file" -ForegroundColor Yellow

Get-Content $logFile | Out-File $consolidatedLog -Append -Encoding ascii

Write-Host "Removing log created by proqry tool $logFile" -ForegroundColor Yellow

Remove-Item $logFile

$portStatus = "UNKNOWN"

#Write-Verbose "Exitcode $LASTEXITCODE"

switch ($LASTEXITCODE)

{

0 {$portStatus = "OPEN"}

1 {$portStatus = "CLOSED"}

2 {$portStatus = "FILTERED"}

Default{$portStatus = "UNKNOWN" }

}

$portStatusObj = New-Object -TypeName psobject

Add-Member -InputObject $portStatusObj -MemberType NoteProperty -Name "ServerName" -Value $serverNameIP

Add-Member -InputObject $portStatusObj -MemberType NoteProperty -Name "Port" -Value $portNo

Add-Member -InputObject $portStatusObj -MemberType NoteProperty -Name "Protocol" -Value $prtcl

Add-Member -InputObject $portStatusObj -MemberType NoteProperty -Name "Status" -Value $portStatus

#Write-Verbose "Returning result"

Return $portStatusObj

}

#region portprofiles

$portProfiles = @()

#DP