Discussion Locked

Re-designing network - throw out SBS?

0 helpful
15 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I run a network of 15 users, which will probably only go to 25 in the next 12 months.

However, I have one powerful server running SBS 4.5, NT 4 (compaq Prosignia Twin PII Xeon 450, 512Mb RAM).

On this we run:
ERP Software running on Progress 9 (8 users) + ODBC connection for reports, set to get @ 5x more use next 12 months (& up to 15 users).

Sales & Marketing Software running on Pervasive SQL, now 1 user, will be 4 users.

Payroll software running on Progress 8, 1 user, will remain1 user.

Veritas Backup Exec v8.5

3 Gb of shared files.

+ All the SBS packages (Exchange, Proxy etc..), most of which we do not use because:

a - our SBS console doesn't function properly
b - If I activate Exchange, DHCP fails.
c - I am planning to expand the network to include dedicated mail server, web server, scanning server (w/ Adobe Messenger)

So. My background is in programming / analysis, not in Net Admin, but I am doing a lot of reading up on the subject, and I think my SBS set-up is a dead donkey.

But I may not have done enough reading. I would like someone to propose to me a good network design, whether that be making better use of the existing SBS set-up (and how to fix those problems!) or how to go about distributing my services over a better infrastructure.

Thanks to anyone who has answers :-)

Anton Wilson

15 replies

by shanghai sam

If the budget is not a problem. I whould say:
dont mix Application servers with File/print/netorking servers. By that I mean, use one server for DHCP and WINS (if thats what you use) and file/print serving. Make sure that that server has a good recovery plan, do backups every night, use RAID harddrives.
On an application server make sure that it dosnt share file and printer (even a SQL database is better that its on a file server not on the same server as the SQL server itself) that way SBS will work fine. Always have a recorvery plan for all servers but you dont need daily backup on an application server since the data dosnt change as often, RAID is also not a bad idea even on an application server but its not a must in such a small network.

by shanghai sam

If the budget is not a problem. I whould say:
dont mix Application servers with File/print/netorking servers. By that I mean, use one server for DHCP and WINS (if thats what you use) and file/print serving. Make sure that that server has a good recovery plan, do backups every night, use RAID harddrives.
On an application server make sure that it dosnt share file and printer (even a SQL database is better that its on a file server not on the same server as the SQL server itself) that way SBS will work fine. Always have a recorvery plan for all servers but you dont need daily backup on an application server since the data dosnt change as often, RAID is also not a bad idea even on an application server but its not a must in such a small network.

by shmaltz

If the budget is not a problem. I whould say:
dont mix Application servers with File/print/netorking servers. By that I mean, use one server for DHCP and WINS (if thats what you use) and file/print serving. Make sure that that server has a good recovery plan, do backups every night, use RAID harddrives.
On an application server make sure that it dosnt share file and printer (even a SQL database is better that its on a file server not on the same server as the SQL server itself) that way SBS will work fine. Always have a recorvery plan for all servers but you dont need daily backup on an application server since the data dosnt change as often, RAID is also not a bad idea even on an application server but its not a must in such a small network.

by kmsanton

Introduced a few more questions as well as answering a few - not the fault of the writer, but unfortunately of my incomplete knowledge of the subjects.

by mckaytech

In a single-server environment that requires SQL, Exchange and Proxy services, SBS is very cost effective and even throws in a few freebies like fax and modem sharing.

But the only reason I would think about sticking with SBS in the scenario you presented is if you want to implement Exchange within the existing product licenses (and costs). You're already using a non-Microsoft SQL product so you don't need that part and there are better products than Proxy server for much less money. Without the Exchange factor, you'd be better off with a standard install of NT Server or W2K Server.

As far as your problem list, I never did like the SBS console and tend not to use it anyway. There are alternate management tools available.

The Exchange/DHCP problem is a complete mystery to me. But it should be solveable - the two can, and have been, successfully implemented in many SBS installations.

Your expansion plans can be managed in several different ways. A standard installation of NT Server supports IIS and that will take care of the Web server part and you can add member servers to an SBS domain without too much trouble if you need to bring additional hardware on-line.

If it were my problem to solve, I guess I would probably move the SQL components to an NT4 or W2K member server, where they could live with the web server and, perhaps, the scanner server. Exchange and the domain components (PDC, WINS, DHCP, Proxy Server) would remain on the SBS server.

paul

by rachel_s

Anton:

I believe that SBS has a limit of 25 users/connections - so be careful. I'd double check to make sure, but if you are going to have 25 people, you may want to evaluate how many concurrent connections you are going to have and how quick you may be expanding.

-Rachel

by kmsanton

not designed to solve my problem, and... didn't!

But it was a good point that could have had a big impact on my decision, however I was already aware that SBS 4.5 increased the user limit to 50.

by wlbowers

I have SBS 4.5 and have had the same problems plus a few. My SBS came with 25 users. I went to fixed tcpip addresses and disabled the DHCP, this was at a microsoft techs suggestion. Less headaches that way. You know that you have two free incident calls with Microsoft tech support. An incident is as many calls necessary to solve the problem. Once I used my 2 incidents to weed out my problems, things are running smooth enough I am going to wait until I can talk the boss into upgrading to server2000.

SBS is a lot of apps in one package. It can be a mess to manage. I did get real intimate with the Microsoft knowledgebase. I havent had any problems for months.

Hope this helps Lee

by kmsanton

Didn't really offer any advice on expanding the network, but did point me in the direction of the 2 free tech calls, which might help if approached correctly.

by jolly roger

Unless you've got more money to throw around than most of us do, I would suggest upgrading to the just-released SBS 2000. Hopefully, this will solve all, if not most, of your problems. If not all, then perhaps the free tech calls could get it cleaned up. SBS 2000 is Windows 2000-based and I think it's a much more reliable platform. SBS 2000 continues the SBS 4.5 50-seat tradition. Another reason I suggest the upgrade is that Microsoft has consistently improved each version of SBS, from the admiitedly horrible 4.0, to SP1, to 4.1, and then 4.5. I don't have any first-hand experience with SBS 2000 (it just came out on Feb. 21) but based on my Windows 2000 experience I much prefer it over NT4. One final word of caution is to be very circumspect of changing things in SBS. It's very touchy about that. Even moving folders around can cause major problems. Hope this helps.

by shanghai sam

I have heard that for the moment, SBS 2000 is not an option, due to it's current instability (teething troubles).

I just don't like SBS, but perhaps we can get a better set-up with it in the future. Thanks for your answer.

This discussion is closed to new replies.