Core upgrade information

Use the information in this section for upgrade information specific to this release. For detailed instructions on how to upgrade Core using this upgrade information, refer to the Core System Manager Guide

Core and Enterprise Connector should be running the same version and the same build.

• Core upgrade readiness checklists
• Check disk space availability
• Core upgrade paths
• Core upgrade URL
• Backing up Core

Before you begin 

Read Before you upgrade .

Core upgrade readiness checklists

This section provides checklists to help you successfully complete the upgrade process for Core and Sentry software. The checklists include:

Pre-Upgrade checklist

Before you upgrade, we encourage you to do a pre-upgrade checklist.

Table 17.  Pre-upgrade checklist

Check	Tasks	References
	Prepare and plan for downtime	Core (1 - 3 hours) Sentry (5 - 20 minutes)
	Review relevant documentation	See Core product documentation.
	Check certificates	iOS Enrollment, Portal HTTPS, Client TLS certificates When using mutual authentication, the Portal HTTPS certificate must be a publicly trusted certificate from a well-known Certificate Authority. For details, see “Mutual authentication between devices and Core” in the Core Device Management Guide for iOS and macOS Devices. MDM Certificate (check a month before expires) Local CA Knowledge Base article: Renewing an expired local CA certificate.
	Check Boot partition	Verify you have at least 35 MB free for /boot. See Check disk space availability in this document for details on how to perform this check. Knowledge Base article: Core Upgrade: Increase Boot Partition to 1GM if Avail Space is less than 35MB.
	Ensure there is enough disk space	Old File System (2 GB /mi and 5 GB /mi/files) New File System (10 GB /mi) Knowledge Base article: Resizing Disk Partition of a Core Virtual Machine.
	Check for new system requirements	Minimum 80 GB hard drive If there is insufficient storage, increase the available disk space using the procedure outlined in Resizing Disk Partition of a Core Virtual Machine Call Ivanti support if issues persist when physical appliances and VMs have the minimum required disk space configured Port 8443 for Summary MICS - Configuration Service (that is, the service that supports System Manager.)
	Review your backup and high availability options	Physical backup: built in backup, showtech all VMware backup: VDMK backup, snapshot High Availability: confirm HA version 2.0 Knowledge Base article: How to tell if your Core has HA 2.0 If using HA 1.0, contact Ivanti Professional Services to upgrade to 2.0.
	Set up your proxy configuration (if required)	Manually set the upgrade URL and use HTTP instead of HTTPS.
	Prepare test devices	Client: Get clean test devices, open client and check-in, check iOS log. Core: Note the watchlist and label numbers.

Upgrade considerations

After the pre-upgrade planning, we recommend you review the following considerations:

Table 18.  upgrade considerations

Check	Considerations	References
	DB Schema and Data	Run pre-validation check after downloading the repository from System Manager. If this task fails, contact Ivanti Support.
	Understand the stages	Download vs. Stage for install Reboot when the system displays: Reboot to install https://<serverFQDN>:8443/upgrade/status
	Leverage CLI upgrade commands (as appropriate)	See Core Command Line Interface (CLI) Reference
	Understand scenario options	Single server High availability: Option 1: little downtime: Upgrade secondary Upgrade primary Option 2: zero downtime: Upgrade secondary Failover to secondary Upgrade primary Re-establish sync Download guide: Core High Availability Management Guide Review section: HA Core Software Upgrade Procedures
	Monitor the upgrade	Log into the Admin Portal Select Logs > MDM Logs > States > Waiting XML generation pending Monitor upgrade status using: https://<serverFQDN>:8443/upgrade/status
	Additional reboot	Due to a kernel upgrade, an additional reboot is performed when you upgrade. It may take longer than expected for Core to become available on the network.
	Upgrade impact on Windows devices	In some cases, when an administrator initiates Reset PIN for a Windows Phone 10 device, the device does not return a new pin for that device. For more information, see the following knowledge base article: Core Product Bulletin: Reset Pin command Fails to return a New Pin for Windows Phones 10 Devices
	Ports	HTTPS/ port 443 is the default port for fresh installations, but upgraded environments keep the previous port open, for example, port 8080.

Post-Upgrade checklist

After completing the upgrade, we recommend the following verification checklist.

Table 19.  Post-upgrade checklist

Check	Tasks	References
	Testing and troubleshooting	Log into the System Manager Select Maintenance > Software Updates > Software Version Verify that the new version is listed DO NOT re-boot the system once the upgrade process has begun Call Ivanti Support for further investigation
	Verify services	Log into the Admin Portal Select Services > Overview Click Verify All
	Verify devices	Register a new device Re-enroll/check-in existing devices
	HA system cleanup	Set secondary back to secondary Confirm sync

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

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 Storage menu shows you how much Core system storage you are using, and how much is still available.

Procedure 

1. In the System Manager, go to Maintenance > System storage.
2. Click More Details next to the System Storage bar that shows percent used.

3. In this example, the available disk space is 190M.

   

• 11.1.0.0 → 11.3.0.0
• 11.2.0.0 → 11.3.0.0
• 11.3.0.0 (GMRC) → 11.3.0.0

Backing up Core

We recommend that you make a local backup of Core before starting an upgrade. For more information on backing up Core, see the Core System Manager Guide.