Tip: You can monitor the latest changes of a file (example: a log file with the latest logons). Get-Content -Path 'C:\ProgramData\chocolatey\logs\chocolatey.log' -Tail 10 -Wait -Tail 10 : to display the latest 10 lines of the file -Wait : to see the updates in real time
Tip: You can specify a folder by using a GUI instead of manually copy/paste the path:
|
1 2 3 4 5 6 7 8 9 10 11 |
# Solution 1 Add-Type -AssemblyName System.Windows.Forms $browser = New-Object System.Windows.Forms.FolderBrowserDialog $null = $browser.ShowDialog() $path = $browser.SelectedPath # Solution 2 $application = New-Object -ComObject Shell.Application $path = ($application.BrowseForFolder(0, 'Select a folder', 0)).Self.Path |
Tip: There are several ways to work with network drives: WScript.Network COM object net.exe The following commands create a persistent drive (the drive will still here even after logout or reboot), list and remove the drive.
|
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 |
$shareName = '\\server\folder' $network = New-Object -ComObject WScript.Network # Add # Credentials not required net.exe use M: $shareName /PERSISTENT:YES $network.MapNetworkDrive('M:', $shareName, $true) # Credentials required net.exe use M: $shareName /PERSISTENT:YES /USER:DOMAIN\username * $network.MapNetworkDrive('M:', $shareName, $true, 'DOMAIN\username', 'password') # List net.exe use M: $network.EnumNetworkDrives() # Remove net.exe use M: /DELETE $network.RemoveNetworkDrive('M:', $true, $true) |
Note: When providing credentials, in this example I use the IP Address as it is a workaround here.
Tip: Sometimes you need to execute a Powershell script and keep the console open once the script is finished to see the result (or errors). You can use the parameter -NoExit : NoExit : Does not exit after running startup commands. powershell.exe -NoExit –File 'C:\scripts\Get-DiskSpace.ps1'
Tip: The automatic variable $PROFILE refers to Powershell profiles.
|
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 |
# Check if a profile exists Test-Path -Path $PROFILE # Current User,Current Host Test-Path -Path $PROFILE.CurrentUserCurrentHost # Current User,Current Host Test-Path -Path $PROFILE.CurrentUserAllHosts # Current User,All Hosts Test-Path -Path $PROFILE.AllUsersCurrentHost # All Users, Current Host Test-Path -Path $PROFILE.AllUsersAllHosts # All Users, All Hosts # Create a new profile for current user New-Item -ItemType File -Force $PROFILE # CurrentUserCurrentHost New-Item -ItemType File -Force $PROFILE.CurrentUserCurrentHost New-Item -ItemType File -Force $PROFILE.CurrentUserAllHosts # Edit psEdit $PROFILE (only for ISE) ise $PROFILE (only for ISE) notepad.exe $PROFILE # Reload (without restarting Powershell) & $PROFILE .$PROFILE # List profiles $PROFILE | Format-List * -Force |
Note: A Powershell profile is just a ps1 file.
Tip: You can display the code (definition) of a function (or of a module for example): (Get-Command psedit).Definition
Tip: You can list the common parameters: [System.Management.Automation.Cmdlet]::CommonParameters Powershell v4 Powershell v5 There are two new common parameters: InformationAction and InformationVariable. Note: To list the optional parameters: [System.Management.Automation.Cmdlet]::OptionalCommonParameters
Tip: You can quickly open file(s) in a new tab in Powershell ISE with psEdit (or ise) :
|
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 |
### psEdit ### One file psEdit .\script1.ps1 Multiple files psEdit -Filenames @('.\script1.ps1','.\script2.ps1', $profile) ### ise ### One file ise .\script1.ps1 Multiple files ise -File ".\script1.ps1,.\script2.ps1, $profile" |
3 tabs opened: # ise is an alias to powershell_ise.exe # psEdit is a function
Tip: You can store the output of a command in a variable and at the sametime have this output on the screen. It is like “2 in 1”, you save and output. Note: no need to put the $ sign.
|
1 |
Get-ChildItem -OutVariable files |
One line (needed to store and output on the screen) Two lines (needed to store and output on… Read More »
Tip: You can convert WMI date (format DTMF Distributed Management Task Force) to DateTime:
|
1 2 3 4 5 6 7 |
$installDate = (Get-WmiObject -Class Win32_OperatingSystem).InstallDate # Solution 1 [Management.ManagementDateTimeConverter]::ToDateTime($installDate) # Solution 2 ([WMI] '').ConvertToDateTime($installDate) |
Note: Use CIM cmdlets (available since PowerShell v3) instead of WMI cmdlets, moreover CIM return a more understandable datetime format : (Get-CimInstance -ClassName Win32_OperatingSystem).InstallDate MSDN: ManagementDateTimeConverter.ToDateTime Method