I have scattered machines that install manually just fine but show up as a “key” in ADNM. the client says all is running. I am in the middle of deploying, mostly pushing out through ADNM but some are manually installed from a share. We have 180 licenses and only about 10 machines deployed. The catalog has a load of machines without the agent as it scanned my AD but that should NOT meant hey are using a license. HELP!!!
As far as I know that’s normal behavior, I’ve seen it too. It detects my Linux systems, but since they’re in ADNM they’re a license. After every discovery task I have to remember to clear out Linux machines. Really hope the next version (whenever that is…) addresses that.
Hi Jbogut,
is your PC on the network is larger then your license? if Yes, just ignore the “key” icon in ADNM.
key icon in ADNM is mean that your license have not enough for detected PC.
My suggestion is don’t run the discover network just add manually all computer you want to install the avast! antivirus.
for doing deployment push installation, please make sure that all of the PC have disable the firewall and your local policy on the security option have been set to “Classic - local users authenticate as themselves”
to disable the firewall i believe is easy, and to change the local policy use the step below here:
Windows XP Professional
go to Administrative Tools and select ‘Local Security Policy’
select ‘Local Policies|Security Options|Network access: Sharing and security model for local accounts’
select ‘Classic - local users authenticate as themselves’
click ‘OK’.
Windows 2003 member server
go to Administrative Tools and select ‘Local Security Policy’
select ‘Local Policies|Security Options|Network access: Sharing and security model for local accounts’
enable ‘Define this policy setting:’
select ‘Classic - local users authenticate as themselves’
click ‘OK’.
Windows 2003 domain controller
go to Administrative Tools and select ‘Domain Controller Security Policy’
select ‘Local Policies|Security Options|Network access: Sharing and security model for local accounts’
tick ‘Define this policy setting:’
select ‘Classic - local users authenticate as themselves’
click ‘OK’.
have a nice day ;p
thanks, I had run the discovery already so I was screwed there. You can’t ignore the key because you cannot manage the computer which has it. I ended up deleting a load of “detected” machines…I assume the discovery is by SID because it pulled in machines we haven’t had here for 5+ years!..now it seems OK…thanks!