Powershell – ‘Get-WBJob’ and ‘Get-WBSummary’ unrecognised commands

powershellwindows-server-2008

I am using a script that is set to run every morning read if teh last backup failed or completed and then puts it into a html page. This works fine on all of our 2012/2012R2 servers using the

Get-WBJob

and

Get-WBSummary

commands but this doesn't work on server 2008 Is there any alternative for those commands on this server version or is syntax slightly different? Please see below for relevant parts of the script. The 2008 server is also running version 2.0 of powershell

$WBJob = Get-WBJob
$WBSummary = Get-WBSummary
$WBErrorMsg = $WBJob.ErrorDescription + "'n" + $WBSummary.DetailedMessage
$WBResult = $WBSummary.LastBackupResultHR

Best Answer

On Server 2008 you need to install it first, see https://technet.microsoft.com/en-us/library/cc732081.aspx

In the Add Features Wizard, on the Select Features page, expand Windows Server Backup Features, and then select the check boxes for Windows Server Backup and Command-line Tools.

Related Solutions

Powershell – Run PowerShell script within a maintenance plan

You can run your PowerShell script within SQL Server 2008 Agent (SQL Server's job scheduler). Using SQL Server Management Studio, create a SQL Server job and select a PowerShell job step. In the job step information specify the full path to your PowerShell script file.

Sql-server – Powershell script runs in an infinite loop when executed a certain way

Powershell seems to be sensitive to what it receives as standard input (using < to redirect stdin). It may be receiving characters it's not expecting. I would recommend removing all newlines and saving your script in notepad. So your script would look something like this:

$instance = ''; $latest_output = "Hi"; $cmd = "etc...

With the few tests I did I received different behavior according to the encoding, whitespace and characters used. May be just the way cmd redirects input.

You may also wish to post your issue to the powershell puppet project in github.

Also, you might not want to use write-host since it is a stdout to the console and may be issues as well.

On a slightly unrelated note try this:

$psi = New-Object System.Diagnostics.ProcessStartInfo;
$psi.FileName = "powershell.exe"
$psi.UseShellExecute = $false
$psi.RedirectStandardInput = $true
$p = [System.Diagnostics.Process]::Start($psi)

Hit ctrl-c then you should see something like this:

PS C:\> PS C:\>

Powershell definitely exhibits wierd behavior when it comes to input redirection.

Best Answer

Related Solutions

Powershell – Run PowerShell script within a maintenance plan

Sql-server – Powershell script runs in an infinite loop when executed a certain way

Related Topic