Feature Update Deploy

• 3 min to read •

Important Information

Syxsense uses a local intelligent file downloading model to ensure efficiency in Feature Update installations.

To take advantage of this efficiency, always target devices on the same LAN. 

Once the installation ISO is downloaded to the target devices and the installation has started, Syxsense will monitor the installation while the device is still connected.

Once the installation has rebooted the device, after the end-user accepts it, the process is in the hands of the installation ISO used.

Prerequisites 

An uploaded ISO

Video Tutorial: How to Create Feature Update TaskVideo Tutorial: How to Create Feature Update Task

Watch an example of this task  Video

Guided walk-through: How to Deploy a Feature UpdateGuided walk-through: How to Deploy a Feature Update

Create:

From the Tasks menu click 'Create' > Choose 'Feature Updates' 

 You can also create a Feature Update task by clicking the 'Quick Install' button on the Feature Updates tab. Drop-down TitleDrop-down Title

Where:

Select which devices to deploy  Feature Updates to using either Predefined Device Queries, User Defined Device Queries, Device Groups, Specific Devices & Active Directory Targets or All Devices > Click 'Next'.

 Targeting more than one device on the same site, in the same task, will allow the devices to efficiently deploy by using Syxsense's internal intelligent file downloading model.

What:

Select the Feature Update you wish to deploy > Click 'Next'.

Prepare your 'Application' beforehand, but the 'Create New Application' option is available if it hasn't been prepared before starting the task wizard.

When:

Select when you would like your application to be deployed > Click 'Next'.

 You may configure Maintenance Windows during which a Feature Update will be completed, a repeat interval such as 'repeat every Monday' for unsuccessful devices, and the Protect option to ensure the software does not run during important business hours.

Reboot

Select if you would like your device to be rebooted following the deployment of software > Click 'Next'.

 You can specify if snooze options should be used.

Summary:

Review the settings of the task and if configured correctly, click Finish to save the task.

Once the task has been created the following will occur (in order).Drop-down TitleDrop-down Title
  • The task will be put into progress and all targeted devices will accept the deployment.
  • The 'Pre-Installation' interface options, as configured during the Feature Update image creation, should ALWAYS be used to warn the end-user.
  • The 'Pre-Installation' interface options will validate to ensure the end-user is ready to start the deployment. Once it's approved or the timers have elapsed, the task will start the Feature Update image download. This takes between 15-45 minutes, depending on the environment's network speed (and disk write speed).
  • Once downloaded, the task will mount the ISO and execute the Windows 10 upgrade routine.
  • A few moments later, when the device is ready to perform the upgrade, the end-user will receive the 'Post Installation Reboot' interface options. This is the end-user's last chance to postpone the deployment before the device reboots and installs the upgrades.
  • Once the device is rebooted, the operating system will upgrade. This takes between 30-90 minutes, depending on strictly disk speed and health of the OS.

When the upgrade is finished, the device will perform a final reboot and continue back to the native operating system. The Feature Update task will show as 'Done' and 'Success' in the tasks list.

TroubleshootingTroubleshooting

The list below will highlight some of the possible result statements with resolution.

Issue/Result Statement Reason/Resolution
'Not Connected' The device has a MicroAgent already installed, and it is not responding. The device is offline/not connected to the network.
'Partial success' The device started the task and completed a scan of some of the updates; however, the device could not complete the task.
'Target device disconnected' The device started the task target device disconnected before any updates were scanned.
'Lost Connection' The device started the task but disconnected at any point in the task. Typically shown if target device disconnected before any updates were scanned.
'Not enough free disk space' The device does not have enough disk space to download the content. Ensure target device has enough disk space and re-attempt deployment task.
'Thread Being Aborted' or any other 'ErrorCode' The device likely has existing security software that does not trust Syxsense. 3rd party software must be populated with exclusions to trust this solution.

Last Update: Mar 12, 2024

Copyright ©2024 by Syxsense, Inc. All Rights Reserved