Changes

From Amahi Wiki
Jump to: navigation, search
1,867 bytes added ,  02:00, 18 November 2010
m
Reverted edits by Acecydoxose (Talk) to last revision by Cpg
SOHO Features
* support for group policy'sThis could be used to push computer settingsNote: related page on a [[Pro Version Requirements | 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.# usergroups#* 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.
TODO:# Establish a working group.#* better mailserver administrationwho likes to work on amahi business, and likes to do what.add/#create/edit userssome kind of guidelines#* what needs to be done first, how do we do it.start/stop the mailserver#* what parameters need apps to adhere to, like security, edit settings for and interaction with the mailserver.core#* network tools can apps share the same (SMPbasic)layout, and how should this be done?Monitor network bandwith usage, # make amahi business ready.manage subnets#* allow user based groups,and group based logins.administer network settings#* set guidelines for webapps, dhcp, dnsperhaps allow them to share a single user database for login to apps.#* allow different groups to see a different dashboard.#* Windows Updateallow app restriction, a solution security meganism needs to the MS Update Server, be build so that allows admins can decide what users have access to "push" what appselected updates to clients, instead of #*allgroup based application configuration?#* updates from the windows update site. * Virus protectionIf a nice antivirus solution can be found, that would be allow apps to show different information based on a plususer's group id.
(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.
Trusted, Bots, Bureaucrats, emailconfirmed, Administrators
3,789

edits