remote powershell and sql error

[ThomasMc]

I can't test most of this as it seems to not be supported in 2003 but might be worth a go

Code: Select all

# Run elevated on the computer that will be remoting into Veeam Server
Enable-WSManCredSSP Client –DelegateComputer veeam01

# Run on the Veeam Server and SQL box
Enable-WSManCredSSP Server

# Back to the client your be connecting to veeam on again
$s = New-PSSession veeam01 -Authentication CredSSP -Credential domain\UserYourRunningAs

Invoke-Command -Session $s -ScriptBlock {
   Add-PSSnapin VeeamPSSnapIn
   Get-VBRJob
}


Windows Remote Management (WinRM) supports the delegation of user credentials across multiple remote computers. The multi-hop support functionality can now use Credential Security Service Provider (CredSSP) for authentication. CredSSP enables an application to delegate the user’s credentials from the client computer to the target server.
CredSSP authentication is intended for environments where Kerberos delegation cannot be used. Support for CredSSP was added to allow a user to connect to a remote server and have the ability to access a second-hop machine, such as a file share.
For more information about CredSSP, see KB 951608.
Note WinRM clients and servers will support CredSSP authentication only with explicit credentials.
Windows XP, Windows Server 2003, and earlier: CredSSP is not supported.

[Tulror]

Hi Thomas,

Good news!

I have tested your commands and its working.

I overlooked the command "Enable-WSManCredSSP Server" which I had run only on the veeam server.
After I ran this command I get the supposed output from the Get-VBRJob.

Now I can extend my script with other command.

Thanks alot for your help!

[ThomasMc]

Excellent news

[pizzim13]

[merged]

I am seeing an issue when using powershell remoting on a veeam 6 server that has its database on a separate sql 2008r2 database server.

Code: Select all

PS H:\> New-PSSession -ComputerName "veeam" -Credential (Get-Credential) | Enter-PSSession

[veeam]: PS C:\Windows\system32> Get-VBRJob

WARNING: You should update your PowerShell to PowerShell 2.0 version.
Get-VBRJob : SQL server is not available
    + CategoryInfo          : InvalidOperation: (Veeam.Backup.Po...mmand.GetVBRJob:GetVBRJob) [Get-VBRJob], CAppExcept
   ion
    + FullyQualifiedErrorId : Backup,Veeam.Backup.PowerShell.Command.GetVBRJob


I can run Get-VBRJob locally on the Veeam server and it returns the correct results. I can run Get-VBRJob locally on a different Veeam server with a local sql db and it returns the correct results. Has anyone else seen this type of behavior?

Case [ID#5188473]

[Sethbartlett]

Check out this thread

[Gostev]

Also, did you mention what the warning says? Wasn't PowerShell remoting only added in v2?

[ThomasMc]

I think the Veeamshell checks the PsVersion from the Get-Host(or its .net counterpart) which oddly enough will say its version one on a remote session.

Code: Select all

[coor01]: PS C:\> (Get-Host).Version

Major  Minor  Build  Revision
-----  -----  -----  --------
1      0      0      0

[coor01]: PS C:\> $PSVersionTable.PsVersion

Major  Minor  Build  Revision
-----  -----  -----  --------
2      0      -1     -1


so wouldn't worry about that warning

[pizzim13]

Thanks Seth/Thomas. That worked as advertised.