Windows 2000 (Advanced) Server (newbie) 1

[Tezdread]

Hi, I'm going to install Win2k Server for the first time and would like some feed back from the people that know before I go ahead and install it.

I am going to run it on a PIII 500+ with 256mb RAM (PC133) 20gig HD etc. Will this be sufficient?

Is there anything important that I need to know before I install? Taking into account this will be the first time I've ever used MS server software. I will be installing it on a clean fomatted HD.

It will be installed on a small network consisting of 2 Win2k Machines, 1 WinXP Pro machine and 1 Red Hat Linux box which will be used as a server/gateway running FTP to the outside world. I want to install all my software on the server so I don't have to install it on each computer if this can be done?

I would like it to be a domain controller (although I'm not completely sure what this is) so that all the other computers/users have to logon to the server, this would then bring up the users profile no matter what computer they logon from.

I need to do a lot of reading up on all this as I'm not to sure of the capabilities and limitations of the server. But if anyone wants to tell me what they think the best or most used function is on the server I would be happy to see it.

Cheers
Tez

 

[franklin1232]

First thing is good luck. Besides that why Win2k advanced for such a small network. Why not linux across the board you already have one box running?

Well you machine hardware is not a server. At the minimum you should have redunency in your hard drives. Software mirroring at least. You ram is to low. the Operating system alone will consume more than half just to run core apps. If you want to run programs from it you will probally want to use the terminal services that come with you server software. With only a few users it won't put much burden on your server, but I get more memory because the gettin is good.

Setting you server up as the domain controller is easy. Pick a domain like companyxyz.com. If you choose to install active directory you will also need to use DNS. I recommend the Microsoft DNS server, but if you already have one then, well good luck there too.

Then setup your domain login account using the active directory administrator. Since your new to Windows servers you should have tons of fun with permissions, profiles, and shares.

Summary:
1. Follow the setup wizards and post more questions
2. Terminal services for remote access to software not Admin mode.
3. Think about getting a real server. One hard drive crash and you'll have nothing left.
4. Active directory it's new, runs everything, and could use better tools.

I'll try to keep helping just reply to the post.

 

[AlexIT]

I believe that your computer will be sufficient for a Win2k AD box. As Franklin posted get the memory because it is cheap and helps somewhat, also you will need to have a backup plan and stick to it, because the hard drive will be your weak point to this box. I would imagine that the Win2K server would be used for network login, software install, and storage mostly (Linux is NAT and FTP server right?)
I have a P133 with 96MB memory in my lab that runs Win2k AD server, integrated DNS, and DHCP. Sometimes I add RRAS (NAT AND VPN) and even Exchange (once!) This box crawls to provide to my five test clients, but it locks up less than my Win98 desktops... Just plan to check the logs daily when you get going.

Alex

 

[Tezdread]

Thank you for the feedback!

I wasn't sure if it was the advanced server when I posted the message and when I got back I realised it is the standard 2k server.

I'm installing Win2k server for the experience more than anything else, I've been using a peer to peer network for some time and now feel like moving up a step )

RAM is something that I will add more of as and when I can, I am looking into backup software, Peersoftware seems to offer some good stuff but if you know of something cheaper that will do the job I would be happy to look at it.

You are right AlexIT about what I will be using the systems for, although most of my storage will be on the Linux box and this will be things like images and music as they will also be shared VIA FTP.

I will post more when I'm up and running. Thanks again.

 

[Maruis]

Hi guys good posts...

Couple of more things to think of:

Remember to increase your page file.
The build in back-up software works pretty good.
Be prepared to rebuild a couple of times, lets call it practice.
Add a second HD if you can it will help your server a lot if you have a page file on each HD, because it will page a lot as soon as you start hitting it. With AD enabled a domain controller runs at 200 meg RAM without load, give and take a few meg.

Also make sure that you stop/disable the services that you dont need i.e. NNTP. It will just use resources that you need.
MS installs services that you do not choose at startup by default.

Hope this Helps

Maruis
"I sleep at home not on my Job!"

 

[Tezdread]

"Page Files/Rebuilds" ) I am hoping that it all makes more sense once it is installed and running! I will install a new HD when I can, and i'm looking at getting a RAID/PCI Card hoping that this will give me some HD Mirroring facilities? a good book is also on the list )

