December 2007 - Posts
OCS 2007 has a bunch of documentation waiting to be read but sometimes it is a tough task to get the documentation piece by piece. We can download each document in this page: http://technet.microsoft.com/en-us/bb629431.aspx however we can download all together in a single download, as it follows:
All Office Communications Server 2007, Office Communicator 2007 and Live Meeting 2007 client for Office Communications Server documentation
This documentation package contains all Office Communications Server 2007, Office Communicator 2007 and Live Meeting 2007 client for Office Communications Server documentation.
Get all documentation here: http://www.microsoft.com/downloads/details.aspx?FamilyId=760A3FF9-7F82-4A5F-841D-5E528B1DA334&displaylang=en
Powered by Zoundry
A new update of the Exchange Server 2007 Mailbox role storage requirements was released, the new updates are listed bellow:
- We have updated the log generation numbers per message profile to be in line with our updated guidance.
- In v11.8, we decided to list the database cache per mailbox in the Storage Requirements results section. However this lead to confusion because it was named "Memory Profile / Mailbox" which implied that you would only utilize the associated amount of memory with the message profile (i.e. 5MB with Heavy profile), however that is not always the case. For example, 1200 2GB Light message profile mailboxes only requires 5GB of RAM (1200 * 2MB + 2GB), however the design requires 13 databases, which with SP1 requires 6GB of RAM. ESE will utilize 4GB of that RAM for the cache. As a result, 4096MB / 1200 ≈ 3.5MB per mailbox. So to make this clear, we have changed this text to be "Database Cache / Mailbox" which indicates how much cache is available per mailbox.
- In the scenario where you override the IOPS prediction formula for your mailbox tiers, we have adjusted the "Read:Write Ratio" input to allow you to enter any read percentage you would like, rather than restricting you to a few key ratios.
- We updated the "Database Reads / Mailbox" calculation description.
- We updated the Log Replication Requirements worksheet, simplifying the data displayed in the results section.
- We have included new functionality for log replication requirements. You now have the input options for entering your network link type and its associated latency. These options are then used to recommend TCP/IP optimization settings for Windows Server 2003 when utilizing geographically dispersed clustering and/or standby continuous replication. In addition, if the chosen network link cannot sustain the throughput requirements for log replication, we will recommend an appropriately sized network link and Windows Server 2003 TCP/IP optimization settings.
Read more at source: http://msexchangeteam.com/archive/2007/12/20/447780.aspx
Powered by Zoundry
Here are some quick descriptions to some other helpful docs in the OCS Library that will help with your Office Communications Server 2007 deployments.
Read more at source: http://communicationsserverteam.com/archive/2007/12/07/34.aspx
DPM protects either Exchange Server 2003 SP2 or Exchange Server 2007. During the protection group wizard we are able to copy the ese.dll and eseutil.exe in order to run eseutil to validate the backup process on the DPM side to decrease the workload in Exchange Servers.
Basically we just need to copy both files from the Exchange Server box to DPM Server, but we have some variables such as: Which DPM are we running? (x64 or 32bits), Exchange 2003 doesn't run in x64, Exchange Server 2007 doesn't run in 32bits.
To resolve this issue of DPM version versus Exchange Server versions, there is a section into the DPM documentation where we can find a table with all possible configurations, as it follows:
Grande abraço,Anderson Patricio
SP1 introduced some changes in the ESE. MsExchangeTeam.com has been writing about these changes, we can see it in the following two posts:
The Exchange Server documentation team is pleased to announce the following Exchange Server 2007 content.
You can see these articles and other Exchange Server documentation content in the Microsoft Exchange Server TechCenter.
To see what content has changed for Exchange Server 2007 with Service Pack 1, take a look at What's New in Exchange Server 2007 SP1.
The following downloads are also now available for SP1 content:
Read more at source: http://msexchangeteam.com/archive/2007/12/05/447692.aspx
I've been upgrading some Exchange Server 2007 to SP1 since last November 30, and here are some hints that can be helpful in your environment:
- Install the .Net Framework 2.0 SP1 (http://www.microsoft.com/downloads/details.aspx?FamilyId=029196ED-04EB-471E-8A99-3C61D19A4C5A&displaylang=en) or at least this kb (http://support.microsoft.com/default.aspx/kb/942027)
- If you are running Veritas Backup Agent for the Operating Sytem, disable it before starting the upgrade process (the process name should be beremote.exe)
- If you are installing using a TS session make sure that there is no other session using Exchange Management Shell or Exchange Management Console
- If you are using ForeFront for Exchange version 10, you have to update it to SP1
- If you have ExchangeServer authentication selected in the receive connector, this connector must have the fqdn or netbiots name of the Hub Transport server in the FQDN parameter
- If you are using ForeFront you must make sure that the ForeFront services are disable during the upgrade process (see this kb: http://support.microsoft.com/?kbid=929080)
- Some Services might have open files, the setup will inform the process and PID. If you need more information you can run tasklist | find "<PID-Number>"
- If you've installed any software that requires a reboot, you should do that before deploy SP1 because the setup will require a reboot in order to continue the SP1 upgrade process
By the way, you can get the SP1 for 32bits and x64 at http://go.microsoft.com/fwlink/?LinkId=104387
Have you experienced something different? If yes, please drop me a line and I will be adding to the current list.
Ps.: Thanks for Mauro Rita from Portugal by correcting the .Net Framework SP1 link.