Hi,

thanks for the long summary of issues and suggestions you found, I’ll only address the topics I feel are critical, so sorry if something is missing.

Old name, the product was renamed quite recently. Thanks for pointing this out.

This behavior is same as in standalone avast application. We don’t feel it’s necessary to change, in fact, you like it’s similarities with the traditional avast…

On one hand, I can understand your wish to “control” applications on your computer, on other I have some counter arguments that I will shortly present here with a few options:
a) This folder name really says it all - it’s “ProgramData”. Data managed by the program. Average user (or even well above average user) really has no clue what these files contain and how they could use these.
b) The more locations your product (product sections) resides in, the harder the config&support. So, now we only have to point the user to one folder and everything interesting for the support/dev should be “here” or in it’s sub folders.
c) Workaround: If you wish to have such data on a different partition (or a physical hard drive), change the windows settings to point to a location you wish to use. All well-behaved applications should then pick up the new setting and your program data will reside elsewhere. I understand having this on a different physical hard drive can sometimes increase performance etc…
d) PS: To ease the pain a little bit, consider apps such as certain editions of Outlook or Outlook express… These even stored your emails in the ProgramData, now that’s something I would not be sure is pure “prog data”. With the mirror files, I am sure they’re in proper location.

a) Currently we don’t support AD users. Future releases may have this option, in future releases user roles will be introduced, but not for this release.
b) AD groups won’t be reflected into our product. AD groups are hierarchical, our groups are not. The product is meant to be easy to understand and handle. Tree structure is difficult to comprehend and manage for not-so-advanced user, so we decided not to support hierarchies, thus we can’t mimic this behavior of AD or other LDAP store.

A word of advice: don’t change anything here. The system should work with what ever advanced settings it was shipped with and if you don’t know what you’re changing, you could cripple the whole app… Don’t touch this, please. It’s a dangerous place and you could get your self into state where we won’t be able to help you. But you’ve read that in the dialog you had to click, right? :smiley:

No, it does not work. This operation is not supported and will not be supported at least for this major release.

Logging in trough a proxy? There are known issues in such scenarios, we’re working on fixing this.

Next beta version will contain better “bulk” actions just for this purpose, we’re currently in the process of internal testing of this.

Way too many things can go wrong - this process is quite complicated. Look into the logs (aswrinst.log and the service log) for more info, might help you a bit.

I like this, we’ll give this a tought for future release, for the time being, bear with us…

Cheers

jx