More information here:
http://blogs.technet.com/b/nexthop/archive/2012/04/16/office-communications-server-2007-r2-updates-now-available-april-2012.aspx
Showing posts with label ocs r2. Show all posts
Showing posts with label ocs r2. Show all posts
Tuesday, 17 April 2012
Friday, 11 March 2011
Cumulative update package for Communicator 2007 R2: March, 2011
Monday, 8 November 2010
Office Communications Server 2007 R2 Tool: Adoption Reporting
From DrRez blog:
More info about it here.
The Adoption Reporting Tool enables administrators to more easily measure both usage and adoption of Microsoft Office Communications Server 2007 R2 in their enterprise.
More info about it here.
Friday, 24 September 2010
Friday, 23 July 2010
OCS, MOC and Group Chat Updates: July 2010
A couple more updates for OCS 2007 R2.
Updates that are released for Communications Server 2007 R2 - KB968802
Description of the cumulative update package for Communicator 2007 R2: July 2010 - KB2028888
This cumulative update fixes the following issues:
This package seems to have no new updates, just previously released updates.
Description of the update for Office Communications Server 2007 R2 Group Chat Client: July 2010 - KB2032922
Description of the update for the Office Communications Server 2007 R2 Group Chat Administration Tool: July 2010 - KB2032949
This package seems to have no new updates, just previously released updates.
Updates that are released for Communications Server 2007 R2 - KB968802
- Update for Audio/Video Conferencing 2028578 Description of the cumulative update package for Office Communications Server 2007 R2, Audio/Video Conferencing Server: July 2010
- Update for Core Components 983471 Description of Cumulative update for Office Communications Server 2007 R2, Core Components: July 2010
- Update for Communicator Web Access 983469 Description of the cumulative update package for Office Communications Server 2007 R2, Communicator Web Access: July 2010
- Update for Conferencing Attendant 2028574 Description of the cumulative update for Office Communications Server 2007 R2, Conferencing Attendant: July 2010
- Update for Conferencing Announcement Service 969823 Description of the update package for Office Communications Server 2007 R2, Conferencing Announcement Service: July 2009
- Update for Monitoring Server 971298 Description of the update package for Office Communications Server 2007 R2, Monitoring Server: July 2009
- Update for Response Group Service 2284304 Description of Cumulative update for Office Communications Server 2007 R2, Response Group Service: July 2010
- Update for Standard/Enterprise edition Server 983472 Description of cumulative update for Office Communications Server 2007 R2: July, 2010
- Update for Standard/Enterprise edition Server Back End 2032834 Description of the cumulative update package for Office Communications Server 2007 R2 database: July, 2010
- Update for Unified Communications Managed API 2.0 Core Redist 64-bit 982170 Description of the cumulative update for Office Communications Server 2007 R2, Unified Communications Managed API 2.0 Core Redist 64-bit: July 2010
- Update for Web Conferencing Server 2028582 Description of the cumulative update for Office Communications Server 2007 R2, Web Conferencing Server: July 2010
Description of the cumulative update package for Communicator 2007 R2: July 2010 - KB2028888
This cumulative update fixes the following issues:
- 2252163 Starting Office Communicator 2007 R2 for first time causes additional network traffic
- 2251520 A distribution group displays incorrect information in Office Communicator 2007 R2 after you change the distribution group name
- 2251474 Calling an Office Communicator 2007 R2 user fails when you change a matching number in the Company_Phone_Number_Normalization_Rules.txt file
- 2251473 You cannot send non-English messages continuously in bold, italic or underline font in Office Communicator 2007 R2
- 2250890 Error message when you send a large file by using Office Communicator R2 and a Office Communications Server server that has the Forefront Security for Office Communications Server component installed
- 2250113 You cannot input DBCS characters into the password field when you try to log on to office communicator 2007 R2
- 2231823 An additional delay is caused by Office Communicator 2007 R2 when you put your computer in hibernation or in standby
- 2268858 The last dialed telephone number for a contact changes to "Communicator Call" after you start Communicator 2007 R2 or Communicator 2007
- 978164 A conversation window opens unexpectedly when you press ENTER in the Search box in Office Communicator 2007 or Office Communicator 2007 R2
This package seems to have no new updates, just previously released updates.
Description of the update for Office Communications Server 2007 R2 Group Chat Client: July 2010 - KB2032922
- 2190298 You receive an unhandled System.NullReferenceException exception in Office Communications Server 2007 R2 Group Chat Client
- 2277126 Header information is also copied when you copy a story message in Office Communications Server 2007 R2 Group Chat Client
- 2277132 The position of the Office Communications Server 2007 R2 Group Chat Client window is changed after an unsuccessful logon
- 2277137 The title of a story message is replaced by the content from of a story message in Office Communications Server 2007 R2 Group Chat Client
- 2277375 Delays in presence updates or high latency in database operations may occur when OCS 2007 R2 and OCS 2007 R2, Group Chat are running under high concurrency
- 2277605 The User-Agent header in the SIP request that is sent by Office Communications Server 2007 R2 Group Chat Admin Tool is not unique and clear enough
Description of the update for the Office Communications Server 2007 R2 Group Chat Administration Tool: July 2010 - KB2032949
This package seems to have no new updates, just previously released updates.
Wednesday, 14 July 2010
Description of the update for Communicator Mobile 2007 R2: July 2010
There's a new update for Communicator Mobile. You can get it here.
Issues that this hotfix package fixes
- Provides home screen support for new home screens in Windows Mobile 6.5+ phones.
- Provides integration within the phone dialer for Windows Mobile 6.5+ phones.
- Enables Communicator Mobile 2007 R2 to recognize when the phone is roaming and by default prevents Communicator Mobile 2007 R2 from signing in to roaming networks.
- Provides additional support for joining conference calls from a Windows Mobile appointment. To do this, press Menu, and then press Join Conference.
- Lets users log on by using a user name in the user@example.com format, in addition to the domain\user format.
- Enables the functionality by which callbacks are now automatically accepted when the user uses the Call via Work option.
- Resolves the problem in which the Microsoft Installer (.msi) installation fails on a Windows XP Service Pack 3 (SP3)-based computer. In this situation, users should install Communicator Mobile 2007 R2 by using a (.cab) installation.
- Fixes the problem in which AT&T FUZE devices that are set for a High-Speed Downlink Packet Access (HSDPA) connection cannot handle voice and data at the same time. In this situation, calls that use the Call via Work option fail unless the device is reverted to 3rd Generation (3G) by disabling HSDPA.
Tuesday, 29 June 2010
Changing the shared folders location
I recently i had to change the shared folders locations on a OCS R2 installation and it all went smoothly, or at least appeared to :)
Instructions are simple, insert your CD or go to the folder where you have OCS R2 setup and re-run the setup. Click on Prepare Prepare Environment and then Create Enterprise Pool.
You will then face the same questions that you had to fill when you installed it. At some point the wizard will ask for the share folders location and you can change then.
Just make sure on the Reuse Existing Database page, clear the Replace existing database check box or else all your existing data will be lost (not good!).
Looks simple and effective but... it lacks some steps.
First you will need to go over to the Front End IIS and re-map all the virtual directories to the new shares. This one is easy to notice as you get alot of warnings soon enough.
Second, you will find this warning on event viewer:
Event ID 32020 Task Cat. (1055)
What i had to do to change it was (it might be another solution but i didn't found it):
Go to Start -> Run -> wbemtest
Click connect and type root\cimv2 and then connect.
Now, click on query and type this:
There will be a few instances returned but only one will have the DataLocation filled. You will have to change that to the new location.
And it's sorted.
Instructions are simple, insert your CD or go to the folder where you have OCS R2 setup and re-run the setup. Click on Prepare Prepare Environment and then Create Enterprise Pool.
You will then face the same questions that you had to fill when you installed it. At some point the wizard will ask for the share folders location and you can change then.
Just make sure on the Reuse Existing Database page, clear the Replace existing database check box or else all your existing data will be lost (not good!).
Looks simple and effective but... it lacks some steps.
First you will need to go over to the Front End IIS and re-map all the virtual directories to the new shares. This one is easy to notice as you get alot of warnings soon enough.
Second, you will find this warning on event viewer:
Event ID 32020 Task Cat. (1055)
Unable to create the Application Host data directory.Oops... looks like something wasn't changed. :-)
Unable to create the directory \\ocs old shares\AppStore\Microsoft.Rtc.Applications.Acd. The network path was not found.
.
Cause: See error message.
Resolution:
Create the directory manually.
What i had to do to change it was (it might be another solution but i didn't found it):
Go to Start -> Run -> wbemtest
Click connect and type root\cimv2 and then connect.
Now, click on query and type this:
Select * from MSFT_SIPApplicationConfigSetting where Backend="sql_instance"
There will be a few instances returned but only one will have the DataLocation filled. You will have to change that to the new location.
And it's sorted.
Subscribe to:
Posts (Atom)