10.6.3.2 Why is it not available on smcupdate.emc.com?

[david_waugh]

Hello

Why is it the some packages can be downloaded from smcupdate.emc.com but others cannot? For example 10.6.3.0 can be upgraded to by clicking on check updates in the Netwitness GUI, but 10.6.3.2 has to manually be downloaded from RSA Live and then manually applied.

In many enterprise environments, there may be many jump boxes and proxies in the way that make this a difficult process?

Why do we not have the option of applying all patches through live?

What is the reason for making the customer experience more difficult than it needs to be?

[JohnSnider]

Currently smcupdate (and the GUI) only support updates to the service pack level (ex. 10.6.3), for some reason, the patch level (4th number) was not supported, mainly due to how they test the updates and how the versions are supported in the GUI. I have already brought this to the attention of Engineering and why they need to support all for levels of versioning.

As of now, if you upload 10.6.3.1, you can no longer upgrade a 10.6.0.0 box (it will have error saying "upgrade path not supported", because currently when you upload the patch files, they are mixed in with the service pack files and are not kept in a separate path to allow you to switch between them.  Hopefully this issue will be fixed in a future release, and we will truly support multi-version repos (or at least the ability to select which repo is being served to the clients)

So in  a nutshell, the reason for not including "patches" in the smcupdate download, is that it would break the ability to upgrade hosts on any other version except the latest Service pack.

Yes it's a pain, hopefully it will get changed soon,

[david_waugh]

Thanks John for the update. Hopefully it will be fixed soon!