Terminating errors are errors that result in an exception being raised. When an exception is raised the current script block will immediately stop. Those errors are the kinds of errors that are caught using the catch part of the try/catch statement. An example of a terminating error is if you divide by something by 0. i.e. if you run this script block:


{
1 / (1-1)
'This will never execute'
}


you will never see the ‘This will never execute’ string because the script terminates when it attempts to divide a value by zero.

Non-terminating errors are errors that do not cause a script to terminate. These types of errors are not catchable using try/catch statements unless you specifically tell PowerShell that you want them to be treated as terminating errors. For example, consider this script block:


{
Get-Command -Invalid Value
'Hello'
}


If you did not want the second command to execute if the first command returns an error you would either have to add “-ErrorAction Stop” to the end of the first command (instructing PowerShell to treat errors from that command as terminating errors) or you would have to insert “$ErrorActionPreference = ‘Stop’” before the first command (instructing PowerShell to treat all errors in that script block as terminating errors). Either of these will allow you to catch those errors in the catch portion of your try/catch statement. The only other alternative is to specifically check to see if a command raised an error or not, like this:


{
Get-Command -Invalid Value
if ($?) {
'Hello'
}
}


Hope this helps.

many thanks

Another question. I tried the error handler with the try catch block. if we have 2 command in the try block,and the first command in try generates an error, process execute the block catch but execute after the 2 command.

Should there be a specific process to go into catch block and not execute next command in block try?

try{

command 1
command 2

}catch{
write host …

}

The reason your parameters are being treated as part of the array is because of the commas you use between them. In many programming languages, commas are used to separate parameters in function calls. This is not the case for PowerShell. You can separate parameters with spaces, or you can pass in the parameters by name. Also switch parameters are not the same as boolean parameters. If you want them, you include the switch. If you don’t, you simply leave it out. For the New-LocalUser function, with the values you have specified, you would do this:

$password = ConvertTo-SecureString -String passwordUser -AsPlainText -Force
New-LocalUser -Name @(‘A’) -Password $password -FullName ‘FullName 102′ -Description ‘Description 102′ -PasswordNeverExpires -ComputerName @(‘RDN5V197′) -Credential administrateur

This will prompt you for a password for your administrateur account when you run it. If you don’t want the prompt, you could replace administrateur with $TempCredential as you have in your example script.

I hope this helps. Let me know if you have any additional questions.

Kirk out.

i use function New-LocalUser from your Network.powerpack. Very nice code !!

however, when i call it, the first parameter which is a string array of users ( i think), has the value “A,”",FullName 102,description 102, ,”False” ,”False” ,”True”, “False”, @(“RDN5V197″), $null”, corresponding to all the parameters.

i call it with the following way :

$password = “mypassword” -asSecureString
$tempCredential = New-Object System.Management.Automation.PsCredential “administrateur”,$password
$password = $tempCredential.GetNetworkCredential().Password

New-LocalUser @(“A”),”passwordUser” , “FullName 102″, “description 102″ ,”False” ,”False” ,”True”, “False”, @(“RDN5V197″), $tempCredential

is it possible for you to answer me with an exemple call of this function ?

Marco