Need help setting up small company server 2

[digitsdad]

Hello,
I inherited the job of configuring our company server, a Dell 6100, SCSI Raid 5, older system. We have less than 50 clients, mostly Win 98, 2000pro, and XP home edition. I would like to set the server up to do our Student Logins, as well as run Exchange. I suggested running Windows 2000 Server with Exchange 2000 Server. My question is, how do I set this up? I figured that I would configure it as a Domain Controller, but what kind of IP address should I use? Should I use some kind of private IP address? I assume that I will have to set up some kind of firewall? Also, we have an ISP hosted website, what kind of considerations to I have to take into account to get our email, etc from the website?
My apologies for the list of questions, I sort of inherited this assignment and I am in somewhat over my head!
Thanks, Paul

 

[markdmac]

well, first off you are going to have a problem if you create a domain. Your Windows XP Home machines don't have the ability to join a domain. You will need to either use a peer to peer network or upgrade those machines. While you are at it I would suggest you get rid of the 98 boxes and make then 2K or XP, Win98 can work on a Win2K domain but you won't be able to take advatage of all the features offered such as Group Policy and login scripts via Group Policy.

Based on the number of workstations, I'd suggest you do the upgrade on those machines and go with Win2K Server as a Domain Controller. this gives you a centralized point of security and you won't need to maintain 50 seperate security databases.

Get yourself a Linksys or similar Cable/DSL Router which can act as a firewall. Use that to seperate your server from the Internet.

Your Linksys will default to 192.168.1.1 so you might as well for simplicty sake use that IP addressing scheme and set your server as 192.168.1.2. Setup DHCP on your server so you don't need to assign or manage IP addresses on your 50 clients.

When you have installed the server software, run DCPROMO from the Start/Run prompt. This will initiate the Active Directory Wizard. You should be able to follow the prompts without a problem.

Since your web site is housed outside your location I suggest you select a DNS name with a .local extension, for example if your web address is myplace.com choose myplace.local when prompted during the DCPROMO.

I hope you find this post helpful. Please let me know if it was.

Regards,

Mark

 

[digitsdad]

Hello Mark,
Boy, I can't believe it! That was a great response, and so quick! I am trying to get the boss to do the upgrades to W2kpro on all the machines, your reply really helps me to convince him-your other ideas are perfect, that is sort of what I had in mind but I needed to hear it from an expert. I can't get into the server room today to find out, but I think that we have a Linksys DSL router. Do they all default to 192.168.1.1? I guess that when I set up W2k Server or Exchange Server I will point to that address? I have done a basic installation of W2k Server on the machine already, will running DCpromo take care of all the configuration, including changing the IP address etc?
Again thank you very much for the great response,
Paul

 

[markdmac]

Hi Paul,

If you are pushing your boss for the upgrades, you are better off pushing for XP than 2K for those boxes that were running XP Home. Keep in mind the software lifetime of an OS. microsoft is already planning to release XP Reloaded which can be kind of looked at like the release of Win98 Second Edition. Big differences between the two but not quite a new OS. Win2K Pro is already 4 years old, so switching an XP machie to that would not make sence. Going from 98 to Win2K would since the hardware requirements are less, but if you could go ALL XP it would certainly make your support burden easier.

If you currently have the server setup as a standalone server then you are in fairly good shape. Most of the headache is already over. You can at this point if you need to change the IP but that may not be necessary. Take a look at your current configuration to determin what needs to be done.

A typical installation (if there is a such a thing) would be to have your server have for example an Ip of 192.168.1.2. It would be configured with DNS. Your DNS Server would have listed as forwarders the IP address of your ISPs DNS servers. The TCP/IP DNS properties on the Server NIC would point to itself (192.168.1.2). The gateway for the NIC would point to your LinkSys at 192.168.1.1.

Also on the server would be DHCP with a scope ranging from 192.168.1.3 to 192.168.1.254.

As for your question on the default of the LinkSys, yes they all default to 192.168.1.1, they come with a plank User ID and a password of admin. If you have not already done so you should change this immediately and set a user id/password combination that no-one can guess. I can't tell you how many networks I have run into that still have this totally unsecure default still enabled.

When you run DCPROMO it will install DNS if it is not already installed ont he server and I would suggest that you let it do just that to ensure it is set up correctly.

In looking at your post I see you mention WHEN you set up Exchange. Have you already purchased Exchange Server?

If you have not then you should probably consider purchasing Microsoft Small Business Server. This would be the most cost effective way for you to get a server upgrade to Win2K3 and at the same time get Exchange 2K3. In addition, with SBS comes a free upgrade to Outlook 2003. SBS 2K3 supports up to 75 clients. If you don't see yourself going past that number then this owuld be a great solution for you. The built in Wizards will make administration a lot easier for you since it sounds like you are just starting out on supporting servers.

If you need more firepower to sell that idea beyond the cost savings, look at the added functionality.

