avast! on Twitter |
avast! on Facebook
avast! support forums > avast! Business Protection
Beta2 install/config/usage quirks/problems/compliments
wpn:
20-4-11 ADDED WISHES
21-4-11 ADDED Question
Ill open a new thread to post found problems and all for this Beta2 release
compliments
* Installation of IIS doesn't show the dosbox anymore, thank you, i love it!
* kudos for the improved mirror progress, still freakishly slow tho, but not really important for now
* Thank you for the context menu (right mouse-click) in the NETWORK > GROUP VIEW
* Wonderful solution for computers that you don't want to install to (unmanaged group)
Quirks
* The SQL server SEARCH button does not find any sql servers.
I used a tool from Quest software named Quest Discovery Wizard for SQL server and this tool does find the servers with the instances (but i had to point the tool towards the ip address of the server, so the not finding could be a thing on my side in my test environment).
I put the servername\instancename in the box manually and the installer accepted it, so it did connect. If the server\instance didn't exist the installer wouldn't continue either (i tested this)
Since the DB on another server is installed in either mixed mode or windows authentication, i would expect i could give in a user which to use for database access.
In the SQL authentication i cant change the SSPI and i cant give in a username so eventually the database couldnt be created (according to the log) and the installation aborted prematurely.
For this i have chosen (for this BETA) to download the express SQL again
* The silverlight page give the notification in IE 8 and IE 9 about compatibility view. This for example is not shown for Google.com, but also shows for Avast.com. Its really minor
* The log file still knows xx seconds (up to 1 minute) if the remote deployment failed or not
* TO EDIT
Problems
* Run as service logon setting: This setting is a kind of hidden and per computer setting.
In the Early beta release thread i got this answer on why there is no hierarchical tree menu like AD uses
--- Quote ---
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.
--- End quote ---
This mandatory setting (which SHOULD only be solved by using group policies in offices which use AD), which makes everything HARDER to configure for the "not-so-advanced".
So far i have not been successful deploying the client to a wide open computer.
I have given the account used for deployment (the domain/enterprise/schema administrator) the LOGON AS SERVICE rights on the client machine (manually). In the logs this is the error now:
--- Quote ---Logonuser administrator testbzw error 1385 (Logon failure: the user has not been granted the requested logon type at this computer)
--- End quote ---
* After manual installation the client computer STILL does not communicate with the SBC. Nothing in the logs accept for the vague notification SERVER DIDNT RESPOND IN TIME! (log-file: avastnet)
During installation i had to tell the installer the DNS name from my SBC machine, i did but it doesn't communicate!
(anywhere where i can look for more details or for turning on debugging?)
Questions
* In which mode should the SQL Server 2008 R2 instance be installed when its on a separate server? Mixed authentication or Windows authentication?
* will there be even more improvements on the creating mirror installation part? like a download speed indicator?
* why is there a DOMAIN option in the settings from deployment tasks? If this setting is detected automatically why do i still need to fill in the domain name in the username for deployment?
* Where are the controls of installing Webrep or Gadget in the SBC console? i dont want my users to have those installed. I can choose them to be installed or not with the manual installation, not with the deployment
* How/where can i control Safezone via SBC
* How/where can i control the firewall via SBC?
* How will updates be done for the SBC server itself?
Suggestions
* Give the unmanaged group box a different color for the titelbar and the contentcell, something light shade of red would be nice so you know those computers are unmanaged (and a possible risk)
OR!
Make the default group the unmanaged group. Found computers have no avast installed. This could be a chained task (which i know i wont use) find computer > install avast. BUt the default group is unmanaged by default since there is no automatic installation chained on it from installation of SBC..... (does that still sound clear?)
* Deploying is something WAY different then updating. Could you please seperate those in the JOBS > SCHEDULER screen?
* In the quickstart document it tells that when the computer icon is RED there is no communication OR a possible infection (found a virus).
Seperate these 2 please with different icons.
1) Show a network disconnected icon if there is no communication
2) Show a virus/bug icon if a virus has been found
Wishes
* Choice for mirror file placement! Either at installation or in the GUI. THis to be able to comply to company rules for data placement! Why would you put frequently accessed USER data on an expensive RAID setting and on the OS disk!? My extensive argumentation and idea's can be found here and here
spi:
compliments and Quirks, I agree with WPN.
I also like the Advanced Mode on Admin Setting. I know where is the logs file and the others things regarding the avast SBC installed.
PC TestI install the SBC beta 2 on XP SP3 with netframework 2, 3.5sp1, 4 | MSSQL2008 Express | IIS | Memory 1024Mb | HDD 10Gb | Workgroup name is Workgroup and running on VM
Problem
* Creating Computer discovery for Workgroup can not found any computer with others workgroup name, what i can find is only computer with workgroup name with Workgroup.
* Deployment on PC with in workgroup shown successfully but on the logs file shown that error 3 event if i do the push install on the SBC PC installed.
I have turn on the file and printer share, also turn off the firewall
Error Logs
--- Quote ---C:\Documents and Settings\All Users\Application Data\AVAST Software\Administration Console\Packages\setup.exe error 3 (The system cannot find the path specified.
--- End quote ---
Question
* Why the logs files and everythings about avast SBC is put on hidden folder (C:\Documents and Settings\All Users\Application Data\AVAST Software\Administration Console\Logs) as my experience Application Data is a hidden Folder on XP
Wish
* On the admin menu please put the link for check the logs files so we not need to open the logs files directly.
I will update more i found on this second beta when i found some problem or have question.
BTW, thanks to wpn to give me an idea for writing more structural
wpn:
@SPI
can you check your mirror directories? seems like it cant find the files in the mirror directory, if there is nothing, try running the mirror.exe file manually
Why the hidden: the directory you mention is a hidden folder, as the name states, the application should put its data in that directory
Avast fulfills to compliance rules according to the microsoft rules for application data (hence we are not allowed to adjust the current beta's to comply with the companies (avast customer!) mandatory rules for data placement)
Next to that, in XP a normal user has admin rights, you dont want a normal user to screw up this folder by accident :)
---- but only avast can clarify this for sure of course :D
my pleasure....
ive always seen the buttons above the textarea, never cared to use it... but sometimes i go crazy (no video from this, you perverts) and start hitting buttons :D
and this was the result.... i have to say i like it a lot better too... hopefully JX can appreciate it too :)
wpn:
OK.... i did another clean install from Win7 (reverted to a clean installed snapshot) now the deployment runs good....
cant figure out why since for the rest there hasnt been anything changed in settings on either side....
however in the remote install log from SBC the deployment (I monitor it by reopening the logfile every so many seconds) it shows that the setup was running at 70% for 5minutes and 50 seconds (noticed this in previous beta too)....
i looked in the client settings and found an option where you can set the ip or dnsname for the console.
THis is filled in already AND filled with the correct information, it shows the DNS name from my SBC server...
I changed the DNS to the IP, without luck... the server can be accessed without problems....
I checked with wireshark if there is any communication....
there seems to be a lot of communications between the server and the client, but only in the form of ack/sync pakkets...
cant find any data packets
would it help if i dump a communication file for the more experienced network pakket inspection people?
spi:
--- Quote from: wpn on April 20, 2011, 11:14:06 PM ---
I checked with wireshark if there is any communication....
there seems to be a lot of communications between the server and the client, but only in the form of ack/sync pakkets...
cant find any data packets
would it help if i dump a communication file for the more experienced network pakket inspection people?
--- End quote ---
share with me i have cacepilot tools, maybe can help.
Navigation
[0] Message Index
[#] Next page