rful011
November 30th, 2008, 08:48 PM
We have a large nod32 installation (roughly 10K clients, currently 2.7 and working on upgrading...). After a year of using Nod we are generally very pleased but their is one small fly in the ointment (isn't there always? ;)
We are a large university comprised of 7 different faculties and central organisation all of which run their own desktop support organisations and AD domains. We do not generally use netbios names to identify machine but rather use static IP addresses and FQDNs. THis leads to problems with nod's reporting as everything is tied to netbios names :(
I have just discovered that when I generate a client report (CSV) the IP address is not included (even though I have it displayed in RA client tab). This is a serious issue as I want to analyse the alert reports daily and flag machines that need human attention. To do this in an automated fashion I really need the IP address of the machine, not just its netbios name.
Can anyone help?
Cheers, Russell
We are a large university comprised of 7 different faculties and central organisation all of which run their own desktop support organisations and AD domains. We do not generally use netbios names to identify machine but rather use static IP addresses and FQDNs. THis leads to problems with nod's reporting as everything is tied to netbios names :(
I have just discovered that when I generate a client report (CSV) the IP address is not included (even though I have it displayed in RA client tab). This is a serious issue as I want to analyse the alert reports daily and flag machines that need human attention. To do this in an automated fashion I really need the IP address of the machine, not just its netbios name.
Can anyone help?
Cheers, Russell