Wow…62 views, 10 days, not a single response. My other 2 questions are just as bad.
Hey Avast; are you listening? I’m evaluating your demo to see if I want to give you my money, but my confidence in your support is falling quickly…and if you won’t support your product, I won’t buy. You’re call…
the listing \server1\xxx would lead me to believe that the volume is being accessed in “network” and “share” mode, not “local system”…I don’t think the Local System “account” can access network shares…
…so I’d be inclined to try:
a) create a user login “_avast_services”, perhaps…
b) set up file/folder permissions (perhaps a security group, depends on number of users, number of servers, folders, etc (manageability))
c) change Security Policy to allow (that new user, or group)
1) allow log on as a service
2) allow access machine via network
d) change the AVAST services credentials to start under that new user…
you’re mileage may vary…but that’s what I’d explore…(it might even help address your other post regarding where the “infection detected” message popped up (server console, rather than TS User desktop)…(although that one sounds more like configuration of alerts within the application)…