reboot a list of servers and output results to file.

psnewbie2013 — Mon, 20 May 2013 05:00:00 GMT

I am new to powershell and i am trying to write a simple script that will reboot a list of machines (XP, and 7) and input the results of the reboots to a text file. I created the below script that reboots the machine and creates the output file, but when I open the file I do not see any results in it.

restart-computer (get-content c:\reboot\rebootlist.txt) | out-file -filepath c:\results.txt

I also found the below script but for some reason it will not work, but it's not rebooting the machines. I can get it to show me the list of machines in the text file but it does not reboot them. My plan was to get it working and output the results to a file, but it's not working out for me.

Get-Content C:\reboot\rebootlist.txt |
   Where {test-connection $_ -quiet -count 2} |
   foreach {
    write-host "Restarting $_ "-force "Green"
    Restart-Computer $_ -force -whatif}

Please let me know if you have any suggestions.

Import-PSSession, bug or bug-like feature?

JMMurrah — Fri, 17 May 2013 05:00:00 GMT

Good Morning,

I've come across a strange error with the import-pssession cmdlet, and wanted to run it by the experts. I'm using it in a larger account creation script the import the exchange cmdlets from an exchange server to create a mailbox. In testing it all in the shell the below commands work fine:

$session = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri http://$exchangeserver/powershell

Import-PSSession -session $session -AllowClobber -DisableNameChecking

However, when I run them in my larger script, I get the below error:

Import-PSSession : Cannot convert null to type "System.DateTime".

At C:\scripts\importbug.ps1:8 char:5

+ Import-PSSession -session $session -AllowClobber -DisableNameChecking

+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

+ CategoryInfo : MetadataError: (:) [Import-PSSession], ArgumentTransformationMetadataException

+ FullyQualifiedErrorId : RuntimeException,Microsoft.PowerShell.Commands.ImportPSSessionCommand

Now I couldn't for the life of me figure out what Import-PSSession would be doing with any dateTime values, or even what null variable I was passing to it. After deconstructing my script I narrowed it down the following minimum code to illustrate the error:

Function Get-Exchangecmdlets {

param(

[string]$ExchangeServer,

[datetime]$date

)

$session = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri http://$exchangeserver/powershell -AllowRedirection -Authentication Kerberos

Import-PSSession -session $session -AllowClobber -DisableNameChecking

}

Get-Exchangecmdlets -ExchangeServer 'exchangeserver1' #This throws the error

Get-Exchangecmdlets -ExchangeServer 'exchangeserver1' -Date "10/10/2013" #This does not

So it seems that when import-pssession runs, it validates all the variables in its parent function. Since $Date wasn't specified, it was null, which can't be converted to DateTime, hence the error. This error also appeared with parameters using the [validatescript] setting, such as:

Function Get-Exchangecmdlets {

[cmdletbinding()]

param(

[string]$ExchangeServer,

[ValidateScript({test-path (Split-Path -Path $_ -Parent)})]

[string]$ErrorLog

)

$session = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri http://$exchangeserver/powershell -AllowRedirection -Authentication Kerberos

Import-PSSession -session $session -AllowClobber -DisableNameChecking

}

Get-Exchangecmdlets -ExchangeServer 'exchangeserver1' #This throws the error

Import-PSSession : Cannot bind argument to parameter 'Path' because it is an empty string.

At C:\scripts\importbug.ps1:10 char:5

+ Import-PSSession -session $session -AllowClobber -DisableNameChecking

+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

+ CategoryInfo : InvalidData: (:) [Import-PSSession], ParameterBindingValidationException

+ FullyQualifiedErrorId : ParameterArgumentValidationErrorEmptyStringNotAllowed,Microsoft.PowerShell.Commands.ImportPSSessionCommand

I didn’t test the other validation methods, but I suspect they’ll all throw the error.

Once identified this is easy enough to work around, I simply made a separate function for the import-pssession with no optional parameters and no validation. However, since optional parameters should only be validated if a value is provided, this seems rather bug-like to me. Nothing in the documentation for Import-PSSession jumped out at me as suggesting that variables are re-processed or anything like that.

Thoughts?

Need to get the exit code when I run this script, I didn't get any exit code or error level

Juan Pablo — Wed, 01 Feb 2012 06:00:00 GMT

I'm running the following script and need to get a error level or exit code to run another script and stop a window service if this script find the event 560, but even if the script find any event or not, I get the exit code or error level 0, I have try many different things like writing exit, but now i'm just closed of everything.. I will appreciate any help a lot.

$timevar = Get-Date

$timevar = $timevar.AddHours(-.05)

get-eventlog security -after $timevar |where {$_.eventID -eq 560} |where {$_.Message -like "*READ_CONTROL*"} |where {$_.Message -like "*WRITE_DAC*"} |where {$_.Message -like "*Volume3\Esker_Test*"}

Thanks in advance.

Search results for 'sectionid:230' matching tag '#errorlevel'

reboot a list of servers and output results to file.

Import-PSSession, bug or bug-like feature?

Need to get the exit code when I run this script, I didn't get any exit code or error level