Exporting All AD Computers list by OU using PowerShell

Exporting All AD Computers by OU using PowerShell


When you run this script, it generates a CSV file containing the following details for all computers in the specified OU:

  • DistinguishedName: The full Active Directory path of the computer object.

  • Name: The hostname of the computer.

  • ObjectGUID: The unique identifier for the computer in AD.

  • OperatingSystem: The installed OS on the machine.

  • OperatingSystemVersion: The version of the installed OS.

  • LastLogonDate: The last recorded logon date of the computer.

The output file C:\Reports\AllComputers.csv can be opened in Excel or any text editor for further analysis.

-------------------------------------------------------------------------------------------------------------

# Define the Organizational Unit (OU) to search

$OU = "DC=CCM,DC=LOCAL"  # Change this if you want to target a specific OU


# Retrieve all computers within the specified OU and export to CSV

Get-ADComputer -SearchBase $OU -Filter * `

    -Properties DistinguishedName, Name, ObjectGUID, OperatingSystem, OperatingSystemVersion, LastLogonDate |

Select-Object DistinguishedName, Name, ObjectGUID, OperatingSystem, OperatingSystemVersion, LastLogonDate |

Export-Csv -Path "C:\Reports\AllComputers.csv" -NoTypeInformation


Write-Host "Report generated: C:\Reports\AllComputers.csv"

Popular Posts

Windows 11 24H2 Upgrade using Intune Feature Updates Policy

Image
How to Deploy Feature Updates Using Intune: A Step-by-Step Guide Microsoft Intune provides a streamlined method for managing Windows feature updates across your organization. In this guide, I'll walk through the essential prerequisites, policy creation steps, deployment, and monitoring process to ensure a smooth rollout of feature updates using Intune. 1. Verify Prerequisites Before you create a feature update policy, ensure the following prerequisites are met on the target devices: Device Enrollment : Devices must be enrolled in Intune, either as Microsoft Entra hybrid joined or Microsoft Entra joined . Supported OS : Devices must be running a supported version of Windows 10 or Windows 11 . Telemetry Settings : Devices must have the telemetry level set to Required . You can configure this via Devices > Windows> Configuration > Create Policy > Templates>  Device Restrictions > Reporting and Telemetry > Share Usage Data >Set as Required...
Read more

Deploying a Script through Intune to a Linux PC

Image
Can Intune Deploy Shell Scripts to Linux Devices? Yes! Just like deploying PowerShell scripts to Windows, Intune can also deploy shell scripts to Linux devices. In this blog, I'll walk you through the process of deploying shell scripts to Linux using Intune, making it easier to automate tasks and manage Linux endpoints efficiently. Prerequisites Before deploying a shell script via Intune, ensure the following requirements are met: 1. Intune and Microsoft Entra ID Your environment must have Microsoft Intune configured for device management. This setup enables secure enrollment and policy enforcement on Linux devices. 2. Linux Device Enrollment The Linux PC must be properly enrolled in Intune to receive policies and scripts. If the device is not enrolled, follow Microsoft's documentation on Linux enrollment in Intune. Deploying the Shell Script Once the prerequisites are met, follow these steps to deploy your shell script through Intune: Access Microsoft Intune Sign in to the ht...
Read more

Removing Obsolete Computer Records from Active Directory Using PowerShell (Only Windows Client Versions)

  Removing Obsolete Computer Records from Active Directory Using PowerShell Active Directory (AD) environments can accumulate obsolete computer objects over time. These stale records not only clutter the directory but can also pose security risks. This article provides a PowerShell-based approach to identifying and removing outdated computer records from Active Directory. Identifying Obsolete Computer Accounts The first step in cleaning up AD is to identify inactive computers based on their last logon timestamp and password last set date. Below is a PowerShell script to find obsolete devices that have not logged in for more than 60 days: Import-Module ActiveDirectory $DaysInactive = 60 $time = (Get-Date).AddDays(-$DaysInactive) # Identify obsolete devices $obsoleteDevices = Get-ADComputer -Filter { (LastLogonTimeStamp -lt $time -and PasswordLastSet -lt $time) -and (OperatingSystem -like '*Windows 10*' -or OperatingSystem -like '*Windows 11*' -or OperatingSystem...
Read more

Deleting Registry.pol and Forcing Group Policy Update Using a Batch File - Deploy through SCCM

  Deleting Registry.pol and Forcing Group Policy Update Using a Batch File - Software update cycle scan failures  In some troubleshooting scenarios ( specially software update cycle scanning errors)  , it is necessary to remove the Registry.pol file to reset Group Policy settings and force an immediate update. This guide outlines how to accomplish this using a batch script and deploy it via SCCM.  Step 1: Create a Batch File Script to Delete Registry.pol and Update Group Policy @echo off setlocal :: Define paths set "RegPolPath=C:\Windows\System32\GroupPolicy\Machine\Registry.pol" :: Check if the file exists and delete it if exist "%RegPolPath%" del /f /q "%RegPolPath%" :: Force Group Policy update gpupdate /force :: Notify user echo Group Policy has been updated successfully. pause Open Notepad. Copy and paste the script above. Save the file with a .bat extension (e.g., ResetGPO.bat ). Step 2: Deploy the Batch Script Using SCCM 1. Create an SCCM Packag...
Read more