A few months ago Microsoft released an updated version of the Office Communications Server 2007 Edge Server Deployment Guide.
This document guides you through the deployment of edge servers in your Office Communications Server 2007 topology. You typically deploy edge servers after you have deployed Office Communications Server in your internal network.If you need to communicate with users and organizations outside your internal network by using your Microsoft Office Communications Server 2007 deployment, you need to deploy one or more edge servers. You install edge servers in your perimeter network (also known as screened subnet) so that users outside your organization’s firewall are authorized before they obtain access to your Office Communications Server deployment.
The information in this document includes the following:
- Guidelines to help you decide which edge servers you need and which topologies to deploy.
- Procedures to configure DNS, firewalls, a reverse proxy, and a Director.
- Steps to deploy and configure a load balancer, individual edge servers, and certificates.
- Environment configuration settings.
- Validation of edge server configuration.
Get it here.
The Resource Kit Tools for Office Communications Server 2007 R2 (version 6907.0) was released in February 2009.
You can use the set of deployment, technical tools and references to complement the product documentation delivered in R2. Supported platforms to run the ResKit Tools are Windows Server 2003 Service Pack 2 and Windows Server 2008.
Note that the tools should be used exclusively with OCS 2007 R2 (RTM) only. These are essentially the same tools shipped in the updated OCS 2007 R2 Resource Kit.
Download and more information here.
Microsoft has released the Office Communications Server 2007 R2 Capacity Planning Tool. The Capacity planning and load simulation toolkit is for Office Communications Server 2007 R2 and can be using for planning and sizing situations together with the planning guide.
This release of the Office Communications Server 2007 R2 Capacity Planning Toolkit contains tools and documentation to simplify your hardware planning, provide you with increased knowledge and best practices for performance tuning, and improve your ability to verify the performance of your intended Office Communications Server 2007 R2 deployments.
The Capacity Planning Toolkit is intended for use by IT professionals in a test environment prior to production deployment. These tools should never be used against a live production environment.
Download it here.
Microsoft has release Office Communications Server 2007 R2 as downloadable VHDs ready to use with Hyper-V for testing purpose.
Start evaluating Office Communications Server today. Office Communications Server 2007 R2 delivers streamlined communications for your users so they can find and communicate with the right person, right now, from the applications they use most (like Office Outlook).
Note:
1. This trial software is intended for evaluation purposes only.
2. There is no product support for this trial. You are welcome to share your trial experience with others and to ask for advice by participating in the forums.
It is also recommended to ensure that you have a clean install of x64 edition of Windows Server 2008 to be able to use the Hyper-V technology. Prerequisites, installation steps, OS recommendations, and known issues of Hyper-V can be found here
Download the VHDs from here.
Download Size:
664 KB – 8902.6 MB
When this error is seen in the Communicator 2007 and Communicator 2007 R2 client, it can be a number of issues.
Here’s a few steps to check:
- Validate the password for the service account (RTCComponentService) used on the AppPool “LSGroupExpAppPool”
- Make sure the AppPool is started “LSGroupExpAppPool”
- Make sure the default website running the /Abs – application has a SSL certificate applied and that it’s responding on port 443 (https)
- Shut down and restart the Communicator 2007 (R2) client
These steps helped for me, when seeing the failure “Cannot synchronize address book” on all Communicator 2007 clients.
Address Book regeneration:
In case the Address Book needs to be regenerated, it can be done using these steps:
From the OCS folder: “C:\Program Files\Microsoft Office Communications Server 2007\Server\Core”:
- Run: “abserver –regenUR” and wait 5 min.
- Run: “abserver –SyncNow” and wait 5 min.
A few references:
Error seen in Communicator 2007 R2:
There was a problem connecting to Microsoft office outlook. Your profile is not configured correctly. contact your system administrator with this information.
It can be solved in several ways:
- Make sure the default Outlook profile matches the “profile” = e-mail used for signing into OCS, equal your sip address:
Go to: HKEY_CURRENT_USER\Software\Microsoft\Windows NT\CurrentVersion\Windows Messaging Subsystem\Profiles
Change DefaulProfile to your default profile name (Control Panel > Mail > Profiles)
Or go to: Control Panel > Mail > Profiles, select “prompt for a profile to be used”, restart outlook, select the profile, and click options, and select default profile. Restart outlook.
Another solution can be to run fixmapi.exe on the computer having this problem, If the default profile is already set correctly.
This solved the problem for me on a client running Vista and Outlook 2007 and no Exchange Admin tools.
Further reference:
Microsoft has released Forefront security for Office Communications Server (FSOCS) as RTM.
FSOCS provides fast and effective protection against IM-based malware for OCS 2007 and OCS 2007 R2 environments by including multiple scanning engines from industry-leading security partners. FSOCS also helps reduce corporate liability by blocking instant messages containing inappropriate content.
This release includes:
- 64bit support
- Support for OCS 2007 R2
- Support for OCS 2007 Enterprise Edition server roles
- Integration with OCS 2007 Access Edge role to protect corporate IM from external public IM threats
- Localization in 11 languages
It’s available for download here: FSOCS
I’ve seen this a few times during the installation of OCS 2007 R2, the “Office Communications Server Monitoring Agent” wont start, it immediately stops, with no real errors on screen or in the event log.
Error that pops up, on screen: “some services stop if there is nothing to do”.
Reason, it’s because the pre-requirements for Monitoring Service is not meet, it needs the Microsoft Message Queuing Service (MSMQ).
If you need the Monitoring Service, you’ll need to install the MSMQ.
This can be done using:
Servermanagercmd.exe -I MSMQ-Server
The error is also stated in this forum thread: http://social.microsoft.com/Forums/en-US/communicationsserversetup/thread/418720e6-4c61-46e2-81ac-21350c19e223/
