The Office Communications Server 2007 R2 Management Pack monitors all editions of Office Communications Server 2007 R2.
The Office Communications Server 2007 R2 Management Pack monitors Standard and Enterprise Edition of Office Communications Server 2007 R2. This release also incorporates the Quality of Experience (QoE) MP which was previously a separate Management Pack. Monitored types are event log entries, performance counters, as well as stateful monitoring of QoE. Note that this version of the Management Pack only monitors Office Communications Server 2007 R2, and cannot be used to monitor Office Communications Server 2007.
Office Communications Server 2007 R2 monitored objects are:
Enterprise Edition, Standard Edition, A/V Authentication service, Application Sharing Server, A/V Conferencing Server, Conference Announcement Service, Conference Attendant Service, Web Components, Archiving Server, Communicator Web Access, Mediation Server, Monitoring Server, CDR Server, SIP Proxy Server, A/V Conferencing Edge service, Access Edge service, Web Conferencing Edge service, Monitoring Server, QoE of A/V Conferencing Server, QoE of Mediation Server, and QoE of network locations.
Feature Bullet Summary:
Alerts indicating service impacting events, Alerts indicating configuration, and other non-service impacting issues, State monitoring of Office Communications Server services, and Product knowledge: Cause and resolution of identified problems.
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).
Once installed, the OCS trial lasts for 60 days.
It is a multipart download that is rather large overall, but includes just about every piece imaginable of the OCS suite, pre-installed:
Windows 2008 Domain controller:
DC.part1.exe, DC.part2.rar, DC.part3.rar
Thankfully, there is a relatively simple workaround for Outlook 2007 and an additional registry setting needed for Outlook 2003 SP2.
Step 1 (Exchange 2000/2003 only): Add a SIP proxy address in Exchange Server for the user account that specifies the user's SIP URI.
Step 2 (Outlook 2003 SP2 only):
By default, Outlook 2003 SP2 does not search for the user's SIP address to get the presence information.
1. Click Start, click Run, type regedit, and then press ENTER.
2. Locate the following registry subkey: HKEY_CURRENT_USER\Software\Microsoft\Office\11.0\Common\PersonaMenu
3. Click Edit, point to New, and then click DWORD value.
4. Type QueryServiceForStatus, and then click OK.
5. Double-click QueryServiceForStatus, type 2, and then click OK.
6. Click Edit, point to New, and then click DWORD value.
7. Type EnableDynamicPresence, and then click OK.
8. Double-click EnableDynamicPresence, type 1, and then click OK.
9. Exit Registry Editor.
After you create these registry keys, Outlook 2003 SP2 shows presence information.
I've seen many topics on forums and Microsoft PSS tickets, but I'm curious if anyone out there has 100% successfully setup OCS 2007 R2 Edge server with PIC to AOL.
I put emphasis on 100% successful because the current behavior I see typically is like this:
Sometimes people on AOL will receive IMs from users behind the OCS 2007 R2 Edge.
Sometimes people behind the OCS 2007 R2 Edge will receive IMs from AOL users.
The behavior seems very inconsistent.
If you use an OCS 2007 R1 Edge, AOL connectivity seems to "just work".
I suspect this is a bug in the codepath for AOL PIC in the R2 Edge server, but I have no proof. So, I'm asking, has anyone setup OCS 2007 R2 Edge with PIC to AOL and it works 100% of the time? If so, I want to pick your brain to see where our setups might be different.