September 2009 - Posts
Yesterday the official Exchange team blog : You had me at EHLO, announced the support policy for the new Exchange 2007 SP2 release. In short: Exchange 2007 SP2 will not be supported on Windows Server 2008 R2.
The team will focus on getting Exchange 2010 ready and supported on Windows Server 2008 R2. Full details in their article here.
It has come to our attention that some articles published here might contain pieces or particles of articles written by other people without a proper source indication or copyright.
We do not intend to steal writings or copyrighted information from other individuals and sincerely apologize for the few occasions this might occured. We will make sure this will not happen again.
Communified.net Team
As some of the users that asked me this question, you might have noticed that your Outlook 2007 autocomplete cache is suddenly quite slow. Even worse, the bigger the NK2 file is, the more slower it gets..
It seems that the problem is caused by the buffer overflow protection settings of the McAfee virusscanner. Until McAfee fixes the issue, you can exclude Outlook from "protection" by adding an exclusion locally for outlook.exe under Buffer Overflow Protection settings:.
- Click, Start, Programs, McAfee, VirusScan Console.
- Right-click on Buffer Overflow Protection and Select Properties.
- With the Buffer Overflow Protection tab selected Click Add.
- In the Process name field type the following: outlook.exe then click OK.
Note: if the options are unavailable or greyed out, youre scanner is probably managed by EPO. See your EPO admin if thats the case.
Last week I spent some time building up a fresh new laptop with Windows 7. Installed Office 2007 en of course the Office Communicator, the OCS Attendant Console and the Live Meeting client with the Outlook Conferencing add-ins.
So far so good, everything seemed to work as expected. Except one thing, there was no presence information available in Outlook. The personnames options in Outlook were grayed out, so unable to set. I tried all the possible Outlook GPO settings but still no luck. Pretty annoying and frustrating
After some more research I noticed the following registry key:
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\Outlook\Call Integration]
Where the REG_SZ:"IMApplication" Value contained the data: Attendantconsole.exe
Hmm, this couldn't be right, I only use the Attendant console for testing purposes and nothing else. I changed the registry value mentioned above to: Communicator.exe. Restarted Outlook and... problem solved. So it seems that if you install the OCS Attendant console after the Office Communicator it assumes the Attendant Console will be your default IM Application. Conclusion you can install both applications (but not run at the same time) but only one of them can be the preferred client to integrate presence in to Outlook.
Microsoft has just released a new white paper on using certificates with Office Communications Server. Although entitled "OCS 2007 R2 Deploying Certificates" it actually covers both 2007 and 2007 R2 versions of OCS.
This is a very comprehensive document (just short of 100 pages) that covers everything from basic requirements down to specific scenarios like sample LCSCMD commands for requesting certificates for a reverse proxy. A number of the common problems and misunderstood areas have been addresses in much more detail and the original planning and deployment documents, so we highly recommend reading through this document.
The white paper can be downloaded directly from the link below:
Deploying Certificates in Office Communications Server 2007 and Office Communications Server 2007 R2
http://go.microsoft.com/fwlink/?LinkId=163083
The OCS R2 documentation set has been updated:
Overview
The full set of Office Communications Server 2007 R2 documentation is contained in the download file named Communications_Server_2007_R2_Documentation.chm.
Selected, high-value sections of the documentation are also provided as separate Word documents for IT Pros who are interested in specific topical areas. Topics covered include:
- New server and new client features
- Planning and architecture
- Deploying Certificates (applies to both Office Communications Server 2007 and 2007 R2)
- Deploying Enterprise and Standard Edition
- Deploying specific types of servers and some related technologies, such as load balancers, including Monitoring Server, Archiving Server, Group Chat Server, and Edge servers
- Deploying features, including Enterprise Voice, dial-in conferencing, and Response Group Service
- Upgrading from the Evaluation Edition to a full released version
- Migration from Live Communications Server 2005 or Office Communications Server 2007
- Administering Office Communications Server 2007 R2, Communicator Web Access, and Group Chat
- Backup and restoration
- Security
- Troubleshooting
- A reference guide for using the command-line to deploy and manage Office Communications Server 2007 R2
- A glossary of unified communications terms used in the documentation
- A documentation roadmap
Find download links here