Clean Node_modules with PowerShell

As we do many experiments with UI based frameworks node_modules folders occupy a large portion of the disk space and after a few years, the disk space starts to diminish.

I have a 500GB SSD hard disk in my laptop and have recently run out of space and started to analyze what is that occupies so much space. I do not store personal images and documents on my laptop, at least not more than 1-2 GB.

When I analyzed the code base folder I realized that the experiments I did years ago are still on my machine and needed some cleanup. The easiest way was to remove unused data without any kind of loss is by deleting the huge node_modules folder in every project I did not use currently.

For this purpose, I wrote below PowerShell script to clean up all the node_modules folders in my code folder

Get-ChildItem -Path . -Filter node_modules -Recurse | Remove-Item -Force -Recurse

The "Get-Childitem" here gets all the folders with path "." (which is the current folder I am running the script in) with filter as folder name "node_module" and pipes in into "Remove-Item" command. This command recursively finds all the files and folders inside and deletes them without confirmation. ("Force" parameter is added to avoid asking yes/no before deleting each folder)

After executing this command I was able to recover more than 20Gb of disk space.

Original article source at: https://www.c-sharpcorner.com/

#powershell #node #modules

Monty Boehm

1671922500

Fix for PowerShell Script Not Digitally Signed

Introduction

If you are getting this error which says .ps1 file cannot be run because the file is not digitally signed. You cannot run this script on the current system

The File PS1 Cannot Be Run Because The File Is Not Digitally Signed

Cause

By default, the command prompts are set to run only the scripts that are digitally signed. Usually, in prod servers this could be the ideal case.

Fix

But in some cases, you may not need digitally signed scripts to execute the standard admin jobs, such as getting the system performance, or generating the M365 services report or running some standard migrations from on-prem to cloud. In this case, you can set the execution policy for current user to unrestricted.

Set-ExecutionPolicy Unrestricted -Scope CurrentUser

The File PS1 Cannot Be Run Because The File Is Not Digitally Signed

After running this command, you should be able to run the unsigned PowerShell scripts for this user.

Original article source at: https://www.c-sharpcorner.com/

#powershell #digital

Fix for PowerShell Script Not Digitally Signed

Ramiro Daugherty

1671311940

How to Easily Unzip Multiple Zips using PowerShell

Problem: Unzip mulitple files in one go.

PowerShell

PowerShell is a task automation and configuration management program from Microsoft, consisting of a command-line shell and the associated scripting language

I started working on PowerShell years back when I started with dev ops to automate simple tasks, like packaging the application products, automated builds, etc.

When I hit a problem like unzipping a huge number of files, my very first thought was to select all the files and right-click and select unzip, but this did not work. That's when I landed on the below line to unzip bulk.

$files = Get-Childitem .
foreach($fs in $files){Expand-Archive $fs -DestinationPath .}

The file line reads all the files in the current directory (. implies current directory, you can also give full directory path)

The second line is using PowerShell "Expand-Archive" command to unzip all the zip files in the list.

Expand-Archive
      [-Path] <String>
      [[-DestinationPath] <String>]
      [-Force]
      [-PassThru]
      [-WhatIf]
      [-Confirm]
      [<CommonParameters>]

Steps

Save the commands mentioned in ps1 file: myscript.ps1
Open windows PowerShell and run the script file: .\myscript.ps1

If this fails, then set the execution policy to unrestricted for this session and try again.

Conclusion

If you are using a windows machine and need a quick way to unzip files, then go with expand-archive.

References

Original article source at: https://www.c-sharpcorner.com/

#powershell #zip

How to Easily Unzip Multiple Zips using PowerShell

Desmond Gerber

1671276780

How to Find List Of Inactive Users in Microsoft 365 Using PowerShell

Finding inactive users in an organization is very difficult where hundreds of users are working. Many organizations share information with external users or guest users who do not belong to their organization. For example, some companies connect with their customers on MS teams or shares information through SharePoint or One Drive where they provide access as guest users. Many times, companies do not have information about whether those guests’ users are still active or not. How many days they last logged in?

One simple solution is login to Azure Active Directory and navigate to a specific user and get the last login date. But it is very time-consuming to go to every single user and get the last login date.

Another solution is Azure Audit Log which captures users’ activity with datetime.

Get-AzureADAuditSignInLogs -Filter “userPrincipalName= ' UserPrincipalName '” -Top 1

The parameter -Top is for the maximum number of records to return. In case of above we will get last one record.

The above PowerShell command returns last sign in datetime of the specific user of any of the apps like MS Teams, SharePoint, One Drive, etc. Use Get-AzureADUser to get a list of users and loop through it to get each specific user’s last sign-in date. Here, there is one challenge in using Get-AzureADAuditSignInLogs command in loop. It returns a throttling issue when looping through a set of users.

To resolve the problem, just add Start-Sleep -Milliseconds 10 at the end of each request. We will be using this in try/catch.

Below is the complete PowerShell script which reads users from Azure AD, get last sign-in date of each user, and save it in CSV file.

Function FindLastSignInDate {
    param ( [string]$upn )
    $AllUsers = @()
    $DateToday =(Get-Date).ToString("yyyy-MM-dd")
    $Days = 0
    $filter = "userPrincipalName = '" + $upn + "'"
    Try {
       $Result = Get-AzureADAuditSignInLogs -Filter $filter -Top 1 | Select-Object CreatedDateTime, UserPrincipalName
        $LoginTime = $Result.CreatedDateTime
        if($LoginTime -ne $null){
            $LoginDate = $LoginTime.substring(0,10)
            $ts = New-TimeSpan -Start $LoginDate -End  $DateToday
            $Days = $ts.Days
            $AllUsers += [pscustomobject]@{
                UPN= $UPN
                LoginDate = $LoginDate
                Days = $Days
            }
    }
    Catch
    {
            sleep 10
            GetLastSignInDate $upn
    }
    finally {
        $AllUsers | Out-File "c:\LastLogin.csv" -Append
    }
}
Import-Module AzureADPreview
$Result = ""
$output = ""
$filter = ""

#Connect to Azure AD
$user = "xxxxxxxxxx@xxxxxxxxx.com"
$password = "xxxxxxxxxxxx"
$secPass = ConvertTo-SecureString $password -AsPlainText -Force
$Cred = New-Object System.Management.Automation.PSCredential ($user, $secPass)
Connect-AzureAD -Credential $Cred
$Users = Get-AzureADUser -all $true
Foreach($user in $Users ){
    $upn = $user.UserPrincipalName.ToLower().Trim()
    FindLastSignInDate $upn
}

The above script will create a CSV file.

Original article source at: https://www.c-sharpcorner.com/

#powershell #microsoft

How to Find List Of Inactive Users in Microsoft 365 Using PowerShell

Ramiro Daugherty

1670069069

Install PowerShell Modules In Offline Mode

Introduction

In this blog, we will learn to manually install PowerShell modules. Recently, I was working on VM desktop with restricted access to perform PowerShell tasks, no direct internet access, and PSRepository access for installing modules. If you do not have any restrictions, we can install PowerShell modules from the official PowerShell gallery repository using the command "Install-Module".

Note
There is no direct repository to download modules from the official PowerShell gallery. You can download only NuGet(a .nupkg file) package from the official site to install the module, but this will not be the complete module installation.

Prerequisites

PowerShell version 5.1 or newer

Below are the steps to manually installing PowerShell modules,

Step 1

To ensure that the module exists, launch PowerShell and search for it in the PowerShell Gallery.

Find-Module -Name “module name”