Tezdread

 

[DeanEwalt]

I did about the same thing a year ago. Installed Win2k and struggled and struggled. Book by Minasi helped a lot. Ran ok on 256mb but better at 384, but no one using it. Active Directory looked completely unnecessary and a lot of stuff not needed. Added a second HD for backup. Win Backup works good. I setup IIS and am running Webhosting for fun and glory. Security has been biggest problem. Too much, too little. FTP security still dies every day or two.
Will be glad to answer questions, but not the tuff ones. I installed Win NT 5 times before I got what I wanted, three years ago, and then the HD crashed. Nothing left.
drDean@pobox.com for more suggestions.

 

[Maruis]

Hi Again

Windows 2000 Server can mirror drives via its Disk Management software.
You can use it and save money on the Raid controller.

Have fun and post any questions you may have. Hope this Helps

Maruis
"I sleep at home not on my Job!"

 

[HenryMonster]

Take care of security issues ASAP, especially if your
machine has a public IP address: believe me, you'll get
infected with Nimda in an eye-wink, if you do not install
Microsoft recommended security patches as per

http://www.microsoft.com/technet/treeview/default.asp?url=/technet/security/topics/Nimda.asp

Install W2k SP2 and IE SP2.

Frequently check Microsoft security bulletins:
their great software is so bloated with bugs, which
create a very fertile soil for exploits, that you better
do this daily.

My modest personal experience can offer some more
recommendations:

1) stick to Microsoft W2K certified hardware;
2) do not install hardware & software, which
is intended for a workstation, like CD-writers,
scanners, napsters, etc.
install only what you need for server-related tasks.
3) if you need to have a modem hooked up to your
W2K server you'll be better off using an external
modem with DSP (digital signal processor) rather
than winmodems
4) update your antivirus definition files
once new version is posted
5) 512Mb of Ram is good for you rig performance;
don't waste your time waiting while W2K is paging
in&out

 

[TheOtherKiwi]

What have you guys done to use 200Mb of RAM when nothing is running? Mine uses less than 100Mb with AD, DNS, DHCP, a couple of Office 2K apps...you name it, its running. Add memory for sure, but only if you need to. The point of understanding how to tune WIN2K is to determine requirements first and then respond according to real-world experiences.

Just throwing hardware at the problem almost always is not the solution.

I hope the "server" described above is using SCSI, I have seen pathetic performance from "high-speed" IDE/ATAPI devices...my two cents worth...

 

[Maruis]

Good point.

I have a testing system that only runs as app server. No one is connected, no DHCP,DNS,AD,IIS ext. It sits idle at 100 meg.

So I believe your system is optimally tuned. Good job!

Have Fun Hope this Helps

Maruis
"I sleep at home not on my Job!"

 

[Tezdread]

Thanks for all your help and comments. I am now in the setup for the first time. I hope that I can change it easily because I am not sure what I should be selecting.

I have this settings so far,

Per server. Number of concurrent connections 5 (this is how many computers on the network) Is this easy to change when I add a new computer?

Components;
• Indexing Service : on
• IIS : Common Files, Documentation, FTP Server, FP2000 Extentions, IIS Snap-In, Internet Services Manager (HTML), SMTP Service, World Wide Web Server.
• Management and monitoring Tolls: All on
• Network Services : COM Internet Services Proxy, Simple TCP/IP Services, WINS.
• Script Debugger : on
• Terminal Services : Client Creator Files, Enable Terminal Services
• Terminal Services Licensing : on
• Windows Media Services : on , Admin : on

Terminal Services Setup: Application Server Mode : on (what is the "Terminal Services Licensing Server used for?)

Now I have the choice of two in Terminal Services Setup, The first is Permissions compatible with Windows 2000 Users
The other is Premissions with terminal Servies 4.0 Users

If I am just running popular programs like Office, Photoshop etc will I need the second option?

 

[coachdan]

Book mentioned earlier by DeanEwalt (Mastering Windows 2000 Server) is excellent to help you with your project. I am currently going through the same things you are and it has helped me greatly. You can get it on-line at

http://www.minasi.com

, it will link you to a site to purchase from (probably Amazon.com). Hope you enjoy it.

coachdan