NetXMS Forum

Thanks again Alex.

Unfortunately I seem to be only able to run version 3.0.2258, as I haven't had the chance to test later net files etc.

Hopefully all of this information will help other users.

Regards
Chris

Hi Alex
Sorry for the delay in responding, have been away in remote areas doing service calls etc.
That helped me fix the issue.
For anyone else having the same issue, I would recommend delete the databse file from your master image, then new id will be created with the new database.
In my case where we had already deployed and the units were remote and I couldn't delete the database file, as it was in use by the agent I resolved as follows.

1. edit the agent file and add
   DataDirectory = c:\netxms\lib
   under the ConfigIncludeDir section.
2. MAKE SURE you save the agent file.
3. Restart the agent and adopt with the new agent id.

Hope this helps anyone else in the same situation.

I am currently creating my own solution with netxms, as I hadn't realised you already had an ATM solution.
Our machines don't appear to be supported.

I will PM after speaking to our management to discuss further.

Thanks again for your help.

Unfortunately we are looking after older xp/7 windows systems, due to being ATM machines.
We have some images of hard drives, which we are using to upgrade to ssd drives, but this is causing duplicate agent id.
How can we generate a new agent id ?

Thanks
Chris