Execute remote windows command within Bamboo job

[Deleted user]

I'm trying to deploy a package (install a few exes, copy files, and start a windows service) to a windows server. What's the best tool to do this? In general there are batch scripts on the test and prod servers that do everything I need. How do I run them remotely from a bamboo job?

When I was working on linux servers, I just used ssh and it worked great. But I'm working with windows servers now. I found PsExec.exe which actually does what I'm looking for on a command line. But if I run it inside a bamboo job, it just hangs.

I see the following:

---

29-Jan-2012 12:49:10Beginning to execute external process for build 'MyBuild - Default Job'

... running command line:

C:\Tools\PsExec.exe

\\myServer

-u

myDomain\myAdminUser

-p

password

ipconfig

... in: C:\bamboo-home\xml-data\build-dir\JOB-NAME\MySubfolder

29-Jan-2012 12:49:10

29-Jan-2012 12:44:48PsExec v1.98 - Execute processes remotely

29-Jan-2012 12:44:48Copyright (C) 2001-2010 Mark Russinovich

29-Jan-2012 12:44:48Sysinternals - www.sysinternals.com

hangs....

---

I had a similar problem with Powershell and solved it by adding <NUL to the end of the command, which worked great even in a Bamboo job.

So in short, what's the best way to execute a remote command within a Bamboo job? If PsExec, how do I get it to not hang?

Thansk!!

[Joe Clark · Accepted solution]

Is the bamboo agent running as a Windows service or as a user process? The first time you run psexec (or any sysinternals tool) on a computer, you'll get a EULA popup window that you need to accept. If your bamboo agent is running as a windows service, it may be hanging because it's unable to interact with the desktop to display the dialog?

You could also try fiddling with the command line parameters you pass into psexec. A quick google of "psexec hangs" should a couple of people suggesting to try using the "-d" and/or "-e" flags.

If you get stuck with psexec, you could try writing a really basic HTTP server that listens on your remote system for a command from your bamboo agent to execute the local process? Kinda hacky, though :)

[Deleted user]

Joseph - that was the exact issue!!

I was logged in as User1 and was running the PsExec as -u Admin1, which worked on the command line. But the popup that I accepted was for User1. I had to login as Admin1 to dismiss that dialog. Now Bamboo finished the job successfully.

[Joe Clark]

Nice! I'm glad you were able to sort it out :)

[MikeTrebilcock]

You can get around the EULA problem with a switch /accepteula

[Eric Hood]

Note that you have to have an updated psexec that makes use of this token.  The version I had didn't have it.  Updated to latest, and ok now.

[Bob Swift OSS (Bob Swift Atlassian Apps)]

You can run FreeSshD (http://www.freesshd.com/) on Windows/Windows server so it can be similar to what you are use to on linux.

[Deleted user]

thanks for the suggestion! I'll keep that in mind.

[Deleted user]

As a side note - I was running Bamboo as a different user than myself. So yes, the EULA that shows up the first time you run PsExec was causing the hanging.