Welcome to MUCUGUK Sign in | Join | Help

Microsoft Unified Communications & RTC User Group, United Kingdom

OCS 2007 Architectural Capacity, Hardware requirements an dServer Roles

Last post 11-01-2007, 9:54 by saltbartechnologies. 1 replies.
Sort Posts: Previous Next
  •  10-14-2007, 8:18 177

    OCS 2007 Architectural Capacity, Hardware requirements an dServer Roles

    I've spent the past couple of weeks reading up on information about OCS, and stumbled across a couple of references concerning the architectural planning requirements.

    Maybe it's a case that there was far too much information made available, and that we quickly became overwhelmed with the level of information - after all we did ask for it.

    Attached is information that has been cobbled together from several different sources (including Microsoft), that may be of use if you are planning your architecture.

    My only recommendation is that as Microsoft move towards the launch, they will be releasing more upto date guides and marketing information; so it will be worth keeping an eye on the downloads sites and the home pages.

    The document is in XPS format, which can be viewed in either Internet Explorer, or via one of many free viewers that have become available upon the internet - a suggestion would be "XPS Viewer" -http://www.microsoft.com/whdc/xps/viewxps.mspx- which runs on Windows XP Service Pack 2

    Arthur


    Arthur Pounder
  •  11-01-2007, 9:54 187 in reply to 177

    Re: OCS 2007 Architectural Capacity, Hardware requirements an dServer Roles

    Very useful chart, thanks.

    We'll be installing an Enterprise edition SQL database pool for OCS2007, but are currently running an LCS2005-SP1 Standard edition pool containing our SIP enabled users .. i'm assuming at this stage that user migration between pools will be straight forward and something like selecting all users, properties, and adding them to another pool. The MoC should then detect the new pool at next sign-in ?

    JT.

View as RSS news feed in XML
Powered by Community Server, by Telligent Systems