Re: active directory on small network
- From: "Les Connor [SBS MVP]" <les.connor@xxxxxxxxxxxx>
- Date: Sat, 24 Feb 2007 14:44:07 -0600
Hi comfuted,
You must abandon your current train of thought ;-). The best way, in fact the only way, to have a good experience with SBS - including a disaster recovery plan - is to install and configure SBS as it's intended.
You do this by booting from CD1, and following the scripted installation right through to the end. Accept the defaults. You'll be provided with a TODO list, follow it through in order, and you'll have a functioning network - in a known state - and with a documented recovery procedure. It may not be an 'optimal' installation, but it will certainly function.
Suggesting "no AD", or "no DNS", or not using the SBS wizards to configure things, is not an option. You either have to learn, or have an experienced SBSer install and configure this for you.
You could also elect not to use SBS, in favor of a windows server and/or a peer-peer network; but I'd recommend you perservere with SBS as it has an incredible number of benefits. But it must be done right.
Have a look at Andy Goodmans walk-through articles on installing SBS.
http://www.sbs-rocks.com/articles.htm#SBS%202003%20Articles
--
Les Connor [SBS MVP]
"comfuted" <comfuted@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:F30B444A-5AF8-45B2-A06A-5722E2B918A3@xxxxxxxxxxxxxxxx
I have a 6 user system running Windows 2003 SBE. We do not use Exchange, and
not host a web site (but might in the future). My original install did not
utilize active directory and everything went well. I had a disaster had a
consultant help me with the recovery. He apparently installed AD. I have
since added a couple of user accounts using the regular Manage Users. Today I
looked at AD for the first time and see that these users are not listed.
These users have encountered more trouble installing applications on their
workstations, requiring a login by an administrator even though they are in
the Power Users group on their machines. I do not know whether this has
anything to do with active directory.
I am trying to come up with a disaster recovery plan and it appears that AD
is a major issue, so I feel I should get my system as simple as possible and
eliminate thngs that will cause me trouble in the future.
My questions are:
1) Is there a good reason for me to use AD?
2) If so, do I need to get the new users on it? Will I have to rebuild their
local configurations?
3) If AD is not valuable, can I remove it? How?
4) DNS is also running, probably just to support AD. If I kill AD,
can/should I kill DNS also?
Thanks in advance for your help.
.
- Follow-Ups:
- Re: active directory on small network
- From: comfuted
- Re: active directory on small network
- Prev by Date: Re: RAID Version & Backup advice please
- Next by Date: Re: Terminal services
- Previous by thread: FTP - IIS_Clusftp.dll
- Next by thread: Re: active directory on small network
- Index(es):
Relevant Pages
|
