intranet @ win2k server

before you start with the actual installing and configuring of the server, what do you need to know?
* what do i need?
* who can do what?
* security?
* control of the server?
* ...?

and how can i answer these questions?
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Eesh... for 125 points man...  =P  You're asking for a NOVEL for only one hundred and twenty-five points.  I'd like to say I feel like taking the time to tell you all of that... but...  I don't.  You're gettin' the idea though with some of the questions to ask.  It really depends on way too many variables that you'll have to decide where to branch to from the answers you get.  I'll give some quick pointers tho', and some good references.  I won't write a novel here... but I'll try and help a lil'.  It sounds like you're not doing this for yourself, but for your company, or a company, so that's where I'll target my answers/questions for you.

Well, if you haven't bought the hardware yet... figure out how many users max, and average you'll have using it at the same time, and figure out what services you'll run, and look on microsoft tech docs for suggestions on recommended ram, hard drive, processor speeds, etc for what you want.  Once you find the recommended, then multiply it by around 1.25 or 1.5 at least and go with that.  This allows some flexibility for the future.  =P

Next... ask all the major questions, what do the users needs.  Web, email, shares (as usual), if shares... then you'll prolly need active directory if you really want to lock things down.  If so, start your planning early, making it easy on you later, and easy on any future tech if you actually write or plan it out in Visio, or something.  Figure out what groups of people need access to what information, etc etc.

Figure out your admins.  If you're only going to be the admin, this makes it real easy.  If you're not... do your administrators actually know what they're doing?  Do you trust them enough with full access?  If not, you can make special limited accounts for them with only enough administrative access to say... reset passwords, or something.

Then, install the damn thing.  Do the usual smart 2k server install by NOT enabling IIS or anything until after you service pack and security update to the fullest.  Then, only enable the services you need, don't go service happy.  =P  If you don't need the webserver, by god don't enable it, please.  Enable active directory if you planned to do so, and create users and groups.  

At this time I ask that you are doing this on a private network, usually of just the server and another computer of yours (w/ a crossover).  Test your users and groups, make sure they have the right access to the files they need, and nothing more.  Make sure your webserver works (if you're using one), your ftp server works (if you're using one), and any other services that can be tested.  I advise that you now jump online and look for a hardening guide for windows 2000, there's tons freely available on the web.  Hardening guides basically are step-by-step guides to locking down the security of your windows 2000 server.  They may very well save you.  =P  You can do more testing, and installing any intranet applications they need hosted at this point, making sure they work properly (real estate offices often have server-side apps, so do some manufacturing plants).  Other than that you're pretty much good.  You can set the beast free.  Slowly make those Admin accounts and lock them down with a customized MMC, and limited rights if you don't trust them (As you shouldn't!) and hopefully all will be well with your 2k server.  Throw it in a rack/cabinet, lock it up, and you should be good.

Last piece of advice, get a book, or seach online for good 2000 planning guides.  There are a few out there... but I've found that they pretty much are only good for certain kinds of networks.  A good book, and reading always helps... and well... experience always helps.  =)  So after you do this one, the next one you setup you will be that much wiser.  =P

And here's a book link... it sounds interesting, but I haven't read it and can't recommend it from personal experience.  Most of my 2k knowledge has come from manuals, and much personal experience (and sometimes... failures)
Windows 2000 Server: Planning and Migration

 - Insolence

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Yikes... I just realized... I did almost write a novel... =P
vincentvdnAuthor Commented:
i can only offer the points i have ;)

anyways thx a lot for the information, it is very usefull
I do care... and I think I answered the question well, but I believe vincent was just waiting for another expert's opinion on this matter, and well... no one responded but myself which is rather disappointing.  =P

 - I
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows 2000

From novice to tech pro — start learning today.