CODEWITHSUNDEEP
powershell
oiad462
oiad462

Reputation: 21

Why will PsExec not execute a .ps1 script remotely?

I am trying to write a script in PowerShell that gathers free space on the C: drive and then appends it to a .csv file on a network drive.

Our company does not have PowerShell enabled by default. Remote PowerShell commands are restricted. Because of this, I have to script things out, then kick them off using PsExec.

I have two scripts for this process. The first one, is the one I run from my machine, this script asks for my credentials and then uses a foreach loop to cycle through a .txt file with IP addresses telling each IP to launch the second script from a network drive. The second script gathers the free space, performs a math function on it, then appends the hostname and free space to a .csv file on the network.

However, the second script never runs. After the connection is established using PsExec, my console just sits there. It should kick off the script and then loop again to the next IP. I have tested the second script manually on some of the target machines with no issues.

Locally executed script:

$username = Read-Host "Username"

$outputPath = "\\network\directory\sub-directory\FileName.csv"
$IPpath = Read-Host "Enter the path for the list of IP addresses"
$IPs = Get-Content -Path $IPpath
Add-Content -Path $outputPath -Value """IP"",""Free Space"""

foreach ($IP in $IPs)
{
    if (Test-Connection -Count 1 -ComputerName $IP -Quiet)
    {
        \\network\directory\subdirectory\psexec.exe -accepteula \\$IP -u domain\$username -h PowerShell -ExecutionPolicy Bypass -Command \\network\directory\sub-directory\diskSpaceCheck.ps1
    }
    else
    {
        Add-Content -Path $outputPath -Value """$IP"",""Offline"""
    }
}

Remotely executed script (diskSpaceCheck.ps1):

$outputPath = "\\network\directory\sub-directory\FreeSpace.csv"
$hostname = hostname

$disk = Get-WmiObject Win32_LogicalDisk -Filter "DeviceID='C:'"
$freeSpace = [System.Math]::Round((($disk.FreeSpace) / 1GB))
Add-Content -Path $outputPath -Value "$($hostname), $($freeSpace)"

I don't think you can have an if statement inside a foreach also but I've tried it without the if test and got the same results. I can't figure out why the remote machine won't execute this script. I have another script that is copied to these machines and then executed in the same manner that works correctly.

Also, the target machines are locked down to limit their use for only specific purposes. These machines use a generic auto logon and generally have access to a few applications. Everything else is inaccessible, including Windows Explorer, Control Panel, etc. I tested this script on some of the machines local to my office, and it worked fine.

I was thinking maybe a networking latency issue? Can that impact PsExec or .ps1 scripts? I can remote onto the machine, log out, log in with my credentials and run the script while PsExec just sits at running the command I gave it.

Any advice would be appreciated.

Upvotes: 2

Views: 10063

Answers (2)

oiad462
oiad462

Reputation: 21

I figured it out. The script was running but it was just sitting there waiting for another command. I added a stop-process command to the script that runs remotely.

Stop-Process -Name powershell

Now it runs, and then exits with error code -1.

Upvotes: 0

Aman Sharma
Aman Sharma

Reputation: 1990

This can occur if you are using PSExec to directly execute the Ps1 file. Instead use PSexec to execute PowerShell.exe and pass your ps1 file as a parameter.

Also check this question: Run PowerShell on remote PC

Upvotes: 1

Related Questions