| Throughout the installation of MetaFrame Conferencing Manager you might run in to a few issues. In the following sections I have documented the most common issues. For more troubleshoot assistance please refer to the Conferencing Manager 2.0 Administrator Guide and the Citrix support web site.
The information in this article applies to: Microsoft Exchange 2000 Server To create an Organizational Forms Library in Exchange 2000, follow these steps: 1. Click Start, point to Programs, click Exchange, and then click System Manager. 2. Click to expand Administrative Groups. 3. Click to expand Folders. 4. Click Public Folders. 5. On the System Manager toolbar, click Action. 6. Click to select View System Folders. 7. In the console tree, right-click EForms Registry. 8. Click New, and then click organization form. 9. In the Name box, type the name of the folder. 10. Under Eforms language, click to select the appropriate language. To create copies of the Organizational Forms Library on other servers, click the Replication tab, and then type the name of server that you want to carry the copy of the Organizational Forms Library.
NOTE: An Organizational Forms Library is a special type of public folder that is listed only with system folders. You can have only one Organizational Forms Library for each language per organization.
To set storage limits for an Organizational Forms Library, click the Limits tab.
To create a description of an Organizational Forms Library, click the Details tab.
To set permissions for each user, click the Permissions tab.
The information in this article applies to: Microsoft Exchange Server 4.0, Microsoft Exchange Server 5.0, and Microsoft Exchange Server 5.5. Forms that are installed into the Organization Forms Library are available to the entire Organization. The following steps summarize how to setup the Organization Forms Library for forms to be installed: 1. In the Exchange Administrator program click Forms Administrator on the Tools menu. 2. If Organization Forms is not defined, click New to create the Organization Forms library, and set the proper language. 3. Expand Organization, Folders, System Folders, Forms Registry. 4. Double-click on the Organization Forms object to open the properties and click Client Permissions. 5. Give a person or a group the Owner role to allow the user or group to install forms in the organization forms library. A user who is trying to install a form must have Owner permission to that library or folder, including public folders. Forms installed in the organization forms are available to anybody in the organization through the client by selecting New Forms from the Compose menu. Forms installed in the folder, including a public folder, are available when a user selects that particular folder. For additional information on managing and installing forms, click the article number below to view the article in the Microsoft Knowledge Base: 147604 XGEN: Managing Forms Installed on Exchange Server
The information in this article applies to: Microsoft Exchange 2000 Server. When you attempt to publish and or update a form to the Organizational Form Library, you may receive the following error message: 
This occurs because the user publishing the form does not have the appropriate access. By default, Microsoft Exchange 2000 Server grants Read-only rights on the EForm folder to the Everyone group. To grant a user the ability to publish a form to the Organizational Forms Library, grant the user All Folder rights, as well as All Message rights. 1. Open the Exchange System Manger expand the Folder node expand Public Folders 
2. Click Action from the menu bar click View System Folders. 
3. Expand the EFORMS REGISTRY node and right click on the Organizational Forms Library used to store the MetaFrame Conferencing custom Outlook form click Properties. 
4. Click the Permission tab click the Client permissions button. 
5. Click Add to add the appropriate user accounts. 
6. Select the Exchange user account you want to grant access to add / change / delete the customer form to and click OK to continue. 
7. Select the newly added user, click to drop down the Roles drop-down box and select Owner. Click OK to continue. 
8. Click OK to finish. You have now successfully granted the user in question the correct permissions to configure form in the Organizational Forms Library. You will need to exit and reload Outlook for the change to take affect.
The information in this article applies to: Microsoft Exchange Windows 3.x client 4.0, Microsoft Exchange Windows 95/98 client 4.0 and Microsoft Exchange Windows NT client 4.0. Forms installed in the Organization (ORG) Forms Library are not viewable except by the user who created and installed them. The form library is viewable, but the forms themselves are not. Forms that have been installed in public folders, the personal forms library, or PST files are still available. The correct permissions are not set on the ORG Forms Library system folder in the Microsoft Exchange organization. To resolve this issue set the default permissions on the ORG forms library to (at least) reviewer. 1. In the Microsoft Exchange Server Administrator program, open the following system folder: 2. Folders/System Folders/EFORMS Registry/Organization forms folder. 3. Press ALT+ENTER to see the properties of that folder. 4. Click the Client Permissions button. 5. In the Permissions dialog box, change the default rights to at least reviewer (which will give users the ability to read items). 6. Click OK and close the ORG Forms Library properties. 7. Quit the Microsoft Exchange Client and restart the client. The users should now be able to see the forms in the ORG forms library and also be able to install and run them.
Hotfixes are one way of updating an application to address bugs and or add features. As of the date of publication, Citrix has released the following hotfixes to address issues in MetaFrame Conferencing Manager 2.0. 
MCM200W001 - For Windows 2000 and Windows 2003 Released on May 22, 2003, hotfix MCM200W001 addresses the following issues: Launching a published application in a conference failed when the name of the published application contained double-byte characters and the application was published on a server other than the server where the Conference Room component was installed. This hotfix allows you to launch a published application on a server other than the server where the Conference Room component is installed when there are double-byte characters in the application name. To download MCM200W001 please visit: http://support.citrix.com/servlet/KbServlet/download/2890-102-9380/MCM200W001.msi This hotfix is required to be installed on all servers running Citrix MetaFrame Conferencing Manager 2.0.
MCM200W002 - For Windows 2000 and Windows 2003 Released on July 22, 2003, hotfix MCM200W002 addresses the following issues: Resolves the problem where the status bar help tips for some of the menu options were incorrect. Users of the Spanish language version were unable to leave or end conferences. To download MCM200W002 please visit: http://support.citrix.com/servlet/KbServlet/download/2890-102-9380/MCM200W002.msi This hotfix is required to be installed on all servers running Citrix MetaFrame Conferencing Manager 2.0. 
MCM200W003 - For Windows 2000 and Windows 2003 Released on September 17, 2003, hotfix MCM200W003 addresses the following issues: Outlook 2002 and Service Packs 2 and 3 for Office 2000 ship with Microsoft's Outlook Object Model Guard. The security features of Outlook Object Model Guard are designed to protect users from most email and worm viruses that replicate through Outlook. By default, Outlook Object Guard blocks applications from accessing the Outlook address book and prompts users to allow access. As a result, when you integrate MetaFrame Conferencing Manager with Outlook 2002 or Outlook 2000 Service Packs 2 or 3, users scheduling a MetaFrame Conference through Outlook using the MetaFrame Conference Form are presented with the security warning dialog box. For more information, see the Citrix Conferencing Manager Administrators Guide. Users could not send meeting requests through Outlook after applying the Outlook patch fix for Conferencing Manager. To download MCM200W003 please visit: http://support.citrix.com/servlet/KbServlet/download/3166-102-10421/mcm200w003.exe This hotfix is required to be installed on all servers running Citrix MetaFrame Conferencing Manager 2.0 servers configured for Microsoft Exchange Integration. 11. Publishing Resources through the Management Console Publishing an application on a MetaFrame XP server makes it available to ICA Client users (with proper authorization). You can publish applications across multiple servers in the server farm. With Citrix Load Manager, part of the XPa and XPe server, you can balance connections to guarantee users will connect to the least-loaded MetaFrame XP server. With application publishing, you can: Increase your control over application deployment Shield users from the mechanics of the Windows server environment Push application icons and shortcuts to user desktops through Program Neighborhood Configure File Type Associations for Client to Server Content Redirection. The Management Console for MetaFrame XP simplifies application publishing. With the Citrix Management Console, you can publish applications on any server in the MetaFrame XP server farm, including servers that are temporarily out of operation. Types of Applications You Can Publish MetaFrame XP supports publishing of the following types of applications. Standard Applications You can publish any application that can run on the Windows console (32-bit Windows applications, 16-bit Windows applications, DOS applications, POSIX applications, and OS/2 applications). Citrix Installation Manager Applications To publish Citrix Installation Manager Applications, you must install Citrix Installation Manager on your network. Citrix Installation Manager performs remote unattended installation of applications on Citrix servers. Using Installation Manager, you can simultaneously install an out-of-the-box application on all Citrix servers on your network from a single point without manual intervention. You can install applications on servers regardless of their physical location, network connection type, or individual hardware setup. Citrix Installation Manager can push application installations to Citrix servers and it can uninstall applications. Publishing a Citrix Installation Manager application causes each server that you specify, to download and install the application. Deleting a published Installation Manager application uninstalls the application from each server that you specified to run the application. For more information on Installation Manager, please refer to the Installation Manager Chapter later in this document. Content Publishing Content Publishing was added to MetaFrame through Feature Release 1 and it required that you have a FR1 licenses installed and activated. This feature allows you to publish document files, media files, Web URLs, and any other type of file from any network location. Icons for published content appear in Program Neighborhood, on the desktop, and in Web Interface 2.1. Users can double-click published content icons to access content in the same way they access published applications.
Using Published Applications When you publish an application, configuration information for the application is stored in the IMA data store for the server farm. The configuration information includes properties of the ICA connection, including its name, users who can connect to the application, and client-side session properties that include window sizes, number of colors, level of encryption, and audio settings. To the ICA Client user, a published application appears very similar to an application running locally on the client device. When the users access applications through a Web Interface application portal, the applications they are authorized to access appear as icons on a customized Web page. Web Interface connects the users client device to the application and downloads the appropriate ICA Client, if necessary, to the users device. You can also configure the client to utilize the Program Neighborhood Agent to seamlessly add published application icons to the users local desktop, programs group or system tray and even add local file type associations that point back to published MetaFrame XP applications.
|