Welcome to the Microsoft Office Communications Server 2007 (Public Beta) Release Notes. Refer to this file for information regarding known issues about Setup, management, Edge Servers, Archiving and CDR Servers, Communicator Web Access, and meetings.
© 2007 Microsoft Corporation. All rights reserved.
This document contains important information that you should know before you deploy and use the Public Beta version of Microsoft Office Communications Server 2007, the Public Beta version of Live Meeting 2007 client, and the Public Beta version of Communicator Web Access (Office Communications Server 2007 Release). For detailed information about Office Communications Server 2007, refer to the Office Communications Server 2007 Public Beta documentation.
Issue: We do not support running Office Communications Server 2007 Public Beta in a Beta 3 environment. Coexistence between beta 3 and public beta servers is not supported. Additionally, you cannot upgrade computers running Office Communications Server 2007 Beta 3 to Office Communications Server 2007 Public Beta.
Workaround: Perform a clean installation of Office Communications Server 2007 Public Beta and deploy public beta versions of Office Communications Servers in a public beta environment only. To migrate users from beta 3 to public beta, see the Migrating from Beta 3 to Office Communications Server 2007 Public Beta document.
Issue: When you try to activate a newly created service account, activation fails. Activation of the server fails if the account has not finished Active Directory replication.
Workaround: Create the service accounts that you want to use before you run Setup. Ensure that you allow enough time for replication of the Active Directory Domain Services to complete. If you created the service account during the activation process, retry activation after allowing time for Active Directory replication to complete.
Issue: From an evaluation version of the Standard or Enterprise Edition CD, if you click on Install Standard Edition or Install Enterprise Edition in setup and click Save in the File Download Dialog, the following error is displayed:
Unable to launch Office Communications Server 2007 Public Beta Deployment Tool – The system cannot find the file specified
Resolution: Run the installation process and click Run instead of Save.
Issue: You can run the Create Pool wizard or command line option on a Front End Server if the SQL client tools are available on that server. When you do so, on a Front-End Server with Microsoft SQL Server 2000 client tools installed and attempt to connect to a SQL Server 2005 back-end database, the dbsetup script terminates abnormally, and the pool creation fails.
One of the following errors are displayed:
An error occurred during the pool backend detection:
Pool backend discovery failed.
SQL Server 2005 Backwards Compatibility Pack must be installed on this machine for connecting to SQL Server 2005 SP1 or later.
OR
An error occurred during the pool backend detection:
Pool backend discovery failed. [hr=0xC3EC79FA]
This can happen due to network or credential problems. Please make sure network is good and logon has sufficient permissions.
Resolution: Choose one of the following:
· Run the Create Pool task on the SQL Server back-end database
· Install the SQL Server 2005 Backward compatibility toolset on the Front-End server.
Issue: QFEs are required for Office Communications Server 2007 (Public Beta).
Resolution: Install the available hotfixes. See the following Microsoft knowledge base for more information for installing QFEs on all Office Communications Server:
http://support.microsoft.com/kb/918462
http://support.microsoft.com/kb/923028
http://support.microsoft.com/kb/917949
For Office Communications Server 2007 and Live Communications Server 2005 with Service Pack 1 coexistence, the following QFEs are required on all Live Communications Server 2005 SP1 servers http://support.microsoft.com/default.aspx?scid=kb;EN-US;911996 and http://support.microsoft.com/kb/921543/.
Issue: Setup may fail if the destination folder name has non-ASCII characters (including UNICODE, double byte character set (DBCS), UTF-8, and UTF-16). Also, Setup will succeed, but the server will not start if non-ASCII characters are contained in the following:
· Computer name
· Domain name
· User name
Prevention: Use only ASCII characters in the destination folder name, domain name, and user name.
Issue: Changing the FQDN of a server that is part of an Office Communications Server 2007 Standard Edition or Enterprise Edition pool deployment is not supported. There are various dependencies in the deployment, including servers not functioning correctly and homed users not being able to connect.
Workaround: Deactivate and uninstall the Office Communications Servers, change the FQDN of these servers as desired, and then install and activate the Office Communications Servers with the new name.
Issue: When a load balancer is configured in DNAT mode, Front End Servers cannot route SIP packet to the pool FQDN. Instead each Front End Server should route SIP packets to itself. This does not work in some scenarios.
Workaround: On each Front End Server add an entry in %windir%\system32\drivers\etc\hosts file for pool FQDN that points to loop back network as shown below:
127.0.0.1 <poolname>.<domain>.com
For example:
127.0.0.1 pool1.contoso.com
Issue: When running SQL 2005 SP2 on the back-end server of an Enterprise pool, over time performance can degrade and the total CPU usage increases. This is a known issue with SQL Server 2005 SP2. For more details, see http://support.microsoft.com/default.aspx/kb/927396
Workaround: Use one of the following two options
Option 1
Use the following steps to add a SQL trace flag for T4618
1. Open SQL Server Configuration Manager: Point to Start, point to All Programs, point to Microsoft SQL Server 2005, point to Configuration Tools, and then click SQL Server Configuration Manager.
2. Select RTC SQL server instance in SQL Server 2005 Services, right click on the instance and then click Properties.
3. Click the Advanced Properties tab and Edit Startup Parameters.
4. Append ;-T4618 to the end of the Startup Parameters list (note that startup parameters are separated by semicolons).
Option 2
Or manually add the following registry value:
Name | Value
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\{0}\MSSQLServer\Parameters\SQLArgN | -T4618
(where N is the next SQL parameter number and {0} is the SQL instance name found under the following key below that maps to the RTC instance)
Name | Value
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\Instance Names\SQL
Issue: Office Communications Server 2007 will not operate correctly if there are too many trusted root certification authorities (CAs) installed on an Office Communications Server. As a result communications between Office Communications Server components fails.
This issue is caused by an optional Windows Update release entitled Root Certificates Update.
Resolution: If you have installed this Windows Update, do the following to remove unnecessary trusted root CAs:
1. Click Start, point to Run, and then type MMC.
2. Press Enter.
3. On the File menu, click Add/Remove Snap-in.
4. Click Add.
5. Select Certificates, and then click Add.
6. Select Computer account, and then click "Next".
7. Choose Local computer and click Finish.
8. Click OK.
9. In the Certificates snap-in, navigate to Trusted Root Certification Authorities\Certificates.
10. Carefully inspect the list of trusted CAs and delete those that aren't needed.
Issue: If you configure Intelligent IM Filter to send warning messages for instant messages containing hyperlinks by selecting Allow instant messages that contain hyperlinks. Enter the warning message at the beginning of each instant message containing hyperlinks on the URL filter option, instant messages containing hyperlinks are allowed, but the warning is not displayed.
Resolution: None for this release.
Issue: If you use LcsCmd.exe to delegate user administration permissions and the operation fails, it can leave the RTC database in "restricted_user" state, and rtc database will stop accepting simultaneous connections. As a result RTCService and other Office Communications Server components start operating incorrectly.
Resolution: Use the following steps to resolve this issue:
1. Stop all Office Communications Server related processes (Server processes, WMI, MMC, etc) that connect to SQL Server.
2. Log on to the Backend SQL server and open SQL management Studio.
3. Connect to the database instance on local machine.
4. Expand the "Databases" node on the left pane. You would see that databases "rtc" and "rtcdyn" are marked (Restricted User)
5. Execute the following query.
use master
alter database [rtc] set
multi_user
alter database [rtcdyn]
set multi_use
If the query fails with a timeout error, restart the SQL server to flush out all connections and repeat steps 3, 4 and 5.
6. Restart Office Communications Server services and components.
Issue: Office Communications Server 2007 administrative snap-in and Office Communications Server 2007 snap-in in Computer Management are not available on 64-bit operating systems by default.
Resolution: If you are using Office Communications Server 2007 Administration Tools, click Start, point to Run, and then type mmc -32. This command starts the mmc.exe as a 32-bit application. Use the Add/Remove snap-in option to add the Office Communications Server 2007 Administrative snap-in. If you are using Computer Management Snap-in (on an Edge Server for example), click Start, point to Run and then type mmc -32 compmgmt.msc. This command starts the Computer Management as a 32-bit application. Use the Add/Remove snap-in option to add the Office Communications Server 2007 Computer Management snap-in.
Issue: Office Communications Server 2007 performance monitor counters are not available on 64-bit operating systems by default.
Resolution: Click Start, point to Run, and then type perfmon -32. This command starts the Performance Monitor as a 32-bit application. By default, the Performance Monitor runs as a 64-bit application on 64-bit operating system.
Issue: When performing cross-forest moves through Active Directory (and using a tool such as ADMT), a contact might be deleted during a move from one forest to another in either of the following scenarios:
· In a central forest in an Office Communications Server deployment if a User object is moved without carrying over the SIDHistory.
· In an Exchange cross-forest scenario where GalSync is used to replicate users as contacts.
In both scenarios the Contact object in the central forest is deleted and recreated. This causes all the user data (SIP contacts, permissions, and contact groups) to be deleted from the “Live” Server database and a new SIP user to be created in its place. This deletion will also cause the user to be deleted from that user’s watchers contact lists.
Prevention: Before you use the Move operation, use the Dbimpexp.exe tool to export the user's data from the Office Communications Server database. Then import the user's data after the Move operation. The export/import step needs to be performed on the pool that homes the user. Watchers of the user will be prompted to re-add the user to their contact list after the user has logged on following the move.
The Dbimpexp.exe tool and documentation can be found in the %systemdrive%\Program Files\Microsoft Office 2007\Server\Support directory.
Issue: If you have configured one or more federated partner domains with the FQDNs of the associated Access Edge Server on the Allow tab of your Access Edge Server properties that share a common parent domain, and you want to temporarily block one or more of these domains, then you must enter each domain that you want to block on the Block tab, rather than just entering the parent domain into the blocked domains list.
Example:
You have entered three federated partner domains on the Allow tab
sales.contoso.com
eng.contoso.com
hr.contoso.com
In order to temporarily block all of these domains without removing them from your configuration, you would normally be able to enter just "contoso.com" into the blocked domains list. However, this may not work in this release, so you must enter all 3 of the domains into the blocked domains list.
Resolution: Add each child domain and the parent domain on the Block tab of the Access Edge Server properties.
Issue: Audio is distorted and can be unintelligible when it is transmitted by an A/V Conferencing Server that is running on a computer with multiple processors, multiple cores, or hyperthreading technology.
Resolution: Install the Windows hotfix described in the knowledge base (KB) article 896256: http://support.microsoft.com/?id=896256.
Issue: When an Office Communications Server user sets his or her presence to Do Not Disturb (DND) in Office Communicator, users on the MSN network of Internet services and the Yahoo! public IM networks can still send instant messages and these users do not know that the Office Communications Server user cannot see these messages.
Workaround: No resolution until these issues are fixed by MSN and Yahoo! network.
Issue: When an Office Communications Server user has an IM conversation with Yahoo! user, the Yahoo! user may see more than one pop-up window.
Workaround: No resolution until this issue is fixed by Yahoo! network.
Issue: AOL users cannot join IM conferences that are hosted by Office Communications Server.
Workaround: None. This is by AOL design.
Issue: When a Yahoo! user joins an IM conference, the user can no longer participate in one-on-one IM conversations with the organizer.
Workaround: No resolution until this issue is fixed by the Yahoo! network.
Issue: Users of Microsoft Office Communicator 2007 can invite users of previous versions of Communicator, Microsoft Windows Messenger, and Microsoft Windows Live Messenger to IM conferences. However, if a Tablet PC or other device capable of sending Tablet PC ink sends an ink-based message in the conference, the users of previous versions of Communicator and Windows Messenger will not receive the ink-based message. There is no feedback that indicates the ink-based message was not sent or received successfully.
Resolution: None in this release.
Issue: If a user's display name in Active Directory is greater than 254 characters long, that user cannot participate in conferences: either joining or scheduling a conference on Office Communications Server.
Resolution: Modify the display name of the user to be less than 254 characters.
Issue: User cannot make PC to phone calls when encryption is on. This setting is controlled by the following registry key: HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Communicator\PC2PCAVEncryption policy is set to require encryption (with a value of 1) then PC to phone calls will fail.
Workaround: Set this registry key value to 0 or 2.
Issue: In some complex Office Communications Server 2007 topologies, such as those with multiple pools and many domains, in the VoIP properties, on the Location Profiles tab, the location profile list is not updated when you add a new location profile. When you attempt to add a new location profile and click Apply, the entry disappears.
Resolution: After adding (and saving) the location profile, close and re-open the VoIP Property Page. The data will be refreshed and the newly added entry will be visible.
Issue: In the Public Beta release of the Microsoft Office Live Meeting client, the following functions are not supported:
· Microsoft Office Live Meeting Add-in for the Microsoft Office PowerPoint presentation graphics program.
· Windows Live Messenger Add-in.
· Microsoft Office Live Meeting Add-in for the Microsoft Office Outlook 2000 messaging and collaboration client
· Command-line arguments when installing the Add-in for Outlook
· Microsoft Windows XP 64-bit operating system on 64-bit hardware only: Importing Microsoft Office documents except .ppt files (importing.ppt files is supported)
Resolution: None.
The following notes and limitations are specific to running the Microsoft Office Live Meeting client on the Windows Vista operating system.
· Playback of a recorded meeting is not supported when you are using the Mozilla Firefox Web browser running on the Windows Vista operating system.
· If you do not have Adobe Flash player, version 9.0.28.0 or higher, the meeting client may become unresponsive while viewing Flash Player content.
Issue: The Office Communicator account setting is shared with the account setting for the Live Meeting client and the Conferencing Add-in for Outlook account setup. If you change the account setting for one of these applications, the account settings will change for the other application.
Resolution: None.
Issue: When you are connected to a Microsoft Office Live Meeting (Public Beta) meeting through a Virtual Private Network (VPN), you may experience poor quality voice and video functionality.
Workaround: Because it can be more reliable, use full external access or a direct corporate connection (without VPN access) for connecting to Office Live Meeting (Public Beta).
Office Live Meeting (Public Beta) dialing characters are entered differently from those used for Office Live Meeting 2005. When entering dialing information, use the following characters to represent a pause:
· In Office Live Meeting 2005, use a comma (,) to represent a pause
· In Office Live Meeting 2007, use the letter p to represent a pause
Issue: Importing a .VDX or .VSD file created in the Microsoft Office Visio 2003 or 2007 drawing and diagramming software to the Live Meeting client will cause Visio to stop responding, and may cause the Office Live Meeting client to stop responding. If you attempt to import a Visio .VST or .VSS file, the Live Meeting client will display an error message that includes a workaround.
Workaround: Open the file in Visio and print it as an Office Document Imaging File (mdi). Then import the .mdi file in to the Office Live Meeting client.
Issue: By default, the meeting presenter cannot see the results of a polling slide.
Workaround: To see the results of a polling slide, click the Show Poll Results icon in the polling slide.
Issue: This issue occurs for users who have both Live Meeting service and Live Meeting server accounts configured in the Conferencing Add-in for Microsoft Office Outlook. If the user schedules a meeting using Live Meeting manager, and then opens Outlook and selects the server account, Outlook synchronizes the calendar and out-of-date meeting reminders appear. The user can dismiss the reminders, but they will reappear. Eventually, dismissing the reminders results in an unknown error.
Resolution: Delete the meetings from Live Meeting manager or from Outlook.
Issue: In a meeting with both computer audio and telephone conferencing, a presenter can bridge the computer audio and telephone audio by using the Connect Telephone and Computer Audio option. With this option, the presenter can talk to participants using a phone and participants using computer audio. The presenter can disconnect from the telephone audio by either clicking the disconnect button or manually hanging up the phone. However, clicking the disconnect button after connecting to a phone number may cause the dialog box to remain in a “disconnecting” state indefinitely. After hanging up the phone, it may take a long time for the connection to disconnect
Workaround: Exit and re-enter the meeting to return the user interface to the correct state.
Issue: If you connect a Microsoft Office RoundTable communications and archiving system device to a laptop after starting Live Meeting, the computer audio (VoIP) connection closes.
Workaround: Open the Voice & Video pane and click the Join Audio button to reconnect to computer audio. You can avoid this issue by connecting the RoundTable device to your laptop before starting Live Meeting.
Issue: If you are trying to join an Office Communications Server 2007 meeting and you do not have the Office Live Meeting client installed, you will get an “out of memory” error message.
Workaround: Before joining the meeting, click the client installation link in the meeting invitation to install the Office Live Meeting client
Issue: When you schedule a meeting using Office Communications Server 2007 and computer audio is turned off when you join the meeting all video functionality will be disabled.
Workaround: None.
Issue: Upon installation, the Microsoft Office Live Meeting client installs a printer driver, the Microsoft Office Live Meeting Document Writer, which you can use to upload almost any document type to a meeting. If upload fails, the problem may be that the Microsoft Office Document Imaging (MODI) driver is not installed.
Resolution: Remove the Microsoft Office Live Meeting client and then restart the print spooler. To do so, follow these steps:
1. Click Start, and then click Control Panel.
2. Double-click Add or Remove Programs.
3. Click Microsoft Office Live Meeting 2007 Public Beta.
4. Click Remove.
5. Exit Control Panel.
6. Click Start, click Run, type mmc, and then click OK.
7. On the File menu, click Add/Remove Snap-in.
8. Click Add, click Computer Management, click Add, and then click Finish.
9. Click Close.
10. Click OK.
11. Expand Computer Management, expand Services and Applications, and then click Services.
12. Right-click Print Spooler. Click Stop, and then click Start.
13. Reinstall the Microsoft Office Live Meeting client.
Issue: Office Communications Server 2007 has a meeting policy that specifies whether users are allowed to share application control with external participants. If the policy specifies that a user cannot share control, and the user attempts to share control with an external participant or an external participant attempts to take control during a meeting, the server prevents the action but does not provide any notification or error message.
Resolution: This issue will be resolved in a subsequent release.
Issue: On computers that are running the Microsoft Windows 2000 operating system, the latest release of the Microsoft DirectX End-User Runtime must be installed; otherwise, the Live Meeting client will stop responding when you attempt to join a meeting.
Resolution: Install the DirectX 9.0c End-User Runtime, which is available at http://www.microsoft.com/downloads/details.aspx?FamilyID=0a9b6820-bfbb-4799-9908-d418cdeac197&DisplayLang=en.
Issue: As a result of default firewall settings, the Office Live Meeting (Public Beta) client may be blocked from joining meetings by Norton Internet Security 2006. When you try to join a meeting, you will receive an error message.
Resolution: Disable Norton Firewall specifically for the Live Meeting client.
Issue: Users may experience distorted audio quality being streamed from computers with:
· Multiple CPUs
· CPUs with multiple cores
· CPUs with HyperThreading.
Resolution: Apply the Windows hotfix described in KB 896256: http://support.microsoft.com/?id=896256
To assist the Live Meeting team in troubleshooting problems found in this beta release of the Live Meeting 2007 client, you can enable client-side logging. To do so, set the following registry keys as described:
[HKEY_CURRENT_USER\Software\Microsoft\Tracing\uccp\LiveMeeting]
· "EnableFileTracing"=dword:00000001
· "Tracing"=dword:00000001
These settings will allow the client to maintain a detailed log in the %USERPROFILE%\tracing\ directory. The file names will be of the form LiveMeeting-uccp-*.log.
Detailed client-side logging supplements the default logging that is provided in the %TEMP% directory. Those log file names are of the form pwconsole-debug*.txt.
Meet Now and Meet Now Option will not appear if you do not uninstall the Live Meeting 2007 (Beta 3) client
Issue: Meet Now and Meet Now Options will not appear if you do not uninstall the Live Meeting 2007 (Beta 3) client before installing the Live Meeting 2007 (Public Beta) client.
Resolution: Remove the Microsoft Office Live Meeting 2007 (Beta 3) client and then install the Live Meeting 2007 (Public Beta) Client:
1. Click Start, and then click Control Panel.
2. Double-click Add or Remove Programs.
3. Click Microsoft Office Live Meeting 2007 Beta 3.
4. Click Remove.
5. Exit Control Panel.
13. Install the Microsoft Office Live Meeting Public Beta client.
Live Meeting 2007 Public Beta must be installed when viewing a Live Meeting recording
Issue: : You will not be able to view application sharing in a Live Meeting recording if you do not have Live Meeting 2007 Public Beta installed.
Resolution: Install the Live Meeting 2007 Beta meeting client before viewing a recording.
Microsoft Office Project 2007 files will fail to import
Issue: You cannot import Microsoft Office Project 2007 files in to the Live Meeting client.
Resolution: You can share the files or use the Screen Snapshot feature to show Project 2007 files.
Lockdown registry key does not suppress the upgrade message
Issue: When the lockdown registry key (HKEY_LOCAL_MACHINE\Software\Microsoft\Live Meeting\8.0 \Lockdown, REG_DWORD=1) is set, if the user exits a meeting and a newer version of the client is available, an upgrade message displays.
Workaround: This issue will be fixed in a future release.
Do not use the prototype USB phone device for Live Meeting or Communicator conferencing
Issue: The prototype USB phone will not function for Live Meeting sessions or Communicator conference calls.
Resolution: Do not use the prototype USB phone device for Live Meeting or a Communicator conferencing.
Issue: The default location for client-side recording is the My Documents\My Meetings folder. If a user has a roaming profile, or if a user stores his or her My Documents folder on a network share, client-side recording will send large amounts of data to the network folder. If the network is not fast enough or if the network is congested, significant performance issues and capture degradation will result.
Resolution: Users who have mapped their roaming profiles or My Documents folders to network locations should change the recording directory for client-side recording to folders on their local drives.
Issue: Recordings should be published using the same version of the Office Live Meeting client that was used to record them. If publishing jobs are pending and you upgrade the Office Live Meeting client before the jobs are completed, any changes that are introduced in the new client version that affect recording or publishing compatibility could cause the publishing process to fail.
Workaround: Always ensure that all pending recordings are published before upgrading the Office Live Meeting client. After publishing completes, published recordings can be played back regardless of the version of the client you have installed because the publishing process embeds the appropriate version of the client into the recording.
Issue: When playing back a recorded Live Meeting on Windows XP with a Mozilla Firefox Web browser and Microsoft Windows Media Player 11, if you maximize the window, the video playback displays a black screen.
Workaround: To redisplay the video, open a new browser window and overlay the video frame.
Issue: When playing back a recorded Live Meeting on Apple Macintosh when the display setting is 256 colors, the video does not display.
Workaround: None.
Issue: If a Live Meeting recording has been saved on a server using a file path that contains Asian language characters, users who try to view the recording on Mozilla Firefox 2.0 will not see the video or application sharing slides.
Workaround: None.
Issue: In Live Meeting Recording Manager, recordings that were made by using earlier pre-release versions of Live Meeting are listed with a status of “Error.” These recordings cannot be played by using Live Meeting Recording Manager.
Workaround: Navigate to the folder containing the recording and open the .htm file to play the recording.
Issue: If you do not verify your logon information your Live Meeting account settings will not be applied.
Resolution: Once you have configured your Live Meeting account, make sure to click the Test Connection button to verify your log on information.
Issue: Conferencing Add-in for Microsoft Office Outlook installer requires the Microsoft Windows Installer version 3.0 or above. Without the appropriate installer, you will see an error message from Windows Installer.
Resolution: Make sure you have installed the latest Windows Installer available for your operating system. For information about Windows Installer, see this KB article: http://support.microsoft.com/default.aspx?scid=kb;en-us;893803
Issue: E-mail invitations sent from Office Communications Server 2007 (Public Beta) to e-mail clients other than Microsoft Outlook (for example, MSN Hotmail, Outlook Express, and others) may not work.
Resolution: Follow the troubleshooting instructions in the invitation. Start the meeting client and join the meeting with meeting ID, entry code, and location in the troubleshooting section.
Issue: If a Meeting Organizer's account was created using the Microsoft Office Live Meeting Service API, then meeting presenters will not receive e-mail with the expected contents: meeting coordinates, test creation, in-meeting test administration, and in-meeting survey.
Resolution: For Presenters to receive automatic e-mail notification (meeting coordinates, test creation, in-meeting test administration, and in-meeting survey) use the Live Meeting manager to create meeting Organizer accounts. Furthermore, you can use Live Meeting manager to create an alternate account for an existing meeting Organizer accounts that had been previously created using the XML API.
Alternate Resolution: Use the following procedure to send an email notification:
1. From My Home under Upcoming Meetings, click the meeting title to view the Meeting Details page. You can view:
· Presenter URL
· Meeting ID
· Presenter Meeting Key
· KeyAudio information
2. Click Events
3. Locate the event for which you want to send an e-mail notification.
4. Click the event title to view the Event Details page.
5. Using e-mail, you can send the following information to the event Presenter either as a message or Calendar meeting:
· Event title
· Meeting title
· Meeting time
· Presenter URL
· Meeting ID
· Presenter Meeting Key / Entry Code
· Audio information
· Survey URL (Create a Web slide to conduct the survey during the meeting)
· Test URL (Create a Web slide using the Test URL. Login as Presenter using the Entry code and Meeting ID. Click Start for the test to begin for attendees)
Note: To test your system, visit http://go.microsoft.com/fwlink/?linkid=52354
Issue: This issue occurs for users running certain configurations of Microsoft Outlook 2002 with the Conferencing Add-in for Microsoft Office Outlook installed. When the user clicks Send or Send Update in a Live Meeting item in Outlook, a security warning dialog box appears.
Workaround: The user can acknowledge the security warning and continue.
Issue: This issue occurs when running Microsoft Office XP on Windows XP or Windows 2000. If the computer date is not adjusted correctly for the new daylight savings time schedule, the conferencing add-in will not work if you attempt to schedule conferences that will occur between March 11th and April 1st or between October 28th and November 4th.
Workaround: Double-click the clock in the taskbar, click the Time Zone tab, and then select the Automatically adjust clock for daylight saving changes check box. If this does not fix the issue, you can upgrade the version of Microsoft Office or Windows.
Issue: Outlook displays an error "Cannot install the custom actions. The object could not be found."
Resolution: Search for the file frmcache.dat. Delete this file, and then restart Outlook.
Issue: In the Public Beta version of Communicator Web Access (2007 release), the supported browsers are:
|
Operating System |
Internet Browser |
Authentication Mechanism |
|
Microsoft Windows® 2000 SP4 |
Microsoft Internet Explorer® 6 SP1 |
NTLM Kerberos Forms-based Custom |
|
Windows XP SP2 |
Internet Explorer 6 SP2 Internet Explorer 7 |
NTLM Kerberos Forms-based Custom |
|
Firefox 2.0.latest |
Forms-based Custom |
|
|
Windows Vista™ |
Internet Explorer 7 |
NTLM Kerberos Forms-based Custom |
|
|
Firefox 2.0.latest |
Forms-based Custom |
|
Mac OS X 10.4.9 |
Safari 2.0.4 Firefox 2.0.latest |
Forms-based Custom |
While other operating system and browser combinations might work, they are unsupported for the Public Beta release.
Workaround: N/A.
Issue: You cannot install Communicator Web Access in a domain with a fully qualified domain name that contains non-ASCII characters.
Workaround: None in this release.
Issue: Signing in to Office Communications Server 2007, Communicator Web Access from an Internet Explorer 6 with Service Pack on a computer running Windows 2000 can cause the browser to stop unexpectedly. This is caused by Communicator Web Access’s use of the AlphaImageLoader filter to scale images. refer to the following knowledge base article for more details: http://support.microsoft.com/default.aspx?scid=kb;EN-US;824463.
Resolution: Apply the Internet Explorer 6.0 SP1 hotfix available at http://www.microsoft.com/downloads/details.aspx?FamilyId=FE29CEBB-6877-4409-AAFF-06E7EBCC16DC&displaylang=en.
Issue: You can use ISA Server 2004 to provide external user access to the Communicator Web Access (2007 release, Public Beta) service. To do so, you publish the Communicator Web Access Web site, which should use SSL, on the default port 443. You can then configure ISA Server 2004 to redirect the external traffic on port 443 to a different internal port, for example, 444.
When ISA Server 2004 redirects traffic, it changes the port in the request URL from external port (443) to the internal port (444). ISA Server 2004 then adds the internal port (444), to the external URL (https://cwa.contoso.com:444 instead of https://cwa.contoso.com:443). In this scenario, Communicator Web Access receives a request URL that includes the internal port number (https://cwa.contoso.com:444), even though the request is coming from the external port. When the web UI controls attempt to download additional resources from this URL with the internal port number, the request fails.
Workaround: Upgrade ISA Server 2004 to ISA Server 2006 will solve the issue.
Issue: When legacy redirection is configured on Communicator Web Access (2007 release, Public Beta), and a user (Alice) who is homed on Live Communications Server 2005 with SP1 attempts to sign in to Communicator Web Access (2007 release, Public Beta), Alice will be prompted again for her credentials before she is redirected to Communicator Web Access (2005 release).
Workaround: None for Public Beta.
Issue: This situation occurs when a conference exists between an Office Communicator 2007 (Public Beta) client and a Communicator Web Access (2007 release, Public Beta) client. If the instant message font is chenged in either client, the font change is not seen in the other client when the message is recieved. The font follows the setting in the receiving client.
Workaround: None for Public Beta. This is by design.
Issue: It is possible to get the IIS MMC and the Communicator Web Access Manager (2007 release) out of synch. One way to do this is to stop the virtual server in the Manager, and perform an iisreset at the command line. However, the virtual server still shows a stopped status in the Manager. Also, the Start menu item from the virtual server right-click menu in the Manager is disabled.
Workaround: The workaround is:
This document supports a preliminary release of a software product that may be changed substantially prior to final commercial release. This document is provided for informational purposes only and Microsoft makes no warranties, either express or implied, in this document. Information in this document, including URL and other Internet Web site references, is subject to change without notice. The entire risk of the use or the results from the use of this document remains with the user. Unless otherwise noted, the companies, organizations, products, domain names, e-mail addresses, logos, people, places, and events depicted in examples herein are fictitious. No association with any real company, organization, product, domain name, e-mail address, logo, person, place, or event is intended or should be inferred. Complying with all applicable copyright laws is the responsibility of the user. Without limiting the rights under copyright, no part of this document may be reproduced, stored in or introduced into a retrieval system, or transmitted in any form or by any means (electronic, mechanical, photocopying, recording, or otherwise), or for any purpose, without the express written permission of Microsoft Corporation.
Microsoft may have patents, patent applications, trademarks, copyrights, or other intellectual property rights covering subject matter in this document. Except as expressly provided in any written license agreement from Microsoft, the furnishing of this document does not give you any license to these patents, trademarks, copyrights, or other intellectual property.
© 2007 Microsoft Corporation. All rights reserved.
Microsoft, MS-DOS, Windows, Windows Mobile, Windows NT, Windows Server, Windows Vista, Windows Live, Active Directory, DirectX, Internet Explorer, MSN, OneNote, Outlook, PowerPoint, RoundTable, SQL Server, Visio, and Visual Studio are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries.
The names of actual companies and products mentioned herein may be the trademarks of their respective owners.