Author Topic: Workgroup Discovery issue  (Read 3351 times)

0 Members and 1 Guest are viewing this topic.

pascal.g

  • Guest
Workgroup Discovery issue
« on: August 17, 2011, 12:24:03 PM »
Hi,

We installed avast! BP on a network with AD. BP is installed on the DC, running SBS 2011, which is running on an Hyper-V with Windows 2008 Server R2.

No problem whatsoever with domain discovery. However, we need to use the workgroup discovery for the Hyper-V PC which is not in the domain.

When we do that, the task ends without errors, but doesn't find the Windows 2008 Server R2 PC, so for now, we installed the managed client manually on stand-alone.

There's no other noticeable problem with the network and communication between the servers, so why isn't it detected?

Offline lukas.hasik

  • Moderator
  • Advanced Poster
  • *
  • Posts: 931
  • Product manager of Avast Security for Windows
Re: Workgroup Discovery issue
« Reply #1 on: August 17, 2011, 11:35:47 PM »
AFAIK - workgroup discovery looks to network neibrhood and AD discovery looks in AD.
However you can always add the computer "manually". Use the Add Computer button at Network tab.
Quality is also a feature.

pascal.g

  • Guest
Re: Workgroup Discovery issue
« Reply #2 on: August 18, 2011, 08:34:59 AM »
We added the computer manually and installed the managed client also manually, but it doesn't communicate with the console.
This doesn't really surprise me, since the computer using Hyper-V should've been found by the Workgroup discovery (we can see it in the network from the SBS, under the same workgroup).
Am I missing something here?