1. What's New in the Meeting Maker Admin

     Resolved Issues in Version 7.3

• Location Availability for Recurring Meetings (# 3824)
  
  In version 7.1, the third instance or later of a recurring meeting incorrectly checks location availability in GMT rather than in the selected time zone. Therefore, first-come first-served locations that are actually free may incorrectly decline meetings. This issue is resolved in version 7.3.

• Guest Deletion of Palm™ Device Meetings (#3733)
  
  In version 7.1, if a meeting guest declines a meeting and then synchronizes with a Palm device, the Meeting Maker Conduits delete the meeting on the Palm devices of any other meeting guests who synchronize with Palm devices, including the meeting owner. This issue is resolved in version 7.3.

• Long Host Files (#3788 & #3789)
  
  In version 7.1, host files cannot exceed 255 characters. When you create a custom installer and the IP addresses and DNS names exceed 255 characters in the host file, the installer crashes when you attempt to run it. This issue is resolved in Meeting Maker version 7.3.

• Relative Reminders After Upgrade from Version 6.x (# 3777)
  
  In version 7.1, when you upgrade to a version 7.1 or 7.2 database from a version 6.x database import, Meeting Maker bases all relative 15 minute reminders on the GMT time zone, regardless of the time zone you selected during the database import. This issue is resolved in Meeting Maker version 7.3.

•  Connection Issues (#3898)
  
  In version 7.1, in rare cases users experienced difficulty signing in to the Meeting Maker server. This issue is resolved in Meeting Maker version 7.3.

• Busy Time Delays for Macintosh® Users (#3834)

In version 7.1g (74), Macintosh users experience a busy time delay when they create or modify a proposal guest list. This issue is resolved in Meeting Maker version 7.3.     

 

New in version 7.3

• iCal Enabled Windows Client
  
  The Meeting Maker Client for Windows now automatically sends an iCal attachment to all external meeting guests who receive an email invitation. Non-Meeting Maker users may be able to use the iCal attachment to add the meeting to their own calendaring software.

• Improved Java Client
  
  The version 7.3 Java Client now supports banners and both TCP and SSL connectivity. 

Back to Table of Contents

2. Upgrading from a Previous Version of Meeting Maker

• Selecting a Time Zone when Upgrading

  When upgrading to Meeting Maker version 7.x from a previous version (such as 6.0.8), you must first export your Meeting Maker database, then import it into your new version 7.x Meeting Maker server. When importing, you must now select a time zone; this is the Work Hour Time Zone, which Meeting Maker uses to calculate the user's availability for incoming meeting proposals. Each user account imported is assigned this Work Hour Time Zone. In most cases, you should select the same time zone as the one assigned to your pre-version 7.x Meeting Maker server.

  WARNING: It is very important that you select the correct Work Hour Time Zone when importing a Meeting Maker version 6.0.8 (or previous) database into your Meeting Maker version 7.x server. Every user account that you import during this upgrade is assigned the time zone you select.

  WARNING: When importing a Meeting Maker version 6.0.8 (or previous) database from a text file, Meeting Maker Admin does not require you to select a time zone. However, it is very important that you select the correct Work Hour Time Zone when importing. If you do not select a time zone, you must specify a Work Hour Time Zone for each individual Meeting Maker user imported into the version 7.x server.

  In versions of Meeting Maker previous to 7.x (such as 6.0.8), individual user accounts did not have associated time zones. If you are upgrading from a Meeting Maker version previous to 7.x, every imported user account is assigned the Work Hour Time Zone you choose when importing. If you are upgrading from Meeting Maker version 7.x to version 7.x or higher, or importing any Meeting Maker version 7.x database into a version 7.x or higher server, only user accounts that do not have an assigned and valid time zone are assigned the Work Hour Time Zone you choose when importing.

• Installing or Upgrading in a Multi-Server Environment
   
  Meeting Maker now retrieves cross-server busy time information directly from other servers rather than from the hub. Therefore, when you install or upgrade Meeting Maker in a multi-server environment, you must make sure that all Meeting Maker Clients in your environment have DNS names or IP addresses for every server in your environment. This information is stored in each Client's comparam file (comparam.ini on Windows®, ON Com Parameters on Macintosh, and .onrc on Solaris®), and can be entered by the user at sign-in.
   
  If you are upgrading a multi-server environment and all your Clients already have IP addresses or DNS names for all servers entered in their local comparam files, you do not need to do anything and can upgrade normally. You do not need to read the rest of this note.
   
  If you are upgrading in a multi-server environment and all your Clients do not already have IP addresses or DNS names for all servers entered in their local comparam files, you may want to create a custom installer that will replace their local comparam files with one you create. For information about creating custom installers for Windows, see http://connect.meetingmaker.com/support/kbase/view.cfm?id=2124. For information on creating custom installers for Macintosh, please contact Meeting Maker technical support.
   
  If you are using auto-upgrade, contact Meeting Maker technical support for a new upgrade.lst file.
   
  If you are installing for the first time in a multi-server environment, you can ensure that your Clients all have a complete list of server addresses in one of the following ways:

  • In Windows environments, make sure that the setup.ini file contains host information for all Meeting Maker servers in your environment.

  • In Macintosh or mixed environments, provide all users with a list of DNS names or IP addresses they can enter manually at sign in, OR

  • Contact Meeting Maker technical support for a custom installer

• Upgrading Palm Handheld Device Users

  Importing Remote Information

  When upgrading to Meeting Maker version 7.x, you must first export your Meeting Maker database, then import it into your new version 7.x Meeting Maker server. If your Meeting Maker environment includes users who synchronize a Palm OS® handheld device with Meeting Maker, you must select the "Import Remote Information" option when importing your database into the Meeting Maker version 7.x server. To do so, open the Meeting Maker Admin, select File > Import, and check the Import Remote Information checkbox on the Meeting Maker Importer dialog box. This option normally applies only to importing databases in multi-server environments. However, if your users synchronize Meeting Maker with a Palm device, you must select the Import Remote Information option even if your Meeting Maker environment includes only one server.

• Upgrading on Macintosh

  Meeting Maker no longer supports AppleTalk® network protocol. If you connected to the Meeting Maker server using AppleTalk before upgrading to version 7.x, when you attempt to log in for the first time after upgrading, your Meeting Maker server does not appear in the available server list. To access your server, click Select from the Meeting Maker Login screen to select a server, then choose either TCP or IP protocol. Then click Configure and enter the IP or DNS address of your Meeting Maker server. If you are unsure of the server address, ask your Meeting Maker administrator. Click OK; your Meeting Maker server appears in the list of available servers.

• Upgrading on Solaris

  For previous versions of meetingmaker, it was recommended that users installing Meeting Maker on a Solaris computer set the MMHOME variable to the directory where Meeting Maker is installed. To successfully install Meeting Maker version 7.x, you must set the MMHOME variable to the Meeting Maker installation directory. If you are upgrading your Meeting Maker environment through Auto-Client Upgrade, all Solaris users must set the MMHOME variable to the Meeting Maker installation directory in order to successfully install Meeting Maker version 7.x.

• Restoring User Preferences after Upgrading

  Some preference settings are stored on the local workstation, rather than associated with a specific user account. After an upgrade, these locally-stored preferences reset to the system default values. Below is a partial list of preferences that reset to their default values after an upgrade:

  • Notification preferences for proposals and activities reset to 15 minutes. Restrict Notification Times preferences are also cleared.
    To re-enter these preferences, click the Notification tab in the Preferences dialog box.
    

  • Sign In Automatically setting is cleared.
    To re-enable, click the Login tab in the Preferences dialog box.

  • Local SMTP Host setting is cleared.
    To re-enter, click the General tab in the Preferences dialog box.

  • Calendar display preferences for the Daily Calendar, Monthly Calendar, and banners reset to system defaults.
    To re-enter these preferences, click the Calendar tab in the Preferences dialog box.
    
  • Proxy List order resets to alphabetical.
    To restore any custom sorting of your Proxy list, you must manually move each user in your Proxy list again.
    

• Additional Upgrade Information

  You can find specific technical notes about upgrading on our website at "http://support.meetingmaker.com"

  Be sure to read the technical note specific to the Meeting Maker version from which, and to which, you are upgrading.

Back to Table of Contents

3. Known Issues in Meeting Maker Admin Version 7.3

• Auto-pick and Proxy Calander Update Availability When Using a Virtual Private Network

  If you are running a Virtual Private Network (VPN) while you are logged in to Meeting Maker, you may experience latency issues. For example, the auto-pick function may default to midnight instead of finding the earliest possible time all guests can attend a meeting. Also, proxied calendar information may not update until you log in to Meeting Maker without running the VPN.

• Importing a 6.0.8 (or Previous Version) Server from a Text File

  WARNING: When importing a Meeting Maker version 6.0.8 (or previous) database from a text file into a version 7.x server, Meeting Maker Admin requires you to select a time zone. You should select the same time zone to which the previous server was set. For more information about upgrading to version 7.x, see Upgrading from a Previous Version of Meeting Maker.

• Email Authorization

  The Meeting Maker automatic email authorization feature is not compatible with the Lotus Notes® email application. In Meeting Maker version 7.x, after completing the email authorization form, you can click "Email" to automatically create an email message addressed to Meeting Maker, Inc. and pre-populated with the authorization information. If your default email application is Lotus Notes, the email created will not contain the authorization information. To obtain the authorization information, navigate to the root directory on the computer on which you are running Meeting Maker Admin, and open the file named "MMXPREG.FAX" in a text editor application. Copy the text in this file, and paste it into an email addressed to mmreg@meetingmaker.com. Alternatively, you can print MMXPREG.FAX, and fax it to Meeting Maker, Inc. at +1 781 487 3503.

• Creating a Server
  
  When you create a new Meeting Maker server using the Meeting Maker Admin, you must first close the Meeting Maker Server application. You can restart the Meeting Maker Server application when you are done creating the new server.

• Exported Data Files 

  When exporting a server, you must specify in the filename that the export file is of type .DAT.  If you do not specify this in the filename, you must switch the import dialog to show all file types in order to find your export files.

• Label Change on Import

  When you export and import your calendar, labels on meetings to which you are a guest may be lost.

• Backup on Installation
  
  When you back up a server or local database on installation, Meeting Maker saves the file backups in a backup directory, but does not change the file names of the backups.  As a result, backup servers may appear in the server list on sign-in.  You may want to change server backup file names by hand.

• Auto Shutdown and Daylight Savings Time

  Auto Shutdown does not adjust to accomodate shifts in Daylight Savings Time.

• Offline Reminders

  If you are forced offline when a server shuts down, you do not receive reminders during the time that the server is down.

• Recurring Meeting Limits
  
  To set the server limit for Max Recurrences Per Meeting to be infinite, enter a 0.

• To Do Import/Export

  The Priority setting of To-Dos to which you are a guest incorrectly appears as Urgent after importing to version Meeting Maker version 7.x from any version of Meeting Maker below 7.0.

• Cross-Server Busy Time and Holidays

  When a user on one server views the busy time of a user on another server, if holidays are set differently on the servers, the busy time shows the holidays of the viewing user rather than the correct holidays of the viewed user.

• Server Names Containing ASCII Characters

  If you create a server name containing extended ASCII characters, the server name may display differently on a Macintosh or Unix Client. Meeting Maker, Inc. recommends not using extended ASCII characters in server names.

• Uninstalling the Meeting Maker Client on Macintosh OS X
  
  When you uninstall the Meeting Maker Client on Macintosh OS X, the Meeting Maker Admin and Server are also uninstalled if they are present on the same machine.

• Auto-Upgrade on Macintosh OS X
  
  When you auto-upgrade Meeting Maker on Macintosh OS X, the new version of Meeting Maker installs to the default directory even if your previous installation of Meeting Maker was in a custom directory.

• Macintosh OS X Server Configuration Files
  
  The file serverpref.ini is no longer used to configure the Macintosh OS X Server. Enter logging preferences in the server.conf file instead. If you have old configuration files, you do not need to make any changes. The Macintosh OS X Server can still read the old files. However, settings in the server.conf file override preferences in the serverpref.ini file.

• Installing on Macintosh OS X
  
  Do not install the Meeting Maker Admin on Macintosh OS X while logged in as root. If you do, permission problems may occur.

• Navigation Buttons in HTML on Macintosh

  If you upgrade to Meeting Maker 7.x from a previous version of Meeting Maker, the navigation buttons on HTML published calendars on Macintosh do not work.  To avoid this problem, delete the file ppchtml.exp in <Install Direcory>:Meeting Maker Exporters before upgrading.  If you have already upgraded, delete this file and then re-install Meeting Maker.

• Auto Upgrade on Solaris

  When you upgrade from any Meeting Maker version before 7.0.1 using Auto Upgrade, Solaris Client users may experience the following problem with background download of the new files.  The first time the user logs in to Meeting Maker, the Solaris Client downloads the first file and then stops.  The download continues normally the next time the user logs in, or when the server is switched to foreground download.

• Linux Close Button
  
  You cannot close the Meeting Maker Admin or Server window using the close button on Linux. To close the Admin or Server window, select Close from the File menu.

• Installing the Meeting Maker Client on a Partitioned Windows NT Drive

  If you install the Meeting Maker Client on a partitioned Windows NT machine with little room available on the C drive, the Client may not install successfully even if there is sufficient room on the partition where you are attempting to install the Client.  You may also receive incorrect messages stating that certain install files are missing.

Back to Table of Contents

4. Contacting Meeting Maker, Inc.

• Before Calling Technical Support

  In order to receive technical support, you must have a maintenance contract. The Meeting Maker support staff is available to help you with any questions regarding Meeting Maker. Before calling Meeting Maker Technical Support, make sure:

  • Your workstation conforms to Meeting Maker hardware and software requirements.
  • Any Meeting Maker problems are not related to a computer virus. As a precaution, use a virus protection program on a regular basis.

• When Calling Technical Support

  When calling support, write down any error message or messages associated with the problem and call from a telephone near the computer where the problem occurred. In addition, have the following information available to help the Technical Support staff answer your question quickly:

  • Your Meeting Maker account number
  • Computer models involved
  • Meeting Maker version number
  • Operating system version of desktop computer, and if necessary, servers involved
  • Any special hardware or network configurations that may affect the problem
  • On Macintosh, any special control panels, chooser extensions, system extensions, or network extensions running on the computer
  • On Windows, any special network drivers running on the computer

• Contact Information

  Contact Meeting Maker Technical Support using one of the methods below:

  Telephone: 1-800-282-7319, and enter "1" for Meeting Maker Support
  Hours: Monday - Friday 9:00 AM to 7:00 PM, US Eastern Time
  Fax: 1-800-282-7414
  Email: mmhelp@meetingmaker.com
  World Wide Web: Additional technical documentation is available at http://support.meetingmaker.com
  

Back to Table of Contents