At 3.00 am this morning the ‘find computers’ task ran.
It found a computer called ‘tsclient’ with name Microsoft Terminal Services.
We use TS and have done for over a year.
We have used Avast for nearly three months, having purchased and licenced a corporate solution a few weeks back.
We normally use the windows RDC to connect to the server, but yesterday I was trialling the tsweb connection.
My guess is that the tsweb connection has somehow triggered this, but I am unsure of the significance of finding this ‘computer’.
Any ideas??
Thanks
Matt
PS I like this software and I like these forums - I have used them a few times already to get some answers.
Delay - no probs. This new computer is grey, doesn’t affect functionality as far as I can tell.
For our network generally I don’t use a domain, and we have no active directory established. Detection method is NT LAN Manager.
Workkgroup/ domain AMS detects in is “Microsoft Terminal Services”.
The ‘computer’ tsclient does show in the Network Neighbourhood. (My network places → Entire Network → Microsoft Terminal Services). This reminded me that I have also recently added ‘map local drives on connection’ for my TS logon only (no other logons), my local drives are the only drives shown in this area. So perhaps this is related. I am logged on daily for most of each day, mutiple logons throughout the day.
The ADNM shows last communication date as ‘undefined’.
Hmm, I don’t think you have to worry about this… I don’t see a way we could filter the machine out of the Discovery task result set (if the Network Neighborhood thing is showing it as well).
If I were you I’d just create a group in the Catalog for it and move the machine to it, so that it doesn’t distract you…
Or, if your network is more or less static, you can delete the weekly schedule for the Discovery task.
