2.0 no longer skips a deployment to a machine?

It seems like 1.6 would not redeploy to a machine unless the force check box was checked. Was this functionality removed from the UI in 2.0 ? I was a little surprised when I redeployed to an environment, I expected only the new machines to get a deployment but they all we updated.

Hi Eric, yes, this has been changed in 2.0.

The issue notes a variable that can be set to gain the old behaviour, but this isn’t exposed through the UI yet (discussion attached to the ticket).