Expert Commentary: 2012 Scripting Games Advanced Event 6

re: Expert Commentary: 2012 Scripting Games Advanced Event 6

Jan Egil Ring — Sun, 29 Apr 2012 09:59:32 GMT

@K_Schulte @Srisas I made some customizations to the script, so the line numbers I mentioned above is incorrect. The correct numbers from the original script is 61 and 66.

I also forgot line 83:

ComputerName = $result.__server;

One additional tip: You may want to use Unicode encoding on Export-Csv:

$outputObject | Export-Csv $outputPath -NoTypeInformation -Encoding Unicode

re: Expert Commentary: 2012 Scripting Games Advanced Event 6

Jan Egil Ring — Sun, 29 Apr 2012 09:46:23 GMT

@K_Schulte @Srisas To make it work in V2, do the following changes:

Line #63: $output = @(Wait-Job $j | ForEach-Object {Receive-Job $_})

Explanation: In PowerShell 3.0 we got a new feature called "Property Unrolling", which made this line work in V3 without using a foreach:

www.nivot.org/.../PowerShell-30%E2%80%93Now-with-Property-Unrolling!.aspx

Line #71: Write-Progress -Activity "Processing" -Status $result.__server

Explanation: Like Jason Hofferle said; In PowerShell 3.0, the __Server property will have a PSComputerName alias for consistency.

re: Expert Commentary: 2012 Scripting Games Advanced Event 6

Srisas — Fri, 27 Apr 2012 10:09:35 GMT

On Powershell V3, $output = @(Wait-Job $j | Receive-Job) also worked fine. The script as provided by Lee works fine with Powershell V3, but gives the errors mentioned in the comment by @K_Schulte in Powershell V2.

re: Expert Commentary: 2012 Scripting Games Advanced Event 6

Lee Holmes [MSFT] — Fri, 27 Apr 2012 03:23:42 GMT

@Jason and @mjolinor - It requires only WMI to be enabled. Not PowerShell Remoting. Can you file a doc bug on connect.microsoft.com/PowerShell

re: Expert Commentary: 2012 Scripting Games Advanced Event 6

mjolinor — Thu, 26 Apr 2012 17:15:35 GMT

I didn't use background jobs. After reading, as Jason did, that using -AsJob requires remoting on both the local and target systems. I'd read Ed's hints that he'd posted the day before and noted that the scenario did not specify that I could expect all the servers to be 2008R2 with remoting enabled. That caused me to think that using that as a solution might produce a failing grade if it was tested against W2K servers.

re: Expert Commentary: 2012 Scripting Games Advanced Event 6

Srisas — Thu, 26 Apr 2012 03:27:24 GMT

Thanks, Jason. Yes, Powershell 3.0 does have this alias, was trying out the solution on Powershell 2.0 ( which is what I used for the Scripting Games ) and this alias is not present in 2.0.

re: Expert Commentary: 2012 Scripting Games Advanced Event 6

Jason Hofferle — Wed, 25 Apr 2012 13:09:38 GMT

The help for Get-WmiObject notes the following for the -AsJob parameter:

Note: To use this parameter with remote computers, the local and remote computers must be configured for remoting. Additionally,

you must start Windows PowerShell by using the "Run as administrator" option in Windows Vista and later versions of Windows,. For

more information, see about_Remote_Requirements.

Srisas: In PowerShell 3.0, the __Server property will have a PSComputerName alias for consistency.

re: Expert Commentary: 2012 Scripting Games Advanced Event 6

Cruz_Daniel — Tue, 24 Apr 2012 15:22:33 GMT

This makes me feel good about using Jobs in my entry but I can see I have a bit to learn. This is a good one.

re: Expert Commentary: 2012 Scripting Games Advanced Event 6

Srisas — Tue, 24 Apr 2012 10:12:29 GMT

I believe Get-WmiObject does not use the remoting infrastructure, hence the PSComputerName property will not be available in the result, we can use the __SERVER property instead. Otherwise, as @K_Schulte mentioned, we get an error in Write-Progress, and the excel file created does not contain the computer name.

re: Expert Commentary: 2012 Scripting Games Advanced Event 6

Srisas — Tue, 24 Apr 2012 09:12:43 GMT

I am seeing similar results as @K_Schulte. With more than 1 machine, $output is empty. The following also does not return anything

$j | Receive-Job

whereas Receive-Job -job $j works fine.

If the ChildJobs.Count is more than 1, this behavior is observed. If only 1 machine is specified ( ChildJobs.Count is 1 ), output is displayed properly.