Note: related page on a pro/small business version.
- support for group policy's
- This could be used to push computer settings.
- administrative templates
- password settings,
- network settings,
- user settings.
- adding users to groups
- user groups allow for different settings/logins, making it easier to modify what user may see what information on the network
- better mailserver administration
- add/create/edit users,
- start/stop the mailserver,
- edit settings for the mailserver.
- network tools (SMP)
- Monitor network bandwith usage,
- manage subnets,
- administer network settings, dhcp, dns.
- Windows Update
- a solution to the MS Update Server, that allows to "push" selected updates to clients, instead of *all* updates from the windows update site.
- Virus protection
- If a nice antivirus solution can be found, that would be a plus.
- Establish a working group.
- who likes to work on amahi business, and likes to do what.
- create some kind of guidelines
- what needs to be done first, how do we do it.
- what parameters need apps to adhere to, like security, and interaction with the core
- can apps share the same (basic) layout, and how should this be done?
- make amahi business ready.
- allow user based groups, and group based logins.
- set guidelines for webapps, perhaps allow them to share a single user database for login to apps.
- allow different groups to see a different dashboard.
- allow app restriction, a security meganism needs to be build so that admins can decide what users have access to what app
- group based application configuration?
- allow apps to show different information based on a user's group id.
currently im look at Xmail (http://www.xmailserver.org/) which is an easy to configure pop3/smtp mailserver, that also has a webinterface (http://dev.waaf.net/xmail/screenshots.html) if we could manage those two to work with amahi, we have a simple, but powerfull mailserver for an average company.
for group policys (i think administrative templates fall in the same catagory) all that needs to be done is a more advanched tab of the shares tab in the amahi setup. basicly all we need is to edit the /etc/smb.conf file which the hares tab also does. perhaps a new tab that says "Advanched network settings" or something can be made. this allows for samba to be configured as the Primairy Domain Controller, which is all thats needed for group policy's to be distributed. login scrips and other settings are automaticly pulled from the server's netvol share i think.
(12/07/2009) At this point i successfully managed to have my HDA act as a domain controller. see PDC for more information.