Re: Help on figuring out what workload for what server.....

Hello Andy,

Mathieu has taken out the SBS at the beginning. (SBS taken apart) His proposal
doesn't include the SBS. Because you are near on 75 users i think and if
you will grow up his proposal give you the option for that.

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.

> On Sep 25, 4:46 pm, "Mathieu CHATEAU" <gollum...@free.fr> wrote:
>
>> Hello,
>>
>> SBS taken apart, never install Exchange on a DC...
>>
>> 60 users is close to 75, which is the SBS limit.
>>
>> Let me propose the target. You need:
>> -2 DC
>> -1 exchange
>> -1SQL
>> -1Sharepoint
>> -1 Symantec
>> -1 WSUS
>> -some license manager
>> -1 file server / printer /fax
>> -1 ERP
>> -1 TS
>> -1 backup
>> You have:
>> Server 1: Compaq Proliant ML370 G2 (PIII 1.13 GHZ, 1.5 GB RAM, 6 18
>> GB SCSI
>> Hard drives, 2 Gigabit NICs
>> Server 2: Compaq Proliant ML370 G2 (PIII 700 MHZ, 1 GB RAM, 6 9 GB
>> SCSI
>> Hard drives, 2 Gigabit Nics
>> Server 3: HP Proliant DL 380. Dual Intel Xeon 3.4 GHZ. 3 GB of
>> RAM. 6 72
>> GB SCSI Drives. 2 Gigabit Nics
>> Server 4: HP Business Desktop. 2 GB of Ram 1 Pentium 4 3.0 GHZ.
>> Server 5: Hp Business Desktop. 650 MB of RAM. 1 P4 2.8 GHZ
>> Server6*:HP ProLiant DL 360. 4 GB of RAM, 2 1.8 GHZ Quad Core Xeons,
>> 6 146
>> GB SCSI Drives
>> My proposal:
>> upgrade Server1 (and server2 if possible) to 4G of ram (except if you
>> move
>> on exchange 2003 to server6)
>> Make server 2 DC+GC + DNS
>> Make server 6 "2003 standard" + sharepoint + lake knowledge.
>> move WSUS to server 6
>> move Veritas to server 6
>> remove server 5 (not a real server
>> You may concentrate services on server 3 and server 6*. But SQL would
>> love
>> to stay alone for performance.
>> You will have to replace server 1 & 2 soon. Adding them memory is
>> just to
>> stay alive
>> Remove these "Business desktop" which don't have raid i guess as soon
>> as you
>> can
>> --
>> Cordialement,
>> Mathieu CHATEAUhttp://lordoftheping.blogspot.com
>> "Andy" <andy.lisow...@gmail.com> wrote in message
>>
>> news: ups.com...
>>
>>> Ok, this may be long but bear with me. I am at a smallish
>>> manufacturing company with about 55-60 users. I am going to tell
>>> you my current server configuration first.
>>>
>>> Server 1: Compaq Proliant ML370 G2 (PIII 1.13 GHZ, 1.5 GB RAM, 6 18
>>> GB SCSI Hard drives, 2 Gigabit NICs
>>>
>>> Runs: Windows 2000 Server. It is the Domain Controller/GCS.
>>> Exchange 2000. File server. Symantec Antivirus Corporate Edition/
>>> Symantec System Center.
>>>
>>> Server 2: Compaq Proliant ML370 G2 (PIII 700 MHZ, 1 GB RAM, 6 9 GB
>>> SCSI Hard drives, 2 Gigabit Nics
>>>
>>> Runs: Windows 2003 Server. WSUS. Various Server based licensing
>>> managers (Autocad, for example), File Server. Print Server. Fax
>>> Server.
>>>
>>> Server 3: HP Proliant DL 380. Dual Intel Xeon 3.4 GHZ. 3 GB of
>>> RAM. 6 72 GB SCSI Drives. 2 Gigabit Nics
>>>
>>> Runs: Windows 2003 Server. Microsoft SQL Server Enterprise
>>> Edition. Visual Manufacturing (Our ERP type system). This server
>>> typically has half a gig of RAM unused and 2 GB of Page File use.
>>>
>>> Server 4: HP Business Desktop. 2 GB of Ram 1 Pentium 4 3.0 GHZ.
>>>
>>> Runs: Windows 2003 Server. Terminal Server
>>>
>>> Server 5: Hp Business Desktop. 650 MB of RAM. 1 P4 2.8 GHZ.
>>>
>>> Runs: Windows 2003 Server. Veritas backup software.
>>>
>>> We are looking at implementing a Sharepoint Server and a product
>>> called Knowledge Lake which would allow us to scan in and auto file
>>> a bunch of documents. It would be using SQL Server pretty heavily.
>>>
>>> I was thinking about buying....
>>>
>>> HP ProLiant DL 360. 4 GB of RAM, 2 1.8 GHZ Quad Core Xeons, 6 146
>>> GB SCSI Drives
>>>
>>> With Windows SBS 2003 (I'm aware of user limitation and all the
>>> other stuff already. Just stick with me on this one even if you
>>> don't agree with SBS 2003 necessarily.)
>>>
>>> Now I would have.....
>>>
>>> New Server Running: Domain Controller/CGS, Exchange 2003, SQL
>>> Server, Sharepoint/Knowledge Lake, File Server
>>>
>>> Server 1 (Old Domain Controller) running: Windows Server 2003.
>>> Terminal Server. Outlook Web Access
>>>
>>> Server 2 running Windows Server 2003, Symantec AV Server. Print
>>> Server, Backup Server, Licensing Server. Backup Catalog Server
>>>
>>> Server 3 Running Windows Server 2003, SQL Server, the Visual
>>> Manufacturing system, and being a Backup Catalog Server
>>>
>>> Does this seem like a legitimate configuration or would a
>>> Sharepoint/ KNowledge Lake type database lumped on to the Exchange
>>> Server cause a major problem with performance?
>>>
>>> The other option may be to upgrade the Server running our ERP system
>>> to 2003 Enterprise Server, bring it up to 8 GB of RAM, and use that
>>> for both the Visual Manufacturing server and the
>>> Sharepoint/Knowledge Lake Server.
>>>
>>> Another option has been to stand pat with what the current servers
>>> have and just buy another seperate server to run the Sharepoint/
>>> Knowledge Lake software. This would leave us at Windows 2000 Active
>>> Directory and Exchange 2000.
>>>
>>> Any comments on what you would do would be much appreciated. Price
>>> is very much a limiting factor, but if performance would be terrible
>>> on any one of the setups I want to avoid it.
>>>
>>> Thanks,
>>>
>>> Andy
>>>
> Wait a minute, you don't have to have Exchange on the Small Business
> Server?
>