IT Employment

General discussion


Moving from peer to peer to MS Small Business

By dtomandl ·
We are going to move from or peer to peer network, to a server based. We would like to incorparate email, printing, and file sharing and maybe host our own site. Does anyone have any guides lines that we should start with, like start with the file sharing, then email, then the web site. Is hosting a wab site a big security risk? How easily can it get hacked into.
Is there some kind of beginners guide to give me some direction?

Thanks in advanced!


This conversation is currently closed to new comments.

Thread display: Collapse - | Expand +

All Comments

Collapse -

Use entry leval NOvell Linux

by Oz_Media In reply to Moving from peer to peer ...

You will get afordability, security, performance that MS cannot and never has offered. Plus woith Linux for desktops you get a full desktop suite full of useful software and tools, inclusive.

Your server requirements are VERY minimal where as a MS solution will cost far more in hardware (unneccessarily of course), maintenence is loss, fewer patches, fewer reboots, fewer crashes, fewer vulnerabilities etc.

MS is old hat and not stacking up to better technologies, Novell Linux and Linux for Desktops (as easy as Windows to become familiar with and use)is going top save you time AND money while offerinh security and stability so hat you can get work done instead of patching and cleaning all day.

Collapse -


by dtomandl In reply to Use entry leval NOvell Li ...

After many disscusion with upper management, they are not convinced the the Novell Linux match up is right for us. They like the MS name and want to stick with it(not my choice). Thanks

Collapse -

by secure_lockdown In reply to Thanks

don't use linux if you are a MS shop and ESPECIALLY if mgtm are keen on MS. linux has benefits - but its a very different beast. if you don't have the resources to support it - you are up s*&t's creak without a paddle.


Collapse -


by dtomandl In reply to

Thanks, I went into a meeting the other day and one of the UM asked about using both. He will be informed!

Collapse -

Microsoft's SBS 2003

by CG IT In reply to Moving from peer to peer ...

We use SBS 2003 Platinum edition with ISA server [did use SBS 2000]. I've familiar with it so I like it and recommend it. Others will undoubtably boo and throw paperwads cuz I suggest a Microsoft product but it works for us.

Collapse -


by dtomandl In reply to Microsoft's SBS 2003

Have you had any kind of formal training? I am going to need it, I think. When you first set the box up, what order did you set it up in? Does it matter? I need some kind of plan to show the Upper Managment on how I will attack this endvor. Are there any good resources avaliable on net about this. Things I know, I will be setting up 2 domains, one for the our office and one for our shop. I am not sure if this is the right approach, but I dont want the shop people to have access to office files. Any help is greatly appericated!!! as the UPs are pushing to get this in place ASAP!

Collapse -

by CG IT In reply to Questions

Yes I have formal training MCSA/CCNA/ MCP+ Security.

When I first setup the box the installation Wizard basically walk you through the entire process step by step.

NO DO NOT SETUP 2 SEPERATE DOMAINS!!! SBS will NOT establish a trust relationship with other domains. It will allow subdomains within the same domain namespace [inplicit trust].

Yes you can use Active Directory to create security polcies for groups of users e.g. one for the pencil necks and another one for the worker bees. Then you assign folder permissions ADDING the pencil neck group and leaving out the worker bee group. REMOVE the everyone group or just uncheck all the boxes. DO NOT USE Deny on the everyone group cuz then everyone will be denied access.

Collapse -

by CG IT In reply to

good sources of information: Microsoft SBS 2000 web site, Microsoft SBS Newsgroups.

NOTE: SBS intergrates via wizards the setup process for Exchange, DNS, DHCP,IIS,SQL,RRAS, ISA Shared Fax, Shared Modem, DFS, your internet connection instead of having to configure each one individually. It also has a all encompassing management console to manage each componet [in lieu of a MMC snap in you create] It also has a Health Monitor which will give you info on each componet [ISA,Exchange,DNS, etc] Each one DOES operate just like a stand alone server though so if you know DNS,DHCP,ISA,SQL,Exchange you'll know how to work it in SBS. SBS 2003 is different than SBS 2000 mostly in the GUI and how it's laid out.

Collapse -

by CG IT In reply to

In response to the guy who said keep things seperate cuz if one fails the whole thing comes down, well If a hardware componet fails, yeah the whole box comes down and people start booing you in the hallway.

If exchange fails, mail fails but nothing else. SQL Server will NOT install on the same drive as SBS O/S. You can add a seperate drive for SQL on the SBS box if you want. You can have a member server on SBS to run SQL. Exchange MUST be installed WITH SBS and can not be installed seperately [part of the SBS installation process]. You MUST patch each componet seperately e.g. you've got to go to the Exchange site and manually download the patches and service packs and install em. Same with ISA server and with SQL Server. W2K service packs and hotfixes will work with windows update or SUS update BUT SUS update will NOT get Exchange/SQL/ISA server patches/hotfixes etc.

SBS 2000/2003 flavors IMHO works BEST with ISA server AND 2 NICs. WAN and LAN. If you've got to subnet out get a managed switch . I use Norton Corporate Antivirus 8.1 w/Exchange filtering. I like it. Set it up and it basically runs itself. Gets updates, sends em out to clients, does auto scheduled scans, does a network Notice if a virus is found [sends you and email to boot] and is managed on the SBS DC box. I use a Seagate Travan 20 tape backup to backup the SBS box and use the backup program that comes with W2K. I also use a hardware RAID mirror for the SBS box. With everthing on it including 58 users and their mailboxes I use about 15 GB[but I'm constantly cleaning out user mailboxe stores of old deleted files and DO NOT allow users to store em more than a couple of days. Of everything THAT chews up disk space the most.

I've run SBS now for about 5 years going from a small 6 computer network to a 4 server 58 workstation network [small by comparison to HUGE corps in #'s but nonetheless it operates the same as a huge just on a small scale] Remember its quality not quantity that counts. .

Collapse -

Only two that are worth anything

by pgm554 In reply to Moving from peer to peer ...

Novell SBS 6.5 or M$ SBS 2003.

They are both very good at what they do.

Major differences between the two are as follows:

1. Novell will scale to 100 users (SBS 2003, 75 users)

2. Is cheaper ($399 vs. $599 for SBS 2003 Basic 5 users)

3. Novell allows for 2 servers out of the box (and more for a fee) M$ allows 1, if you want to add more, it must be an independent stand alone box (no trusts allowed)

4. Novell includes 2 node clustering out of the box (iSCSI SAN included)

5. Novell Branch Manager (WAN appliance for file and print) for remote offices. (Can?t do that with SBS 2003, no trusts allowed)

6. Zenworks for Desktops (imaging, application, and patch management) it is an SMS equivalent that actually works without having to pay extra.

7. GroupWise (Exchange equivalent)

8. Border Manager (ISA equivalent)(ISA 2000 only available w/M$ 2003 premium edition)

With SBS 2003 you just get basic file, print, WEB server for $599, if you want the whole banana,, it's $1499.

So, SBS 6.5 gives you everything SBS 2003 does (and more) and is roughly 75% less expensive.

Related Discussions

Related Forums