Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

8
  • You don't need CMD at all to run commands on a remote machine at all, you know that, right? Regardless of that - why did you add the tags for different PowerShell versions? Are you asking for a specific version? If not you should remove these tags. Thanks in advance. 👍🏼 Commented Nov 25, 2024 at 20:32
  • @Olaf Thank you for your response. I removed the version specific powershell tags. Here is what I'm trying to achieve. Octopus is the orchestrator - Run a ps1 command on a remote server (Step1) - Execute a bunch of other stuff, deployments etc - Run another ps1 from the same window as Step1 Commented Nov 25, 2024 at 20:35
  • I don't know octopus ... why you need to run it from the same window? If you need to run stuff in sequence just run it in sequence. 🤷🏼‍♂️ Commented Nov 25, 2024 at 20:39
  • We are trying to deploy to a VMWare capture machine. It involves running Start-AVAppCapture command, install the application and run Stop-AVTask to create the VHD file. But Stop-AVTask should be run from the same session that ran Start-AVAppCapture Commented Nov 25, 2024 at 20:43
  • I have no experiences with VMWare but I don't see the issue. You can run whatever you want from within the same script/session. 🤷🏼‍♂️ ... I guess I'm missing something. 🤔 Commented Nov 25, 2024 at 21:11