Core 11.5.0.0 Release and Upgrade Notes - Product ...
41
Core and Connector 11.4.0.0 – 11.5.0.0 Release and Upgrade Notes Revised: February 14, 2022 For complete product documentation, see: Ivanti Documentation Home Page Copyright © 2022, Ivanti. All rights reserved. Privacy and Legal
-
Upload
khangminh22 -
Category
Documents
-
view
0 -
download
0
Transcript of Core 11.5.0.0 Release and Upgrade Notes - Product ...
Core and Connector 11.4.0.0 – 11.5.0.0 Releaseand Upgrade NotesRevised: February 14, 2022
For complete product documentation, see:Ivanti Documentation Home Page
Copyright © 2022, Ivanti. All rights reserved.Privacy and Legal
Revision historyFor the complete revision history, see the online version of this document.
Copyright © 2022, Ivanti. All Rights Reserved. Privacy and Legal.
Page 2 of 41
Revision history
ContentsRevision history 2About Core 4Before you upgrade 4
New features summary 6General features 6Android Features 9iOS Features 12Windows features 13Related information from previous releases 13Mobile Threat Defense features 13
Support and compatibility 15Supported browsers 21Supported browser resolutions 21Related information from previous releases 22Support Policy 22
Supported languages 23Language support on Android and Android Enterprise devices 24Language support on iOS devices and macOS devices (legacy features) 24Language support on Windows devices (legacy features) 24
Resolved issues 25Related information from previous releases 27
Known issues 28Related information from previous releases 29
Limitations 30Related information from previous releases 30
Core upgrade information 31Core upgrade readiness checklists 31Upgrade considerations 33Check disk space availability 35Core upgrade paths 36Related information from previous releases 37Core upgrade URL 37Backing up Core 37
Enterprise Connector upgrade information 38About Enterprise Connector upgrade 38Enterprise Connector upgrade paths 38Enterprise Connector upgrade URL 39
Documentation resources 40Core documentation 40
Copyright © 2022, Ivanti. All Rights Reserved. Privacy and Legal.
Page 3 of 41
Revision history
About CoreCore is a mobile management software engine that enables IT to set policies for mobile devices,applications, and content. This product enables Mobile Device Management, Mobile ApplicationManagement, and Mobile Content Management capabilities.
Before you upgradeBefore you upgrade, you must consider the possible impact of certain security enhancements on yourenvironment.
Understand the impact of TLS protocol changes
For heightened security, when you upgrade to Core 10.3.0.0 or supported newer versions, Core'sconfigurations for incoming and outgoing SSL connections are automatically updated to use only protocolTLSv1.2. TLSv1.2 cannot be disabled.
This change occurs regardless of the protocol settings before the upgrade.
This change means that Core now uses only TLSv1.2 for incoming and outgoing connections with allexternal servers. Examples of external servers to which Core makes outgoing connections are:
l Standalone Sentryl Integrated Sentryl Connectorl SCEP serversl LDAP serversl Core Gatewayl Apple Push Notification Service (APNS)l Content Delivery Network serversl Core support server (support.ivanti.com)l Outbound proxy for Gateway transactions and system updatesl SMTPS servers
Copyright © 2022, Ivanti. All Rights Reserved. Privacy and Legal.
Page 4 of 41
l Public app stores (Apple, Google, Windows)l Apple Volume Purchase Program (VPP) serversl Apple Device Enrollment Program (DEP) serversl Android for Work servers
Therefore, if an external server is not configured to use TLSv1.2, change the external server touse TLSv1.2.
To determine TLS protocol usage with external servers:
l For outgoing connections from Core to external servers, use the Ivanti utility explained in thefollowing article to determine the TLS protocol usage with those servers:https://forums.ivanti.com/s/article/Core-10-2-upgrade-disables-TLS-1-0-and-TLS-1-1-by-default-9256
l For incoming connections to Core from external servers, determine each server's TLSprotocol usage (no Core utility is available).
For more information:
l Threat Advisory: Notice of Deprecation of TLS 1.0 and 1.1 on MobileIron Systems
l "Advanced: Incoming SSL Configuration" and "Advanced: Outgoing SSL Configuration" in theCore System Manager Guide.
Copyright © 2022, Ivanti. All Rights Reserved. Privacy and Legal.
Page 5 of 41
About Core
New features summaryThe following new features and enhancements are available in this release.
General featuresl Online release notes now include previous releases: With this release, online release notes willbecome cumulative, and you will be able to see releases back at least one current and one prior baserelease. For example, the online Core 11.5.0.0 release notes include release information from Core11.5.0.0, 11.4.1.0, and 11.4.0.0. PDF release notes will continue to include only the current releasedetails, with links to the earlier information online.
l New verification of TLS server certificates: Transport Layer Security (TLS) server certificates usedto secure Core systems require Certificate Revocation List (CRL) Distribution Point (DP) extensions.Online Certificate Status Protocol (OCSP), is not supported at this time. Previously, an Administratorcould upload a TLS certificate that Core does not support. With this release, Core validates that a TLSserver certificate includes a CRL DP extension in four actions: activation of the certificate in SystemManager, activation of the mutual authentication feature, inclusion in a certificate pinning policy,and inclusion in a certificate pinning request. A TLS server certificate that doesn't pass these fourvalidation checks will generate a message, explaining the error.
l Support for bridging old and new client mutual authentication CA certificates: Previously,updating a Certificate Authority (CA) certificate for client mutual authentication required re-registering all devices currently enrolled under that certification. With this release, you can:o Upload and select a new client mutual authentication certificate for devices going forwardo Retire the previous certificate, while still allow existing devices to check in.For more information, see Mutual authentication between devices and Core in the Core DeviceManagement Guide for your operating system.
l Core support for Splunk Heavy Forwarder mutual authentication: With this release, Coresupports the Splunk Heavy Forwarder for secure mutual authentication to Splunk. The feature isenabled from the System Manager Settings > Data Export > Splunk Indexer page, where you canadd, modify, delete and view your Splunk indexer information. For full information, see Data export:Splunk in the Core System Manager Guide.
Copyright © 2022, Ivanti. All Rights Reserved. Privacy and Legal.
Page 6 of 41
l Updated Splunk Forwarder supports Splunk Enterprise Server 8.x: The Splunk Forwarder inCore now supports Splunk Enterprise Server 8.x. For more Splunk information, see the CoreSystem Manager Guide.
l New option to enforce only one Local User: In high-security environments, it is a best practiceto allow only one Local User to be enabled. Once installation is complete, use the CLISHlimitUser command in the Configuration Wizard to limit the number of Local Users to one (thisfeature has no effect on the number of LDAP users). Once installed, you will need help fromIvanti customer support to change this configuration. Attempts to create another Local Userfrom the Core Devices & Users > Security > Local Users menu generates an error messageexplaining the prohibition. In high availability (HA) environments, a reboot is required after afailover to re-enable the restriction. For more information, see Managing local users in theAdmin Portal in Getting Started with Core.
l Support for mutual authentication between Core and Sentry: Core and Standalone Sentrynow support mutual authentication by default. Minimum version requirements are:o Core - 11.5.0.0 and newer versionso Standalone Sentry - 9.15.0 and newer versionsCore will only initiate mutual authentication if Sentry is running 9.15.0 or newer software.
l Registration passcode expiry time now configurable: Previously, when registration invitationswere sent, a registration PIN number was generated that was good for five days (120 hours).With this release, you can customize the number of hours the registration password is valid, from4 hours (the default) to a maximum of 72 hours. For more information, see Setting passcode andregistration code defaults in Getting Started with Core.
l Core support for Apache Log4J logging utility version 2.17.1: In this release, Core supportfor Log4J logging utility has been upgraded to 2.17.1, to avoid any possibility of a zero-dayvulnerability in earlier versions. This update should not affect your system behavior.
l More context for some audit logs: Previously, audit logs only included information about whatwas changed. With this release, some logs (configurations, policies, labels, compliance groups,rules and actions) will also include the "before" values as well as the "after." You can view the logsfrom the Core Logs > Audit Logs page. Logs with before and after values display an icon youcan click to see the new information. The new log information is generated for the followingactions:o Create - the "Before" column will be empty.o Edit or change - Both before and after values display.o Delete - The "After" column will be empty.
Copyright © 2022, Ivanti. All Rights Reserved. Privacy and Legal.
Page 7 of 41
New features summary
For more information, see Audit log information in the Core Device Management Guide for yourOS.
l Core installation on Hyper-V 2016 server is supported: With this release, Core can beinstalled on a Microsoft Hyper-V 2016 server. The Hyper-V 2016 includes Windows Hypervisor, aWindows server driver model, and virtualization components. Hyper-V is delivered as part ofMicrosoft Windows Server 2016. For more Hyper-V information, see Virtual Core requirements inthe On-Premise Installation Guide for Core and Enterprise Connector
l New customization options for the self-service user portal (SSP): Three new customizationoptions are available in this release:
o Hide or display the QR code and registration URL: A new configuration check box hasbeen added to the Settings > System Settings > Users & Devices > Device Registrationpage that allows you to choose whether or not to show users a QR code and registration URL.This option is enabled by default. When deselected, the QR code and registration URL do notdisplay to users.
o Hide or display the self-service portal (SSP) Activity page: A new configuration check boxhas been added to the Settings > System Settings > General > Self-Service Portal pagethat allows you to choose whether or not to show users their activity in the SSP. This option isenabled by default. When deselected, the SSP Activity page does not display to users.
o Hide or display the Settings option: Previously, the Settings option was always visible toclient users from the SSP Action menu (upper-right, under user name). In this release, theadministrator has the option to remove the Settings link from the SSP Action menu. Two newcheck boxes are available from the Core General > Self-Service Portal > Self-ServicePortal page:o Show settings for local users - Deselecting this option disables the Settings menu forlocal users.
o Show settings for LDAP users - Deselecting this option disables the Settings menu forLDAP users.
These settings determine whether or not clients can see the Settings option in the SSPAction menu.
For more information, see Disabling options in the SSP in the Core Device Management Guidefor your operating system.
Copyright © 2022, Ivanti. All Rights Reserved. Privacy and Legal.
Page 8 of 41
New features summary
Android Featuresl New lockdown options for Android devices using Android Enterprise: In this release, youhave new lockdown options for Android Enterprise devices.
Android Enterprise Mode Lockdown options
Device Owner orWork Profile onCompany-owned devices
Allow location settings modification – If selected, users canmodify the location settings of the managed device. This optionis available in the Lockdown Policy > Android > Manageddevice > Device Restriction section.
Allow date and time modification – If selected, users canmodify the time or date of the managed device. This option isavailable from the Lockdown Policy > Android > Manageddevice > Device restrictions section.
Work Profile and WorkProfile on Company-owned devices
Allow back-up service – If selected, users can enable or accessthe back-up files on the managed profile. This option isavailable from the Lockdown Policy > Android > WorkProfile > Android 8+ section.
Work Profile onCompany-owned devices
Manage personal apps for Work Profile on Company-owned Android devices: Previously, company-owned devicesusing Work Profile had no app management options for thepersonal side of their device. The user had full freedom to installany app on their Personal Profile. This freedom may not alwaysmeet organizational guidelines for a corporate-owned asset.With this release, administrators can now control the apps auser is allowed to install in the Personal Profile of their manageddevice (for devices running Android 11.0 and above). The newoptions are available from the Core Policies & Configs >Policies > Lockdown policy > Android Enterprise section:
Enable app control on Personal Profile – When enabled, youcan select your level of app management:o Allowed Apps – Only allow apps that are explicitly addedto this list. No other apps can be installed.
TABLE 1. NEW LOCKDOWN POLICY OPTIONS IN 11.5.0.0
Copyright © 2022, Ivanti. All Rights Reserved. Privacy and Legal.
Page 9 of 41
New features summary
o Disallowed Apps – Allow all except these specific apps frombeing installed. Choosing an option displays the Packagestable, where you can add, delete, and save the app packageson your list.
TABLE 1. NEW LOCKDOWN POLICY OPTIONS IN 11.5.0.0 (CONT.)
You can view your selections from the Core Devices & Users > Devices > View logs ondevices > Policies tab. For more information on Lockdown policies, see Lockdown policies intheGetting Started with Core guide.
l New Security policy options for Android managed devices: In this release, you have newSecurity policy options for Android Enterprise devices.
Android EnterpriseMode
Security option
Device Owner orWork Profile onCompany-owneddevices
Enable Security Logging on Android - When enabled,information is collected for security auditing purposes. These helpadmins identify suspicious activity by remotely tracking deviceactivity, including app launches, Android Debug Bridge (adb)activity, and screen unlocks. These logs become available toadministrators on demand. To protect the privacy of the user,some information (such as personal app launch events) arehidden, or redacted (for example, details of the physical volumemount events).
For all AndroidEnterprise devices
Enable Network Logging on Android - When enabled, networkand connectivity information is collected. Network logging can beused to troubleshoot any issues with device connectivity for workapps and can be used for historical forensics. Once enabled, Coreallows administrators to collect the logs on demand. Network logscontain DNS lookup and connect() library call events. These libraryfunctions are recorded while network logging is active:o getaddrinfo()o gethostbyname()o connect()
TABLE 2. NEW SECURITY POLICY OPTIONS IN 11.5.0.0
Copyright © 2022, Ivanti. All Rights Reserved. Privacy and Legal.
Page 10 of 41
New features summary
When network logging is enabled for Work Profiledevices, the network logs will only include work profilenetwork activity, not activity on the personal profile.
TABLE 2. NEW SECURITY POLICY OPTIONS IN 11.5.0.0 (CONT.)
You can view your selections from the Core Devices & Users > Devices > View logs ondevices > Policies tab. For more information on these policies, see Security Policies inGettingStarted with Core.
l Full device passcode attributes: For Android 12 devices in Work Profile mode, complexpassword type and password length are not supported. As a result, they are reported in Core as"Unsupported." For more information, see Security policies in Getting Started with Core.
l Always-On VPN for AOSP for Android Enterprise devices: In AOSP mode, you can haveAlways-On VPN status for devices using Android 10 and later supported versions. For moreinformation, see Managing the closed network / AOSP devices in the Core Device ManagementGuide for Android and Android Enterprise Devices.
l Android 7+ Inventory MAC address: To preserve device user privacy, on Android 7+ devices,Core accepts a randomized MAC address for inventory purposes and now also collects truephysical MAC address for inventory. Inventory MAC is the hardware-based MAC that is reportedafter a device is registered and is only available for company-owned modes, namely DeviceOwner mode and Work Profile on Company Owned Device mode. Inventory MAC support is alsoavailable via substitution variables. For more information, see Inventory MAC address in the CoreDevice Management Guide for Android and Android Enterprise Devices.
l Corporate wallpaper for Android devices: This new feature for corporate owned Androiddevices allows the administrator the option of distributing an image as wallpaper and as a Lockscreen image. The image will automatically be applied to the device. This feature is onlysupported in Work Managed Device mode. For more information see Setting wallpapers fordevices in the Core Device Management Guide for Android and Android Enterprise Devices.
Copyright © 2022, Ivanti. All Rights Reserved. Privacy and Legal.
Page 11 of 41
New features summary
iOS Featuresl OS Software update command removed from menu: Administrators will now only be able toset OS Software updates through a policy. In Devices & Users > Devices page, the Actionsmenu item has had the following options removed: 'iOS Software Update" and "macOS SoftwareUpdate." This applies to iOS and macOS devices. See Configuring iOS and macOS softwareupdates in the Core Device Management Guide for iOS and macOS Devices.
l Software update recommendation cadence: Administrators can set a user's device to allow allavailable, the highest available, or the lowest available OS software update. Applicable toiOS 14.5 or later and iPadOS 14.5 or later. For more information, see Software updaterecommendation cadence in the Core Device Management Guide for iOS and macOS Devices.
l macOS registration configurations disabled upon upgrade: For new MobileIron Coredeployments, Ivanti’s support for macOS device management has been transitioned to IvantiEPM and MobileIron Cloud.
l Dynamic Privacy Policy presentation:When a device user is registering their device via iReg orwith in-app registration, the privacy policy will display. The privacy policy is dynamic, based onthe enrollment type. This feature is only applicable to iOS devices. For more information, see theMobile@Work 12.11.50 for iOS Release Notes.
l Account-driven Apple User Enrollment: User Enrollment can now be set up so device userscan self-enroll in MDM User Enrollment from the Settings page on their device. This feature usesthe device user's managed Apple ID, making their devices managed. Once enrolled,administrators can view information in the Apple User Enrolled Device field in the Device Detailspage. There is required action that must be taken by the device users. See Account-driven AppleUser Enrollment in the Core Device Management Guide for iOS and macOS Devices.
l Changes to User Enrollment: The following configurations and policies are no longerapplicable to User Enrollment.o Configurations > System > Multi-User Secure Sign-Ino Configurations > Apple > iOS / tvOS > Managed Domainso Configurations > Apple > iOS / tvOS > Encrypted DNSo Configurations > Apple > iOS / tvOS > Network Usage Ruleso Configurations > VPN > all VPN configurationso Policies > iOS > iOS Only > Single-App Modeo Policies > iOS > iOS Only > Global HTTP Proxyo Policies > iOS > iOS Only > Cellular
Copyright © 2022, Ivanti. All Rights Reserved. Privacy and Legal.
Page 12 of 41
New features summary
o Policies > iOS > iOS Only > Home Screen Layouto Policies > iOS > iOS Only > Notification SettingsIvanti recommends administrators to update their labels associated to the above configurationsand policies to "Apple User Enrolled Device" + "Equals" + "True" or iOS.apple_user_enrolled_device=true. For more information, see Configurations page, Managing Policies, and VPNsettings overview in the Core Device Management Guide for iOS and macOS Devices.
The new Apple User Enrollment registration flow for LDAP Users/Groups must use single inviteor bulk invite registration to verify that managed Apple ID was generated correctly. Theadministrator should also check the logs for any managed Apple ID failures. If the existingregistration process is already using PINs, the registration will still work. For more information,see User Enrollment with Apple Business Manager in the Core Device Management Guide foriOS and macOS Devices.
l New iOS 15 Restrictions: There are three new restrictions for iOS 15:o Force Translation Processing Only on Deviceo Require Managed Pasteboardso Allow Cloud Private RelayFor more information, see iOS and tvOS restrictions settings in the Core Device ManagementGuide for iOS and macOS Devices.
Windows featuresl Windows registration configurations disabled upon upgrade: For new MobileIron Coredeployments, Ivanti’s support for Windows device management has been transitioned to IvantiEPM and MobileIron Cloud.
Related information from previous releasesIf a release does not appear in this section, then there were no associated new features andenhancements.
l Core 11.4.0.0 - New features summary
Mobile Threat Defense featuresMobile Threat Defense (MTD) protects managed devices from mobile threats and vulnerabilitiesaffecting device, network, and applications. For information on MTD-related features, as applicable forthe current release, see theMobile Threat Defense Solution Guide for your platform, available under theMOBILE THREAT DEFENSE section on the Ivanti Product Documentation page.
Copyright © 2022, Ivanti. All Rights Reserved. Privacy and Legal.
Page 13 of 41
New features summary
Each version of the MTD guide contains all Mobile Threat Defense features that are currentlyfully tested and available for use on both server and client environments. Because of the gapbetween server and client releases, new versions of the MTD guide are made available with thefinal release in the series when the features are fully functional.
Copyright © 2022, Ivanti. All Rights Reserved. Privacy and Legal.
Page 14 of 41
New features summary
Support and compatibilityThis version of Core is supported and compatible with the following product versions:
SAML / Identity Provider
Product /Component
Supported Compatible
SAML /Identity Provider
l OpenSAML 3.3.0l ADFSl Oktal Ping Identityl OneLogin
l Shibboleth
TABLE 3. SAML / IDENTITY PROVIDER SUPPORTED AND COMPATIBLE PRODUCTS AND COMPONENTS
LDAP
Product /Component
Supported Compatible
LDAP Windows Active Directory
l Server OS: Windows Server 2012R2, Version 6.3l Server OS: Windows Server 2016
IBM Domino ServerServer OS: Windows Server 2008, Version: 8.5.2
Windows ActiveDirectory
l Server OS:Windows Server2003, Version: 5.2
l Server OS:Windows Server2008, Version: 6.1
TABLE 4. LDAP SUPPORTED AND COMPATIBLE PRODUCTS AND COMPONENTS
Copyright © 2022, Ivanti. All Rights Reserved. Privacy and Legal.
Page 15 of 41
Hardware appliances
Product /Component
Supported Compatible
Hardwareappliances
l M2200 (Core and Enterprise Connector)l M2250 (Core)l M2600 (Core)l M2700 (Core)
Not applicable
TABLE 5. HARDWARE APPLIANCES SUPPORTED AND COMPATIBLE PRODUCTS AND COMPONENTS
Reporting database
Product / Component Supported Compatible
Reporting Database 2.1.0.0 1.9.1.0, 2.0.0.0, 2.0.0.1, 2.0.0.2
TABLE 6. REPORTING DATABASE SUPPORTED AND COMPATIBLE PRODUCTS AND COMPONENTS
Monitor
Product / Component Supported Compatible
Monitor 2.1.0.0 1.2.1.0, 2.0.0.0, 2.0.0.1, 2.0.0.2
TABLE 7. MONITOR SUPPORTED AND COMPATIBLE PRODUCTS AND COMPONENTS
Sentry
Product / Component Supported Compatible
Standalone Sentry 9.14.0 9.8.1, 9.9.0, 9.12.0, 9.13.0
Integrated Sentry 6.4.0 6.2.0–6.3.0
TABLE 8. SENTRY SUPPORTED AND COMPATIBLE PRODUCTS AND COMPONENTS
Copyright © 2022, Ivanti. All Rights Reserved. Privacy and Legal.
Page 16 of 41
Support and compatibility
Access
Product / Component Supported Compatible
Access R51 Not applicable, because only the latestversion is available to all customers.
TABLE 9. ACCESS SUPPORTED AND COMPATIBLE PRODUCTS AND COMPONENTS
Android
Product / Component Supported Compatible
Android 7.0, 8.0, 8.1, 9.0, 10.0, 11.0, 12.0
Mobile@Work 11.4.0.0, 11.5.0.0 9.3.0.0–11.3.0.1
Tunnel (Android native, AndroidEnterprise, and Samsung KnoxWorkspace)
4.6.1 4.3.0, 4.3.2, 4.4.0, 4.5.0,4.6.0
Secure Apps Manager 9.3.0.0, 9.4.0.0 8.3.0.0–9.2.0.0
Email+ (Android AppConnectand Android Enterprise)
4.1.1, 4.2.0*
* Email+ 4.2.0 is targeted to releaseon January 27, 2022
3.0.0–4.1.0
Docs@Work (AndroidAppConnect and AndroidEnterprise)
2.17.1, 2.18.0*
* Docs@Work 2.18.0 is targeted torelease on January 24, 2022
2.0.0–2.17.0
Web@Work (AndroidAppConnect)
2.5.1, 2.6.0 2.1.0–2.5.0
TABLE 10. ANDROID SUPPORTED AND COMPATIBLE PRODUCTS AND COMPONENTS
Copyright © 2022, Ivanti. All Rights Reserved. Privacy and Legal.
Page 17 of 41
Support and compatibility
iOS
Product /Component
Supported Compatible
iOS iOS 12–iOS 15.2 iOS 11
Mobile@Work 12.11.40, 12.11.50*
* Mobile@Work 12.11.50 is targeted to releaseJanuary 25, 2022.
12.0.0–12.11.30
Tunnel 4.1.5 2.4.1–4.1.4
Email+ 4.1.1, 4.2.0 2.6.0–3.18.0
Docs@Work 2.19.0, 2.19.1, 2.20.0*
* Docs@Work 2.20.0 is targeted to release onJanuary 24, 2022
2.2.0–2.18.2
Web@Work 2.14.0 2.0.0–2.13.2
Apps@WorkContainer app
Not supported l 1.1.2–1.2.0 whenusing [email protected], 9.0.1, or 9.1.0
l 1.3.0 when usingMobile@Work 9.5.0
Help@Work Help@Work does not work on iOS 10and newer versions. Use theTeamViewer app for Help@Worksupport.
2.0.2–2.1.1
TABLE 11. IOS SUPPORTED AND COMPATIBLE PRODUCTS AND COMPONENTS
Copyright © 2022, Ivanti. All Rights Reserved. Privacy and Legal.
Page 18 of 41
Support and compatibility
macOS
Product /Component
Supported Compatible
macOS/OS X 12.01
Support for macOS management will betransitioned to Ivanti Endpoint Managerand MobileIron Cloud.
10.1–11.6.1
Tunnel 4.1.3 3.0.0, 4.1.0, 4.1.1
TABLE 12. MACOS SUPPORTED AND COMPATIBLE PRODUCTS AND COMPONENTS
tvOS
Product /Component
Supported Compatible
tvOS 15.1.1 12.4–15.1.0
TABLE 13. TVOS SUPPORTED AND COMPATIBLE PRODUCTS AND COMPONENTS
Copyright © 2022, Ivanti. All Rights Reserved. Privacy and Legal.
Page 19 of 41
Support and compatibility
Windows
Product /Component
Supported Compatible
Windows l Windows 10 Pro, Windows 10Enterprise (version 21H1)
l Windows 11 Pro, Windows 11Enterprise
Support for Windowsmanagement will betransitioned to IvantiEndpoint Manager andMobileIron Cloud.
l Windows 10 Pro, Windows 10Enterprise (versions 1703, 1709, 1809,1903, 1909, 2004)
l Windows HoloLens (versions 1701,1803)
Note the following:With 1803, Apps@Work cannot be pushedto the device because of a known Microsoftissue. We recommend that customers stayon the H2 branches of Windows 10 toensure a longer support lifecycle. The -09versions of the OS have a 30-month supportlifecycle from Microsoft, while the -03versions only have an 18-month supportlifecycle. For more information, seehttps://support.microsoft.com/en-us/help/13853/windows-lifecycle-fact-sheet.
Apps@Work 9.6.0.256 Not applicable (all listed versions are testedand supported)
Tunnel 1.2.3 1.2.0, 1.2.2
TABLE 14. WINDOWS SUPPORTED AND COMPATIBLE PRODUCTS AND COMPONENTS
Copyright © 2022, Ivanti. All Rights Reserved. Privacy and Legal.
Page 20 of 41
Support and compatibility
Supported browsers
Browser Supported Compatible
Internet Explorer 11 9*, 10*
Chrome 96 93, 94, 95
Firefox 95 92, 93, 94
Safari Not supported 10.1*
Edge Not supported Not compatible
Chrome - iPad Not supported Not compatible
Safari - iPad Not supported Not compatible
TABLE 15. SUPPORTED BROWSERS
* This configuration is not covered under the Ivanti product warranty.
Supported browser resolutions
Browser resolution Supported Compatible
800x600 No No
1024x768 No Yes*
1280x1024 Yes Yes
1366x768 Yes Yes
1440x900 Yes Yes
Higher resolutions No Yes
TABLE 16. SUPPORTED BROWSER RESOLUTIONS
* This configuration is not covered under the Ivanti product warranty.
Copyright © 2022, Ivanti. All Rights Reserved. Privacy and Legal.
Page 21 of 41
Support and compatibility
Related information from previous releasesIf a release does not appear in this section, then the support and compatibility values from the nearestlisted older release apply to the missing release.
l Core 11.4.0.0 - Support and compatibility
Support Policy
Supported productversions
The functionality of the product and version with currently supportedreleases was systematically tested as part of the current release and,therefore, will be supported.
Compatible productversions
The functionality of the product and version with currently supportedreleases has not been systematically tested as part of the current release,and therefore not supported. Based on previous testing (if applicable), theproduct and version is expected to function with currently supportedreleases.
TABLE 17. DEFINITIONS FOR SUPPORTED AND COMPATIBLE
Copyright © 2022, Ivanti. All Rights Reserved. Privacy and Legal.
Page 22 of 41
Support and compatibility
Supported languagesl Chinese (Simplified)l Chinese (Traditional)l Dutch (Netherlands)l Englishl French (France)l German (Germany)l Hungarian (Hungary)l Italian (Italy)l Japanesel Koreanl Polishl Portuguese (Brazilian)l Romanian (Romania)l Russianl Slovakl Spanish (Latin American)l Swedish (Sweden)
Related information from previous releases
If a release does not appear in this section, then the supported languages from the nearest listed olderrelease apply to the missing release.
l Core 11.4.0.0 - Supported languages
Copyright © 2022, Ivanti. All Rights Reserved. Privacy and Legal.
Page 23 of 41
Language support on Android and Android EnterprisedevicesRefer toMobile@Work for Android Release Notes for a complete list of supported languages forAndroid and Android Enterprise devices.
Language support on iOS devices and macOS devices(legacy features)SeeMobile@Work for iOS Release Notes for a complete list of supported languages for iOS devices.
SeeMobile@Work for macOS Release Notes for a complete list of supported languages for macOSdevices.
Language support on Windows devices (legacy features)Core supports the following languages and locales in client apps on Windows devices:
l Chinese (Simplified)l Chinese (Traditional)l Englishl French (France)l German (Germany)l Japanesel Koreanl Portuguese (Brazilian)l Russianl Spanish (Latin American)
Copyright © 2022, Ivanti. All Rights Reserved. Privacy and Legal.
Page 24 of 41
Supported languages
Resolved issuesThe following resolved issues are in this release.
l VSP-66503: There was an issue with the Enterprise Connector displaying the Certificate Pinningoption from the System Manager Certificate Mgmt page, although this option is not supported onthe connector. This issue has been fixed. The Certificate Pinning option displays for Core, but not forConnector, from the System Manager.
l VSP-66265: There was an issue in which LDAP attributes present in the Core Devices & Users >Users > View logs for User > User Groups table were not displaying properly in the user interface.This issue has been fixed. All LDAP attributes now display as expected.
l VSP-66264: Previously, when an iOS app specified a minimum OS version as an integer, that OSversion did not display as expected in Apps@Work or the app. This issue has been fixed.
l VSP-66263: Previously, removing a subset of app restrictions against an iOS device would fail, dueto improper generation of the action entry in the database. This issue has been fixed.
l VSP-66236: Previously, the iOS section of the Security Policy menu did not include the option foriOS release 12.5.5 in the drop-down menu. This issue is resolved. Release 12.5.5 is now available inthe Security Policy > iOS section.
l VSP-66214: There was an issue with some of the Device Registration page submenu options listedunder the wrong subheading. This issue has been fixed. The Device Registration menu optionsdisplay as expected.
l VSP-66110: Core no longer generates unnecessary system event alerts for expired local certificateauthority (CA) certificates after the certificate has been retired.
l VSP-66063: Previously, Windows 10 App Store searches would fail when run from new installationsof Core 11.4.0.0. This issue has been fixed. New installations of Core 11.4.0.0 can successfully searchWindows 10 App Store as expected.
Copyright © 2022, Ivanti. All Rights Reserved. Privacy and Legal.
Page 25 of 41
l VSP-66056: A bug fix incorporated into Core 11.3.0.0 and newer releases drastically slowed oneof the Cisco Identity Service Engine (ISE) Application Programming Interface (API) calls. This issueis fixed in this release.
l VSP-66028: There was an issue with Core not generating an error message when an invalidHTML app configuration file was uploaded. This issue has been fixed.
l VSP-66016: Previously, when a Trusted Host was added, it would sometimes fail to displayproperly in the System Manager > Maintenance > HA Configuration > Manage SSH Keys popupwindow. This issue has been fixed.
l VSP-65995: Previously, during an upgrade, Core did not report signature verification failures tothe user interface, resulting in the download appearing to be successful. The subsequent attemptto stage for installation resulted in repeating the download, and it was not possible tosuccessfully stage the upgrade under these conditions. This issue has been fixed.
l VSP-65994: There was an issue in which Core pre-upgrade package files--which are necessary tocomplete an upgrade--were not being downloaded correctly when upgrading through theCommand Line Interface (CLI). This issue has been fixed. Both upgrades from the CLI and the userinterface now download the necessary files to complete the upgrade.
l VSP-65991: Previously, in-house apps (.apk files) failed to upload to the Admin portal AppCatalog due to a limitation in the Android application package (APK). This issue has been fixed.
l VSP-65977: There was an issue with Core rejecting Android XML configurations for Zebradevices if they were larger than 32 KB. This issue has been resolved. Core accepts theseconfiguration files up to 512 KB.
l VSP-65925: With the release of Windows 11, there was a compatibility issue between Core andthe Windows 11 Operating System Edition name and Platform name. This issue has been fixed.Core now supports Windows 11 OS as expected.
l VSP-65877: There was an issue where, after an upgrade to Core, administrators were unable toopen the Core Admin portal in a browser. This issue has been fixed. After an upgrade to 11.5.0.0,the Admin portal will open on supported browsers, as expected.
l VSP-65862: There was an issue whereby Core did not accept Apple Volume Purchase Plan (VPP)account tokens if the organization name contained 16-bit Unicode characters. This issue hasbeen fixed. Core now accepts these tokens.
Copyright © 2022, Ivanti. All Rights Reserved. Privacy and Legal.
Page 26 of 41
Resolved issues
l VSP-65837: Previously, if a user in the Pinned Server Certificate Policy menu clicked Save whenno certificate was selected, the console would stop responding. This issue has been fixed. TheSave button is not enabled if no certificate is selected.
l VSP-65748: There was an issue when adding a new Device Space from the Admin > DeviceSpaces page. When adding a list with many different platforms, an incorrect error messagewould display: "Query size must be between 0 and 2000." This issue has been fixed. Core nowbehaves as expected when creating Device Spaces.
l VSP-65689: The option to install Core 11.4.0.0 on the Core M2700 appliance with an ISO imagefrom a bootable USB drive now works as intended.
l VSP-65653: The System Manager > Settings > Network > Interfaces > Physical Interfaces tablenow correctly lists the number of network interface ports (NICs) on a Core M2700 appliance assix.
l VSP-65481: Previously, when retired devices were re-registered to Core, they did not send anupdated Azure device identifier. This resulted in the Azure portal weekly job report listing thecompliance status for these devices incorrectly. This issue has been fixed. Devices that are re-registered to Core now display correct compliance status in the Azure portal weekly job report.
l VSP-65164: There was an issue with Mobile@Work for Android silent installation requests usingthe wrong user ID value for Apps@Work requests. This issue has been fixed. Android silent appinstallation requests now work as expected.
l VSP-64695: There was a minor corner-case issue related to privilege revocation. This issue hasbeen fixed.
l VSP-62502: There was an issue with an LDAP Sync attribute not syncing correctly. This issue hasbeen fixed. ThemS-DS-ConsistencyGuid LDAP attribute now syncs as a binary attribute, asexpected.
l VSP-61195: The "Touchdown" app has been removed from the Exchange configuration as it isno longer available on the Google Play store.
Related information from previous releasesIf a release does not appear in this section, then there were no associated resolved issues.
l Core 11.4.1.0 - Resolved issuesl Core 11.4.0.0 - Resolved issues
Copyright © 2022, Ivanti. All Rights Reserved. Privacy and Legal.
Page 27 of 41
Resolved issues
Known issuesThe following known issues are in this release.
l VSP-66576: There is an issue with the Core App Catalog being unable to successfully import the"eCONFIG - Smart-Ex 02" app. Currently, there is no workaround.
l VSP-66562: There is an issue with macOS reports appearing in the mobile device management(MDM) device logs for shared iPads. This issue does not impact the performance or functionality ofthe devices.
l VSP-66548: There is an issue with the Mobile4ERP public app failing to install on Android Enterprisedevices. The app goes into a loop updating details and never resolves. There is no workaround atthis time.
l VSP-66524: There is an issue with new Mobile@Work iPhone users who are unable to access theirMy Devices tab when logged into a Secure Sign-In multi-user web clip with other new users. There isno workaround.
l VSP-66462: There is an issue with the new Apple User Enrollment registration process sometimesgenerating incorrect managed Apple IDs. You must use the single device invitation or the bulkdevice invitation process to verify that the managed Apple IDs were generated correctly. You shouldalso check the logs for any managed Apple ID failures. If the existing registration process is alreadyusing PINs, the registration will still work.
l VSP-66451: In Federal Information Processing Standards (FIPS)-enabled Core deployments, SplunkIndexer version 6.x running over Secure Socket Layer (SSL) is unable to securely connect to Splunk.There is no workaround.
l VSP-66442: There is an issue when upgrading from Core 10.8.0.0 or older to a Core 11.X release.Backups taken of the upgraded 11.X release fail to restore properly, due to a change in the UniqueIdentifier (UID) or Globally Unique Identifier (GUID) across the versions.
Copyright © 2022, Ivanti. All Rights Reserved. Privacy and Legal.
Page 28 of 41
l VSP-66298: Script-run Get MDM Profile API requests fail when the special characters "+", "/",or "=" are included in the deviceInfo parameter.Workaround: Avoid using special characters in the deviceInfo section of the Get MDM ProfileAPI request script.
l VSP-66218: The Knox Attestation API version 2 is no longer supported by devices running theSamsung Knox operating system (OS) 3.8 and later. The devices operate normally, except theCore attestation check fails, even when the check was successful.Workaround: No current workaround. These devices require Knox Attestation API version 3,which Ivanti plans to implement for the next release.
l VSP-65924: There is an issue with non-compliant Mobile@Work devices being listed in theMicrosoft Azure Device Compliance report as still compliant, with a compliance status code of"Interaction Required on EMM." There is no workaround.
l VSP-65679: There is an issue with the Device Wi-Fi configuration. If the administrator specifies"Auto" as the configuration proxy, and does not provide a URL for the proxy automaticconfiguration (PAC) value, the configuration erroneously treats the configuration proxy as"None" instead of "Auto." This issue is scheduled to be resolved in the next release.
l VSP-57766: The /api/v1/dm/labels/{label-name}/{device-uuid} API call returns anerror when associating a label containing a forward slash (/).Workaround: Do not apply device labels through the API if the labels include a forward slash.
Related information from previous releasesIf a release does not appear in this section, then there were no associated known issues.
l Core 11.4.0.0 - Known issues
Copyright © 2022, Ivanti. All Rights Reserved. Privacy and Legal.
Page 29 of 41
Known issues
LimitationsThe following limitations are in this release.
l VSP-66144: Due to an Apple limitation, the Enforced Fingerprint Timeout restriction is not availablefor iOS devices, although it is available for macOS devices.
l VSP-62043: There is a vendor issue that is blocking Core from accessing restrictions set on macOSdevices. A ticket has been filed with the vendor.
Related information from previous releasesIf a release does not appear in this section, then there were no associated limitations.
l Core 11.4.0.0 - Limitations
Copyright © 2022, Ivanti. All Rights Reserved. Privacy and Legal.
Page 30 of 41
Core upgrade informationFor detailed instructions on how to upgrade Core using this upgrade information, refer to the Core SystemManager Guide.
Core and Enterprise Connector should be running the same version and the same build.
l Core upgrade readiness checklistsl Check disk space availabilityl Core upgrade pathsl Core upgrade URLl Backing up Core
Before you begin
Read "Before you upgrade " on page 4.
Core upgrade readiness checklistsThis section provides checklists to help you successfully complete the upgrade process for Core and Sentrysoftware. The checklists include:
Pre-Upgrade checklist
Before you upgrade, we encourage you to do a pre-upgrade checklist.
Check Tasks References
Prepare and planfor downtime
l Core (1 - 3 hours)l Sentry (5 - 20 minutes)
Review relevantdocumentation
See Core product documentation.
TABLE 18. PRE-UPGRADE CHECKLIST
Copyright © 2022, Ivanti. All Rights Reserved. Privacy and Legal.
Page 31 of 41
Check Tasks References
Check certificates l iOS Enrollment, Portal HTTPS, Client TLS certificates
When using mutual authentication, the Portal HTTPScertificate must be a publicly trusted certificate from awell-known Certificate Authority. For details, see “Mutualauthentication between devices and Core” in the CoreDevice Management Guide for iOS and macOS Devices.
l MDM Certificate (check a month before expires)l Local CA
Knowledge Base article: Renewing an expired local CA certificate.
Check Bootpartition
Verify you have at least 35 MB free for /boot. See "Check disk spaceavailability" on page 35 in this document for details on how toperform this check.
Knowledge Base article: Core Upgrade: Increase Boot Partition to1GM if Avail Space is less than 35MB.
Ensure there isenough disk space
l Old File System (2 GB /mi and 5 GB /mi/files)l New File System (10 GB /mi)l If there is insufficient storage, increase the available disk space.See this VMware knowledge base (KB) article and this VMware KBarticle for information. Note that these are third-party articleshosted by VMware, whose locations are subject to change.Contact Ivanti Support if you need shell access to the Core VM.
Check for newsystemrequirements
l Minimum 80 GB hard drivel If there is insufficient storage, increase the available disk space.See this VMware knowledge base (KB) article and this VMware KBarticle for information. Note that these are third-party articleshosted by VMware, whose locations are subject to change.Contact Ivanti Support if you need shell access to the Core VM.
l Call Ivanti support if issues persist when physical appliances andVMs have the minimum required disk space configured
TABLE 18. PRE-UPGRADE CHECKLIST (CONT.)
Copyright © 2022, Ivanti. All Rights Reserved. Privacy and Legal.
Page 32 of 41
Core upgrade information
Check Tasks References
l Port 8443 for Summary MICS - Configuration Service (that is, theservice that supports System Manager.)
Review yourbackup and highavailability options
l Physical backup: built in backup, showtech alll VMware backup: VDMK backup, snapshotl High Availability: confirm HA version 2.0
Knowledge Base article: How to tell if your Core has HA 2.0If using HA 1.0, contact Ivanti Professional Services to upgrade to 2.0.
Set up your proxyconfiguration (ifrequired)
Manually set the upgrade URL and use HTTP instead of HTTPS.
Prepare testdevices
l Client: Get clean test devices, open client and check-in, check iOSlog.
l Core: Note the watchlist and label numbers.
TABLE 18. PRE-UPGRADE CHECKLIST (CONT.)
Upgrade considerationsAfter the pre-upgrade planning, we recommend you review the following considerations:
Check Considerations References
DB Schema and Data Run pre-validation check after downloading the repository fromSystem Manager. If this task fails, contact Ivanti Support.
Understand thestages
l Download vs. Stage for installl Reboot when the system displays:Reboot to installhttps://<serverFQDN>:8443/upgrade/status
Leverage CLI upgradecommands (asappropriate)
See Core Command Line Interface (CLI) Reference.
TABLE 19. UPGRADE CONSIDERATIONS
Copyright © 2022, Ivanti. All Rights Reserved. Privacy and Legal.
Page 33 of 41
Core upgrade information
Check Considerations References
Understand scenariooptions
Single server
High availability—Option 1: little downtime:
l Upgrade secondaryl Upgrade primary
High availability—Option 2: zero downtime:
l Upgrade secondaryl Failover to secondaryl Upgrade primaryl Re-establish sync
Download guide: Core High Availability Management Guide
Review section: HA Core Software Upgrade Procedures
Monitor the upgrade l Log into the Admin Portall Select Logs > MDM Logs > States > Waiting XMLgeneration pending
l Monitor upgrade status using:https://<serverFQDN>:8443/upgrade/status
Additional reboot Due to a kernel upgrade, an additional reboot is performedwhen you upgrade. It may take longer than expected for Core tobecome available on the network.
Upgrade impact onWindows devices
In some cases, when an administrator initiates Reset PIN for aWindows Phone 10 device, the device does not return a new pinfor that device.
For more information, see the following knowledge base article:Core Product Bulletin: Reset Pin command Fails to return a NewPin for Windows Phones 10 Devices
Ports HTTPS/ port 443 is the default port for fresh installations, butupgraded environments keep the previous port open, forexample, port 8080.
TABLE 19. UPGRADE CONSIDERATIONS (CONT.)
Copyright © 2022, Ivanti. All Rights Reserved. Privacy and Legal.
Page 34 of 41
Core upgrade information
Post-Upgrade checklist
After completing the upgrade, we recommend the following verification checklist.
Check Tasks References
Testing andtroubleshooting
1. Log into the System Manager
2. SelectMaintenance > Software Updates > SoftwareVersion
3. Verify that the new version is listed
4. DO NOT re-boot the system once the upgrade process hasbegun
5. Call Ivanti Support for further investigation
Verify services l Log into the Admin Portall Select Services > Overviewl Click Verify All
Verify devices l Register a new devicel Re-enroll/check-in existing devices
HA system cleanup l Set secondary back to secondaryl Confirm sync
TABLE 20. POST-UPGRADE CHECKLIST
Check disk space availabilityBefore you upgrade, check disk space availability. At least 35 MB of disk space must be available inthe /boot folder for an upgrade to be successful.
If at least 35 MB of disk space is not available in the /boot folder, contact Ivanti Technical Supportbefore proceeding with the upgrade.
Use one of the following methods to check disk space availability:
The CLI command: show system disk
The following sample output shows the available disk space in the last line. It is 15M in this example.CORE(8.5.0.1a-6)@host.company.com#show system disk
Copyright © 2022, Ivanti. All Rights Reserved. Privacy and Legal.
Page 35 of 41
Core upgrade information
Filesystem Size Used Avail Use% Mounted on
/dev/sda3 181G 20G 153G 12% /
tmpfs 16G 4.0K 16G 1% /dev/shm
/dev/sda1 95M 76M 15M 84% /boot
The System Manager
The System Manager > Maintenance > System Storagemenu shows you how much Core systemstorage you are using, and how much is still available.
Procedure
1. In the System Manager, go toMaintenance > System storage.
2. ClickMore Details next to the System Storage bar that shows percent used.
3. In this example, the available disk space is 190M.
Core upgrade pathsWe recommend the following upgrade paths, which are fully tested and supported.
l 11.3.0.0 → 11.5.0.0l 11.3.1.0 → 11.5.0.0l 11.4.0.0 → 11.5.0.0l 11.4.1.0 → 11.5.0.0l 11.5.0.0 GMRC → 11.5.0.0
Copyright © 2022, Ivanti. All Rights Reserved. Privacy and Legal.
Page 36 of 41
Core upgrade information
Related information from previous releasesl Core 11.4.1.0 - Upgrade pathsl Core 11.4.0.0 - Upgrade paths
Core upgrade URLTo upgrade Core, use the following URL if you specify an alternate URL:
https://support.mobileiron.com/mi/vsp/11.5.0.0-11/mobileiron-11.5.0.0-11
Related information from previous releasesl Core 11.4.1.0 - Upgrade URLl Core 11.4.0.0 - Upgrade URL
Backing up CoreWe recommend that you make a local backup of Core before starting an upgrade. For more informationon backing up Core, see the Core System Manager Guide.
Copyright © 2022, Ivanti. All Rights Reserved. Privacy and Legal.
Page 37 of 41
Core upgrade information
Enterprise Connector upgrade informationFor detailed instructions on how to upgrade Enterprise Connector using this upgrade information, refer tothe Core System Manager Guide.
l "About Enterprise Connector upgrade" belowl "Enterprise Connector upgrade paths" belowl "Enterprise Connector upgrade URL " on the next page
About Enterprise Connector upgradeIn most cases, Enterprise Connector is upgraded automatically after a Core upgrade. Core upgrades includeany new service package necessary for Enterprise Connector. If Connector needs to be updated, then Coreprompts Connector to access the new package and complete an in-place upgrade. In most cases, thisprocess completes successfully, and Connector restarts.
If there is a problem with the in-place upgrade, then Connector makes two additional attempts tocomplete the upgrade. Connector reboots before attempting to upgrade again. If the upgrade is still notsuccessful, then Connector reverts to the previous version and begins running in compatibility mode. Inthis case, you must complete the manual upgrade steps explained in the On-Premise Installation Guide forCore and Enterprise Connector.
Enterprise Connector upgrade pathsEnterprise Connector releases can be directly upgraded only from the following listed releases:
l 11.3.0.0 → 11.5.0.0l 11.3.1.0 → 11.5.0.0l 11.4.0.0 → 11.5.0.0l 11.4.1.0 → 11.5.0.0l 11.5.0.0 GMRC → 11.5.0.0
Copyright © 2022, Ivanti. All Rights Reserved. Privacy and Legal.
Page 38 of 41
Related information from previous releasesl Core 11.4.1.0 - Connector upgrade pathsl Core 11.4.0.0 - Connector upgrade paths
If you are upgrading from a version not listed here, then you need to complete one or more previousupgrades first. See the upgrade guide for that version.
Enterprise Connector upgrade URLTo upgrade Enterprise Connector, use the following URL if you specify an alternate URL:
https://support.mobileiron.com/mi/connector/11.5.0.0-11/mobileiron-11.5.0.0-11
Related information from previous releasesl Core 11.4.1.0 - Connector upgrade URLl Core 11.4.0.0 - Connector upgrade URL
Copyright © 2022, Ivanti. All Rights Reserved. Privacy and Legal.
Page 39 of 41
Enterprise Connector upgrade information
Documentation resourcesProduct documentation is available on the Ivanti documentation website. To access documentation,navigate to a specific product and click the > symbol next to the name to view all documents in thatproduct category.
Core documentationThe following is a complete list of documentation for this product. However, the list of documents updatedfor specific versions will vary, depending on release requirements. Therefore, you might encounterdocuments from previous releases that still apply to the current release.
l Core Release Notes and Upgrade Guide — Contains the following release-specific information: newfeature summary, support and compatibility, upgrade notes, known and resolved issues, andlimitations.
l On-Premise Installation Guide for Core and Enterprise Connector—Contains information needed toinstall Core on a VM or on an appliance. You will find pre-deployment tasks, steps to install andconfigure Core and Enterprise Connector, and set up the VMware tool.
l Getting Started with Core— Contains information you need to get started with Core. Contains anintroduction to the Admin Portal, information about setting up users, devices, and basic policies,managing the dashboard, labels, and custom attributes, registering devices using the [email protected]@Work does not have a separate product guide.
l Core System Manager Guide— Everything you need to know about configuring Core system settings,managing network settings, performing maintenance tasks including upgrading Core, andtroubleshooting issues using the Core System Manager.
l Core Apps@Work Guide— The complete guide to installing, setting up, and managing apps fordevices. Information about the Email+, Web@Work, and Docs@Work are covered in the guides forthe apps.
l Core Delegated Administration Guide— The complete guide to configuring and maintainingdelegated administration with Core.
Copyright © 2022, Ivanti. All Rights Reserved. Privacy and Legal.
Page 40 of 41
l Core Device Management Guide for Android and Android Enterprise DevicesCore Device Management Guide for iOS and macOS DevicesCore Device Management Guide for Windows, including Windows 10 Devices— Everything youneed to know about setting up and managing devices on Core. Each volume is specific to ageneral device platform. Information about Sentry, AppTunnel, ActiveSync, AppConnect, Access,and Zero Sign-on are covered in the related product guides.
l Core High Availability Management Guide— This document includes steps for setting up CoreHigh Availability as well as a description of common HA scenarios and troubleshooting tips.
l Core Command Line Interface (CLI) Reference— The Core command line interface (CLI) enablesyou to access certain Core capabilities from the command line. The reference describes how toaccess the CLI, use the help, the various command modes, and the available commands.
l Core V2 API Guide—API reference guide for the version 2 public APIs.
l V1 API Reference Guide for Core WebService— This reference guide provides developmentinformation for customers and partners intending to use WebService APIs.
l Common Platform Services API Guide—Describes how to use the Event Notification Service andCommon Platform Services (CPS) API with Cloud and Core.
l ServiceNow Integrator Update Set Guide — Describes how to set up and use the ServiceNowIntegrator Update Set.
l Mobile@Work for Android Release Notes — Contains the following release-specific information:new feature summary, support and compatibility, known and resolved issues, and limitations.
l Mobile@Work for iOS Release Notes — Contains the following release-specific information: newfeature summary, support and compatibility, known and resolved issues, and limitations.
l Mobile@Work for macOS Release Notes — Contains the following release-specific information:new feature summary, support and compatibility, known and resolved issues, and limitations.
Copyright © 2022, Ivanti. All Rights Reserved. Privacy and Legal.
Page 41 of 41
Documentation resources
