Import-Module -Name ActiveDirectory

Get-ADUser -Filter * -SearchBase "OU=YourOUName,DC=YourDomain,DC=COM" -properties ScriptPath | Export-Csv "c:\script\ADUser.csv"

Note: In order for this to work, you have to have the ActiveDirectory Module loaded. 

$CheckForFile = "H:\custom.ini"
$FileToCopy = "c:\IT\custom.ini"
$CopyFileTo = "H:\"

$PathTest = Test-Path $CheckForFile
If ($PathTest -eq "false")
    {
    Copy-Item $FileToCopy $CopyFileTo
    }

#uses the Invoke-Item command to launch the application
Invoke-Item "C:\Program Files\executable to launch.exe"

This is for use in a Citrix/Terminal Server environment, so I want to be able to call this script like this: PowerShell copythenlaunch.ps1

When I tested that, I got this:

C:\IT>powershell copythenlaunch.ps1
The term ‘copythenlaunch.ps1′ is not recognized as a cmdlet, function, operable
program, or script file. Verify the term and try again.
At line:1 char:18
+ copythenlaunch.ps1 <<<<

I kept thinking there was some problem with the install of PowerShell (I am running this particular script on a Windows 2003 Server) or that I had some illegal character in the name (it had a number in it originally) or some other simple problem.  Finally I did a search and came across this little bit of conversation:

re: Power and Pith

I just started with PowerShell.

Wanted to run some test scripts from you download.

When I tpye in Beep.ps1 I get "The term ‘Beep.1′ is not recognized….."

What Am I doing wrong?

Friday, December 29, 2006 3:17 PM by MikeL

# re: Power and Pith

> When I tpye in Beep.ps1 I get "The term ‘Beep.1′ is not recognized….."

> What Am I doing wrong?

You are relying upon a traditional bad shell behaviour that has been a security nightmere for decades.

In PowerShell, you have to be explicit if you want to run a command in the current directory.  Type ".\beep.ps1"

Jeffrey Snover [MSFT]

Windows PowerShell/MMC Architect

Visit the Windows PowerShell Team blog at:    http://blogs.msdn.com/PowerShell

Visit the Windows PowerShell ScriptCenter at:  http://www.microsoft.com/technet/scriptcenter/hubs/msh.mspx

Friday, December 29, 2006 5:19 PM by PowerShellTeam

# re: Power and Pith

Thank You for supplying the ".\*" information.  I have been racking my brain for almost two days wondering what I was doing wrong.  And to think it was as simple as using the PROPER .\yourscripthere.ps1 format.

Thank you very very much

Ditto on the thanks…

Windows PowerShell Blog : Power and Pith

When confirmation is turned on by $ConfirmPreference, you can turn it off for any individual cmdlet invocation using "-Confirm:$false".  You can also use "-Confirm:$false" to turn off default confirmation for high impact cmdlets such as Removing a Mailbox.  Another way to turn off confirmation is by setting $ConfirmPreference to "None"; you can limit the effect by setting $script:ConfirmPreference etc, see "get-help about_scope" for more details.

For more details and options besides just turning it off, go see the original post:

Windows PowerShell Blog : ConfirmPreference

$strCategory = “computer”
$strOperatingSystem = “Windows*Server*”

$objDomain = New-Object System.DirectoryServices.DirectoryEntry

$objSearcher = New-Object System.DirectoryServices.DirectorySearcher
$objSearcher.SearchRoot = $objDomain

$objSearcher.Filter = (“OperatingSystem=$strOperatingSystem”)

$colProplist = “name”
foreach ($i in $colPropList){$objSearcher.PropertiesToLoad.Add($i)}

$colResults = $objSearcher.FindAll()
Write-Host $colResults.count
foreach ($objResult in $colResults)
    {
    $objComputer = $objResult.Properties;
    $objComputer.name
    }

If you change the $strOperatingSystem = “Windows*Server*” to something like $strOperatingSystem = “Windows*”  it will return all computer accounts that have “Windows” in the Name field on the Operating System tab of the properties of the AD object:

http://blogs.msdn.com/kalleb/archive/2008/07/19/using-powershell-to-read-xml-files.aspx

Which contained the key to helping me with what I needed to do.  The specific piece I needed was in Lesson 2:

Lesson 2:
Read data from an XML-file.
The XML-file that I’m going to read from has the following structure:
<Users>
  <User>
    <Name>Kalle</Name>
</User>
  <User>
    <Name>Becker</Name>
  </User>
</Users>
Reading data from an XML-file is really easy in PowerShell! Use this command to load the file into an variable:
PS C:\Tmp> [xml]$userfile = Get-Content Accounts.xml

When the xml-file is loaded you can type “$userfile.U” and press tab to get auto completion!! It’s a breeze.

The trick is that you have to actually READ what is in front of you.  The key here is to let PowerShell know that you are reading an xml file, and that is done by placing [xml] prior to getting the content.  I missed that the first six times I read this and couldn’t figure out why I wasn’t getting the results I expected.

We don’t store or report on VMs currently, mainly because we were trying to keep track of total REAL disk used.  VMs often don’t use as much as they think they do, so that would skew the results, as well as the fact that we are reporting on the hosts. 

All of that is the reason that Patrick asked me to come up with some other tool to use for the VMs so I happened to find a few pieces of PowerShell script that I managed to put together to do a pretty good job of providing some of the info we wanted, and I thought I would share that with the 2 people who read my blog. 

$servers = Get-Content servers.txt

#Open Excel and create a new workbook and worksheet
$ExcelSheet=New-Object -comobject Excel.application   
$WorkBook=$ExcelSheet.WorkBooks.add(1)    
$WorkSheet=$WorkBook.WorkSheets.item(1)               

#Header row
$WorkSheet.cells.item(1,1)=”Computer Name”               
$WorkSheet.cells.item(1,2)=”Disk Device ID”              
$WorkSheet.cells.item(1,3)=”Volume Name”                 
$WorkSheet.cells.item(1,4)=”Size (GB)”        
$WorkSheet.cells.item(1,5)=”Free Space (GB)”
$WorkSheet.cells.item(1,6)=”Space Used (GB)”
$WorkSheet.cells.item(1,7)=”Percent Used”

$i=2

ForEach ($ComputerName in $servers)
{   
    echo "Server Name : ", $ComputerName
    $Disks = gwmi –computername $ComputerName win32_logicaldisk -filter "drivetype=3"

    foreach ($Disk in $Disks)
    {
        $Size = "{0:0.0}" -f ($Disk.Size/1GB)
        $FreeSpace = "{0:0.0}" -f ($Disk.FreeSpace/1GB)
        $Used = ([int64]$Disk.size – [int64]$Disk.freespace)
        $SpaceUsed = "{0:0.0}" -f ($Used/1GB)
        $Percent = ($Used * 100.0)/$Disk.Size
        $Percent = "{0:N0}" -f $Percent
               $WorkSheet.cells.item($i,1)=$ComputerName
            $WorkSheet.cells.item($i,2)=$Disk.deviceid
            $WorkSheet.cells.item($i,3)=$Disk.volumename
            $WorkSheet.cells.item($i,4)=$Size
            $WorkSheet.cells.item($i,5)=$FreeSpace
            $WorkSheet.cells.item($i,6)=$SpaceUsed
            $WorkSheet.cells.item($i,7)=$Percent

            $i=$i+1     
    }
}
#Show the results
$ExcelSheet.visible=$true