Release Notes McAfee® Enterprise Mobility Management emmBundle_11.0.4.101.zip

Transcription

Release Notes McAfee® Enterprise Mobility Management emmBundle_11.0.4.101.zip
Release Notes
McAfee® Enterprise Mobility Management
emmBundle_11.0.4.101.zip







About this document
About this release
Bug fixes and Enhancements
Installation instructions
Troubleshooting Installation Issues
Known issues
Finding product documentation
About this document
Thank you for choosing this McAfee® product. This document contains important information
about the current release. We strongly recommend that you read the entire document.
About this release
Release date
11 November 2014
emmBundle_11.0.4.101.zip, containing:
Files included

EMM Extension 11.0.4.101

MePO 1.1.2.103

Help 1100.006
Developed for
use with
EMM 11.0.x
Urgency rating
Recommended – Recommended for all environments. Apply this update at the
earliest convenience.
Bug fixes and Enhancements
This section provides a description of the fixes and enhancements included in this bundle.
Bundle 11.0.4.101
Bug fixes (EMM Extension)


Bug 956796 – Adding iOS version in policy does not work when ePO is in German.
Bug 975168 – User who gets locked out from EMM Portal is unable to be unlocked from
ePO Console.
1
Bug fixes (MePO)

Bug 987139 – [MePO] Mepo Extension Upgrade failed (from 1.0 to 1.1.1).
Bundle Extension upgrade failed with error: The ALTER TABLE statement conflicted
with the FOREIGN KEY constraint
"FK_MWQWorkProcessedID_WorkProcessed_Cascade". The conflict occurred in
database "ePO_xxxxxx", table "dbo.MepoWorkProcessed", column 'ID'.

Bug 987794 – [MePO] MepoWorkQueue contains large amounts of data due to
MepoConfig set to collect data for default value of 5 days.
Changed the default collection interval unit from days to hours. The default collection
interval is 5 hours after applying this patch.

Bug 987987 – [MePO] Mepo does not process requests after successful upgrade, if
upgraded without successfully completing the MePOWorkQueueCleanup script.
Error in EMM Hub log - EMM.Hub.PropertiesToEpoSender
Failed to SendDeviceToePO for device ApplDN6GRTGZDFJ3 with status Error
and message ProcessWorkQueue: Failed, AgentGUID=ecf9ebd4-b7c9-4cb1-3badfd00b76e4831 API=SendDeviceToePO Windows API Error Code = 0x80040e07
Error in Mobile_epo.log - ProcessWorkQueue: Failed, AgentGUID=807db791-ddc9-06e31458-0ab8d51e9767
API=SendDeviceToePO
Windows API Error Code = 0x80040e07
Bundle 11.0.3.103.1
Bug fixes (MePO)

Bug 955763 – Due to a timing issue in a stored procedure, the “MepoWorkQueue” table
in the ePO database may grow unbounded. This issue has been resolved and the
cleanup stored procedure called SP_MepoPurge has been modified to prevent the issue
from happening in the future.
Bundle 11.0.3.103
Bug fixes

BZ#936351 – [EMM Extension] iOS devices with hundreds of apps failed to update
properties and showed as non-compliant
Error in the Server Log: “ePOData_Connection.cpp(xxx): COM Error 0x80040E57”
and “ePOData_ProductProperty.cpp(xxx): COM Error 0x80040E57”
Enhancements

BZ#929381 – [Mobile ePO] Added the request and response logging for MePO

BZ#943293 – [Mobile ePO] Added the timestamp prefix to MePO Request/Response
log files and Debug folder creation if it doesn't exist already
2
Bundle 11.0.2.105
Enhancement

B-79105 – [EMM Extension] Users can be granted permission to view and unlock
mobile device users (who are locked due to exceeding allowed attempts at entering
credentials) whereas ePO Global Administrator permission was previously
required. The Unlock user permission has been added to the Mobile Actions
permission group. Any user who is part of a Permission Set with the Mobile
Actions | Unlock user set to “Allow unlocking users” can unlock a user.
Bundle 11.0.1.103

