Hello JRL,
Basic network setup is that not really. You talk about Active directory which
is installed easy with some clicks. But then the work is starting. AD relies
fully on DNS, so this configuration must be correct. Then policies cone into
play, where you have to know at least some basics.
Also IIS, SQL or Exchange should not be installed on a server where AD is
running, security and performance reasons. AD is the heart of the domain
and if someone is able to hack that machine the complete domain is open to
the hacker. Also a domain should have at least 2 domain controllers with
GC and DNS for redundancy and failover.
See here about some basic documents especially "Windows Server 2008 Step-by-Step
Guide for DNS in Small Networks.doc":
https://www.microsoft.com/downloads/...displaylang=en
For AD start here:
http://technet.microsoft.com/en-us/l...97(WS.10).aspx
Group policies:
http://technet.microsoft.com/en-us/w...y/default.aspx
Best regards
Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!!
http://www.blakjak.demon.co.uk/mul_crss.htm
> I am setting up Server 2008 in a home office, with one pc as a server
> and
> two other vista pc's.
> I have named the domain (for this example http://servername.com ) and
> this
> name is registered with a DNS hosting service.
> The main reason for setting up the server was to have ftp and IIS. Now
> I'd like to set up a basic network, where the vista pc will log in to
> the server for file and print services. I don't need roaming profiles.
> I would like to use active directory services to control file accesses
> and quotas.
>
> Could you please provide some basic guidance as to what I should be
> configuring in order to design this kind of setup? If there are any
> walkthrough's or video demonstrations, that would be best.
>
> Thanks, JRL
>