术语“googet”不被识别为cmdlet、函数、脚本文件或可操作程序的名称。

Question

我按照这里中的说明在本地Windows机器上安装操作系统代理。

以下是我在PowerShell中遵循的步骤(作为管理员)：

(New-Object Net.WebClient).DownloadFile("https://dl.google.com/cloudagents/add-google-cloud-ops-agent-repo.ps1", "${env:UserProfile}\add-google-cloud-ops-agent-repo.ps1") Invoke-Expression "${env:UserProfile}\add-google-cloud-ops-agent-repo.ps1 -AlsoInstall"

一旦我执行此操作，输出是：

googet : The term 'googet' is not recognized as the name of a cmdlet, function, script file, or operable program.
Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
At C:\Users\bot_runner_01\add-google-cloud-ops-agent-repo.ps1:171 char:10
+   if (! (googet listrepos | Select-String -quiet "https://packages.cl ...
+          ~~~~~~
    + CategoryInfo          : ObjectNotFound: (googet:String) [], CommandNotFoundException
    + FullyQualifiedErrorId : CommandNotFoundException

googet : The term 'googet' is not recognized as the name of a cmdlet, function, script file, or operable program.
Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
At C:\Users\bot_runner_01\add-google-cloud-ops-agent-repo.ps1:198 char:24
+   if (! $Version -and (googet listrepos | Select-String -quiet "https ...
+                        ~~~~~~
    + CategoryInfo          : ObjectNotFound: (googet:String) [], CommandNotFoundException
    + FullyQualifiedErrorId : CommandNotFoundException

googet : The term 'googet' is not recognized as the name of a cmdlet, function, script file, or operable program.
Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
At C:\Users\bot_runner_01\add-google-cloud-ops-agent-repo.ps1:205 char:10
+   if (! (googet installed google-cloud-ops-agent 2>&1 | Select-String ...
+          ~~~~~~
    + CategoryInfo          : ObjectNotFound: (googet:String) [], CommandNotFoundException
    + FullyQualifiedErrorId : CommandNotFoundException

No changes made.

我怎么才能解决这个问题？谢谢

Answer 1

我也遇到了同样的问题，我发现在下面的页面中运行‘安装客户环境’脚本对我是有效的：环境