powershell-2.0

I have the following: $aMyArray = $null [xml]$userfile = Get-Content C:\AppSense\Scripts\AmPolicyConversion\AM_dev.xml $i = 0 FOREACH ($j in $userfile.ChildNodes){ FOREACH($k in $j.DocumentElement) { } $i = $i + 1 } I am trying to figure out how to loop through each element within powershell. Then check for an attribute of SID on the element. If exists get attribute value and put that value into an object and for the same element grab second attribute DISPLAYNAME and place into same object. We will create an array of objects. I know I am way off but hope you can help. Use XPATH instead to find

I am trying to pass array of arguments to powershell script file. I was trying to pass the commandline like this in command line. Powershell -file "InvokeBuildscript.ps1" "z:\" "Component1","component2" But it doesn't take the parameters it seems. What am i missing? how to pass array of arguments? Short answer: More double quotes could help... suppose the script is "test.ps1" param( [Parameter(Mandatory=$False)] [string[]] $input_values=@() ) $PSBoundParameters Suppose would like to pass the array @(123,"abc","x,y,z") Under Powershell console, to pass multiple values as an array .\test.ps1

I'm running Windows 7 with PowerShell 2 installed. I've downloaded version 2.1 from here - http://pscx.codeplex.com/releases The Release notes say unblock the zip file - {which I did} extract the contents of the ZIP file to your $env:Home\Documents\WindowsPowerShell\Modules folder I was unsure what $env:Home was so a bit of searching determined that the release notes are expecting an environment variable called Home which doesn't exist on my machine. A bit more searching says use what is defined as ~ on my machine. So in a PS prompt I run cd ~ Which on my machine led to a network drive U: I

I'm writing a powershell v2 script that I'd like to run against a remote server. When I run it, I get the error : Connecting to remote server failed with the following error message : The WinRM client cannot process the request. Unencrypted traffic is currently disabled in the client configuration. Change the client configurati on and try the request again. For more information, see the about_ Remote_Troubleshooting Help topic. I looked at the online help for about _ Remote_Troubleshooting, but it didn't point me towards how to enable unecrypted traffic. Below is the script that I'm using that