UPDATE:
I figured out the issue causing this. When I created my target destination, in the section where you can select tenants and/or tags, I had specified both the tenant and the tag. this caused it to match on all other tenants with that tag.
ORIGINAL:
I have a scenario where I have set up several tenant machines in my dev environment. Each tenant gets a ‘type’ tag. When I run a targeted deployment for that tag, the result is that all tenants with that tag get a deployment for each machine that has the same tag.
My Scenario:
Dev Environment: CAS1 CAS2 (Tenants, both have the tag of Cashier)
Deployment result: Both machines have folders for CAS1 and CAS2.
See screen shots: