-->

ABOUT US

Our development agency is committed to providing you the best service.

OUR TEAM

The awesome people behind our brand ... and their life motto.

  • Kumar Atul Jaiswal

    Ethical Hacker

    Hacking is a Speed of Innovation And Technology with Romance.

  • Kumar Atul Jaiswal

    CEO Of Hacking Truth

    Loopholes are every major Security,Just need to Understand it well.

  • Kumar Atul Jaiswal

    Web Developer

    Techonology is the best way to Change Everything, like Mindset Goal.

OUR SKILLS

We pride ourselves with strong, flexible and top notch skills.

Marketing

Development 90%
Design 80%
Marketing 70%

Websites

Development 90%
Design 80%
Marketing 70%

PR

Development 90%
Design 80%
Marketing 70%

ACHIEVEMENTS

We help our clients integrate, analyze, and use their data to improve their business.

150

GREAT PROJECTS

300

HAPPY CLIENTS

650

COFFEES DRUNK

1568

FACEBOOK LIKES

STRATEGY & CREATIVITY

Phasellus iaculis dolor nec urna nullam. Vivamus mattis blandit porttitor nullam.

PORTFOLIO

We pride ourselves on bringing a fresh perspective and effective marketing to each project.

Showing posts with label powershell. Show all posts
Showing posts with label powershell. Show all posts
  • Mastering PowerShell Commands: A Practical Guide to Get, Set, New, Invoke, Start, Add, Copy, Clear & More

     

    Mastering PowerShell Commands: A Practical Guide to Get, Set, New, Invoke, Start, Add, Copy, Clear & More

     

    A Practical Guide to Get, Set, New, Invoke, Start, Add, Copy, Clear & More

     
    There are PowerShell verb names used to make cmdlets predictable. PowerShell provides many standard verbs such as Get, Set, New, Find, Search, Read, Invoke, Start, Add, Clear, Close, Copy, and Enter. Each verb represents a different type of operation. For example, Get is generally used to retrieve information, Set modifies an existing configuration, New creates a new object, Start begins a service or process, and Copy creates a copy of an existing file or resource. Understanding these verbs helps administrators predict what a command is likely to do. 

     

    1. Get - retrieve information


    This is probably the most important PowerShell verb.

    Get-Service

    Get a particular service:
    Get-Service -Name Spooler


     

    Mastering PowerShell Commands: A Practical Guide to Get, Set, New, Invoke, Start, Add, Copy, Clear & More


    Get processes:
    Get-Process

    Get local users:
    Get-LocalUser


    Mastering PowerShell Commands: A Practical Guide to Get, Set, New, Invoke, Start, Add, Copy, Clear & More


    Think:

    Get = Show me information.

     

    2. Set — change something


    For example:

    Set-Service -Name Spooler -StartupType Automatic

    You're changing the startup type of the Spooler service.

    You'll see something like:

      
    Name     State    StartMode
    ----     -----    ---------
    Spooler  Running  Auto
      

     

    • Name → service name
    • State → whether it's currently Running or Stopped
    • StartMode → how Windows starts it (Auto, Manual, Disabled)

     

    Even you check by GUI -> win + r -> services.msc -> Find Print Spooler or Spooler -> right click on this service ->  Properties

     

    Mastering PowerShell Commands: A Practical Guide to Get, Set, New, Invoke, Start, Add, Copy, Clear & More

     


    Think:

    Set = Change existing information.


    3. New — create something


    Create a folder:

    New-Item -Path C:\Data\Test -ItemType Directory

    Create a file:

    New-Item -Path C:\Data\Test.txt -ItemType File


    In Active Directory:

    New-ADUser -Name "John Smith" -SamAccountName jsmith


    Think:

    New = Create something that doesn't exist yet. 

     

    4. Find — find a resource


    A good PowerShell example is:

    Find-Module -Name Pester

    This searches the PowerShell Gallery for the module.


    Mastering PowerShell Commands: A Practical Guide to Get, Set, New, Invoke, Start, Add, Copy, Clear & More

    Another example:

    Find-Command -Name Get-ADUser

    This helps find which module provides a command.

    Think:

    Find = Locate a PowerShell resource. 

     

    5. Search — search data/resources


    For Active Directory:

    Search-ADAccount -LockedOut

    This searches AD for locked-out accounts.

    Another useful example:

    Search-ADAccount -PasswordExpired

    Think:

    Search = Search for specific conditions/data.

    Important: Find and Search aren't interchangeable. The exact availability of these verbs depends on the installed module/cmdlets. 

     

    6. Read — read input/data



    A common example is:

    Read-Host "Enter your username"

    It waits for the administrator to enter something.

    For example:

    $name = Read-Host "Enter your name"

    Then:

    $name

    Think:

    Read = Receive/read information. 

     

     7. Invoke — execute something


    This is extremely important for System Administrators.

    For example, execute a command on a remote server:

    Invoke-Command -ComputerName SERVER01 -ScriptBlock {
        Get-Service
    }


    PowerShell connects to SERVER01 and executes:

    Get-Service

    You can also invoke a command locally:

    Invoke-Command -ScriptBlock {
        Get-ComputerInfo
    }


    Think:

    Invoke = Execute something.

     

    8. Start — start something


    Start a Windows service:

    Start-Service -Name Spooler

    Start a process:

    Start-Process notepad.exe

    Think:

    Start = Start an operation/process/service. 

     

     9. Add — add something


    Add a user to a local group:

    Add-LocalGroupMember -Group "Administrators" -Member "Atul"

    For Active Directory:

    Add-ADGroupMember -Identity "IT-Users" -Members tom

    Think:

    Add = Add an object/member to something.

     

    10. Clear — clear contents


    Clear a text file without deleting the file:

    Clear-Content C:\Data\log.txt

    The file remains, but its contents are removed.

    Clear the PowerShell screen:

    Clear-Host

    Usually you'll see:

    cls

    which is an alias for Clear-Host.

    Think:

    Clear = Remove existing contents without necessarily deleting the object. 

     

     11. Close — close something


    For example, with SMB:

    Close-SmbSession -SessionId 5

    This closes a particular SMB session.

    Think:

    Close = Close an existing connection/session/resource.


    12. Copy — copy something


    Copy a file:

    Copy-Item C:\Data\report.txt C:\Backup\

    Copy a folder:

    Copy-Item C:\Data C:\Backup -Recurse

    Think:

    Copy = Create a copy somewhere else.

     


    For Currently Logged-in User

     

    Get-CimInstance Win32_LoggedOnUser 

     

     13. Enter — enter a session


    This one is particularly important for Windows administration.

    Enter-PSSession -ComputerName SERVER01

    You'll enter an interactive PowerShell session on SERVER01.

    Your prompt may change to something like:

    [SERVER01]: PS C:\Users\Administrator>

    Now:

    Get-Service

    runs on SERVER01, not your local computer.

    To leave:

    Exit-PSSession

    Think:

    Enter = Enter an interactive session/environment.

     

    The pattern you should remember


    PowerShell cmdlets generally follow: 

    VERB - Noun

    For Example:
     

    Get       - Service
    Set       - Service
    Start     - Service
    Stop      - Service
    
    Get       - Process
    Stop      - Process
    Start     - Process
    
    Get       - LocalUser
    New       - LocalUser
    Set       - LocalUser
    Remove    - LocalUser
    

     

    This makes PowerShell much easier to learn.

    Instead of memorizing hundreds of commands individually, understand the verb + noun pattern. 

     


    💡 Why PowerShell?


    For a Windows Administrator, PowerShell isn't just about knowing commands. It's about using automation and scripting to troubleshoot systems, manage users and services, collect information, and perform repetitive administrative tasks efficiently. 

     


  • 5 PowerShell Commands Every Windows Administrator Should Know

     

    5 PowerShell Commands Every Windows Administrator Should Know

      

    5 PowerShell Commands Every Windows Administrator Should Know 



    If you're working in Windows Administration or IT Support, PowerShell can save a lot of time by turning repetitive administrative tasks into simple commands.

    Here are 5 PowerShell commands I'm currently practicing:


    1. Get-Service


    Check Windows services and their current status.

    Get-Service


    5 PowerShell Commands Every Windows Administrator Should Know

     

    Useful when troubleshooting services that are stopped or not responding.

    Get-Service -Name Spooler

    Get-Service | Where-Object Name -eq "Spooler"

    (Get-Service -Name Spooler).Status



    2. Get-Process


    View running processes and identify applications consuming system resources.

    Get-Process

    Useful for investigating CPU, memory, or application-related issues.

    Get-Process -Name pwsh


    5 PowerShell Commands Every Windows Administrator Should Know



    3. Get-ComputerInfo


    Retrieve detailed information about the Windows system.

    Get-ComputerInfo

    Useful for system inventory and troubleshooting.

     

    5 PowerShell Commands Every Windows Administrator Should Know

    4. Get-WinEvent


    Query Windows Event Logs to investigate system and application issues.

    Get-WinEvent -LogName System -MaxEvents 20


     

     

    5 PowerShell Commands Every Windows Administrator Should Know

    This is especially useful when troubleshooting unexpected errors, service failures, or system events.

    5. Get-LocalUser


    View local user accounts configured on a Windows machine.

    Get-LocalUser

     

     

    5 PowerShell Commands Every Windows Administrator Should Know



    Useful for basic local account administration and auditing.


    💡 Why PowerShell?



    For a Windows Administrator, PowerShell isn't just about knowing commands. It's about using automation and scripting to troubleshoot systems, manage users and services, collect information, and perform repetitive administrative tasks efficiently. 

     

  • How to identify my wbs chargecode in powershell windows 11

     

    How to identify my wbs chargecode in powershell windows 11


    How to identify my wbs chargecode in powershell


    A WBS (Work Breakdown Structure) / Charge code is usually not something Powershell can 'discover' automatically from your system because it's company-specific financial/project data (Stored in tools like SAP, ServiceNow, internal portals, or time-tracking systems).


    1. Check Environment Variables (if your organization uses them)

    Some companies push project/charge codes as environment variables.


    Get-ChildItem Env:
    
    
    


    Look for anything like:

    • WBS
    • CHARGECODE
    • PROJECT
    • COSTCENTER



    2. Check Active Directory (if stored in AD)


    Sometimes WBS/cost center is stored as a user attribute.



    Get-ADUser -Identity $env:USERNAME -Properties *
    
    
    


    Look for fields like:

    • department
    • extensionAttributeX
    • employeeID
    • costCenter



    Filter only relevant fields:


    Get-ADUser -Identity $env:USERNAME -Properties  department,extensionAttribute1,extensionAttribute2



    If you got error like as you can see the image below so in screenshot, the error is very clear:

    Get-ADUser : The term 'Get-ADUser' is not recognized



    How to identify my wbs chargecode in powershell windows 11


    ✅ What this means


    Your PowerShell does not have the Active Directory module installed or loaded.

    Get-ADUser comes from the ActiveDirectory module, which is:

    • ✅ Available on domain-joined machines with RSAT installed
    • ❌ Not available by default on normal Windows installs



    ✅ Fix it (step-by-step)


    🔹 Option 1: Check if module exists but not loaded

    Get-Module -ListAvailable ActiveDirectory


    How to identify my wbs chargecode in powershell windows 11


    👉 If you see output well and good but if you are not seeing then leave it as of now.

    Then just import it:

    Import-Module ActiveDirectory


    Option 2: Install RSAT (Most likely needed)


    Since you’re a IT Support Engineer, this is probably your case.

    Run:


    Get-WindowsCapability -Name RSAT.ActiveDirectory* -Online
    
    
    


    How to identify my wbs chargecode in powershell windows 11


    Install it:


    Add-WindowsCapability -Online -Name RSAT.ActiveDirectory.DS-LDS.Tools~~~~0.0.1.0
    
    
    


    How to identify my wbs chargecode in powershell windows 11



    Option 3: If installation is blocked


    In many corporate environments:

    ❌ You may NOT have permission to install RSAT

    👉 Then:

    Ask IT:

    "Please enable RSAT Active Directory PowerShell module on my machine"


    ✅ After fixing


    Use this correct command 

    👉 Environment variables cannot start with numbers

    ✅ Correct version:

    If your username is your ID:


    Get-ADUser -Identity $env:USERNAME -Properties *
    

    Or explicitly:


    Get-ADUser -Identity 221843 -Properties *
    
    
    



    How to identify my wbs chargecode in powershell windows 11



    How to identify my wbs chargecode in powershell windows 11


    Filter WBS / Charge info (after it works)


    Get-ADUser -Identity $env:USERNAME -Properties * |
    Select-Object Name, Department, Title, extensionAttribute1, extensionAttribute2
    



    Disclaimer



    All tutorials are for informational and educational purposes only and have been made using our own routers, servers, websites and other vulnerable free resources. we do not contain any illegal activity. We believe that ethical hacking, information security and cyber security should be familiar subjects to anyone using digital information and computers. Hacking Truth is against misuse of the information and we strongly suggest against it. Please regard the word hacking as ethical hacking or penetration testing every time this word is used. We do not promote, encourage, support or excite any illegal activity or hacking.




  • WHAT WE DO

    We've been developing corporate tailored services for clients for 30 years.

    CONTACT US

    For enquiries you can contact us in several different ways. Contact details are below.

    Hacking Truth.in

    • Street :Road Street 00
    • Person :Person
    • Phone :+045 123 755 755
    • Country :POLAND
    • Email :contact@heaven.com

    Lorem ipsum dolor sit amet, consectetur adipisicing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua.

    Lorem ipsum dolor sit amet, consectetur adipisicing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation.