Tag: software maintenance

Sonos dumps the device-bricking Recycle Mode

Previous HomeNetworking01.info coverage Sonos multiroom system press picture courtesy of Sonos

The Sonos debacle has raised questions about our personal tech’s life cycle

My Comments

In January, Sonos introduced the “Recycle Mode” which effectively disabled your Sonos network-multiroom-audio device after a certain number of days. It was seen as a way to detach the device from your Sonos-based network-multiroom-audio setup and wipe all of your data out of the device when you relinquish it to an e-waste recycling facility.

It was part of them establishing an end-of-feature-support rule for their older devices made prior to 2015 due to newer faster processing silicon in the newer devices. That is where older devices will only receive software-quality updates and won’t benefit from any newer functionality that Sonos releases.

But there is a reality with this kind of equipment where it is effectively “pushed down” to secondary areas as a way to build out that Sonos audio setup. As well, people do give the equipment away to family, friends and community organisations they are a part of, or sell the equipment through the second-hand market where those of us “putting our foot in the Sonos door” may buy this equipment at a cheaper price.

The social-media users were concerned about the use of that “Recycle Mode” which disabled the Sonos equipment due to it not being available for giving away or selling to the second-hand market. Sonos have answered this issue by removing the “Recycle Mode” and requiring users who are done with a particular piece of Sonos equipment to perform a factory-reset procedure (Sonos instructions) on that unit.

It is a procedure you may do if the equipment is faulty and you want to bring it to a “known quantity” as part of troubleshooting it. But performing this procedure before you relinquish the equipment effectively detaches it from your Sonos account and multi-room audio system while removing any personal configuration data from it including parameters associated with your home network.

They still have to address the issue of a Sonos audio setup consisting of legacy and newer equipment and what happens when newer features come out. The problem still raised is the fact that older equipment would preclude modern equipment from receiving functionality updates. It is although a Sonos multiroom setup will benefit from software-quality updates even if it cannot receive functionality updates.

As well, they would need to address what happens when an online media service revises their software links that enable access to their service via consumer-electronics devices. Would a software update to accommodate this revision be considered a feature-update or a software-quality update whether the result is to provide the same functionality as before or accommodate the service’s new features?

What is being called out is how a high-value network-media device with an expectedly-long service life should he maintained through its service life. It includes how long should it be supported for and what should happen towards its end-of-support time.

Most iPhones and iPads now in circulation to be safe from the KRACK exploit

Article

Apple iPad Pro 9.7 inch press picture courtesy of Apple

Most iPads and iPhones updated to iOS 11.2 now safe from the KRACK exploit

Apple fills the KRACK on iPhones – at last | Naked Security

Previous Coverage

KRACK WPA2 Wi-Fi vulnerability–what is affected

My Comments

There has been intense computing-press coverage regarding the KRACK WPA2 exploit against otherwise-secure Wi-Fi wireless network segments. As my previous coverage highlighted, most of the major regular-computer and mobile operating systems were updated to rectify the vulnerability associated with this exploit.

Check the Settings App on your iPhone for the update

But, as I called out in the article, the iOS 11.1 update that Apple rolled out for their iPhones and iPads only remediated the vulnerability on certain newer devices. Here, it was ignoring a larger installed base of iPhones, iPads and iPod Touches by not providing the remediation for devices earlier than the iPhone 7 or the iPad Pro 9.7 (2016).

Now Apple has rolled out the iOS 11.2 update to extend this remediation to more iOS devices in the field. These include:

  • iPhone 6 encompassing the S and Plus variants, the iPhone SE, the iPhone 5S,
  • 12.9” iPad Pro (1st generation), the iPad mini 2 and its successors, the iPad Air, the iPad (5th generation)
  • iPod Touch (6th generation)

Here, it means that those commonly-used recent iPhones and iPads are now safe against the KRACK exploit. Check your Settings app on your iOS device to be sure it is up to date with this patch.

Microsoft cuts down the out-of-action time users face during the Windows upgrade cycle

Article

Windows will be improving the time it takes to upgrade the operating system

Microsoft is tweaking the Windows 10 upgrade process to reduce downtime | Windows Central

My Comments

A common situation that we face when we update or upgrade the operating system on our computers including our mobile devices is that the device is out of action for some time while the update take place.

Here, the holy grail for operating-system maintenance is that the updates take action once they are delivered rather than needing us to restart the device at all. In the context of business, this means that workers and business owners are able to stay productive without waiting for an update cycle to complete.

Most of these processes involve downloading the necessary files that contain the newest software code then performing fail-safe procedures. This is before the device is rebooted as a measure to make sure the extant software files are unencumbered before they are replaced with the freshly-downloaded files. Then the update procedure makes sure that everything is in place before allowing the user to interact with the system.

Microsoft identified some of the problems associated with the upgrade cycle associated with their Windows operating system and found that a lot of the preparatory work could take place before the system has to be rebooted.

Previously, the user-created configuration and other data had to be backed up and the operating-system files were prepared for installation after the computer was rebooted to instigated the software-update cycle for Windows. Now, from the Windows 10 Fall (Autumn) Creators Update onwards, these procedures will take place before the system has to be restarted. This is because most of these procedures are simply about copying files between locations on the System Disk.

The data-migration action will take place after the system is restarted and the user data will be restored once all the downloaded files are in place. Then the system will be restarted in order to make sure all the functionality is effective and, like with major functionality upgrades, the user may have to interact with the system further to enable this functionality.

The idea behind this move is to have all the preparatory work done while you are able to work with your computer so that it is out of action for a minimal amount of time.

The question here is whether this improved software-update process will take place for maintenance-level updates like the regular software patches and security updates that are delivered to keep Windows secure.

There is still the issue faced with all of the operating system update procedures, especially with significant updates or where mobile devices are concerned. This is where the update requires the device to be rebooted twice and spends some time out of action during that cycle. It also encompasses the requirement for regular computers to boot at least once while patches and security updates are being deployed.

But Microsoft’s step with improving the software-maintenance cycle for the Windows 10 operating system is getting us one step closer towards cutting down on the downtime associated with this process.