Pointsec Mobile Smartphone (Windows Mobile) 3.2.3 Release Notes
Total Page:16
File Type:pdf, Size:1020Kb
Pointsec Mobile Smartphone (Windows Mobile) 3.2.3 Release Notes Revised: November 13, 2008 This Release Notes document provides essential operating requirements and describes known issues for Pointsec Mobile Smartphone (Windows Mobile) 3.2.3. Review this information before installing this product. Note - There may be an updated version of this document and of the other documents you received with your copy of Pointsec Mobile Smartphone (Windows Mobile). You can access the latest version at: http://www.checkpoint.com/support/ In This Document About This Document page 1 About Pointsec Mobile Smartphone (Windows Mobile) page 2 New in This Release page 2 Supported Smartphones page 2 3rd-party Software page 4 System Requirements page 4 General Recommendations page 5 Compatibility between Releases page 5 Compatibility with Other Programs page 6 Known Issues in this Release page 6 FYI page 7 Documentation Feedback page 7 About This Document This document contains information about Pointsec Mobile Smartphone (Windows Mobile) version 3.2.3, such as new features and functions in this release, what problems have been fixed since the previous release and system requirements. In this document, the abbreviation N/A is used. N/A means Not Applicable. Pointsec Mobile Smartphone (Windows Mobile) is also referred to as Pointsec Mobile or Pointsec. Releases prior to version 3.1.0 are referred to by the previous name, that is, Pointsec for Smartphone (Windows Mobile 5). Copyright © 2008 Pointsec Mobile Technologies AB, a Check Point Software Technologies company. All rights reserved 1 About Pointsec Mobile Smartphone (Windows Mobile) About Pointsec Mobile Smartphone (Windows Mobile) Pointsec Mobile provides users of Windows Mobile 5.0 and Windows Mobile 6-based devices with automatic, real-time encryption of information including Microsoft Outlook e-mail and notes - providing convenient and enforceable handheld security for enterprises on the move. New in This Release In this release, the following has been added or changed: New Operating System Supported • Windows Mobile 6.1 New Devices These Windows Mobile 6.1 devices are added in this version: • AT&T Moto Q Global (Motorola Q9h) • AT&T Pantech Duo II • AT&T Samsung Blackjack II File Transfer and Client Deployment .exe Removed Because a majority of administrators use 3rd-party device management software to deploy and manage software on devices, specific file transfer settings and the deployment executable have been removed in this release. If you are not using 3rd-party device management software to handle file transfers and software deployment, you can still perform these tasks manually. See the Pointsec Mobile Smartphone (Windows Mobile) Administrator’s Guide for instructions. File Transfer Settings Removed The following File Transfer settings have been removed from the installation profile: • Transfer files with ActiveSync • Recovery folder • Update folder Client.exe Deployment File Removed The Pointsec Mobile Smartphone (Windows Mobile) Client.exe has been removed from Pointsec Mobile. Supported Smartphones The following tables contain the devices and operating systems that are supported at the time of the release of Pointsec Mobile Smartphone (Windows Mobile) 3.2.3. However, this list is subject to change. To see a current list of supported devices, please visit http://www.checkpoint.com/supportedhandhelds/. Pointsec Mobile Smartphone (Windows Mobile) 3.2.3 Release Notes. Last Update — November 13, 2008 2 Supported Smartphones Windows Mobile 5.0 Devices • Cingular 2125 • Cingular 3125 • HTC MTeoR • HTC S310 • i-mate SP5 • i-mate SP5m • Motorola Q (Alltel, Sprint, Verizon) • Qtek 8300 • Qtek 8310 • Qtek 8500 • Samsung SGH-i600 • Samsung SGH-i607 Windows Mobile 6 Devices • AMOI SMT5700 • HP iPAQ 514 • HTC S620 • HTC S630 • HTC S710 • HTC S730 • Motorola Q9h • Palm Treo 500v • Pantech C810 • Samsung SGH-i320 • Samsung SGH-i617 • Vodafone 1210 Windows Mobile 6.1 Devices • AT&T Moto Q Global (Motorola Q9h) • AT&T Pantech Duo II • AT&T Samsung Blackjack II Note that we always recommend that you upgrade to the latest ROM available from your phone manufacturer. Pointsec Mobile Smartphone (Windows Mobile) 3.2.3 Release Notes. Last Update — November 13, 2008 3 3rd-party Software 3rd-party Software Pointsec Mobile Smartphone (Windows Mobile) 3.2.3 is interoperable with the following 3rd-party products: • Active Sync 4.5 • Mformation DM 5.2.1.3 • Symantec AV 5.5 • Trend Micro AV 3.0 System Requirements Disk and Memory Space Table 1 Disk and Memory Space Component Space Administrator’s workstation 10 MB for Pointsec Mobile Device Approximately 1 MB of free storage memory for Pointsec Mobile. Removable Media (Memory Approximately 1 MB of free space to allow for encryption of data on Card) removable media. Note: Removable media can become corrupt if you attempt to encrypt it when it is full. Operating Systems and Software Table 2 Operating Systems and Software Component Operating system and software Administrator’s PC • Microsoft Windows 2000 Professional, XP Professional, and Vista • Pointsec Administration Console 1.1.1 or later. For requirements regarding Pointsec Administration Console, please see the Pointsec Administration Console Release Notes. • For 2000 and XP: Microsoft ActiveSync software 4.2 or later. • For Vista: Microsoft Windows Mobile Device Center. Client PC • Microsoft Windows 2000 Professional, XP Professional, and Vista • For 2000 and XP: Microsoft ActiveSync software 4.2 or later. • For Vista: Microsoft Windows Mobile Device Center. webRH server • For requirements on the webRH server, see the documentation accompanying SmartCenter for Pointsec—webRH Device • Windows Mobile 5.0, Windows Mobile 6 Classic, and Windows Mobile 6 Professional • Check your hardware vendor’s web site for the latest end-user updates. Account Permissions Required Table 3 Account Permissions Required Account Rights required for folder User Write, read and execute rights to the recovery folder Pointsec Mobile Smartphone (Windows Mobile) 3.2.3 Release Notes. Last Update — November 13, 2008 4 General Recommendations General Recommendations We strongly recommend that you: • Always follow the documented procedures for installing, removing and upgrading Pointsec Administration Console and Pointsec Mobile • When upgrading Pointsec Mobile software on phones, always upgrade to the latest version of Pointsec Administration Console. • Do not attempt to access removable media when installing, removing or upgrading Pointsec Mobile • Always back up data on phones and removable media before installing, removing or upgrading Pointsec Mobile • When installing, removing or upgrading Pointsec Mobile, ensure that the device is • on external power • not configured to power off if unused. • On Pointsec Mobile-protected phones, do not rename or move files used by Pointsec Mobile • When saving installation sets or update profiles on the network, you must mount the drive first • Do not attempt to encrypt full removable media. See the section “Disk and Memory Space” for more information. About Wireless Communication You should be aware that on a device that has wireless communication activated, it may be possible for unauthorized persons to use the wireless communication to access files on the device Compatibility between Releases Upgrading the Module in Pointsec Administration Console • Pointsec Mobile Smartphone (Windows Mobile) version 3.1.0 and later can co-exist on the Pointsec Administration Console with Pointsec for Smartphone (Windows Mobile 5) version 3.0.3 and earlier. However, because these two applications are separate products, you cannot upgrade the module in Pointsec Administration Console from Pointsec for Smartphone (Windows Mobile 5) to Pointsec Mobile Smartphone (Windows Mobile). Upgrading Pointsec Mobile Smartphone on Devices • It is not possible to upgrade to Pointsec for Smartphone 3.0 or later from a version earlier than 3.0. This is because Pointsec for Smartphone 3.0 and later is developed for devices running a different operating system than previously (Windows Mobile 5.0 and Windows Mobile 6 Standard). • When upgrading the software on devices from 3.0.0 to version 3.2.3, you will need to deploy an update profile (.ppp) along with the .cab file on the device. This is not necessary when upgrading from version 3.0.1 or later. Pointsec Mobile Smartphone (Windows Mobile) 3.2.3 Release Notes. Last Update — November 13, 2008 5 Compatibility with Other Programs Compatibility with Other Programs • When synchronizing large amounts of PIM data from computer to device, we suggest that you perform the initial synchronization before installing Pointsec Mobile. Otherwise, the device may become unresponsive. This is due to CPU limitations when Pointsec Mobile is encrypting large amounts of data. Known Issues in this Release The following are known issues in this release: Table 4 Known Issues in this release ID Short description Description 454974 Pantech Duo II (WM6.1): If you remove the removable media from the device while Removable media decryption Pointsec Mobile is decrypting it, then re-insert it and fails if interrupted and resumed restart decryption, the error message “Decryption of removable media did not complete successfully” appears, and some files on the removable media may remain encrypted. Note: Interrupting the removable media encryption or decryption process in any way can result in corrupted files. For more information, see the section Removable Media in the chapter Pointsec Mobile for Users in the Pointsec Mobile Smartphone (Windows Mobile) Administrator’s Guide. 452182 Pointsec creates a corrupt If the removable media (memory card) is full, Pointsec media key file during creates a corrupt media key file (Pointsec Media encryption if memory card is Encryption.prk) upon initial memory card encryption. full The user will not be able to authenticate to the card, nor will he notice that the card is not encrypted. The corrupt .prk file causes the card to fail when used in a smartphone or with Pointsec Mobile Encryption. Note that the data on the card is not corrupted by this issue. Workaround: Use a PC to delete the 0 KB .prk file and free up at least 1 MB of space on the card.