Symantec⢠Mobility: Suite 5.2.2 Release Notes
Transcription
Symantec⢠Mobility: Suite 5.2.2 Release Notes
Symantec™ Mobility: Suite 5.2.2 Release Notes Documentation version: Legal Notice Copyright © 2015 Symantec Corporation. All rights reserved. Symantec, the Symantec Logo, the Checkmark Logo and are trademarks or registered trademarks of Symantec Corporation or its affiliates in the U.S. and other countries. Other names may be trademarks of their respective owners. The product described in this document is distributed under licenses restricting its use, copying, distribution, and decompilation/reverse engineering. No part of this document may be reproduced in any form by any means without prior written authorization of Symantec Corporation and its licensors, if any. THE DOCUMENTATION IS PROVIDED "AS IS" AND ALL EXPRESS OR IMPLIED CONDITIONS, REPRESENTATIONS AND WARRANTIES, INCLUDING ANY IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR NON-INFRINGEMENT, ARE DISCLAIMED, EXCEPT TO THE EXTENT THAT SUCH DISCLAIMERS ARE HELD TO BE LEGALLY INVALID. SYMANTEC CORPORATION SHALL NOT BE LIABLE FOR INCIDENTAL OR CONSEQUENTIAL DAMAGES IN CONNECTION WITH THE FURNISHING, PERFORMANCE, OR USE OF THIS DOCUMENTATION. THE INFORMATION CONTAINED IN THIS DOCUMENTATION IS SUBJECT TO CHANGE WITHOUT NOTICE. Symantec Corporation 350 Ellis Street Mountain View, CA 94043 http://www.symantec.com Technical Support Symantec Technical Support maintains support centers globally. Technical Support’s primary role is to respond to specific queries about product features and functionality. The Technical Support group also creates content for our online Knowledge Base. The Technical Support group works collaboratively with the other functional areas within Symantec to answer your questions in a timely fashion. For example, the Technical Support group works with Product Engineering and Symantec Security Response to provide alerting services and virus definition updates. Symantec’s support offerings include the following: ■ A range of support options that give you the flexibility to select the right amount of service for any size organization ■ Telephone and/or Web-based support that provides rapid response and up-to-the-minute information ■ Upgrade assurance that delivers software upgrades ■ Global support purchased on a regional business hours or 24 hours a day, 7 days a week basis ■ Premium service offerings that include Account Management Services For information about Symantec’s support offerings, you can visit our website at the following URL: www.symantec.com/business/support/ All support services will be delivered in accordance with your support agreement and the then-current enterprise technical support policy. Contacting Technical Support Customers with a current support agreement may access Technical Support information at the following URL: www.symantec.com/business/support/ Before contacting Technical Support, make sure you have satisfied the system requirements that are listed in your product documentation. Also, you should be at the computer on which the problem occurred, in case it is necessary to replicate the problem. When you contact Technical Support, please have the following information available: ■ Product release level ■ Hardware information ■ Available memory, disk space, and NIC information ■ Operating system ■ Version and patch level ■ Network topology ■ Router, gateway, and IP address information ■ Problem description: ■ Error messages and log files ■ Troubleshooting that was performed before contacting Symantec ■ Recent software configuration changes and network changes Licensing and registration If your Symantec product requires registration or a license key, access our technical support Web page at the following URL: www.symantec.com/business/support/ Customer service Customer service information is available at the following URL: www.symantec.com/business/support/ Customer Service is available to assist with non-technical questions, such as the following types of issues: ■ Questions regarding product licensing or serialization ■ Product registration updates, such as address or name changes ■ General product information (features, language availability, local dealers) ■ Latest information about product updates and upgrades ■ Information about upgrade assurance and support contracts ■ Information about the Symantec Buying Programs ■ Advice about Symantec's technical support options ■ Nontechnical presales questions ■ Issues that are related to CD-ROMs, DVDs, or manuals Support agreement resources If you want to contact Symantec regarding an existing support agreement, please contact the support agreement administration team for your region as follows: Asia-Pacific and Japan [email protected] Europe, Middle-East, and Africa [email protected] North America and Latin America [email protected] About Symantec Mobility: Suite 5.2.2 This document includes the following topics: ■ What's New in Symantec Mobility: Suite 5.2.2 ■ Resolved issues for Symantec Mobility: Suite 5.2.2 ■ Performing the upgrade to Symantec Mobility: Suite 5.2.2 ■ Re-wrapping apps and rebuilding the Work Hub ■ Symantec Mobility: Suite System Requirements What's New in Symantec Mobility: Suite 5.2.2 Symantec Mobility: Suite 5.2.2 is a maintenance release to Mobility Suite 5.2. It contains the following new features and functionality: ■ Wrap support for 32-bit Android 5 Lollipop Symantec Mobility: Suite 5.2 introduced support for MDM and Norton Mobile Security functionality on 32-bit Android 5 devices. Mobility Suite 5.2.2 introduces support for wrap functionality on 32-bit Android 5 devices with an OS of 5.0.x and below. This functionality has been certified on the following devices: ■ Nexux 5, Nexus 6, Nexus 7 Note: Nexux 9 is not supported as it is a 64-bit device. ■ Samsung S5 About Symantec Mobility: Suite 5.2.2 Resolved issues for Symantec Mobility: Suite 5.2.2 Note: In addition to the certified devices listed above, Mobility Suite 5.2.2 supports wrap functionality on any Android 5 32-bit device. Note: Symantec intends to provide wrap functionality support for Android 5 64-bit devices in Mobility Suite in the near future. ■ Customized email invite reminder You can now use the customized email invite that you sent to your users as the reminder email as well. Previously, Mobility Suite sent a default email reminder that was non-customizable and appeared in English only. To do this, from Mobility Manager, select Users > Invite users > Invite users to Work Hub. Check Use same template for existing and new users. For a list of resolved issues in this release: ■ See “Resolved issues for Symantec Mobility: Suite 5.2.2” on page 7. Note: Sealed apps will not work on Android L devices until they are re-wrapped with the 5.2.2 wrap kit. For information on Symantec Sealed Program 5.2.2: ■ http://www.symantec.com/docs/DOC8248 Resolved issues for Symantec Mobility: Suite 5.2.2 Table 1-1 lists the issues resolved in Symantec Mobility: Suite 5.2.2. This table specifies whether you are required to re-wrap your apps and/or rebuild your Work Hub. Refer to the Resolution column for additional information or required actions. Table 1-1 Symantec Mobility: Suite 5.2.2 Resolved Issues Description You receive multiple email invites to enroll your device. This occurs when the email invite is sent using an email address that has different letter cases than Active Directory (e.g., [email protected] vs. [email protected]). Additional Information Rebuild Work Hub (Yes/No) Re-wrap apps (Yes/No) N N 7 About Symantec Mobility: Suite 5.2.2 Performing the upgrade to Symantec Mobility: Suite 5.2.2 Table 1-1 Symantec Mobility: Suite 5.2.2 Resolved Issues (continued) Description Additional Information Rebuild Work Hub (Yes/No) Re-wrap apps (Yes/No) The notification that you receive on your device informing you that an updated Work Hub is available may disappear prior to you performing the upgrade. N N You receive a Server error when you select any of the Settings pages in Mobility Manager from a new tenant. N N You receive a traceback if you create an app policy without a policy name and then try to save it. N N Performing the upgrade to Symantec Mobility: Suite 5.2.2 If you are a SaaS customer, you do not need to perform an upgrade. If you are an on-premise customer and are using Symantec Mobility: Suite 5.0 or higher, you can upgrade to Mobility Suite 5.2.2. You can upgrade Mobility Suite using one of the following methods: ■ Upgrade to Mobility Suite using the Installation Wizard ■ Upgrade to Symantec Mobility: Suite using the command line interface Upgrade to Mobility Suite using the Installation Wizard 1 Copy the Symantec Mobility: Suite ISO file to your RHEL/CentOS server (for example, your home directory). 2 Change to the directory containing the ISO file. 3 Mount the ISO file using the following commands as examples: mkdir /mnt/iso mount -o loop <MobilityFile>.iso /mnt/iso Note: In this example, /mnt/iso refers to the installation directory, and <MobilityFile> refers to the ISO file. 8 About Symantec Mobility: Suite 5.2.2 Performing the upgrade to Symantec Mobility: Suite 5.2.2 4 Start the upgrade: cd /mnt/iso sudo ./setup.sh After the packages are unpacked and installed, the Symantec Mobility Manager menu appears: 5 Select Upgrade Existing Installation and then click OK. The upgrade script runs to completion. A successful upgrade is indicated with the message: Upgraded successfully. Upgrade to Symantec Mobility: Suite using the command line interface 1 Copy the Symantec Mobility: Suite ISO file to your RHEL/CentOS server (for example, your home directory). 2 Change to the directory containing the ISO file. 9 About Symantec Mobility: Suite 5.2.2 Performing the upgrade to Symantec Mobility: Suite 5.2.2 3 Mount the ISO file using the following commands as examples: mkdir /mnt/iso mount -o loop <MobilityFile>.iso /mnt/iso Note: In this example, /mnt/iso refers to the installation directory, and <MobilityFile> refers to the ISO file. 4 Start the upgrade: cd /mnt/iso To perform a production upgrade: sudo ./setup.sh --upgrade This is an upgrade to your production (or "live") Mobility Suite instance. All services are restarted upon the completion of a production upgrade. To perform a staged upgrade: ./setup --staged-upgrade A staged upgrade allows you to verify the upgrade will successfully complete without acting upon your data. This mode does not start any of the Mobility Manager Suite services, nor will they start on boot. A staged upgrade may be beneficial for large enterprises that want to test an upgrade before actually enabling the software. The upgrade script runs to completion. A successful upgrade is indicated with the message: Upgraded successfully. Note: You can also use the following switches with setup.sh: setup.sh [-c CONFIG] [-i] [-u] [--installdir INSTALLDIR] [--cachedir CACHEDIR] [--logdir LOGDIR] [--configport CONFIGPORT] [--mysql] [--rabbitmq] [-d] [-v] [--ssl-cert SSL_CERT] [--ssl-key SSL_KEY] [--ssl-bundle SSL_BUNDLE] [--tool {confcheck, addrabbit, validate_bootstrap, conncheck] [-h] 10 About Symantec Mobility: Suite 5.2.2 Re-wrapping apps and rebuilding the Work Hub Re-wrapping apps and rebuilding the Work Hub Symantec Mobility: Suite 5.2.2 introduces support for wrap functionality for 32-bit Android 5 devices, which requires you to rebuild your Work Hub. Rebuilding your Work Hub updates the Work Hub to include the new wrap code associated with the Work Hub or other policy features distributed with this release. Additionally, you are required to re-wrap any apps associated with these features. Depending on the nature of the updated wrap code, you may need to re-wrap a single app, or all apps associated with one or more policies. The Resolved Issues section of this document also specifies whether you must re-wrap apps that are associated with fixes distributed with this release. See “Resolved issues for Symantec Mobility: Suite 5.2.2” on page 7. Finally, your users are required to update their devices with the new Work Hub and re-wrapped apps. After you re-wrap apps or rebuild your Work Hub, users are notified that new versions are available for download. Re-wrapping apps To re-wrap an individual app 1 In Mobility Manager, click Apps. 2 In the center pane, click the app that you want to re-wrap. 3 In the upper right corner, click the Re-wrap icon. 4 Repeat this procedure for each app that you want to re-wrap. To re-wrap multiple apps associated with an app policy 1 In Mobility Manager, click Policies > App Policies. 2 In the center pane, click the app policy that is associated with the apps you want to re-wrap. 3 In the upper right corner, click the Edit icon. 4 Click Save. 5 Repeat this procedure for each app policy that is associated with the apps that you want to re-wrap. Re-building your Anrdroid Work Hub To rebuild your Android Work Hub 1 In Mobility Manager, click Settings > Device configuration. 2 Click Build Android Work Hub. 11 About Symantec Mobility: Suite 5.2.2 Symantec Mobility: Suite System Requirements Symantec Mobility: Suite System Requirements Table 1-2 lists the system requirements for an on-premises installation of Symantec Mobility: Suite, RabbitMQ, the app and email proxies, and the platform requirements for your iOS, Android, and Windows mobile devices. Table 1-2 Symantec Mobility: Suite On-premises Installation System Requirements Symantec Mobility: Suite Requirement Processor 64-bit Memory 8 GB Virtual CPUs (Mobility Suite mandates usage of virtual machines to host on-premises installations) 2 minimum (recommended for Trial versions) Operating System Red Hat Enterprise Linux (RHEL) 6.5 or CentOS 6.5 External Databases MySQL 5.6 or Oracle 11.2 4 minimum (recommended for Production versions) ■ ■ ■ ■ Database Size MySQL for CentOS Red Hat Enterprise Linux (RHEL) or CentOS is supported as an external database with Mobility Suite. MySQL for Windows is not supported for use as an external database with Mobility Suite. Oracle for Windows or Oracle for Linux is supported for use as an external database with Mobility Suite. Oracle for Solaris is not supported for use as an external database with Mobility Suite. 20 GB minimum (recommended for Trial versions) 40 GB (recommended for Production versions) Browsers (for Mobility Manager access) Synchronization of computer clock ■ Internet Explorer 9 and higher ■ Firefox 29 and higher ■ Safari 6.2 and higher ■ Chrome 32 and higher The Mobility Suite administrator is responsible for ensuring that the clock of the server hosting the on-premises installation of the Mobility Suite tenant is synchronized with a valid ntp server. An example of such a server is pool.ntp.org 12 About Symantec Mobility: Suite 5.2.2 Symantec Mobility: Suite System Requirements Table 1-3 RabbitMQ System Requirements RabbitMQ Requirement Minimum rabbitmq-server version 3.4.3 Operating system CentOS 6.5 or Red Hat Enterprise Linux (RHEL) equivalent Processor 64-bit Memory 8 GB Storage 40 GB each server Servers At least 2 different servers in different data centers (RabbitMQ cluster) Ports 5672 Broker connection 55672 Management-agent connections between servers 15672 Management connection 4369 Erlang port 45000-45010 Cluster ports. You can extend this port range in rabbitmq.config if you have more than 3 mirroring servers Table 1-4 App Proxy Minimum System Requirements App Proxy Requirement Processor 64-bit Memory 8 GB CPU 4 cores or virtual CPUs minimum Storage 20 GB Operating System Red Hat Enterprise Linux (RHEL) 6.5 or CentOS 6.5 Table 1-5 Email Proxy Minimum System Requirements Email Proxy Requirement Processor 64-bit Memory 8 GB 13 About Symantec Mobility: Suite 5.2.2 Symantec Mobility: Suite System Requirements Table 1-5 Email Proxy Minimum System Requirements (continued) Email Proxy Requirement CPU 4 cores or virtual CPUs minimum Storage 20 GB Operating System Red Hat Enterprise Linux (RHEL) 6.5 or CentOS 6.5 Java JRE 1.7.51 or later Table 1-6 Device Mobile Platform Minimum System Requirements Mobile Platform Requirement iOS iOS 7.x, iOS 8.x (up to 8.3) Android 4.x, 5.0.x and below Note: Samsung and Nexus 32-bit devices are certified for 5.0.x and below. Note: For the latest list of certified devices and supported Mobility Manager functionality, see: http://www.symantec.com/docs/TECH228998 Windows Windows Phone 8.1 Table 1-7 On-premises Installation Required Site Connectivity Description Required site connectivity Supports Apple push notifications to devices running iOS http://feedback.push.apple.com:2195 applications. Supports Apple push notifications to devices running iOS http://gateway.push.apple.com:2196 applications. Supports Apple store pointer applications http://itunes.apple.com Supports Google Cloud Messaging (GCM) https://www.google.com Supports Android store pointer applications. https://play.google.com Support for Two-Factor-Authentication (2FA) https://login.vip.symantec.com Support for licensing (Symantec License Server) services-prod.symantec.com:443 Supports push email notifications for the Work Mail application through Secure Email Proxy. spoc-pool-gtm.norton.com 14 About Symantec Mobility: Suite 5.2.2 Symantec Mobility: Suite System Requirements Table 1-7 On-premises Installation Required Site Connectivity (continued) Description Required site connectivity Supports Norton Mobile Security https://msws.appcenterhq.com Supports Symantec Sealed applications. https://signer.appcenterhq.com/msproxy Supports Symantec Sealed applications. https://signer.appcenterhq.com 15