First time server 2003 install

[ftook]

Im new to installaing W.server 2003, so please forgive the basic level of question, but im now installing it on a pc. I need to use it as a file sharing system only. Am i correct in thinking that I :

1. install os
2. install active directory
3. create users
4. share folders

i will be linking Vista business to the server.

 

[nevets2001uk]

In principle that's the right order for the high level view of the process. If it's a small environment and you really only need central file storage you may not even need to install Active Directory. Instead you can create local users and file shares and work with those in a workgroup environment.

How many users will this be supporting and is there any requirement for having a domain and directory services in place?

Steve G (MCSE / MCSA:Messaging)

 

[ftook]

Steve - thanks for you reply,

the system will need to support 15-20 users sharing a ms- access database on the server, this plus DHCP is all thats required at the moment.

The users will share access to the database and probably access their files and save them on the server - would the workgroup setting allow for this.

 

[nevets2001uk]

As long as you don't mind creating the 15-20 user accounts on the server as well as the local accounts and profiles on the PC's then a workgroup environment should be OK. It will achieve your goal and be the most simple option to setup. Considering your lack of experience with W2K3 and AD it may be the best route for you. It's worth doing a bit of planning to ensure that a specific requirement for AD won't come along in the near future, because if it's at all likely it might be best to install it now.

It's worth remembering that install AD would also require you to install DNS locally and do some basic configuration of that.

Also note that I have had issues in the past with that many users accessing an Access database across the network. Granted mine was very large but it caused us a few headaches as the data kept currupting. We have sinced moved to using SQL server and have had no issues since.

Steve G (MCSE / MCSA:Messaging)

 

[ftook]

Today I have played about on an old PC ive got and installed the O/S in a domain setup, along with DNS, DHCP, File server and loaded AD, and i linked 2 vista business machines to it with IP leasing for internet access, along with sharing the database. I THINK i covered everything needed but not too sure, but it seemed to work and run fine.

in your opinion with what i did there do you think i should leave it as a domain setup.

 

[nevets2001uk]

If your happy enough setting all that up then a domain may be your best option. In the long run it will ensure you can move forward with the other advantages of having a domain and directory services. You may later want to control the client PC's using Group Policy and or delegate control for creating the users for example.

My only warning would be that it's best to carry out a bit of planning before setting up your first domain and forest as this is not easily changed in the future. A good book that I read some time ago is "Windows Server 2003 Active Directory Design and Implementation" by John Savill. The first few chapters cover the basics of AD and the full planning process for an example environment. It might be worth a read if you want to ensure you think of everything.

Steve G (MCSE / MCSA:Messaging)