Notify Technology Corporation - Confidential




               Notify Technology Corporation
        Release Notice for N...
Notify Technology Corporation - Confidential



      11/04/08                          Jodie Grazier                Modif...
Notify Technology Corporation - Confidential



I. About This Document.......................................................
Notify Technology Corporation - Confidential



I. About This Document

This document serves as the main section of the No...
Notify Technology Corporation - Confidential



          NLPIM_OracleCalDAV.dll                              4.6.0.3
    ...
Notify Technology Corporation - Confidential



              device. Note that this does not apply to iPhone/iPod devices...
Notify Technology Corporation - Confidential



     17.)The ValidateLease service has been modified to reset to 1 availab...
Notify Technology Corporation - Confidential



     4.) For pages that have a table display, added options to view a prin...
Notify Technology Corporation - Confidential



     9.) The IT Policy > Calendar Sync Rules has a new setting for ‘Delete...
Notify Technology Corporation - Confidential



     23.)Added Users Statistics for tracking pim Invitations. New invitati...
Notify Technology Corporation - Confidential



B. NotifyLink Server Things To Know

     1.) Items sent via a CATCHUP com...
Notify Technology Corporation - Confidential



                For IMAP servers that don’t use the deleted flag, deletes ...
Notify Technology Corporation - Confidential



         This does not apply to Windows Mobile devices; Windows Mobile dev...
Notify Technology Corporation - Confidential



View features and issues that are specific to MDaemon.

H. Meeting Maker

...
Upcoming SlideShare
Loading in …5
×

NT Manage Server Escalation Procedures.doc

439 views

Published on

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
439
On SlideShare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
4
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

