Server questions

[auen1]

I have an old server that I'd like to put to use. I like playing around with older equipment as it provides a cheap education, and I am not out much if I break it.

Some info:
The server is a Dell Poweredge 1500SC. It will only be used on my home network, with 3-4 computers.

I do not know much about servers, other than my research on the internet, so any and all advice is welcome. I did do a search on PCMech for servers, and read all the threads that I could find.

So here are a few things that I was wondering about:

I don't know if it is possible, but can I use the server to run applications? For example, could I install and run MS Office or CAD on the server, and use the app on the PC's? Can this be done?

What other good uses can I use this server for, (besides a simple file server), on a home network? I am really just looking for a learning experience, but I'd like to have a functional server when I am done.

I think the server originally came with Windows server 2000. The OS was erased when I got the server. Am I stuck with 2000, or could I install 2003 or 2008? Which version should I look for?

I have many more questions, but I'll just start here and see where it leads me.

Many thanks for any help.

Here is a link to the specs. The one I have has 2 CPU's and 1 GB of RAM installed.
Documentation

[Force Flow]

That machine has some age to it. Server 2003 is supported. I'm not sure about 2008--the driver support doesn't appear to be there. It also falls short of the minimum CPU requirements for Server 2008.

Go to Drivers and Downloads | Dell [United States] and enter the service tag on the machine.

If it still has the original hard drives, I might be concerned about drive failure--just something to keep in mind.

[auen1]

Thanks for the resource link. There are certainly is a lot of drivers and downloads\updates. Here is the service tag link if it helps anyone help me.
Drivers and Downloads | Dell [United States]

[glc]

Could you please post your service tag number?

[auen1]

O right, FQV8G11

(btw, My last post included a link already connected to Dell drivers W/ my service #)

Thanks

[glc]

No, that link gave me the drivers for the last Dell computer I looked up.

Original system configuration was dual 1.4 GHz Tualatin P3's, 1gb ram, Adaptec 39160 SCSI adapter, and 3 Maxtor 18gb SCSI hard drives.

Drivers are available for Win NT 4.0, Win 2000, Win 2003 Server, Red Hat Linux 7.0, and Red Hat Linux 7.1. Red Hat is free.

ftp://archive.download.redhat.com/pu...1/en/iso/i386/

[auen1]

Originally Posted by glc Orignal system configuration was dual 1.4 GHz Tualatin P3's, 1gb ram, Adaptec 39160 SCSI adapter, and 3 Maxtor 18gb SCSI hard drives.

This is exactly what I have. The server has room for 6 hot-swap hard drives. I figure I could always upgrade if needed.

Drivers are available for Win NT 4.0, Win 2000, Win 2003 Server, Red Hat Linux 7.0, and Red Hat Linux 7.1. Red Hat is free.

These are the server OS's that I can use. Yes?
So which OS might be best suited for running programs on the server for the client PC's? My system will be hard wired closed system. (No remote).
I have seen that Windows Server 2003 has a function called "Terminal Services" which run MS programs from a server. But they also have "Terminal Server Licensing" for the clients, which seems a little extreme for my purposes. Here is the link that I found:
How Terminal Services Works: Terminal Services

I was just thinking that it would be nice to keep the larger programs, like MS Office, Adobe suite, CAD, etc. off the PC's. This way, it would lighten the load on the PC's HD, RAM and CPU? And I would just have to install and update the programs in one place? If I could do this, would there be a downside?

Thanks for the replies!

[glc]

That machine doesn't have anywhere near the horsepower needed to run as a true application server. You have a very good file server there, but it will need a lot more hard drive space.

[edfair]

Perceptions of the best way to use the machine vary by how the individuals see the package of all machines.

My vision would be local applications, remote data, and images of the workstations stored on the server if enough hard drive space could be found. Would possibly invoke a network storage drive for the images and a backup for the data on the server.

[auen1]

Ok, I'll pass on the app server idea. I got my hands on a copy of Windows 2003 R2, SP2 Enterprise iso. I'm trying to install it now.

[auen1]

Alright, I have the OS installed and currently updated.
I have a few more questions.

Back to the Dell driver and download link. Would I want to download and install everything listed on that page as per the OS?

Exactly, how do I connect the server to my other computers. At the moment, I have the server connected to my router, via ethernet cable. Does the server communicate through the homegroup setting?

On the Windows 2003 setup page, "Configure your server wizard", I have a dozen server role options. Is it OK to configure all of them right now? Or will this just drag down the system.

Thanks for taking the time to help me out. I can tell that the servers main role, for a while anyway, will be an educational toy. Honestly, I only understand half of the parts, practical uses and terms relating to the server. It's all good. You have to start somewhere.

[edfair]

Probably would be good to download everything applicable, burn it to a CD so you have it next tine, and install just the things you need.

They download them as R#####.exe so would be better to change the name during the download to something you will recognize.

All machines to be visible in the network need to have the same network. I use workgroup even though 7 likes homegroup and XP likes MSHOME.

Having not dealt with 2003 my assumtion is that you get choices of the level the server loads. That it probably is self configuring for the role it is to assume.

Then you share the drive(s) on your server, map the network drive(s) on the workstations. Sharing may automatically happen since it is a server OS.

[glc]

The RIGHT way to do it is set up a domain and active directory - and all computers connecting to it need to have 2000/XP/Vista/7 *PROFESSIONAL*.

Time to do some reading.

[auen1]

@ glc
I have been reading up on creating an active directory. I gave it a try, and think I have set it up properly, on the server side. I am having troubles getting the client's to connect. I used this link to create a local network
How To Create an Active Directory Server in Windows Server 2003

Question: I noticed that you emphasized *PROFESSIONAL*
All my machines run 7 Ultimate. Will this OS not communicate with the server?

Update: I decided that I'd go ahead with a public domain address and I got one. I am having trouble configuring the TCP/IP settings. But I'll keep looking for an answer on my own for a while. For me, the confusing part is this: I get my internet through a Hughesnet dish, then through Tengointernet, then to an antenna, then to my antenna, then to my router and finally to my computer/server. Every one of these connections have an IP. Then add in my public domain IP. I have not figured out exactly which IP's to use yet. I'm pretty sure that Hughesnet, Tengointernet, my antenna and my public domain address have a dynamic IP.
BTW this is the link that I am using, (different from the link above), How do I install Active Directory on my Windows Server 2003 server?
I'm stuck at step 2.
Like I said, I'll keep looking for answers on my own, but am I on the right track? (Any advice is still always welcome though)
Thanks again

[glc]

Ultimate can connect to a domain - I should have said Professional or higher. You should not need a public domain, a local domain is sufficient.