I’ve been using CNUT for 9 years but am a newbie at SM Autoupdate because I thought it wouldn’t work if you checked Public for the IP address.
When I enabled Autoupdate for the AP, CNUT immediately started updating all the SMs it discovered under that AP, without me checking the boxes or even telling it to update anything. Which surprised me. It sounds like you are saying you can check the boxes for which SMs you want the AP to autoupdate, but that’s not what I observed. What am I doing wrong? In the past, I have always given CNUT the IP address of each SM, and checked the boxes for which ones I wanted updated. I’m trying to learn how to use SM Autoupdate. The manual doesn’t seem to be helping me a lot. From: Sean Heskett Sent: Wednesday, August 03, 2016 7:43 PM To: [email protected] Subject: Re: [AFMUG] CNUT question how to autoupdate without downgrading anySMs? yeah what bill and geroge said -sean On Wed, Aug 3, 2016 at 6:07 PM, Bill Prince <[email protected]> wrote: What George said. However.... You can sort by version number,check all the ones at the top of the list (version A), upgrade them to B, then do it again and upgrade everything to C. bp <part15sbs{at}gmail{dot}com> On 8/3/2016 4:51 PM, George Skorup wrote: It does not understand upgrade path. It will update every SM on the sector to whatever version is enabled and highest in the list for that platform. For example, if you have 13.2.1 on top, then 14.1.2 below that, both checked, it will enable auto-update with 13.2.1. You need to manually add only the SMs that you want to update. Or somebody tell me I'm wrong, because that's always the way it has worked for me. On 8/3/2016 6:28 PM, Ken Hohhof wrote: Let's say I have an AP with various SMs that are on FW versions A, B and C. Perhaps new installs got sent out with C on them, but the upgrade path requires that you go A -> B -> C, and some older SMs have been taken to B, while some are still on A. Is there a way to upgrade all the SMs on A to B, without downgrading the SMs on C back to B? I could be really brave and enable both B and C in Manage Packages, and hope that CNUT understands you can't go directly from A to C so those SMs should be updated to B, but the ones already on C can stay there. But I don't trust CNUT to be that smart, or I'm not that brave.
