YooAdmin

Object Oriented Programming Classes and Objects In PowerShell

Of-course Powershell is OOP(Object oriented programming Tool). Which means any developer who know Object oriented Programming would know how to utilize it, that doesn’t mean who are not developers cannot learn Powershell. it’s bit annoying to understand the concepts of the OOP to take maximum use of it.

Classes aka Blueprints

Talking of concept of Classes Lets look at the inheritance in Powershell. How to write a script that will allow us to achieve the Inheritance from a class. Below diagram will show what does Inheritance look like.

There is a Class called Wallet which will basically have the certain base attributes such as Brand, Name of the Wallet, How many cards you can hold, how much money you can keep in it. These attributes are called as variables in the powershell class and the there are functions that a wallet can do, Such as: Spending function.

These are the 2 major characteristics of the Class.
Attributes
Functions

You can see from the below Powershell script that i have created a Class called Wallet. with some attribute and function that a wallet will have. In Powershell Attributes of a class is represented as Variables($brand,$name and etc) and Functions are represented as functions (SpendCash).

class Wallet{
    [string] $Brand
    [string] $Name
    [string] $Card1
    [float] $Card1Bal
    [string] $Card2
    [float] $Card2Bal
    [string] $CashonHand
    [string] $License

    [void] SpendCash ([float]$spent){
        $this.CashonHand -= $spent
    }
}

$fazulwallet = New-Object Wallet

$fazulwallet.Name='Fazul Rahuman'
$fazulwallet.Brand = "LV"
$fazulwallet.Card1 = 'ABC Bank'
$fazulwallet.Card1Bal = 4000
$fazulwallet.Card2 = 'XYZ Bank'
$fazulwallet.Card2Bal = 1500
$fazulwallet.CashonHand = 500 
$fazulwallet.License = "ABCED12341EWE2231"

$fazulwallet.SpendCash(100)

The class by itself doesn’t create the inheritance concept. Until you create a object from that class. $fazulwallet = New-Object Wallet once you create an Object. You now can use those attributes and function in your own object without defining anything, show below.

Now all you need to do it feed the data into the object like below. you can now as many wallets as you want and feed data into it.

We saw how the attributes work now lets look the functions, i created a function called SpendCash if you can see above image which shows i have 500 Cashonhand, Now i will use the function SpendCash to send a 100 from the cash i have in my wallet.

Now i have spent 100 form the cash i had in my wallet by simply running the function called SpendCash. Interesting isn’t it.

The purpose of the Class implementation in Powershell is to create runtime objects which could hold different values but use the same Class to instance an object. This Concept is also used in DSC resources.

Remove User profiles from Servers/Clients

Hello again! Let me tell you something about the user profiles and how annoying can it be once its piled up in a server, where you have to loose Server or Clients space for staffs who basically left the organization. I had to face the same situation in my organization where majority of the servers are filled with user profile which cost the space on server an avg of 7 – 13 Gigs. Once i figured that one server had consumed this much of data been stored since past 5 years on the server I started to run this simple script on majority of the server. The result was surprising where i manged to clear storage around 200GB on all servers that i ran this script. How simply these things are missed and eating up free spaces.

Removing Legacy profiles are good in general Housekeeping obviously do check with Manager or team lead before proceeding with these sort of housekeeping for proper approval and Change raised if its required (Most of the Org will require a Change request for this).

Data Gathering.

Before removing the profile obviously have a report of the finding. the script also puts all the finding into a an Hash Table which is much more easier to read as below. All you have to do is Run the following command to see it in a grid view which is pre-built in Powershell. $Report | out-gridview

Once you have the Data in a readable format its pretty easy to do the rest which is making decision based on it. Now we have the data all we need to do is take the decision whether which date backwards you are going to delete the profiles. Lets say anything below 2015.

Just added a quick script to find out how many users profiles are there that are last access date is less than 2015 – found that are 36 profiles.

Quick counting script

What if there are Accounts which are accessed before 2015 and some of the account needs to be retained without deleting like Administrator, Public or any other specific profiles. then its just another matter if condition.

Excluding specific accounts

