Second, i have a Question, when i run update-tasks on my clients via ADNM it takes ages until the status of the tasks changes from waiting to processing or done/failed. It usually takes about 5 minutes before an update-task is started on the client, sometimes even longer, the tasks normally run for about 30 minuts until the update is completed or fails, is that normal?
I currently have one update-task on a machine that is running since 12:11 pm and now it’s 1:30 pm and it still has it’s status set to waiting, the client is up and has last communicated with the ADNM-server some minutes ago.
I have the same on a client of mine and I do have a theory. I think it has to do with the configured time for communications “every x seconds”, between the server and clients. The more often the server and clients communicate the more traffic you’ll have of course on your net. I haven’t tested it yet though.
This of course, if it applies, would only reduce the amount of time between “waiting” and “processing”. In my understanding “waiting” is the state in which the communication between server and client has not taken place.
You could try reducing the time between communications and also check the settings for push and pop communications. Check the ADNM Manual for where those settings are and what exactly they do.