With SBS you get:
* Enhanced Outlook Web Access
* Windows Sharepoint Services
* Shadow Copy (restore past versions of files without going to tape backup)
* Remote Workplace (remote control your XP machine from any web client that has IE)

I personally find the Shadow Copy to be the most useful feature. With the Sharepoint site you will aslo gaina help desk feature that lets your clients report problems. This is another really handy feature.

I hope you find this post helpful. Please let me know if it was.

Regards,

Mark

 

[markdmac]

Oops posted to soon. Sorry about all the typos. Sure wish these newsgroups had spell check.

I hope you find this post helpful. Please let me know if it was.

Regards,

Mark

 

[Harlequin007]

Read your post with interest Marc. Spot on mate. Glad there are people like you in this forum.


-----------------
Cogito Ergo Sum
-----------------

 

[digitsdad]

Hello Mark,
Thanks again for all the great info-you are going to make me look like I know what I'm doing! Good idea about SBS, I will try that one on the boss.
thanks again,
Paul

 

[markdmac]

You guys are going to make me blush. <g>

Always happy to assist. Let me know if you need additional info when you get in the thick of it. If you can get passed my typing OT instead of TO I tend to make some sense huh?

I hope you find this post helpful. Please let me know if it was.

Regards,

Mark

 

[AV1611]

I wouldn't be so hasty to jump on XP Pro if you have the option to do Win2k pro. As stated it is 4 years old which also means more stability. Service Pack 4 ring a Bell?? Xp Pro has SP1 and many problems in a true work environment. It might run great at home but not in the real world.

If you haven't noticed, all the new viruses really kick its teeth in. Same thing is true of Server 2003. In a environment with a lot of software it is horrible at the moment. Give them another year before you start deploying.

You also better think of the software you might be running on it. It is most likely BUILT on Windows 2k PRO which means it would run better on it.

AV

 

[markdmac]

Sorry but I have to respectfully disagree with AV1611. XP has been around long enough and is a very stable OS. I'd point out that the recent rash of viruses has little to do with XP as an OS, check out your security bulletins and I think you will find that there are as many new patches for Win2K just as there are for XP.

I was a MS employee before XP went public and we were all running it a full year internally before it went on store shelves or on OEM boxes. Xp is in itself over 3 years old and in THAT time frame only had 1 major service pack. That should testify to its stability compared to the 4 that Win2k has now (and Win2K really needs an SP5 to add in all of the POST SP4 fixes.

As a consultant I have worked on MANY client systems, most are now running or switching to XP to GAIN stability, enhanced power management for laptops and remote access capabilities.

Having an up to date and effective AntiVirus program running on both Client/Servers & Exchange should be a normal part of any infrastructure design. My company recommends Trend Micro Client/Server Messaging Suite. (both SBS and Regular). Most viruses take advantage of security holes that Microsoft has already fixed. It is usually the fault of the PC owner for not patching that causes the major problems. Take a look at code red for an example. Microsoft had that hole fixed 6 months before code red hit. A debate on who the responsible party is is like a religious war so I don't want to go down that road. I just want to point out however that these security holes don't affect system stability, that is why it took so long to find them. They unfortunately only make it vulnerable to an attack. I believe that Microsoft's recent efforts have been jenuine and proactive in providing tools to help make patch management easier. Check out SUS server (soon to be renames WUS).

It is true that there can be software issues, but they tend to be the same issues faced when moving to Win2K. Further more, an application can be run with Win2K emulation to avoid problems if they are suspected. Problem is most techs don't even know how to do that, not that the OS doesn't support it.

I hope you find this post helpful. Please let me know if it was.

Regards,

Mark

 

[AV1611]

Points well taken and everyone is due to opinion. But I am a Consultant and my experience has been a rash of problems with XP Pro. As well as 2003 now. I work for a lot of the medical field. UMC Hospital in Lebanon runs a 2003 Server that has software that should run as a service on startup. Not with 2003. It crashes. And if you set alerts up or restarts, they DON'T work.

Same thing with XP on a lot of different software out there. And not many people at ALL are programming on it. They are familiar with 2k Pro and their software was wrote on it. The platform something is written on is what it usually runs better on.

But trial and error in your Environment will have to speak for you. Go Half XP Pro and Half 2k Pro. Especially if you already have 2k Machines. Then if Xp does better for you, upgrade when the budget allows.

I understand Mark's reasoning. But as we all know, with Microsoft, newer means better but with MORE problems.

Stability is what you want.

AV

 

[digitsdad]

Hello AV,
I just wanted to thank you for your ideas as well. Being that the boss is a tightwad, we may wind up starting off with a mixed environment.
Paul

 

[markdmac]

This is a straighforward process. Just check out this MSKB first.

http://support.microsoft.com/?kbid=325379

I hope you find this post helpful. Please let me know if it was.

Regards,

Mark

 

[markdmac]

Please ignore my last post. This was meant for another thread. Had to many windows open. Sorry.

I hope you find this post helpful. Please let me know if it was.

Regards,

Mark