Now you have all the necessary details to add this one command which will do the eliminate the user profiles. get-wmiobject -class win32_userprofile -computername $machinename | ? {$_.LocalPath -eq $semiReport.ProfileLocation} | Remove-wmiobject
The removal part is commented to avoid removing profile mistakenly.

Revealing the full script here. you can pass one machine a time or you can pass a list as well.

$machinename = Read-Host "Please Type the host Name "
#$machinenames = Get-Content -Path "Filepath with machine name" 
$existingusers = Get-ChildItem "\\$machinename\c$\users" | select name
$Report = @()

#if you are using a list please change the foreach $existingusers to $machinesNames

foreach($username in $existingusers){
$checkforsrv =$username.Name.Contains("Adminsitrator")
$checkforpublic = $username.Name.Contains("Public")
$checkforDefault = $username.Name.Contains("Default")


            if($checkforsrv -eq "True"){
            #do nothing.
            }elseif($checkforpublic -eq "True"){
            #do nothing
            }elseif($checkforDefault -eq "True"){
            #do nothing
            }else{

                $name = $username.Name
                
                $SemiReport = New-Object -TypeName psobject -Property @{
                ServerName = $machinename
                ProfileLocation = "\\$machinename\C$\users\$name"
                UserName = $username.Name
                "Size(in MB)" = "{0:N2}" -f ((Get-ChildItem  -Path "\\$machinename\C$\Users\$name" -Recurse| Measure-Object -Property Length -Sum -ErrorAction SilentlyContinue).Sum /1MB)
                LastAccessDate = (Get-ItemProperty -Path "\\$machinename\c$\users\$name" | select LastAccessTime).LastAccessTime
                }
                $Report += $SemiReport | Select-Object ServerName,ProfileLocation,Username,"Size(in MB)",LastAccessdate
            }
}

$count = 0
foreach($entry in $Report){
    if($entry.LastAccessDate -lt "01-01-2015"){
      #Get-WmiObject -class Win32_UserProfile -ComputerName "$machinename" | ? {$_.LocalPath -eq "C:\Users\$name"} | Remove-WmiObject
       $count = $count + 1
    }else{

    }
}
$count

Caution: Please be cautious about the environment always test on test environment and obtain necessary approvals.

Scraping Amazon.co.uk using Powershell

Helloo! I was asked by one of my colleague whether i can create a Web scrape tool in Powershell like its in Python using BeautifulSoup. I told him you don’t be needing any more extra modules to be added into to Powershell to scrape a website for data. Obviously i use Python as much as Powershell too.

The Beauty of the Powershell is that you don’t need additional tools(Python) or modules(BeautifulSoup) to be installed rather you can use this Command which is inbuilt in Powershell “Invoke-Webrequest“. believe me its so powerful – now wonder why its called PowerShell 😛

Using a bit of Source code checks from the https://www.amazon.co.uk site using the Inspect Element i was able to create a script that basically pulls all the necessary information of the products that’s in a specific search criteria value. Present it out as a Table where you can basically see all the details where you can build a database of products if you ran it every few hours and feed the data into the Database for data-mining.

The Challenge of doing is that the Amazon Page is so dynamic in presenting the products where they even change HTML codes structure for even product wise. which was a fun weekend project to create the web-scraper.

Since i haven’t seen anyone paying much importance to the Powershell’s inbuilt tools like invoke-webrequest command. i decided to share this fun weekend project with you all. It took just less than 1 hour to fully program this 41 lines of code.

Let me show you the the result this time before going to the script.

in the above report you can see the following details that’s been pulled from the Amazon using Powershell:
1, Name
2, Link
3, Price
4, Delivery
5, Rating

Using these fields you can create your own Product data repository for further invest or if you are planning to do a start-up if you can think of a potential way.

Lets reveal the fun part the Script.

$Search = "camera"
$BaseURL = "https://www.amazon.co.uk"
$SearchLink = "https://www.amazon.co.uk/s?k=$Search&ref=nb_sb_noss_2"
$result = @()