NT Manage Server Escalation Procedures.doc

  1. 1. Notify Technology Corporation - Confidential Notify Technology Corporation Release Notice for NotifyLink Enterprise Server REVISION HISTORY Date Author Description of Changes 04/16/10 Jodie Grazier See changes to the Oracle section. 04/12/10 Jodie Grazier See changes to the ActiveSync Solution section. 03/12/10 Jodie Grazier See changes to the Oracle and GroupWise sections. 03/04/10 Jodie Grazier See changes to the ActiveSync, MeetingMaker, and Oracle sections. 02/24/10 Jodie Grazier Release of NLES v4.6.x Update 14. See changes to the ActiveSync section (support for Android devices using TouchDown client). 12/04/09 Jodie Grazier Noted with release of NLES v4.6.x Update 12 See changes to the Exchange, Mirapoint, and ActiveSync sections. 10/12/09 Jodie Grazier Announcement of support for webOS devices (Palm Pre). See ActiveSync Solution section for more information. 10/02/09 Jodie Grazier Version 4.6.2 BeamReader support and various bug fixes. 09/23/09 Jodie Grazier Added Outstanding Issue: - meeting invitation notes 11660 07/24/09 Jodie Grazier Version 4.6.1 Added support for WM devices using AS. Added support for iPhone v3.0. Moved AS notes to a new file Added support for LDAP authentication for NLES Admin/Client web console login. 07/10/09 Jodie Grazier Remove item related to SyncML Server (no longer supported) 04/07/09 Jodie Grazier Added note about SMIME being upsupported 10757 02/26/09 Jodie Grazier Version 4.6.0 5/8/10 Page 1 of 14
  2. 2. Notify Technology Corporation - Confidential 11/04/08 Jodie Grazier Modified iPhone items 8814 and 9023 10/24/08 Jodie Grazier Updated iPhone Things To Know 10/20/08 Jodie Grazier Highlighted v4.5.2 New/Changed features in red “(v4.5.2)” 10/17/08 Jodie Grazier NLES v4.5.2 – updated file versions 08/18/08 Jodie Grazier Added iPhone Thing To Know: - multiple NL users with same username 9199 08/13/08 Jodie Grazier NLES v4.5.1 - Added notes for iPhone support. 07/07/08 Jodie Grazier Added link to Google release notice. 06/17/08 Jodie Grazier Added link to Scalix CalDAV release notice 04/11/08 Jodie Grazier Added link to FirstClass release notice 02/08/08 Jodie Grazier Added Feature Not Supported: - Synchronization of Meeting Attendees 7187 11/28/07 Jodie Grazier Added link to MDaemon release notice 11/16/07 Jodie Grazier Added link to Zimbra release notice 11/05/07 Jodie Grazier Added link to CGP release notice 09/20/07 Jodie Grazier Added link to Meeting Maker release notice 09/10/07 Jodie Grazier Added link to Kerio release notice 09/05/07 Jodie Grazier Added link to Mirapoint release notice 08/27/08 Jodie Grazier Added link to Scalix release notice Added Device Things To Know: - Category synchronization - Tracking of invitation responses - Palm Multi-Day events 07/30/07 Jodie Grazier Added link to Exchange release notice 07/19/07 Jodie Grazier Added link to Sun release notice Added Important Thing To Know for ‘Synchronize All Devices’ Added Important Thing To Know for Recipient Lists. 07/11/07 Jodie Grazier Added link to Oracle release notice 06/21/07 Jodie Grazier Added note about user class and LDAP server 05/23/07 Jodie Grazier Version 4.5.0 5/8/10 Page 2 of 14
  3. 3. Notify Technology Corporation - Confidential I. About This Document.....................................................................................................4 II. Installer Information ......................................................................................................4 A. Install Files.................................................................................................................4 B. Program Files.............................................................................................................4 III. Functional Summary.....................................................................................................5 A. Installer New/Changed Features...............................................................................5 B. Server New/Changed Features.................................................................................6 C. User Interface (Web) New/Changed Features..........................................................7 IV. Important Things To Know.........................................................................................10 A. Features Not Supported..........................................................................................10 B. NotifyLink Server Things To Know..........................................................................11 C. Device Things To Know...........................................................................................12 V. Outstanding Issues/Bugs............................................................................................13 A. NotifyLink Server Outstanding Issues/Bugs............................................................13 VI. Mail Server Specifics..................................................................................................13 A. CommuniGate Pro...................................................................................................13 B. Exchange.................................................................................................................13 C. FirstClass.................................................................................................................13 D. Google.....................................................................................................................13 E. GroupWise...............................................................................................................13 F. Kerio.........................................................................................................................13 G. MDaemon................................................................................................................13 H. Meeting Maker.........................................................................................................14 I. Mirapoint....................................................................................................................14 J. Oracle.......................................................................................................................14 K. Scalix.......................................................................................................................14 L. Scalix CalDAV..........................................................................................................14 M. Sun..........................................................................................................................14 N. Zimbra......................................................................................................................14 VII. Specifics for NotifyLink ActiveSync Solution.............................................................14 5/8/10 Page 3 of 14
  4. 4. Notify Technology Corporation - Confidential I. About This Document This document serves as the main section of the NotifyLink Enterprise Server Release Notice. It provides information common to all NotifyLink Enterprise Server systems. Also contained in this document are links to sub-categories of the Release Notice, containing features and issues specific to: • Each of the Mail Servers supported by NotifyLink (Section VI of this document) • The NotifyLink ActiveSync Solution (Section VII of this document) II. Installer Information Original Release Date (NLES v4.6.0): 02/26/2009 Base Product: NotifyLink Enterprise Server A. Install Files File Name Version enterprise_Messaging_Base.exe 4.6.0.9 enterprise_SQL_Base.exe 4. 6.0.9 enterprise_Web_Base.exe 4. 6.0.9 UpdateDB.exe 4.6.0.17 B. Program Files File Name Version AttachmentService.exe 4.6.0.13 AvailableNLUsers.exe 4.6.0.5 GleanerController.exe 4.6.0.28 InternetMsgService.exe 4.6.0.5 NLMonitor.exe 4.6.0.7 Nlpim.exe 4.6.0.3 NLPimService.exe 4.6.0.3 NotificationController.exe 4.6.0.7 ResponseHandler.exe 4.6.0.23 ValidateLeaseService.exe 4.6.0.5 AirSyncRedirect.dll 4.6.0.0 mimepp.dll 3.0.0.16 nlmonitor.dll 4.6.0.6 NLPIM_Base.dll 4.6.0.6 NLPIM_CalDAV.dll 4.6.0.6 NLPIM_CommunigatePro.dll 4.6.0.3 NLPIM_CommunigatePro_CalDAV.dll 4.6.0.3 NLPIM_Exchange.dll 4.6.0.2 NLPIM_FirstClass.dll 4.6.0.3 NLPIM_Google.dll 4.6.0.3 NLPIM_Groupwise.dll 4.6.0.4 NLPIM_Kerio.dll 4.6.0.2 NLPIM_Kerio_CalDAV.dll 4.6.0.0 NLPIM_MDaemon.dll 4.6.0.2 NLPIM_MeetingMaker.dll 4.6.0.4 NLPIM_Mirapoint.dll 4.6.0.4 NLPIM_Oracle.dll 4.6.0.5 5/8/10 Page 4 of 14
  5. 5. Notify Technology Corporation - Confidential NLPIM_OracleCalDAV.dll 4.6.0.3 NLPIM_Scalix.dll 4.6.0.3 NLPIM_Scalix_CalDAV.dll 4.6.0.3 NLPIM_Sun.dll 4.6.0.3 NLPIM_WebDAV.dll 4.6.0.5 NLPIM_Zimbra.dll 4.6.0.2 NLPIM_Zimbra_CalDAV.dll 4.6.0.0 NTC_core.dll 4.6.0.1 ntc_crypto.dll 4.6.0.4 NTC_nlesprotocol.dll 4.6.0.5 smailpp.dll 2.4.0.17 php_libnlgatewayw.dll 4.6.0.11 php_libnlvalidateleasew.dll 4.6.0.0 php_ntc_airsync.dll 4.6.0.2 php_ntc_crypto.dll 4.6.0.6 III. Functional Summary A. Installer New/Changed Features 1.) Added support for Apache 2.2. 2.) Changed PHP distribution to v5.2.6. 3.) Removed the NotifyLinkSupport.exe tool. 4.) Added automatic startup of the NLES AvailableUsers service upon install. 6299 5.) Corrected an error during the installation of the messaging component that occurred when the ‘sa’ password was entered incorrectly. 6280 6.) A new registry key for the log directory has been created. To specify the name of the log files for individual services within this directory, use the LogName registry keys. I. HKLMSoftwareNotify Technology CorporationLogPath, the default is “<InstallDir>logs” II. HKLMSoftwareNotify Technology Corporation<serviceName>LogName 7.) Changed the default value for the ConversionTimeout registry key from 180 to 360. On upgrade, the current setting is maintained. I. HKLMSoftwareNotify Technology CorporationNLES AttachmentService 8.) Changed the default value for the MaxThreads registry key to 1 for new installations. I. HKLMSoftwareNotify Technology CorporationNLES PimService 9.) Added a new registry key for the HTTPTimeout value. This defaults to 90 seconds. I. HKLMSoftwareNotify Technology CorporationHTTPTimeout 10.)The registry keys for MaximumLogSize are now in KB rather than MB. 9559 11.)Eliminated use of the System32 directory and instead add the NotifyLink Enterprise Server directory to the Path. This requires a reboot during installation/upgrade. 12.)Changed the SQL/Database component to no longer require user input to indicate if the SQL Server is Local or Remote. The user is required, however, to specify the version of the SQL Server. 13.)New installations use a 256 bit encryption key for server encrypted data. Users with a v4.6.x device client added after an install/upgrade of NLES v4.6.0 will also use a 256 bit encryption key for user encryption. I. Pre-existing user will continue to use a 192 bit key until they generate a new key in the Security Rules policy of the NLES web. II. Users that have selected TDES encryption must continue to use a 192 bit key. III. Due to this change, a new user added to NLES will not be checked for email or pim until the device has successfully connected to the server to register. This will ensure that and encryption key of the proper size has been generated prior to queuing notifications for the 5/8/10 Page 5 of 14
  6. 6. Notify Technology Corporation - Confidential device. Note that this does not apply to iPhone/iPod devices, users with this type of device will check for email and pim immediately. 14.)Removed several fields, tables, and records in the database that are no longer used. This includes several aspects related to AOL, POP3, and QWR and jobs for ‘WCTP Cleanup’ and ‘WCTP Sent Messages Cleanup’. 15.)The OnDemand/Hosted installer now has a setting for whether or not the Web Component will use SSL. This setting defaults to on. 10018 B. Server New/Changed Features 1.) The NLES AvailableNLEXUsers and NLES AvailableNLSXUsers services have been merged into the NLES AvailableUsers service. 2.) Added the ability to run multiple copies of AttachmentService, GleanerController, and NLPim. 3.) Added the ability to log in HTML. Both new installations and upgrades will now log in HTML. I. To change to standard text logging, edit the LogName registry keys to use an extension “.txt”. i. HKLMSoftwareNotify Technology Corporation<serviceName>LogName II. To make the HTML logs available via a web browser, create a virtual directory in the web server that maps to the “Logs” directory. Note that this can negatively affect performance. 4.) Added support for LDAP redirection. 5.) Added support for Authenticated SMTP (AUTH PLAIN) and SSL/TLS for SMTP. See the SMTP Settings page located within the Server Administration area of the NLES web admin. 6.) Improved handling of HTML emails that do not contain a BODY tag. 7.) Corrected an issue with the subject of an email being incorrect when it was forwarded and contained upper ascii characters. 9687 8.) Corrected an issue that occurred when Smart Sync Read and Smart Sync Delete were enabled. If a new message was changed or deleted prior to the device retrieving it, the message was still sent to the device. 9116 9.) Improved handling of unnamed attachments. Previously, the filename ‘EmailvCard.txt’ was used for all unnamed attachments. Now they will be named ‘Unnamed.<ext>’ where <ext> is the file extension based on the Content Type in the MIME. 4514/7803 10.)Corrected an issue with attachment names that contain upper ascii. Previously, the filename was being set to “NotifyLink Unsupported Character Set”. 11.)Changed encoding of attachments sent to BlackBerry devices. This causes a limitation that prevents attachments converted prior to an upgrade to be retrieved to the device after the upgrade. See Appendix A in the Upgrade Instructions for more details. 12.)For customers experiencing resource problems due to System Monitoring jobs, run times can now be offset to run at different times. This applies to jobs that run on a daily schedule. 6158 13.)Corrected an issue in which the Send Authorization Failures job sent a failure notice for pim authorization when the user is disabled. 6938 14.)Fixed the SQL Server Reports system monitoring job for customers using SQL Server 2005 or 2008. 15.)Added the ClientDeviceSAKey, Sender, Subject, and Time (where applicable) in the Sent Timeout Errors report for emails that have timed out. 16.)Modified ResponseHandler to improve processing time of device to server messages by using one thread per user (for each user that has pending responses during the current cycle). A ResponseHandler cycle starts by determining which users have pending responses, a thread is started for each of these users, the cycle ends when all threads complete or 10 minutes has passed. A new cycle will not being until the previous cycle has ended. I. There will now be one ResponseHandler log file for the cycle information and a ResponseHandler_<CDKey> log file for each user. 5/8/10 Page 6 of 14
  7. 7. Notify Technology Corporation - Confidential 17.)The ValidateLease service has been modified to reset to 1 available grace period when licenses have been successfully validated. Additionally, a grace period has been extended to 72 hours. This means that any NLES system which successfully validates leases at least once in a 72 hour period will never ‘run out’ of grace periods. 9499 18.)Corrected an issue with the Task Synchronization Range that allowed tasks one day beyond the Look Ahead to synchronize to the device. This applied to Echange, Kerio, MDaemon, Sun, and Zimbra collaboration suites. 4109/6228/6769 19.)Increased the maximum size of an OTA load message to 10 MB. 20.)Redline pages now require authentication (USERNAME and PASSWORD parameters) using the same credentials as the administrative web login. 9577 21.)Fixed all services that we not correctly using the EnableLogging registry key. 8632 22.)Corrected an issue with GleanerController and PIM logging that logged http:// even when HTTPS is being used for lease validation. 23.)The ValidateLease service now uses the proxy settings as defined in Server Administration. 9566 24.)Added a log statement to GleanerController when a message is Blocked or Filtered. 5117 25.)Changed pim to truncate the following fields to 250 characters: Task subject/description, Calendar subject and location, Contact first and last names. 5852/6227/6654/6697/7668 26.)Pim processing of events sent to the device will not send the reminder information if the reminder occurs in the past. 8898 27.)When a Clear Device (Wipe) command is sent, all existing HWP records will be marked with NewMsg = 0 so that the device will not unnecessarily pull down the data. 9356 28.)Corrected an issue with message retrieval that applies to BlackBerry users. When the device prompted the user for how many messages to download, all messages were sent rather than the specified number. 10402 29.)Improvements have been made in the AirSync dll to correct issues that caused the iPhone/iPod Mail app to crash or redirect to the home screen. 10334 30.)Corrected an issue with iPhone/iPod devices that cause a contact to be synchronized to the device if it was deleted on the server prior to the device retrieving the contact. 9537 31.)Performance enhancement for AirSync to clear existing Pings when a new Ping is issued (Push method of retrieval). 9572 32.)Modified logging to only log the subject and ID at standard logging. At log level 3, the full XML data is logged (encrypted). Additionally, a log level can now be specified per user (ClientDevices.ASDebugLogLevel). 9831/10291 33.)For iPhone/iPod devices, track the time that the WIPE was sent to the device. This is shown on the Security page. 10082 34.)Corrected an issue that caused the Trash folder to synchronize to the iPhone/iPod device as a regular folder rather than the Trash folder. 10294 35.)Added an option to search only the first and last name fields during Remote Lookup from an iPhone/iPod device. The simplified search can be enabled by setting ServerConfig.ASLDAPSimpleSearch = 1. 9951 C. User Interface (Web) New/Changed Features 1.) Security updates to remove cross-site scripting (XSS) and sql injection vulnerabilities. 2.) Changed web to disallow auto-complete in password fields. 9593 3.) Added an automatic redirect to the login page when the web session expires. There will be a warning displayed 10 seconds prior to the redirect which will allow the user to continue the session. 9518 I. This feature uses the session.cookie_lifetime variable from the php.ini file. If IIS has a shorter timeout, this feature will not apply. 5/8/10 Page 7 of 14
  8. 8. Notify Technology Corporation - Confidential 4.) For pages that have a table display, added options to view a printable version and export to CSV/ XLS format. 5.) Added support for Multiple IT Policies. Each User Class is associated with an IT Policy. For unclassified users, the Default IT Policy is applied. There are also synchronization options (Automatic Push or manual) that define how changes are synchronized to users on the policy. The synchronization setting is defined within the User Class or within the Default IT Policy (for Default policy only). I. See the ‘Managing IT Policies’ and ‘Managing User Accounts > User Classes’ sections of the Administrative Guide for more details. 6.) Changes and additions to the IT Policy Rules include the following. See the Administrative Guide for more details on individual settings. I. Changes for Control Option rules i. Enable Folder Mirroring, Enable Smart Read, and Enable Smart Delete are now able to be set at the IT Policy level in addition to the User IT Policy level. ii. Message Availability now has a minimum of 1 day instead of 15 days. iii. Added Track Device Mail setting for enabling/disabling tracking of originations, replies, and forwards sent from the device. 6929 II. Removed settings in Calendar Sync Rules, Contact Sync Rules, and Task Sync Rules that were no longer being used. This includes conflict resolution, formatting options, Send Daily Summary, etc. 5500 III. New area for Device Password Rules including i. Password 1. Note that the minimum size of 8 is now enforced. ii. Password Strength iii. Password Expiration iv. Password History IV. Modified Lock Password Rules to have individual lock settings for Lock Timeout (now known as Inactivity Timeout) and Lock Password (now known as Password in the Device Password Rules). V. Added Lock Password Rules for i. Challenge Timeout ii. Password Echo iii. Wipe on Failed Unlock Attempts iv. Duress Notification Recipient VI. Added Email Rules for i. Use Trash Folder ii. Track Sent Items (previously Delete Send Commands) 1. This setting now applies to Windows Mobile devices. 5958 VII. The File List Rule now defaults to Never. 8776 VIII. The ‘Update Folders’ button on the Folders page has been renamed to ‘Check Mail Server for Folder Updates’. 9425 IX. Access Rules has been made its own page and redesigned for better usability. 9443 X. Changes to the Security Rules i. ‘Automatic Key Generation’ is no longer an option. 5116 ii. Added a note that ‘Clear Device’ and ‘Clear Device and Cards’ will also lock the device. 7163 7.) Added a note that the Email Rules > Sync Reads and Sync Deletes do not apply to Windows Mobile devices. 6024 8.) The IT Policy > Notification Format Rules now has three separate categories for attachment support: Office Applications, Images, and PDFs. For BlackBerry device users, each category can be set individually to customize the attachment options; attachments that do not fall into any of these categories are sent in native format provided the device supports it (i.e., wav files). For non- BlackBerry users, the categories are irrelevant since all attachments are sent in Original/Native format. 5/8/10 Page 8 of 14
  9. 9. Notify Technology Corporation - Confidential 9.) The IT Policy > Calendar Sync Rules has a new setting for ‘Delete Invitations From Device’ which will detect that status (Accept/Decline/Tentative) of an invitation and delete the invitation from the device’s Inbox based on the setting. The options include None, Only Accepted, Only Declined, Only Tentative, Accepted/Declined, Accepted/Tentative, Declined/Tentative, All Responded. This feature does not apply to Scalix or Scalix CalDav PIM servers. 10.)Added support for attachments sent in Original/Native format to BlackBerry devices; this is the preferred method of attachment support for BlackBerry devices. This feature only applies to BlackBerry devices that meet the minimum requirements (including Operating System v4.5 and NotifyLink device client v4.6.3). See the NotifyLink BlackBerry User and Installation Guide for more information. I. Users with a BlackBerry device that does not meet the requirements can continue to use Dynoplex rendered attachments. II. The plain text attachment option is no longer supported. Users who had this option selected prior to upgrade to NLES v4.6.0 will be automatically set to Dynoplex rendered format for attachment processing. 11.)Added support for Office 2007 file formats (docx, xlsx, pptx) for BlackBerry devices. This applies to all users set to Original/Native format and those users set to Dynoplex rendered format that have Office 2003 on the server running the NotifyLink Messaging Component. 12.)Added automatic cleanup and reset of database information when a Mail or PIM server is edited and when a user’s Mail/PIM server is changed. This applies when: I. A Mail Server’s ‘Incoming Mail Server Name’ and/or ‘Protocol’ is edited. II. A PIM Server’s ‘PIM Server Address’ and/or ‘Protocol’ is edited. III. A user’s ‘Incoming Mail Server’ and/or ‘Calendar/Contact/Task Server’ is edited. 13.)If the User Class is changed for an LDAP Server (from None to a specific class or from one class to another), any users that should no longer have access based on their User Class are rest to not have an LDAP Server. 7040 14.)Added support for redirection from HTTPS to HTTP, this is primarily for connection to PIM Servers. This feature is disabled by default and can be set in the Administrative Web > Server Administration > Allow HTTPS to HTTP Redirection. 6663/8877 15.)Added a configurable ‘Job Email Address’ for all system monitoring jobs. This allows the error reports to be sent to different email accounts rather than sending all error reports to the NotifyLink administrator. 16.)Added ‘Custom Jobs’ to System Monitoring; these jobs are optional and disabled by default. For more information about each job, see the System Monitoring section of the Administrative Guide. I. Device Battery Alert II. Device Memory Alert III. Device Sync Alert IV. Mail Server Processing Check V. PIM Server Processing Check VI. User Login Failures 17.)The NLES Statistics system monitoring job has a new setting for ‘Show Rankings’. This allows the user to enable/disable the ranking section of the email report that is generated. 18.)The NLES Statistics system monitoring job was not correctly reporting when there were only iPhone/iPod devices on the server. This has been resolved by tracking information to the Billing table for iPhone/iPod devices. 10038 19.)The Mobile Message Tag is now configurable in the following ways: I. The MMT can be enabled or disabled. If it is enabled, it can be defined per server or per user class. See the Server Administration > Mobile Message Tag setting. II. If defined per user class, each User Class can set the Mobile Message Tag text (or choose to leave it blank). 20.)In User Administration, added a confirmation screen for the Enable All, Disable All and Remove All buttons. 6618 21.)In User Administration, added ClientDeviceSAKey as a searchable field. 6294 22.)The Server Time Zone and GMT offset are now displayed on the User Statistics page. 9297 5/8/10 Page 9 of 14
  10. 10. Notify Technology Corporation - Confidential 23.)Added Users Statistics for tracking pim Invitations. New invitation and deleted invitation counts will be displayed. The Changed and Load values are not tracked and are expected to be ‘- -‘. 8685 24.)In Server Administration > LDAP Servers, the BaseDN value is now maintained after editing the server. 5959 25.)In Server Administration > LDAP Servers, the username field now allows 100 characters. 10017 26.)In Server Administration, removed the option to ‘Force Device Authentication’. Device authentication is always used. 27.)Changes to Device Management to improve performance. This includes only showing the ‘Attachments Pending’ count when it is manually requested in ‘Check User Status’ for the current user. 9524 28.)In Device Management, fixed an issue that caused the values of ‘Last Activity’ and ‘Messages Pending’ to not refresh. 5981 29.)The BlackBerry device will now send up the PIN information to the server. This can be viewed in the Device Management area by selecting the ‘Device PIN’ column. It is NOT used to overwrite the user’s PIN as defined in User Administration. 30.)Added ‘Check All’ and ‘Clear All’ buttons on the Add/Edit Level page. 10007 III. Server Administration > Administrative Logins > Edit Admin Levels > Add/Edit Level. 31.)In the Edit User page, added a button to synchronize the Mailbox password value to the PIM password fields. 6048 32.)In the Edit User page, the maximum size of the Client Web Login Password is now 100 characters. 10275 33.)Corrected an issue that prevented the Administrative Login password from being edited for the default login that was created during installation. 6002 34.)In the Mobile Web, added a page to set the Attachment options for the user. 35.)The OnDemand/Hosted system had a maximum size for the Company Name field that was inconsistent with the provisioning system. This has been corrected to use 100 characters. 8650 36.)In the Administrative Web and Client Web Consoles, a feature has been added to allow validation with an LDAP server. This is in addition to the current method of defining and managing a password for the NLES web. See the Administrative Web Guide for more details. 10846 IV. Important Things To Know A. Features Not Supported 1.) Reflex/Data devices are no longer supported. This includes the Motorola T900, P935, Timeport, Rim Data devices, etc. 2.) POP3 protocol is no longer supported. If POP3 is being used, it will no longer work after upgrading to NLES v4.5. 3.) Upper ASCII characters are not supported in the text of filters. In some cases, attempting to create a filter using upper ASCII will fail. However, even if the filter can be created, processing of the filter will not be handled properly. 5566 / 5593 4.) Rich text file attachments are not currently supported for BlackBerry Phone devices. RTF file attachments are supported on Palm and Windows Mobile devices. 5797 5.) Synchronization of meeting attendees to the device is not supported. When the user is invited to a meeting, the attendees (recipients) are not sent in either the meeting invitation or the associated calendar event that is sent to the device. 7187 6.) Emails that are encrypted or signed with SMIME or PGP will not be processed correctly by NotifyLink; if there is an attachment on the message it will not be found. 10757 5/8/10 Page 10 of 14
  11. 11. Notify Technology Corporation - Confidential B. NotifyLink Server Things To Know 1.) Items sent via a CATCHUP command for high-speed devices will not show up in the Sent Items folder. Furthermore, when a CATCHUP is performed with a high-speed PUSH device and Notification if turned OFF, the SMS trigger message will not be sent to the device. You must perform a Get/Send from the device in order to retrieve your CATCHUP messages. 2.) If using php before installing/upgrading, you may need to update the php.ini file. If the php.ini file settings are not updated you may have problems downloading attachments greater than 4KB. Check the file located in C:WINNTphp.ini and verify the following values – update the file if needed: max_execution_time = 3600 magic_quotes_gpc = Off magic_quotes_sybase = On max_input_time = 60 memory_limit = 15M post_max_size = 15M file_uploads = On upload_max_filesize = 15M odbc.defaultlrl = 15728646 odbc.defaultbinmode = 1 output_buffering = On display_errors = Off 3.) Dynoplex Administration page is not available until a BlackBerry license has been added to the server. The button will be visible on the Server Administration screen. For upgrading customers: Any BlackBerry device license that was already added to the server prior to the upgrade, the key needs to be updated after the upgrade. Go to License Manager  License Details  Update License 4.) The default registry settings for Gleaner Controller are configured to process up to 5 users every 3 seconds. Along with the default Email Check Interval of 5 minutes, this allows for processing of up to 500 users in 5 minutes by default. 5.) The ValidateLease service is now automatically restarted by NLES Monitor Service when a license is added to the server. Allow 60 seconds for the new license to be detected. 6.) Note for installations on Microsoft SQL Server 2005: the password policy is not enforced; the database may not be created if the specified password does not meet the policy. See the Microsoft SQL Server documentation for full details on the password policy. http://msdn2.microsoft.com/en-us/library/ms161959.aspx 7.) During the Messaging component install, the user will be prompted to enable database permissions for the Disk Space Check and SQL Report Health Monitoring jobs. I. NOTE: If these permissions are not granted, the SQL Report and Disk Space Check jobs will fail. The administrator will receive an email notice of the failure. To grant the permissions after the initial installation/upgrade, perform one of the following: i. Uninstall/Reinstall the Messaging Component and grant the permissions when prompted. ii. As ‘sa’, run the DiskSpace.sql and SQLReports.sql queries from the NLES install directory. 8.) The Log Cycling job remains in the SQL Server Jobs rather than being run by the NLES Monitor Service. SQL Server Express does not support jobs so any customer running Express edition will not have this feature. 9.) A delete is not sent to the device for messages as they expire from the message availability range. 10.)The GleanerController service uses the IMAP Deleted flag as follows I. If the message is flagged as deleted before Gleaner finds it, the message will not be sent to the device. II. If the message is flagged as deleted after Gleaner has found it and sent a notification to the device, a delete will be sent to the device. 5/8/10 Page 11 of 14
  12. 12. Notify Technology Corporation - Confidential For IMAP servers that don’t use the deleted flag, deletes will be detected when the item is III. removed from the folder. 11.)When Smart Gleaner is enabled, you may limit the amount of message body that is read from the server. If Smart Gleaner is disabled, then the entire message will be pulled from the server. These settings can be modified from the Controls options within the Web Admin and Client interfaces. 12.)Using Security features still keeps the user active on the Enterprise Server. Therefore, if the device is missing or stolen is recommended that they also be disabled from the server as well. 13.) If uninstalling the SQL component, use the ‘Change’ option in Add/Remove Programs. The sa password should be entered at the on screen prompt. 14.)When disabling Send Attachments option, the Smart Retrieval settings (under Control Options) will be enabled and set to 10,000 characters. This is to reduce network traffic when Send Attachments is disabled. 15.)If CPU usage is high when a BlackBerry attachment is being processed, a popup may occur to say that the converter application could not be created or initialized. This popup may be cleared; the attachment service will automatically re-try the conversion at a later time. 16.)When the “Folder Mirroring” option is enabled, additional CPU and memory resources may be used. If this is a problem, have users cleanup messages on the GroupWise server for the folders that are being processed. 17.)Subfolders will be displayed in the Folders page of the web even when the parent folder is not present. As a result, these subfolders will appear under an incorrect parent folder. 4917 18.)Some IMAP4 servers specify TLS is supported, but the implementation actually uses SSL. In this situation, the NotifyLink email login will fail with error 10180 (TLS handshake error). One example is UWash (University of Washington) IMAP4 server v2006b.373. Using NotifyLink for email over SSL will work for these servers. 19.)The ‘Synchronize All Devices’ feature only applies to active (Enabled) users. If sending fails for any user(s), the ClientDeviceSAKey(s) will be displayed after the processing has completed. The most likely cause of failure is an invalid PIN or Alias (e.g. contains a space, apostrophe, etc.). 20.)If the OS time zone setting is changed on a server running NotifyLink, the server should be restarted. 5180 21.)For 'Synchronize All Devices', if sending fails for any user(s), the ClientDeviceSAKey(s) will be displayed after the processing has completed. The most likely cause of failure is an invalid PIN or Alias (e.g. contains a space, apostrophe, etc.). 22.)This issue applies when the 'List of Recipients' option is selected in Notification Format. If the total size of the recipient addresses is greater than 2000 characters, the list is truncated in the NotifyLink database. This prevents the device from parsing the list correctly and the result is that the recipient list is not shown. Only the user's email address will be displayed as a recipient. 3887 C. Device Things To Know 1.) Palm is limited to 15 characters for category lengths. Address Books with names longer than this do not synchronize completely to the device. If a Contact in such a Category is edited on the device, the Category will be only 15 characters. The server will then create a new Address Book with the 15-character name. 2.) Gif files on the Treo 600 don’t always open correctly in the browser. If you go home and then back the gif will then display correctly. 3.) Files downloaded to the BlackBerry Phone will lose image data during the Dynoplex rendering process. If the file is then uploaded as an attachment, it will not be identical to the original file. The same thing applies to documents with charts or tables embedded in them. Tables may render with the data still intact, but the table formatting will be lost. 4.) New Categories defined on Palm or Window’s Mobile will not be sent up to the server as a new Address Book until a contact is added to the new Category. 5.) The devices keep track of responses to meeting requests, e.g. attempting to Accept an invitation that has already been Accepted gives a warning message saying "You've already accepted....”. 5/8/10 Page 12 of 14
  13. 13. Notify Technology Corporation - Confidential This does not apply to Windows Mobile devices; Windows Mobile devices allow multiple responses without any warning. 6.) The Palm does not support multi-day events. When a multi-day event is synchronized to the device, it will appear in the Palm calendar on the first day only. NOTE: With the v4.5 client application, an event that spans exactly two days can be synchronized correctly. For example, starting on Jan. 12 at 8:00 p.m. and ending on Jan. 13 at 6:00 a.m. V. Outstanding Issues/Bugs A. NotifyLink Server Outstanding Issues/Bugs 1.) Reference the Knowledge Base for additional information about outstanding issues. 2.) Some email messages that are multipart where the first part’s content type is plain text and the second part is html/rtf may not render correctly. ‘Message’ or the subject may precede the notification body. 3.) Forwarded html messages are displayed differently depending on your email client/viewer. Some viewers may show the html as the body and attach a txt file with the text version. 4.) Any file in the <NotifyLinkInstallDir>webApps directory can be used as an attachment for the “Send Information to Device” feature in Device Management. PHP does not adhere to the Windows file permissions settings, so even files that have access denied to all users can be sent as an attachment. 4914 5.) Meeting invitations created on the device do not synchronize the Notes field to the attendee's email invitation or event. 11660 VI. Mail Server Specifics A. CommuniGate Pro View features and issues that are specific to CommuniGate Pro. B. Exchange View features and issues that are specific to Exchange. C. FirstClass View features and issues that are specific to FirstClass. D. Google View features and issues that are specific to Google. E. GroupWise View features and issues that are specific to GroupWise. F. Kerio View features and issues that are specific to Kerio. G. MDaemon 5/8/10 Page 13 of 14
  14. 14. Notify Technology Corporation - Confidential View features and issues that are specific to MDaemon. H. Meeting Maker View features and issues that are specific to Meeting Maker. I. Mirapoint View features and issues that are specific to Mirapoint. J. Oracle View features and issues that are specific to Oracle. K. Scalix View features and issues that are specific to Scalix. L. Scalix CalDAV View features and issues that are specific to Scalix CalDAV. M. Sun View features and issues that are specific to Sun. N. Zimbra View features and issues that are specific to Zimbra. VII. Specifics for NotifyLink ActiveSync Solution View features and issues that are specific to the NotifyLink ActiveSync Solution. 5/8/10 Page 14 of 14

×