ADNM discovery task only finds installed clients

Installed ADNM last Wednesday. Everything worked great, discovery task found all machines in the domain and they were in the computer catalog with Grey icons. Did a push install on two machines as a test, again everything went smoothly.
Now, only the machines with the client installed will show up. Tried to do another discovery using Lan manager - no good. Tried to do another discovery using Active Director - no good. I searched these forums and could not find any answers either.

The machines with the client installed show up under the root computer catalog folder, not under the domain name as before.

No machines show up under the dynamic folder for uninstalled…

Please help!!

Hi, and welcome to the avast forums.

I’m not sure I understand - when the discovery task originally succeeded, it populated the Catalog with all machines in your network, right? So, then, they mysteriously disappeared? Or how come they’re not there anymore?

Thanks
Vlk

When we did the new discovery they all disappeared.

This is a Win server 2003.

and I went through the properties of the discovery task to make sure it was set to detect all computers.

Well, this is definitely not a feature of the discovery task. It should never REMOVE anything from the Catalog, just add.
It is a strange problem indeed.
What you could try is restart the avast Management Server service.

First close any ADNM consoles that may be running, then, on the AMS machine, restart the “avast! Management Server” service (Administrative Tools → Services) and finally restart the console. Then rerun the discovery task and see if it makes any difference.

BTW does the Discovery task fail, or does it say it succeeded (but just doesnt find any machines)?

Thanks
Vlk

OK we are restarting things right now. I will let you know in a little bit what happens.

Thanks for the very prompt response btw.

OK, here is what we have tried so far:

We restarted the service, reran the discovery task with all the default settings just as we did after the first install, and still only the installed clients show up.

We rebooted the server, reran the discovery task, and still…

The discovery task says that it completes successfully.

I am doing this remotely from my office via email and IM with the IT person at the customer’s location, which is quite a distance away and now the IT person on site is going to be unavailable for a couple hours, so it will be this afternoon before I can try anything else (they don’t have a VPN set up for me yet as this is a new client).

I set it up Wednesday, as mentioned above, and it worked fine for them Thursday, but Friday the catalog was gone. We really need to get the discovery figured out because pushing the install to the clients is the only practical way to do it at this location because the domain covers 4 sites in 4 different states (and I would prefer not to do a login script solution).

If you have any other ideas on what could cause the catalog to go missing, please let me know.

Here is an error message that is filling up the avast event log:

Event Type: Error
Event Source: avast!
Event Category: Client
Event ID: 90
Date: 5/7/2007
Time: 8:57:33 AM
User: N/A
Computer: BACKUPSERVER
Description:
Database command failed [CServer:CreateEngine,80040E2F]: The statement has been terminated.

The BACKUPSERVER is the machine that the ADNM is installed on. After installing the ADNM and pushing the client install to an XP Pro workstation, I then set up another installation package to install the server edition, and pushed it onto the BACKUPSERVER. Maybe that was wrong?? But it seemed to work correctly, the BACKUPSERVER appeared in the catalog with a green icon to show that everything was working.

Interesting. Can you please send the file \DATA\Log\error.log to my email address? (the address is in my forum profile).

Thanks
Vlk

OK, log sent to your email.

Here is a progress update for the forum readers…

We did manage to get the discovery task to work thanks to help from Vlk.

We had to change the properties of the task as follows:

Instead of “Detect all machines on the network” we chose “Detect machines in a specified domain” and entered the domain name into the text box.

This discovered the machines, but still separated them based on client installed or not, some going into the root computer catalog and some going into the domain subfolder.

So now we are going to change the properties to force all the machines into the root catalog folder and see how that goes.

Thanks again to Vlk for his help on this issue.