$Response = Invoke-WebRequest -Uri $SearchLink
$productNames=$Response.AllElements | where {$_.class -eq "a-link-normal a-text-normal"} | select outertext,href # Product
$images = $Response.AllElements | where {$_.Class -eq "s-image"} | select src
$prices= $Response.AllElements | where {$_.class -eq "a-price-whole"} | select outertext # Price
$cents = $Response.AllElements | where {$_.class -eq "a-price-fraction"} | select outertext # Price cents
$deliveries = $Response.AllElements | where {$_.class -eq "a-row a-size-base a-color-secondary s-align-children-center"} | select outertext # Delivery
$ratings = $Response.AllElements | where {$_.class -eq "a-row a-size-small"} | select outertext # Rating

$count = $productNames.Count 

For ($i=0;$i -le $count; $i++){

    $Details = New-Object -TypeName psobject -Property @{
    
    Name = $productNames[$i].outertext
    Link = $BaseURL+$productNames[$i].href
    Price = $prices[$i].Outertext+$cents[$i].outertext
    Image = $images[$i].src
    Rating = $ratings[$i].Outertext
    Delivery = $deliveries[$i].Outertext
    }
    
    $result += $Details | Select-Object Name,Link,price,image,rating,Delivery
}

   $Style = @"
<style>
BODY{font-family:Calibri;font-size:10pt;}
TABLE{border-width: 1px;border-style: solid;border-color: black;border-collapse: collapse; padding-right:5px}
TH{border-width: 1px;padding: 5px;border-style: solid;border-color: black;color:black;background-color:#FFFFFF }
TH{border-width: 1px;padding: 5px;border-style: solid;border-color: black;background-color:green}
TD{border-width: 1px;padding: 5px;border-style: solid;border-color: black}
</style>
"@

$result | select name,Link,Price,Delivery,rating | Sort-Object Price | ConvertTo-Html -Head $Style -Body "<H2>Amazon Product result for $Search</H2>" |Out-File 'C:\temp\Report.html'

I was looking for Camera as a example you can obviously go with any product you would like to search.. the best thing is you get a report in less than 12 seconds. you can see below highlighted.

You might need a bit of HMTL Understanding to modify the script but its not that hard and never late to learn, Like i say its all about learning. Happy Scarping 🙂

Note: Be-caution on using this script for any other purpose/sites as this demonstration is only for educational purpose and to show the potential of Powershell apart of the System management in an organization.

Password Expire Report – Powershell

Hello! welcome to another interesting task i was working on couple of days ago. To give a bit of background of what exactly i was doing.

Part of My Domain to Domain Migration (AKA ADMT Migration) project i was asked to generate a report which basically pulls all of users from the source domain and check the password to check how many users have password expiring sooner. It was a fun task to do, i just added bit of a HTML touch to make it look like an actual report, (Management loves those reports).

Report shows password that expires in a day,10 and 20 days. You get 3 reports also you can modify the script to match your needs.

Less talking and to the point, Script. Please change the below script for your environment.

$useridentified = Get-ADUser -Filter {((enabled -eq $true) } -SearchBase "OU=OUName,DC=domainname,DC=domainname" -Properties givenname,surname,samaccountname,mail,PasswordLastSet | select givenname,surname,samaccountname,mail,PasswordLastSet
$userforpasswordcheck = @()
$Reportforpassword = @()
$10days = @()
$20days = @()
$1day = @()

foreach($Suser in $useridentified){

$userforpasswordcheck += Get-ADUser $Suser.SamAccountName -Properties givenname,surname,samaccountname,mail,PasswordLastSet -Server Servername | select givenname,surname,samaccountname,mail,PasswordLastSet

}

foreach($SingleUser in $userforpasswordcheck){
try{
$NextReset = $SingleUser.PasswordLastSet.AddDays(60)
}catch{
}

   $Passwordreport = New-Object -TypeName psobject -Property @{
    "Firstname" = $SingleUser.givenname
    "Lastname" = $SingleUser.surname
    "Username" = $SingleUser.samaccountname
    "Email" = $SingleUser.mail
    "PasswordLastReseton" = ($SingleUser.PasswordLastSet).Date
    "Expiry" = $NextReset 
    "Daysremaining" = ($NextReset - (Get-Date)).Days
   }

      $Reportforpassword += $PasswordReport | Select-Object  "Firstname","Lastname","Username","Email","PasswordLastReseton","Expiry","Daysremaining"
}

foreach($line in $Reportforpassword){
    if(($line.Daysremaining -eq 1) -or $line.Daysremaining -lt 1){
        $1day += $line
    }elseif($line.Daysremaining -lt 10){
        $10days += $line
    }elseif($line.Daysremaining -lt 20){
        $20days += $line
    }
}

   $Style = @"
<style>
BODY{font-family:Calibri;font-size:10pt;}
TABLE{border-width: 1px;border-style: solid;border-color: black;border-collapse: collapse; padding-right:5px}
TH{border-width: 1px;padding: 5px;border-style: solid;border-color: black;color:black;background-color:#FFFFFF }
TH{border-width: 1px;padding: 5px;border-style: solid;border-color: black;background-color:orange}
TD{border-width: 1px;padding: 5px;border-style: solid;border-color: black}
</style>
"@

$reportpath = 'C:\PasswordEmails\HTML\today.html'

$20days | Select-Object "Firstname","Lastname","Username","Email","PasswordLastReseton","Expiry","Daysremaining" | Sort-Object Daysremaining | ConvertTo-Html -body "<H2> Users Password Check less than 20 days</H2>"-Head $style | Out-File 'C:\PasswordEmails\HTML\20days.html'

$10days | Select-Object "Firstname","Lastname","Username","Email","PasswordLastReseton","Expiry","Daysremaining" | Sort-Object Daysremaining | ConvertTo-Html -body "<H2>Users Password Check less than 10 days</H2>"-Head $style | Out-File 'C:\PasswordEmails\HTML\10days.html'

$1day | Select-Object "Firstname","Lastname","Username","Email","PasswordLastReseton","Expiry","Daysremaining" | Sort-Object Daysremaining | ConvertTo-Html -body "<H2>Users Password Check less than 1 days</H2>"-Head $style | Out-File 'C:\PasswordEmails\HTML\1day.html'

#$Reportforpassword | Select-Object "Firstname","Lastname","Username","Email","PasswordLastReseton","Expiry","Daysremaining" | Sort-Object Daysremaining | ConvertTo-Html -body "<H2>Users Password Check</H2>"-Head $style | Out-File $reportpath

Report will look like as below. Obviously i have to blur the fields. (you know why :P)

Have a nice day!

Project – CITRIX + SCCM + Powershell = PowerScCitrix

Hellooo! The Last couple of days i was busy with some Citrix 7.x + SCCM + Powershell integration for the support teams to quickly work on persistent VDIs which has SCCM Client installed for patching purpose, To be Honest it was amazing to create this Powershell based Application which is very light and powerful.

Applications Abilities are as below:
Citrix Director – Search Sessions user based or Machine based, Poweron, Poweroff and Restart.
SCCM – Deploy SCCM Client (Clearly you can say SCCM server can do it dude whats the need for your Application) – Agreed! But this will look for why SCCM Agent is not installing and will apply pre-defined solutions and get the Agent install – which in my perspective is a key element. Some of the stuff it will look for are – C drive space check, WMI Repository check, Network & firewall check and Connectivity check.

Best about this application is, its fully created in Powershell and can run from Standard Windows desktop in your Corporate environment. PS version should be 4 or above along with appropriate access in you domain.

Here you go the PowerScCitrix!

The project is completed. As you can see i have added additional feature that could help the SCCM Client to be installed on any given environment.

As i get more request of scripts to be created from the teams i work with, I will expand this tool with additional functions to accommodate to help the support teams in managing the Environment.

Indeed Powershell is Great Tool for automation.

Get/Set Out of Office

Getting/Setting OOO (Out of Office) emails are mostly happening with Leavers who left the company on short notice or being kicked out of the Company. Where the account needs to be receiving emails but the other users should be informed about the User that has left the organization and future mails to the mentioned email. The below scripts will show you how to get and set OOO.

Get-Mailbox "User's Email address"| Get-MailboxAutoReplyConfiguration | Select AutoReplyState, InternalMessage

Set Out of Office is pretty straight forward and can you massively if you want to set for a set of mailboxes.

Set-MailboxAutoReplyConfiguration -Identity "user name"-AutoReplyState Enabled -InternalMessage "Out of office mails for Internal staffs" -ExternalMessage "Out of Office mail for anyone Outside the Organization."

Adding Credentials to Powershell Script

Most of the script will require you to add the credentials to it to run with elevated privileges, The below is one of the way you can add credentials to the script.

$usr = "Domain\username"
$Pwd = ConvertTo-SecureString -String "Password" -AsPlainText -Force
$cred = New-Object -TypeName System.Management.Automation.PSCredential -ArgumentList $usr,$pwd

You can now use the Variable for the scripts you use.

Find Disabled users in a AD group

AD Group housekeeping is great way to maintain the access and also to clean up license if you are provisioning users license via AD group, There is a quick and easy way.

Below script will help you

$users = get-adgroupmember -identity "Group name" | select samaccountname

Foreach($user in $users){
    Get-ADuser $user.samaccountname | select samaccountname,enabled
}

Get Mailbox Details

Getting mailbox details are a mundane task for admins. The below script will provide you with general mailbox details that may required

UserID, UserAlias, UserDisplayName, UserType, UserUPN ,UserEmail (Only Primary SMTP) and Mailbox Size.

$CurrentDate = Get-Date
$CurrentDate = $CurrentDate.ToString('dd-MM-yyyy_HH-mm-ss')

$report = @()
$i = 0

$Mailboxes = Get-mailbox -ResultSize Unlimited | Select-Object Identity, Alias, DisplayName, RecipientTypeDetails, UserPrincipalName, PrimarySmtpAddress

Foreach ($Mailbox in $Mailboxes)
{
   $UserID = $Mailbox.Identity
   $UserAlias = $Mailbox.Alias
   $UserDisplayName = $Mailbox.DisplayName
   $UserType = $Mailbox.RecipientTypeDetails
   $UserUPN = $Mailbox.UserPrincipalName
   $UserEmail = $Mailbox.PrimarySmtpAddress

   Write-Host "Email: "$UserEmail

   $MailboxStat = Get-MailboxStatistics -Identity $UserEmail | Select-Object TotalItemsize

   $MailboxSize = $MailboxStat.TotalItemsize


   $userObj = New-Object PSObject
   $userObj | Add-Member NoteProperty -Name "Identity" -Value $UserID
   $userObj | Add-Member NoteProperty -Name "Alias" -Value $UserAlias
   $userObj | Add-Member NoteProperty -Name "DisplayName" -Value $UserDisplayName
   $userObj | Add-Member NoteProperty -Name "RecipientTypeDetails" -Value $UserType
   $userObj | Add-Member NoteProperty -Name "UserPrincipalName" -Value $UserUPN
   $userObj | Add-Member NoteProperty -Name "WindowsEmailAddress" -Value $UserEmail
   $userObj | Add-Member NoteProperty -Name "Mailbox Size" -Value $MailboxSize

   $report = $report += $userObj
   $ii++
}

$report

Get Inbox Rule

One thing most of the Exchange Admins has to go through is
User : “I didn’t receive the email sent to me.”
Admin : “have you created any rules?”
User : “Not sure”
Admin : “Let me Check”
… Few seconds later
Admin : “Yes you have a rule please double check that.”

User goes how did you check that? Admin like i have a script and that script is below LOL just tried to be creative on this.

$i = 0
$Mailboxes = Get-Mailbox -ResultSize Unlimited | Select PrimarySMTPAddress, Name
$Mailboxes.Count

ForEach ($Mailbox in $Mailboxes)
{
   $EMailAddress = $null
   $UserName = $null
   $EMailAddress = $Mailbox.PrimarySMTPAddress
   $UserName = $Mailbox.Name

   Write-Host "Name: "$UserName
   Write-Host "Email: "$EMailAddress
   Write-Host "=================================================="

   Get-InboxRule -Mailbox $EMailAddress | FL | Out-File "Result.txt"
      
   Write-Progress -Activity "Searching for Mailbox Rules..." -status "Proccessed $i of $($Mailboxes.Count)" -percentComplete (($i / $Mailboxes.Count)  * 100) -ErrorAction:SilentlyContinue
   $i++
}

Classes aka Blueprints

Share this:

Share this:

Share this:

Share this:

Share this:

Share this:

Share this:

Share this:

Share this:

Share this: