|
|||||||
![]() |
|
|
LinkBack | Thread Tools | Search this Thread | Rate Thread | Display Modes |
|
|
#1 |
|
Member (7 bit)
Join Date: Apr 2006
Posts: 93
|
domain controller/print server help
Hi,
For our company, I need to build a server/domain controller to support 10 workstations. I already know what parts I will use, but I have some questions about the software. I will be using Windows Server 2003. Can I setup this server as a print server, too? We have a plotter, and another network printer that need to be shared with all workstations. I also have a 24 port Linksys giga-switch to use, along with a wireless router to share the internet. Are there any good walk-throughs that show me how to setup the server as a domain controller, print server, and then setup the workstations. I also need a guide on how to connect them and the printers to the switch. Thanks for the help. |
|
|
|
|
|
#2 |
|
Member (10 bit)
Join Date: Jun 2000
Location: Dorset UK
Posts: 559
|
Hi kentuckyser
I work in a school environment installing 2003 servers, printers workstations etc, unfortunately i did not create the original image but it is just a basic image. After Giving the server its proper name and setting the static IP address and DG I use the Manage your Server interface to install AD and DHCP and DNS. i use the add or remove a role option using the typical settings, This allows you to create a domain name of your choice. After inputting the typical settings the system will reboot. After logging back on you can set the parameters within Group Policy to your choice. If your users need to map drives the you can create a batch file and place this in the C:\windows\sysvol\sysvol\%domain name%scripts folder. I setup the network printers locally creating a tcp/ip port, each printer is given a static IP and reservation host name within AD with the relevant drivers loaded. I can then share the printer out so each workstation once on the domain can see them. I do not then need to load the printer drivers on each individual workstation. I give the switch a static IP addresse and again a reservation / host name in AD. Port one on the switch is the uplink port from the broadband connection we use. Check the switch documentation for setting up. Once the server is up and running the workstations can be added via the switch using the domain admin account created when you setup the server. I add the workstations to the domain reboot then rename the workstation rebooting again. I don't use wireless in the school environment so have no experience there. I'm sure there are plenty of sites on this subject but hope my points raised give you some insight. Doug |
|
|
|
|
|
#3 |
|
Staff
Premium Member
Join Date: Jul 1999
Location: Arlington, TN
Posts: 5,538
|
Some of the advanced stuff that you can do with domains wouldn't really be worth it with only 10 workstations as long as they are in close proximity to each other. Things like creating batch files to map network drives, Group Policy, etc. are great tools but they do have a learning curve on them.
I would start off with a good book. The best that I have found on the subject is Mark Minasi's Windows 2003 server. It has a lot of good info and is a good reference book in addition to a setup guide.
__________________
Want to Make $$$$ with your Computer? No Risk! Simply press shift-4 four times in a row |
|
|
|
|
|
#4 |
|
Forum Administrator
Staff
Premium Member
Join Date: May 2000
Location: Joplin MO
Posts: 37,791
|
I would use HP Jet Directs rather than try to make the server act as a print server. You have 2 choices here - install the printers on each workstation as Jet Direct printers, or install them on the server (yes, still using Jet Direct) and share them.
|
|
|
|
![]() |
| Bookmarks |
| Thread Tools | Search this Thread |
| Display Modes | Rate This Thread |
|
|