我需要使用Azure Powershell Runbook在具有特定用户帐户的远程VM上运行启动过程
function Install-Postgres {
$username = "aact-import-vm1\aact-importer"
$password = "ChangeMe!"
$cred = New-Object System.Management.Automation.PSCredential -ArgumentList `
@($username,(ConvertTo-SecureString -String $password -AsPlainText -Force))
write-output $cred
# run pg installer
Start-Process "C:\Program Files\WindowsPowerShell\Modules\Install-Postgres\postgresql.exe" -ArgumentList `
"--mode unattended", "--unattendedmodeui none",`
"--prefix `"C:\Program Files\PostgreSQL\10`"", "--datadir `"C:\Program Files\PostgreSQL\10\data`"",
"--superpassword `"ChangeMe!`"",`
"--servicename `"postgres`"", "--serviceaccount `"postgres`"", "--servicepassword `"ChangeMe!`""`
-Wait -Credential $cred;
}
$script = Get-Content Function:\Install-Postgres
Out-File -FilePath Install.ps1 -InputObject $script
#Note that the -ScriptPath should not point to the remote path(in remote vm), it should point to the local path where you execute the command Invoke-AzureRmVMRunCommand
$output = Invoke-AzVMRunCommand -ResourceGroupName $resourceGroupName -Name $vmName -CommandId 'RunPowerShellScript' -ScriptPath Install.ps1
write-output $output.Value
#after execution, you can remove the file
Remove-Item -Path Install.ps1
上面的脚本产生以下错误:
启动过程:由于以下错误而无法运行此命令:访问被拒绝。
如果我在没有特定凭据的情况下运行上述脚本,则postgres安装程序会在日志中产生此错误:
Executing icacls "C:\Windows\Temp/postgresql_installer_1ef9b3f2c6" /T /Q /grant "WORKGROUP\aact-import-vm1$:(OI)(CI)F"
Script exit code: 1332
Script output:
Successfully processed 0 files; Failed processing 1 files
Script stderr:
WORKGROUP\aact-import-vm1**$**: No mapping between account names and security IDs was done.
请注意,符号 $ 代替了用户名。
但是,如果我在VM上运行它,则可以正常运行并在日志中生成以下行:
Executing icacls "C:\Users\aact-importer\AppData\Local\Temp\2/postgresql_installer_2662c862ff" /T /Q /grant "aact-import-vm1\aact-importer:(OI)(CI)F"
Script exit code: 0
据我所知,如果我不带凭据就远程运行Runbook脚本,则它将在NTAUTHORITY \ SYSTEM下运行,这就是为什么postgres安装程序日志中使用符号$代替用户名的原因。如果我在本地运行它,它将使用适当的用户,并且一切正常。
问题是:如何指定用户帐户在远程VM上运行启动进程?
答案 0 :(得分:0)
对于那些感兴趣的人:
在获得MS支持的调查后,他们确认Runbook(非混合)始终在NTAUTHORITY \ SYSTEM下运行