Access Solutions Junos Pulse MSS MSG Release 4.2R1 MSS MSG 4.2R1 (4.2.1.229) Juniper Networks, Inc. 1194 North Mathilda Avenue Sunnyvale, CA 94089 USA 408 745 2000 or 888 JUNIPER www.juniper.net January 22, 2013 Juniper Networks, Inc. 1
Contents Junos Pulse MSS MSG Release 4.2R1... 1 Pulse MSS MSG 4.2 R1 (a.k.a. Kentucky Release)... 3 Known Issues and Limitations in Pulse MSS MSG 4.2R1:... 3 Issues Resolved in Pulse MSS MSG 4.2R1 from Pulse MSS MSG 4.1:... 5 Juniper Networks, Inc. 2
Pulse MSS MSG 4.2 R1 (a.k.a. Kentucky Release) Known Issues and Limitations in Pulse MSS MSG 4.2R1: Issue: If you upgrade from MSG 4.0 to MSG 4.2, existing administrators may lose the ability to change enterprise and device profile settings. This problem does not occur when you upgrade from MSG 4.1 to MSG 4.2. (833194) Solution / workaround: All upgrades to MSG 4.2 must be performed from MSG 4.1. To upgrade from MSG 4.0, first upgrade to MSG 4.1. To upgrade from earlier versions, first upgrade to MSG 4.0. Issue: Starting the MSG may fail with the following error: (830211) Exception in thread "main" net.juniper.pulse.msg.admin.operationfailedexception: JBAS014803: Duplicate resource Solution / workaround: The MSG administrator must remove the MSGDatasource and IdentDS entries from the standalone.xml file in the /local/opt/junospulse-msg/jboss-as-7.1.1.final/standalone/ configuration directory. Issue: A device profile can be assigned to an ios device through the console and the API. (846383) Solution / workaround: It is unnecessary to assign device profiles to ios devices. Device profiles apply only to non-ios devices and are ignored if they re assigned an ios device. Issue: In the Devices tab, the Apply Device Profile function may not update a device that already has the profile. (832592) Solution / workaround: To immediately update the profile settings on a device, select the device, click Send Commands, and select the Update Profile command. Profiles also are updated during the next automatic synchronization with the gateway. Issue: When the API gateway is used to send an Application Message to a device over SMS, a FAILED status may be shown on the Command History report with the following error written to the log: (842438) WARNING - EV0052 - [152] [SMSSender] SMS0008 : Error sending message token received: 113, Max message parts exceeded Solution / Workaround: Reduce the message length by a few characters and resend the message to the device. Issue: In some cases, it may be possible to register two devices with the same phone number and credentials. (842742) Solution / Workaround: Delete one of the devices or manually correct the phone number of the appropriate device. Note that this scenario is valid for users allowed to register multiple devices using the same SIM card. Juniper Networks, Inc. 3
Issue: After a CSR for an APNS certificate is generated, the link shows No CSR generated. (833134) Solution / workaround: Refresh the page in the browser. Typically, if a connection to the MSG Control Center is established, the CSR can be downloaded within a minute of being generated. Issue: The exception Could not instantiate serializer occurs when attempting to export an enterprise. (843168) Solution / workaround: Export functionality disabled for ALL typical MSG deployment scenarios. Issue: The View Report button is displayed in the Dashboard for ios devices, but there is no Reports tab available. (815218) Solution / workaround: The Dashboard View Report button for ios devices will be hidden in a future release. Issue: SMS alerts configured on the Dashboard may generate two emails for the same alert. (773127) Solution / workaround: Disregard the duplicate emails. This issue occurs for SMS alerts only. Issue: Removing applications from the Dashboard appears to succeed, but the applications remain on the device. (752975) Solution / workaround: Applications can be uninstalled by the user or, in some cases, from the MSG Console, but not from the Dashboard. Issue: The config.xml file is not updated automatically. (800269) Solution / workaround: If the default configuration is not used, it is necessary to manually update the file at /local/opt/junospulse-msg/etc/config.xml to include new required configuration options. Issue: Errors occur if host names are used instead of IP addresses in the config.xml file. (811152) Solution / workaround: All network hosts must be specified as IP addresses in the config.xml file. Host names are not supported at this time. Note: Support of host names is planned for MSG 5.0R1. Issue: Device registration response time may increase in some environments. (805829) Solution / workaround: In virtual server environments, increased latency might be experienced. Throughput is not affected. Issue: In some cases, spaces in the MSISDN may not be removed when the device is registered, which may cause conflicts with subsequent SOAP calls to the server. (816999) Solution / workaround: Delete the device from the Console and reregister the device. Issue: After upgrade, Dashboard access fails with a phone not found error for enterprises with Monitor and Control disabled. (813366) Solution / Workaround: Users cannot access the Dashboard unless Monitor and Control is enabled for the enterprise. Juniper Networks, Inc. 4
Issue: If you use the Firefox browser, Firefox 11.0 or later is required to upload the CSR to Apple from the Enterprise Settings page. (753847) Solution / workaround: This page is served by Apple servers, and the display of the page is not determined by the MSG. Issue: In the Command History report, the Ack Status of a wipe command may be shown as false in some cases, even though the command was received and executed successfully. (843125) Solution / Workaround: In these cases, please disregard the failed status. Issue: In some cases, deleting a user does not remove the user from the Users page. (847352) Solution / Workaround: Refresh the page in the browser. Issue: The Dashboard Report may display the same message twice in the Search results or Text Messages page. Solution / Workaround: Please disregard the duplicate message. Issues Resolved in Pulse MSS MSG 4.2R1 from Pulse MSS MSG 4.1: Issue: Activemq / jboss rpm versions have to be greater than 4.1 latest branch. (814846) Solution / Workaround: Add the '--force' flag to the RPM command. Status: Will not be fixed (closed) Issue: Exporting an enterprise requires a large amount of disk space. (812306) Solution / workaround: The current implementation is intended to move an enterprise from one MSG system to another and is not optimized for a live system. Administrators should not use this to back up enterprise settings. If this feature is used, it should not be used on a live system or a system with limited free disk space. Status: Will not be fixed (closed). The export enterprise feature will be deprecated. Issue: Sometimes there is no confirmation on the Enterprise->Devices page after changing the settings and clicking Save. (798442) Solution / workaround: When the page is submitted successfully, the Save button is changed to grey/disabled. Issue: An MDM profile with no settings can be assigned in the Device settings page, but not in Device -> Apply MDM Profile. (797080) Solution / workaround: An empty MDM profile should not be assigned to a device. Juniper Networks, Inc. 5
Issue: An Enterprise is not listed or shown blank in some cases. (817770) Solution / workaround: System root users might not be able to view a Partner or Enterprise created outside the current session. Log out and log in again to view the new Partner or Enterprise. Issue: In the VPN settings of the MDM profile, the Role and Realm settings are not populated on Android devices if a certificate is selected for authentication. (800014) Solution / workaround: Certificate authentication is not supported on Android devices. The UI indicates ios only on the profile pages. Status: Fixed in MSG4.2R1 Issue: In the Security/Control section of an MDM profile, an increasing number of red exclamation points (!) are displayed if you enter an invalid value in the Passcode History and Maximum Passcode Age and click Save, and then repeat the process multiple times in succession. (808600) Solution / workaround: The first time an incorrect value is entered, a message at the top of the page displays the valid input range for the field. Issue: The device Unlock command may not work with the existing device passcode. (813029) Solution / workaround: The device may not unlock if the Lock command is sent with a blank value to reuse the existing passcode, even though the same password is sent with the Unlock command. Status: Determined to be a client issue. Issue: JBOSS server.log is filled with messages (WSS1408: UsernameToken Authentication Failed) when performing operations for a user that doesn't exist. (810397) Solution / Workaround: If an attempt is made to perform operations on a deleted user, please disregard the log entries that result for this action. Status: Expected behavior, will not be fixed. Issue: On the Dashboard Settings page under Account Management, devices without SIM cards are not listed. (816747) Solution / workaround: Use other pages to view devices without SIM cards. Issue: If you uncheck the Require passcode on device checkbox on the Security & Control tab of the Android default MDM profile, the box is automatically rechecked when you navigate to the Enterprise Settings page. (817808) Solution / workaround: There is no workaround. Uncheck Require passcode on device for the default Android profile whenever you navigate to the Enterprise Settings page. Status: Issue resolved and verified in MSG4.1R1. Issue: The getenterprisedefaultrequest in the gateway-api interface (version 2) sets the passcode to required in the default Android profile. (817808) Solution / workaround: Upgrade gateway-api to version 3. Juniper Networks, Inc. 6
Status: Issue resolved and verified in MSG4.1R1. Issue: When an MSG session reaches the timeout period it will log out only the active screen, and some pages in the background may appear to be logged in. (812379) Issue: The expiration date on the Device profile page can be set to an empty value. (813804) Status: Working as designed, will not be fixed (closed). The expiration date is not a required field. Issue: When selecting the MDM profile for a device, there is no None/Empty option, which can lead to assigning an MDM profile that will need to be removed. (800741) Status: Closed (not an issue in normal operation). Issue: When editing an MDM profile you will see what appears to be an unlabeled tab on the left side under the Tracking tab. This is just a display issue and not an unlabeled tab. (814512) Status: Closed. Juniper Networks, Inc. 7