Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Next challenges

Recent achievements

  • Global
  • Personal


  • Give kudos
  • Received
  • Given


  • Global

Trophy case

Kudos (beta program)

Kudos logo

You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.

View group

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Bamboo agents after migration from Windows to Linux

In preparation for migrating a production Bamboo system from Windows Server 2008 to Linux (Ubuntu) we have set up a test Bamboo system on Linux and imported the backup zip file from the existing Bamboo production system.

We have installed a remote agent on a new Windows Server 2012 machine which appears to successfully register itself with the test Bamboo system on Linux.

I am however uncertain about what steps to take next. All of the current production build plans and history have imported into the test system correctly, but of course all of the jobs that were configured to build .Net applications now fail because they cannot find an agent to run MSBuild etc.

My question therefore is:

Do I need to delete all of the .Net builds on the new test system and re-create them from scratch using the remote agent running on Windows Server 2012 - or - is there a way to 'switch' them from the previous default agent (which no longer has MSBuild capabilities as it is running on Linux) to the remote agent which does have MSBuild capabilities?

1 answer

1 accepted

1 vote
Answer accepted
rsperafico Atlassian Team Dec 22, 2016

Hello David,

You will be required to add the Microsoft capability in Bamboo to the remote agent on Windows Server 2012 machine. Once you do, you need to make sure the Microsoft tasks within the Jobs are referring to this new capability, otherwise, they will still be making reference to the capability from your previous Bamboo instance on Windows Server 2008.

Kind regards,


Hello Rafael,

Thank you for your quick response. Your answer put me on the right path. Though I did have to remove all of the capabilities from the default local agent (now Linux) first.

The remote agent appears to have an ability to 'auto detect' capabilities which now display correctly (i.e. I didn't need to add them).

Once the above was complete, jobs then declared no agent can run this job. I needed to go through each of them to select the respective MSBuild executable from the drop-down list in all MSBuild task(s).

Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Bamboo

Bamboo 7.1 is here and is packed with value!

I'm happy to announce that Bamboo 7.1 has been released and it’s overflowing with awesome new features. Top-voted issues First and foremost, a bunch of JAC top voted issues has been delivered - y...

943 views 4 7
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you