EDITED 25-01-2012I would like to dedicate this thread for requesting features for (near) future updates on the SBC.
Features that are not present yet and not bugs in the current version.
Some features are taken from this thread:
http://forum.avast.com/index.php?topic=54073.01) Active Directory integration for controlling access to SBC.
I heard this is possibly a future feature. Just pointing out that this product is completely
MS based and therefor should be able to have maximum integration. This means user access based
on domain groups/users instead of locally maintained sbc users.
2)
Offline VPS updates so SBC doesnt need to be hooked up to the internet for updates. Some users require this kind of setup, already noticed years back on the forum for ADNM.
A ship is an example i still remember, it communicates via a private network not hooked up to
the internet.
3)
MSI file creation for other kind of deployment then using the CONSOLE. Possibly for restrictions on account rights with logon as service. This is not needed when the
installation is locally executed without control from the SBC i believe?
4) SBC to SBC migration tool, if the SBC crashes, how can we change the server that is used for
updating without redeploying the client? In ADNM this was done with ASWCHAMS.EXE
5) Mobile device support (Android, iphone, WP7)
6) Linux / Mac support for deployment
7)
Installer:
SQL portion should contain the following: a) A search algorithm that detect the server as well as the instances on the server
b) A possibility to set the windows account that will be used to create the database
c) A test button to test if the given server\instance and account are correct
8 )
Installer:
E-mail portion should contain the following: a) a test button to check if the given settings are correct
b) a report section about the email server (which software it is and if the test was
successful)
9)
Installer:
Mirror portion: A base directory setting which populates the different directory paths which have to be
manually edited if you decide to install the mirror on another place then c:\programdata\
The possibility to have one of the directories (like the logs) to be set to a different
location then the base directory should stay possible. A lot of companies dictate that log
files should not be kept on the same disk as user data.
10)
SBC mirror servers inside the local network. See the comments from Yanto below and
http://forum.avast.com/index.php?topic=79766.011)
Control the client LOCALE setting. I do not wish to see dutch translations in software that I only will look into.
I have never seen any translation that is good enough for an English based product (hence my
disgust of having the OS in the country native language)
I had this wish in the early beta version and my wishlist i believe, there one of the mods
seemed to be interested in this.
12) (e-mail) Notification of newly ready update for the console itself
Extracted from this thread:
http://forum.avast.com/index.php?topic=82084.013) The ability to set the port for ISS that the console should use during installation already
so there will be no problems with other sites already running on that port.
14) All shields controllable via normal GUI instead of partially with advanced settings
15) Adjustable e-mail template for deployment
http://forum.avast.com/index.php?topic=83033.0
16) Apply a any task, to a single computer object without having to modify the job
settings. This was possible in ADNM, and is a heap more efficient then having to modify the
job properties every single time.
So right click on the computer in the context menu should be an option with the name JOBS
and list the defined jobs, for example DEPLOY CLIENT or UNINSTALL CLIENT.
17) Schedule a boot-time scan (so no manual planning), with the possibility that the user that
is confronted with the scan can cancel it. (requested: zhaberman)
18) Make the scheduler intelligent so that when a scheduled scan window is missed because the
client was turned of, the missed scan is not started when the client starts.