Powershell – Page 17

Ping computer with a specific OS

This script use WMI to ping a list of computers. Only specific OS are pinged. Script (with Microsoft Active Directory module loaded : import-module activedirectory) : $ping = new-object System.Net.NetworkInformation.Ping $list = Get-ADComputer -LDAPFilter “(|(operatingsystem=Windows XP*)(operatingsystem=Windows 7*)(operatingsystem=Windows Vista*))” ForEach ($b

Get users that not belong to similar group names

The purpose of this script is to enumerate all users that not belong to group names containing a specific pattern. The output shows samAccountName and email address. The test of the attribute “$user.memberof” has been added because when this attribute

Get service pack level on Windows 2008 servers

This script list all servers in Active Directory running on Windows 2008 and Windows 2008 R2 and check the service pack level (SP2 for Windows 2008 and SP1 for Windows 2008 R2) Script (with Microsoft Active Directory module loaded :

Get server network configuration using WMI

This script follows these steps : scan the Active Directory domain retrieve all Server names (OS name like “Windows*Server*”) ping the server name to check if it is alive if the ping is successfull, a WMI request get the following

Get inactive users (>6 months)

With this script, you will be able to get a list of inactive user accounts in Active Directory. There are two examples : one of them use the Microsoft Active Directory cmdlets and the other uses the Quest one. Script

WSUS server cleanup task

The best way to schedule an automatic cleanup of expired/superseeded update is to use the following Powershell script (source : http://www.peetersonline.nl/index.php/powershell/wsus-cleanup-with-powershell/) Script : #Region VARIABLES # WSUS Connection Parameters: [String]$updateServer = “myWSUSServer.domain.local” [Boolean]$useSecureConnection = $False [Int32]$portNumber = 80 # Cleanup

Testing for Schema Extension Conflicts

Source : http://technet.microsoft.com/en-us/library/testing-for-active-directory-schema-extension-conflicts%28WS.10%29.aspx You can use ADSchemaExtensionConflictAnalyzer.ps1 (http://go.microsoft.com/fwlink/?LinkId=191133), a Windows PowerShell script, to analyze application schema extension .ldf files against a production schema and generate a report on errors, conflicts, and other warnings. For example, if an application schema extension is

Set possible owners on core cluster resources

This script will set possible owners on core cluster resources (IP Address and Name) Script : Get-Cluster -Name ClusterName | Get-ClusterResource -Name “IP Address”,”Name” | Set-ClusterOwnerNode -Owners ClusterNode01,ClusterNode02 References Get-Cluster Get information about one or more failover clusters in a

Set a cluster resource dependency

This script set a cluster resource dependency on a file server clustered resource Script : Get-Cluster -Name ClusterName |` Get-ClusterResource -Name “FileServer-(FileserverResourceHostname)(Cluster Disk 10)” |` Set-ClusterResourceDependency -Dependency [“FileserverResourceHostname”][and [“Cluster Disk 10”]] Reference (http://technet.microsoft.com/en-us/library/ee461029.aspx) Set-ClusterResourceDependency Specify the resources that a particular

Robocopy process management

This script launch 10 robocopy processes simultaneously to copy folders that begin with a letter from ‘a’ to ‘k’ Script : $userfolders = Get-ChildItem \\server\root_shared_folder | Where-Object {$_.Name -match “^[a-k]”} foreach ($homes in $userfolders) { if ((Get-Process -Name “robocopy”).count -le