Checking Active Network Shares within a Domain using PowerShell Script

Use a PowerShell script to iterate through a CSV list of server names and query their active network shares via WMI or CIM. This approach automates the verification process, ensuring that critical file resources are accessible and correctly shared across your domain environment without manual intervention.

Understanding the Requirement

In large enterprise environments, maintaining an accurate inventory of network shares is crucial for operational efficiency and security auditing. Administrators often need to verify that specific shares defined in documentation are actually active and accessible on the target servers. Manual checking is prone to error and does not scale well as the number of servers grows. By leveraging PowerShell, you can automate this validation process, reducing administrative overhead and providing immediate feedback on the status of network resources.

The core objective is to read a predefined list of servers from a CSV file, query each server for its current shares, and identify which ones match the expected configuration. This allows IT teams to quickly spot discrepancies, such as missing shares or unauthorized access points, and take corrective action promptly. For related automation tasks, such as managing user accounts across different domains, see Powershell Script: Creating New Users in Different Domains.

Preparing the Input Data

The script relies on a CSV file containing the list of servers to be checked. This file should have a single column named "ServerName" or similar, listing the DNS names or IP addresses of the target machines. Ensure that the CSV file is properly formatted with no trailing spaces or hidden characters that could cause lookup failures. It is best practice to store this file in a secure, centralized location accessible by the account running the script.

Before running the script, verify that the account executing it has sufficient permissions to query WMI/CIM information on the remote servers. Typically, membership in the local Administrators group or appropriate delegated WMI permissions is required. If you encounter permission errors, ensure the service account used has the necessary rights. Additionally, check if any firewall rules block the necessary RPC ports, as these are essential for remote management queries.

The PowerShell Script Logic

The script uses the Get-CimInstance cmdlet to query the Win32_Share class on each remote server. This method is preferred over older WMI cmdlets due to better performance and reliability in modern Windows environments. The script reads the CSV file, iterates through each server entry, and attempts to retrieve the list of shares.

$servers = Import-Csv -Path "C:\Scripts\ServerList.csv"
$activeShares = @()

foreach ($server in $servers) {
    try {
        # Query for active shares using CIM
        $shares = Get-CimInstance -ClassName Win32_Share -ComputerName $server.ServerName -ErrorAction Stop
        
        foreach ($share in $shares) {
            # Filter out default administrative shares if needed
            if (-not $share.Name.StartsWith("ADMIN$") -and 
                -not $share.Name.StartsWith("IPC$")) {
                
                $activeShares += [PSCustomObject]@{
                    ServerName = $server.ServerName
                    ShareName  = $share.Name
                    Path       = $share.Path
                    Type       = $share.ShareType
                }
            }
        }
    }
    catch {
        Write-Warning "Failed to connect to $($server.ServerName): $_"
    }
}

# Output results to console and export to CSV
$activeShares | Format-Table -AutoSize
$activeShares | Export-Csv -Path "C:\Scripts\ActiveSharesReport.csv" -NoTypeInformation

This script captures the share name, path, and type for each non-administrative share found on the specified servers. It handles connection errors gracefully by logging warnings instead of halting execution. This ensures that one unreachable server does not prevent the audit of others. For troubleshooting issues where scripts fail to run automatically, refer to Powershell Script Not Running in Task Scheduler.

Interpreting and Using Results

Once the script completes, review the exported CSV report to identify any discrepancies between the expected and actual shares. Compare the output against your official documentation to find missing or unexpected shares. You can use Excel or other data analysis tools to filter and sort the results for easier review. Highlighting rows where the share path differs from the documented value can help pinpoint misconfigurations.

If you need to integrate this check into a larger health monitoring system, consider scheduling this script to run periodically using Task Scheduler. Ensure that the scheduled task runs under an account with appropriate permissions and that the execution policy allows the script to run. Regular audits help maintain compliance and security standards within your domain infrastructure.

Optimizing Performance

For environments with hundreds or thousands of servers, consider optimizing the script for parallel execution. Using ForEach-Object -Parallel (available in PowerShell 7+) can significantly reduce the time required to complete the audit. However, be mindful of the load on both the client machine and the domain controllers when launching many concurrent connections. Adjust the throttle limit based on your infrastructure capacity.

You can also refine the query by specifying only the properties you need, rather than retrieving all properties from the Win32_Share class. This reduces network traffic and processing time. For example, selecting just Name, Path, and Type can speed up the operation noticeably. Always test optimizations in a non-production environment first to ensure they meet your performance requirements.

Frequently Asked Questions

What if a server is offline?

The script handles offline servers by catching connection errors and logging a warning message. It continues processing the remaining servers in the list, ensuring that the audit completes even if some machines are unreachable. You can modify the script to skip offline servers entirely if desired.

Can I filter shares by type?

Yes, you can add conditional logic to filter shares based on their Type property. For instance, you might only want to report disk drives (Type 0) and ignore printer shares (Type 1). Adjust the filtering criteria within the loop to suit your specific auditing needs.

How do I handle authentication issues?

If you encounter authentication errors, ensure that the account running the script has the necessary permissions on the remote servers. You may need to provide explicit credentials using the CimSession option in Get-CimInstance if the current context lacks access.

Is this compatible with older Windows versions?

The script uses Get-CimInstance, which requires PowerShell 3.0 or later. For very old systems running PowerShell 2.0, you would need to use Get-WmiObject instead, though this is deprecated and less efficient. Consider upgrading your management workstation to a supported PowerShell version.

Can I exclude certain servers from the audit?

Yes, you can easily modify the script to exclude specific servers by adding a condition before querying. For example, you can check if the server name matches a list of exceptions and skip the query if it does. This provides flexibility in defining the scope of your audit.