Question Locked

Single Domain with Win Server 2003

0 helpful
9 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
I am preparing to install a new server to replace an old one in a peer-to-peer network. I will be using Win 2003 server OS and will have 16 clients running win xp professional. I plan to have only one domain. How do I install the domain without becoming involved with Active Directory? I think I only need DHCP. Is that correct?

9 replies

by jplconsultant

If you create a Windows Domain, you get AD. AD is the methodology used by Windows to manage the domain.

"I think I only need DHCP."
The fact that you "think" means you aren't sure, which means you need to ask more questions about what you want the network to do and what you want the server to do. If you plan on sharing files on the server, you probably want to add the File Server stuff. If you plan on using the server to control MS Updates, then you'll need to set up the IIS stuff.

So the question I have for you is, what precisely do you plan to gain by implementing a Win 2003 domain? Same question, but phrased differently: There's a reason you want to install a new server. What is it / What are they?

If all you're looking for is DHCP for 16 clients, then scrap the server and get a business-class router that has DHCP on it. It's less expensive and less troublesome.

JPL()

by raytmeyer

I cannot thank you enuff. I have 3 big books on Server 2003 and they all give info for large networks. I have searched thru 3 big books looking for the answer you have given me. Thanks again.

The reason we are upgrading to a larger server is that we have a couple of applications that almost everyone uses. The use of them bogs down the present server to a crawl. This server is a Dell Optiplex (about 4 years old) using Win XP pro OS and acting like a file server in a peer-to-peer network.

Now we are upgrading to a Dell Power Edge server with Server 2003 OS pre-installed. I have used Win Server 2000 and am comfortable with it, but my new books go into great detail about how complex and difficult Active Directory is in 2003 version, so I wanted to avoid it if possible. So it is not possible; therefore, I will tackle the setup one-step-at-a-time. When and if I bog down, I will seek help. Keep up the good work. We need people like you. Ray

by jplconsultant

If all you're doing is adding a "true" file server, then keep things simple. When you boot the 2003 machine, use the "manage your server" utility and pick the "File and Print Server" option. That installs some software to make managing the file server easier.

You'll see on that same window is an option to create a Domain Controller and AD and all that stuff. Just don't use it.

Now, you've got a true file server which can be easily added to your current network. Give it a static IP Address, and map your desktops to the new server.

Notice, I don't mention DHCP or reconfiguring your desktops or doing any other changes to the topography of your environment.

This keeps your network simple and easy to manage, and gives you the fix you need.

Write back if you have any questions.

JPL()

by jplconsultant

First, you're welcome for the help. My pleasure. The books are nice, but often they get in the way. :)

Second, Thanks for marking the post as "helpful". It's my first "thumbs up"!

Thanks again,
JPL()

by raytmeyer

To JPL: Many thanks. That is exactly what I have been thinking, but could find nothing about it in these books. Everything in the books is for large networks with numerous servers. Nothing is said about a small network like ours. The books give the impression that I must create a domain which then leads to AD, etcetra. You have saved me a lot of grief and I really appreciate it. Thanks some more. Ray

by jplconsultant

I'm glad I could help. If you have any other problems, don't hesitate to post again.

JPL()

by xt john

Active Directory and Domains seem complicated (and they are), but don't overlook the benefits. If you need to set up secure file sharing, such as folders only accessible to certain users, setting up profiles for each user, and permissions for each user to access folders/resources, is best handled under Active Directory. One of great tool under active directory is the Group Policies Editor. Here you can establish rules on what a user can and cannot do when they sign on. Those rules are 'fed' to their computer at logon. Managing your users is simpler, changing passwords, deleting/adding users, etc.

One of the biggest drawbacks to a single Domain Controller setup is... if the DC goes down, so does the domain. Sure, you can back up files to restore a failed domain. (I've only had to try this once, and it didn't restore, we had to rebuild the Domain anddisjoin/rejoin all the clients).

Depending how secure the network needs to be, a Domain does offer many advantages over a workgroup.

I agree about the DHCP assignment from a router. Most routers will also allow you to assign static IP's to specific machines based upon the computers MAC address.

I'll be happy to share any further info on Domains/AD if you need it:)

by raytmeyer

Thanks, John. Those capabilities you mentioned about AD is what I really would like to provide. I am a bit nervous about attempting it, but I think I will feel my way along and give it a shot. I am doing the preliminaries of setting up and configuring today and will do the networking and testing over this coming three-day weekend. One way or another, I expect to have a working system by 9:00 a.m. Tuesday morning when the users come back to work. Many thanks. Ray

This discussion is closed to new replies.