1

I am in the middle of an AD migration and just setting up with Action1. I am planning to deploy agents via the deployer but I am unsure if the agent can span across forests? Or if I need a deployer per forest?

If I need 1 per forest do I need to create another organization and have seperate deployer installers? or can I use the same deployer on multiple domains?

One final question, If I need seperate organizations/deployer installers… What happens when my users machine migrates to the new domain? Will it still be linked to the original organization?

Thanks.

5 Spice ups
2

the Action1 Deployment agent doesn’t care about your domains.

Organizations (in action1) is simply a way to organize for management of devices.
If you do or don’t set this up its really your choice, but I would say best practice is to create an Origination in Action1 for each real world Organization you support, Then onboard the endpoints to the matching “logical” organization in action1.

4 Spice ups
3

You can use GPOs to push the agents, this might give you greater control.

As for the specific ‘deployer’ it’s also not required per domain, so long as credentials you use can reach the other domains. The credentials must be able to read AD, no domain write or DA accounts needed, but credentials must be available to each endpoint.

If your accounts are completely separate, then you may need a deployer per domain.

TL:DR
So long as the credentials you use can talk to both domain endpoints, one deployer will do the job.

4 Spice ups
4

Thanks for the advice. Do you know if I will need to install a deployer on servers on both domains? Or can it see both forests (via a two way trust)? Pressume client admin permissions for each domain could be an issue.

I pressume if I wanted to filter it by an OU on each domain then I would need 2 deployers?

3 Spice ups
5

Thanks Rod, just saw your reply.

I think I am going to be best to deploy 2 deployers in that case so I can have better control. I pressume the same installer will be ok and clients will all be grouped in the same Action1 organization?

3 Spice ups
6

I don’t have a multi-domain setup to confirm, but I assume this would be fine since it’s bound to your tenant in Action1.

As for clients being grouped - you setup the groups using rules, so if you want domain1\clients and domain2\clients in the ‘clients’ bucket, then you can do this in the settings for each group.

You could also split them by domain, hardware type, CPU model, or a variety of other attributes if you want to.

4 Spice ups
7

FYI, you can add the agent to your gold image or templates if VMs, but you need to do so in a specific way.

4 Spice ups
8

Appreciate the answers, will start testing this now and shout out if I have any further questions.

3 Spice ups
9

Action1 Deployer | Action1 Documentation

Plenty of documentation over here too

4 Spice ups
10

You need to install the agent on every device you want to show up in action1.

That depends on what you mean by deployer. But if you mean installer that you generated from Action1 and you want to automate the devices (each domain) assigning to an Organization in action1, then yes. You need to generate an installer file for each of your two Action1 Organizations.

3 Spice ups
11

@molan

A deployer is a special agent that scans the network and deploys the scanning agent to devices automatically, ideal for multiple domains or devices that are not domain joined.

It’s different to the scanning agent that goes on each device - the deployer watches for devices without an agent and puts one on.

5 Spice ups
12

and I just learned something new :slight_smile:

5 Spice ups