Skip to content

Latest commit

 

History

History
78 lines (59 loc) · 7.46 KB

Powershell.md

File metadata and controls

78 lines (59 loc) · 7.46 KB

Powershell Notes

Table of Contents

  1. Error handling in Powershell
  2. Run as system
    1. PsExec - Does not always work in Sandbox
    2. Sudo for windows
  3. Powershell modules

Error handling in Powershell

This gets the type of the exception from the first error in the error list. The output is the full name of the exception type, that can be used to catch the exception in the square brackets of the catch block.

$Error[0].Exception.GetType().FullName

The most useful properties are:

  • $_.Exception.Message: The error message text.
  • $_.Exception.ItemName: The input that caused the error.
  • $_.Exception.PSMessageDetails: Additional info about the error.
  • $_.CategoryInfo: The category of the error, such as InvalidArgument.
  • $_.FullyQualifiedErrorId: The full ID of the error, such as NativeCommandError.
  • $_.Exception.GetType().FullName – Gets you the full name of the exception

Run as system

Sometimes you need to run a script as system to test. This is usually to test a script that will be run as a scheduled task, or a script for Intune. To do this, you can use the following command:

PsExec - Does not always work in Sandbox

Invoke-WebRequest -Uri 'https://live.sysinternals.com/PsExec64.exe'-OutFile $env:TEMP\PsExec64.exe
Start-Process $env:TEMP\PsExec64.exe '-i -s C:\WINDOWS\system32\WindowsPowerShell\v1.0\powershell.exe'
Start-Sleep -Seconds 5
# After you are done with the script, remove the PsExec64.exe file
Remove-Item $env:TEMP\PsExec64.exe

Sudo for windows

This is a bit hacky, but you can use gsudo to run a script as system.
If using for testing an application to deploy as system via intune, remember to install Visual C++ Redistributable and use SandboxTest.ps1 to launch the sandbox with.

# Download gsudo for windows
winget install gsudo --accept-source-agreements --accept-package-agreements
Update-EnvironmentVariables

# Run the script as system
sudo -s 'C:\WINDOWS\system32\WindowsPowerShell\v1.0\powershell.exe'

Bit hacky, but meh.

Powershell modules

Module name Description Commands
ExchangeOnlineManagement Connect to Exchange Online Connect-ExchangeOnline
MSOnline Connect to Azure AD Connect-MsolService
Microsoft.Graph Connect to Microsoft Graph Connect-MgGraph -Scopes
Microsoft.Graph.Beta Connect to Microsoft Graph Beta Same as above, but commands use MgGraphBeta
AzureAD Connect to Azure AD Connect-AzureAD
AIPService Connect to Azure Information Protection Connect-AipService
ImportExcel Import and export Excel files
MicrosoftTeams Connect to Microsoft Teams Connect-MicrosoftTeams
PnP.PowerShell Connect to SharePoint Online Connect-PnPOnline
Microsoft.Online.SharePoint.PowerShell Connect to SharePoint Online Connect-SPOService
PSDKit Convert JSON to PsCustomObject ConvertFrom-Json -InputObject $JSONInputString | ConvertTo-Psd
MSGraphStuff Module to find needed Graph modules to install + permission scopes Get-CodeGraphModuleDependency -scriptPath C:\path\to\script.ps1
Microsoft.WinGet.Client Repair-WinGetPackageManager Install WinGet as use as a powershell module. Works only in user context in PS5.1, both in PS7/core
Microsoft.PowerShell.SecretManagement Manage secrets in a secure way Get-Secret, Set-Secret, Remove-Secret
PassPushPosh Manage secrets in a secure way Initialize-PassPushPosh, New-Push, "blabla" | New-Push
PSWriteHTML Create HTML reports New-HTML, Add-HTML, Save-HTML