locked
Hardware Requirements for OCS 2007 R2 400 users RRS feed

  • Question

  • Hi,

    I'm looking to deploy OCS 2007 R2 for upto 400 internal users (no external/federated users).

    Our intention is to use a single Standard Edition Server and a Database server for archiving, however the hardware specs in the documentation all show numbers for ~5000 users across their given user model.

    Seeing as we will be <10% of this number the hardware specs seem rather excessive if someone can explain to me how the requirements are determined I can hopefully work out our requirements for myself.

    Any help is appreciated (and yes I have read through the documentation ;))

    Cheers.

    Tuesday, April 21, 2009 9:30 PM

All replies

  • The standard sizing is 8GB for the STD edition and obviously this is much for only 400 users but ...
    I would use at least 4GB of memory for OCS STD because there are many services that run under the STD edition
    For processors it depends how heavy you are going to use Audio/Video Conferencing & Desktop sharing but a Dual Core should be sufficient



    - Belgian Unified Communications Community : http://www.pro-exchange.be -
    Thursday, April 23, 2009 11:14 PM
  • The standard sizing is 8GB for the STD edition and obviously this is much for only 400 users but ...
    I would use at least 4GB of memory for OCS STD because there are many services that run under the STD edition
    For processors it depends how heavy you are going to use Audio/Video Conferencing & Desktop sharing but a Dual Core should be sufficient



    - Belgian Unified Communications Community : http://www.pro-exchange.be -

    I would say A/V will increase over time, the machine will have 1 quad core chip available and 4GB of RAM.

    Do you happen to know the disk IO numbers for archiving are per user? I'm trying to determine if there would be any significant performance impact in not using high speed SAS disks (the current thought is to use 4 7200rpm SATA disks setup in RAID 10)

    Thanks again for any help.
    Friday, April 24, 2009 11:20 AM
  • There are actually no real IO numbers in any sizing docs
    I suspect that you SATA disks will be able to cope with 400 users.
    Will the Archive server be a dedicated machine?

    What you can find in the docs is this typical sizing for HW
    This is a sizing based on 100.000 endpoint so that is very high number of users

    Hardware component

    Minimum requirement

    CPU

    • Dual processor, quad-core 2.0 GHz+
    • 4-way processor, dual-core 2.0 GHz+

    Memory

    8 GB

    Disk

    • 2x RAID 1 (mirrored), 10K RPM or 15K RPM for system files
    • 2x RAID 1 (mirrored) 15K RPM for database log files
    • 8x RAID 10 (striped and mirrored) 15K RPM disks for database data files

    Network

    2 x 1 Gbps network adapter


    You can find a similar thread that talks about sizing
    http://social.microsoft.com/Forums/en-US/communicationsservercapacityplanning/thread/461cf6a4-604e-4ef6-b416-3793f8428b2f/
    - Belgian Unified Communications Community : http://www.pro-exchange.be -
    Monday, April 27, 2009 1:22 PM
  • There are actually no real IO numbers in any sizing docs
    I suspect that you SATA disks will be able to cope with 400 users.
    Will the Archive server be a dedicated machine?

    What you can find in the docs is this typical sizing for HW
    This is a sizing based on 100.000 endpoint so that is very high number of users

    Hardware component

    Minimum requirement

    CPU

    • Dual processor, quad-core 2.0 GHz+
    • 4-way processor, dual-core 2.0 GHz+

    Memory

    8 GB

    Disk

    • 2x RAID 1 (mirrored), 10K RPM or 15K RPM for system files
    • 2x RAID 1 (mirrored) 15K RPM for database log files
    • 8x RAID 10 (striped and mirrored) 15K RPM disks for database data files

    Network

    2 x 1 Gbps network adapter


    You can find a similar thread that talks about sizing
    http://social.microsoft.com/Forums/en-US/communicationsservercapacityplanning/thread/461cf6a4-604e-4ef6-b416-3793f8428b2f/
    - Belgian Unified Communications Community : http://www.pro-exchange.be -

    Thanks again for the info.

    I guess I'll just need to setup and test it out, worst case scenario would be a re-configuration of the archiving server. Cheers.
    Thursday, April 30, 2009 2:26 PM
  • I run OCS on VMware ESX 3.5 using 2GB RAM and 2CPU. It's currently using 300Mhz.

    Looking at the past month the CPU have never reached 100% except for once.

    Do not overscale your implementation.

    I'm sure you can add more hardware if the implementation is successful.

    You do not need the minimum as Microsoft recommends. It's scaled for thousands of users.
    Monday, May 4, 2009 4:01 PM
  • Be very carefull when virtualising OCS certain scenario's will have bad experience especially if you use Audio & Video Conferencing.
    - Belgian Unified Communications Community : http://www.pro-exchange.be -
    Monday, May 4, 2009 8:44 PM
  • Deli please stop spreading these rumours. We've runned OCS since OCS 2007 Beta years ago and never experienced any problems. If you experience problems like you somehow fail to go into detail on, please look for other details than blaming the virtualization layer.
    Wednesday, May 6, 2009 9:06 AM
  • Good to hear that it works for you.
    But keep in mind that supportability is a big thing and that I have had many companies leaving the virtualization infrastructure for OCS because of problems.
    Unless Microsoft specifies otherwise I will never suggest people to go virtualized with OCS! That is my personal opninion, everyone can have his own opinion.

    So I will adapt my previous post:
    Be very carefull when virtualising OCS certain scenario's MIGHT have bad experience especially if you use Audio & Video Conferencing.
    - Belgian Unified Communications Community : http://www.pro-exchange.be -
    Wednesday, May 6, 2009 11:51 AM