Showing posts with label fixing client over writes in action 1. Show all posts
Showing posts with label fixing client over writes in action 1. Show all posts

Tuesday, March 11, 2025

How to fix clients overwriting other clients in Action 1

Action 1 is a great patch management system.  However one thing you should not do is add the action 1 client when imaging, the client should always be added on after or you will need to run a script to clear a registry entry.

The issue looks like this


The client that was imaged shows up but then when the action 1 client is imaged and deployed it doesn't change a registry entry so when you have systems with the action 1 client imaged and deployed the clients over write each other in the action 1 web interface.



Uninstalling and reinstalling the action 1 client will not fix the issue however clearing the registry value should, and should not require re-installing the client.

On the affected system(s) check the registry 

HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Action1

The 'agent guid' should be unique, if not stop the service and clear the registry value; then restart the service.

You can also get the information for this fix form Action1

https://www.action1.com/documentation/distribution-with-pc-images

1) Install Action1 agent on the computer that will be the image
2) Open Start > Services > Stop 'Action1 Agent' service
3) Open Start > Regedit > Clear 'agent.guid' value

HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Action1



Crontab changes in Linux 26.04 vs previous versions

I use a small Linux server to control the turning on and shutting off our client stations with crontab.  The system I typically use is Ubunt...