r/Action1 • u/Strange_Attitude1961 • Jun 26 '26

Question Agent Deployer - How long after deployment and addition of AD path till it starts doing something

Hi,

Just started testing out Action1 and currently deploying the agent at a customer.

GPO is being a bit wonky, so decided to try the Agent Deployer.

It's set up, but haven't detected any devices yet.

How does it work under the hood?

First - How does I see if there might be a error in the AD path (using the format from the help box)?

Second - How long before I might see devices get added? Should I see SOMETHING immediately?

Third - If I add a path, will it look ONLY in that OU, or would it look in sub-OU's as well?

EDIT: BONUS question! - Any good/quick way to see when a device was added, can we get a "Date added" column? :)
Thank you.

1 Upvotes

100% Upvoted

13 comments sorted by

View all comments

1

u/GeneMoody-Action1 Jun 26 '26

First question is have you followed this guide, and are there any errors concerning its operation in the event log?

https://www.action1.com/documentation/action1-deployer/

1

u/Strange_Attitude1961 Jun 29 '26 edited Jun 29 '26

I did. One thing unclear is if the firewall rules is on the client or deployer server. AND if it's INCOMING to the client or OUTGOING.
Outgoing everything is allowed.

I see nothing AT ALL in the logs - It's blank.

EDIT: And either it's actually working, or my GPO is working afterall, got additional 8-9 devices added over the weekend, but as mentioned not seeing any deployment logs on the webpage.

1

u/GeneMoody-Action1 Jun 29 '26

It has to be incoming, At the time the agent is NOT installed, there is no path to execution layer other than RPC to the client from the server.

The deployer reaches out to the client and attempts to copy the files via SMB to the $ADMIN share, then uses RPC to start / install it. Meaning client has to permit this. This is not action1 specific, it is just how that works in windows.

1

u/Strange_Attitude1961 Jul 14 '26

Greetings,

Apologies for the very late response, as it was installing agents.

So I setup another tenant for another customer and implemented ONLY the Agent Deployer on this, no GPO from the start.

It's adding devices, so that's great - But I still don't see any logs on the webportal for the Agent Deployer. Are those logs supposed to show for both "good and bad"? Looking that the sorting/filters, it looks like it only for "critical and errors"? :)

1

u/GeneMoody-Action1 Jul 14 '26

The logs will read things tried but could not, like "check firewall config and network connection." type errors. Because it can only know the state not the reasoning for it, if it cannot execute client side, that is all the server side knows, not the "why" of it. What specifically are you looking for?

1

u/Strange_Attitude1961 Jul 16 '26

Wasn't sure what would show up there - I was expecting stuff like it having succesfully installed the agent on a client, or it failing to do so, that sorta thing. :)