Hi Marc

I was in the same situation. What I did:

1. run instance and RDP to it
2. change password for Bamboo user (u need to know it)
3. go to Scheduler disable existing task which starts bamboo-agent and create similar one which runs every e.g minute (it needs to have only one instance so make sure it won't start many instances, you can find it in task settings). This task needs to be executed by Bamboo user (that is why you need password)
4. go to EC2Config (in windows on your instance) YOU NEED to change settings for Administrator password, then you are ready for next step
5. install what you need to install
6. go to EC2 console and to you instances page
7. create new image from running instance
8. when new image is created go to Bamboo setting and create new image settings which point AMI to your new image.
9. and then be happy

I don't know if this is the right thing to do. Can someone from Atlassian team confirm if that is OK to do?

You can add an image configuration with ami-1f750268 for Ireland.
and once you set up the image capabilites correctly, everything should work fine.

Hello, we are the clients to find this bug.
We are using the EU Ireland region and our Bamboo image configuration uses another windows stock image that is not fixed according to the list above.
Our windows stock image is:

Can you pls advise if we have to change regions of what we have to do to set one of the fixed AMI as our stock windows image.

thanks Marc Miller

Fixed images:

image.US_EAST_1.EBS.x86_64.windows.Windows\ 2008=ami-976edafe
image.ASIA_PACIFIC_SE_1.EBS.x86_64.windows.Windows=ami-c21a2390
image.SOUTH_AMERICA_1.EBS.x86_64.windows.Windows=ami-f550d6e8
image.US_EAST_1.EBS.x86_64.windows.Windows=ami-50697038
image.EU_CENTRAL_1.EBS.x86_64.windows.Windows=ami-e0f4cafd
image.EU_WEST_1.EBS.x86_64.windows.Windows=ami-1f750268
image.US_WEST_2.EBS.x86_64.windows.Windows=ami-77764b47
image.ASIA_PACIFIC_NE_1.EBS.x86_64.windows.Windows=ami-b4f520b4
image.ASIA_PACIFIC_SE_2.EBS.x86_64.windows.Windows=ami-fb81ffc1
image.US_WEST_1.EBS.x86_64.windows.Windows=ami-6b3bd22f

Scheduler runs C:\Users\Bamboo\start-agent.bat that sets some variables and then calls C:\opt\bamboo-elastic-agent\bin\bamboo-elastic-agent.bat.
I'd use C:\Users\Bamboo\start-agent.bat.

The script is C:\opt\bamboo-elastic-agent\bin\bamboo-elastic-agent.bat .

It's not in the C:\Users\Bamboo\ but it uses this directory.
Running it as any user other than Bamboo won't work.

dan.austin scheduler should have run a script that is in C:\Users\Bamboo\ directory as Bamboo user.
I don't remember exact name right now, but it should be obvious. If you can run it as Bamboo user it's even better.

Is there any way to manually start the agent after RDP'ing into it? I looked in Control Panel>Add/Remove Programs to see if the agent was installed. I didn't see it there. Should I see it there?

Service is run by Bamboo user, its password has expired (after default 42 days...). That's why service will not run.

Administrator user has 'password never expires'.
Bamboo user has not 'password never expires' (though should have) - error in script?

I'll check script and we need to regenerate windows images.

I can see no workaround that would allow us to start agent on old image now.

532: Logon failure: the specified account password has expired.