Corrected a build issue which caused the EMM Extension installation to fail in some
cases (BZ#913977) which, in turn, prevented installation of the fix for BZ#892987.
Bundle 11.0.0.282
Bug fixes

BZ#892338 – [Mobile ePO] Application list containing Japanese characters did not
display correctly

BZ#888079 – [Mobile ePO] iOS devices with certain Japanese characters in the name
failed to fully provision

BZ#883147 – [Mobile ePO] Certain German words did not display correctly

BZ#877285 – [Mobile ePO] Operating under heavy load sometimes resulted in
SendDeviceToePO errors in the EMM Hub event viewer

BZ#901976 – [Mobile ePO] Devices failed to provision or receive policy updates in a rare
circumstance when an unexpected database entry existed

BZ#892987 – [EMM Extension] The string “User Uninstalled” on the Device Status page
was incorrectly localized in Japanese
Enhancement

BZ#842934 – [Mobile ePO] Improved performance (decreased processing time)
Installation instructions
Before you begin
 You must have EMM 11.0.X installed.

Cleanup Script:
o
If replacing the bundle in a system where EMM is already installed: A
cleanup script must be run prior to installing the bundle. Execute the MePO
cleanup script according to instructions provided in KB81907. The MePO
1.1.2.103 component included in this bundle may not install successfully if the
script is not run. This script may take hours to complete if a large amount of
3
data needs to be cleaned up. So, please plan your installation accordingly. If the
script is terminated for any reason except successful completion, please reexecute the script until it successfully completes before proceeding with bundle
installation. Proceed with installation as soon as the script is successful.
o
If installing EMM for the first time: The MePO cleanup script does not need to
be run.
Installation
To install (replace) the emmBundle_11.0.4.101.zip in an already-installed EMM system:
1. Follow the Cleanup Script instructions the Before you begin section if not already
done.
2. Ensure that the emmBundle_11.0.4.101.zip extension file is in an accessible
location on the network.
3. In ePO, click Menu | Software | Extensions | Install Extension.
The Install Extension dialog box appears.
4. Browse to and select emmBundle_11.0.4.101.zip, then click OK.
5. An Install Package confirmation screen displays. Click OK.
Verifying Installation

You can verify that this bundle installed correctly by confirming the version numbers are
correct.

In ePO, from Menu | Software | Extensions | Server, see the McAfee Mobile ePO
version displayed as 1.1.2.103.

In ePO, from Menu | Software | Extensions | Mobile, see the McAfee Enterprise
Mobility Management version displayed as 11.0.4.101.
Troubleshooting Installation Issues
Common issues encountered during/after installation

None.
Known issues
For a list of known issues in this product release, see this McAfee KnowledgeBase article:

KB83338.
Finding product documentation

McAfee provides the information you need during each phase of product implementation,
from installation to daily use and troubleshooting. After a product is released,
information about the product is entered into the McAfee online KnowledgeBase.
1
Go to the McAfee Technical Support ServicePortal at http://mysupport.mcafee.com.
2
Under Self Service, access the information you need:
4
To access...
Do this...
User
documentation
1 Click Product Documentation.
2 Select a Product, then select a version.
3 Select a product document.
KnowledgeBase

Click Search the KnowledgeBase for answers to your product questions.

Click Browse the KnowledgeBase for articles listed by product and version.
COPYRIGHT
Copyright © 2014 McAfee, Inc. All Rights Reserved.
No part of this publication may be reproduced, transmitted, transcribed, stored in a retrieval system, or translated into any
language in any form or by any means without the written permission of McAfee, Inc., or its suppliers or affiliate companies.
TRADEMARK ATTRIBUTIONS
AVERT, EPO, EPOLICY ORCHESTRATOR, FOUNDSTONE, GROUPSHIELD, INTRUSHIELD, LINUXSHIELD, MAX (MCAFEE
SECURITYALLIANCE EXCHANGE), MCAFEE, NETSHIELD, PORTALSHIELD, PREVENTSYS, SECURITYALLIANCE, SITEADVISOR, TOTAL
PROTECTION, VIRUSSCAN, WEBSHIELD are registered trademarks or trademarks of McAfee, Inc. and/or its affiliates in the US
and/or other countries. McAfee Red in connection with security is distinctive of McAfee brand products. All other registered and
unregistered trademarks herein are the sole property of their respective owners.
LICENSE INFORMATION
License Agreement
NOTICE TO ALL USERS: CAREFULLY READ THE APPROPRIATE LEGAL AGREEMENT CORRESPONDING TO THE LICENSE YOU
PURCHASED, WHICH SETS FORTH THE GENERAL TERMS AND CONDITIONS FOR THE USE OF THE LICENSED SOFTWARE. IF YOU
DO NOT KNOW WHICH TYPE OF LICENSE YOU HAVE ACQUIRED, PLEASE CONSULT THE SALES AND OTHER RELATED LICENSE
GRANT OR PURCHASE ORDER DOCUMENTS THAT ACCOMPANY YOUR SOFTWARE PACKAGING OR THAT YOU HAVE RECEIVED
SEPARATELY AS PART OF THE PURCHASE (AS A BOOKLET, A FILE ON THE PRODUCT CD, OR A FILE AVAILABLE ON THE WEBSITE
FROM WHICH YOU DOWNLOADED THE SOFTWARE PACKAGE). IF YOU DO NOT AGREE TO ALL OF THE TERMS SET FORTH IN THE
AGREEMENT, DO NOT INSTALL THE SOFTWARE. IF APPLICABLE, YOU MAY RETURN THE PRODUCT TO MCAFEE OR THE PLACE OF
PURCHASE FOR A FULL REFUND.
5