In the Nefsis client software, running the software update fails with the following error message: Unable to update. [151: HTTP protocol error. 404 Not Found. / / StatusCode=404]Client software build is 281.
We've removed the 'Check for updates' feature in the updated dedicated version of Nefsis. There are a few reasons why we're doing this:1. Dedicated installations can use a different version than the cloud.2. Dedicated users typically do not have the rights needed to install an application to their Program Files folder.3. The cloud version may not be compatible with the version used on the dedicated installation.
If the client software will no longer be able to detect that there is a new version of the software available in a dedicated installation, what is the recommended model for client software updates? If it is deployment of a new .MSI package, that's great, but how does an administrator know that there is a new version available to deploy?
The way its intended to work is that we send out notifications to the deployment owners or other administrative points of contact that an update is available, and they are then free to deploy it to their users as they see fit. If they need a few weeks due to workload or in order to complete an internal assessment of the software, they are free to postpone updating their deployment. The goal is to give administrators more control over the version used by their clients, and to give them the ability to schedule updates at a time convenient for them. We realize that our cloud update schedule may not work for everyone so we provide the dedicated version as a more controlled option.And you are correct, we will be providing all of the client MSI packages with each revision of the dedicated server.
Is there a link that can be used to always download the latest version of the client in MSI format?
I believe there is... you may want to contact firstname.lastname@example.org for precise details.The only thing to watch out for is the type of Nefsis service you are on (Online or Dedicated), as the releases can differ slightly sometimes.If you're using a Dedicated installation of Nefsis (i.e. a server located in your company), I'd probably stick with the EXEs and MSIs provided as part of that deployment (so you know everyone is on the same release).
In the Nefsis client software, running the software update fails with the following error message: Unable to install web components [StatusCode=200]Client software build is .331.
You have the most recent build (331), so it looks like the update was successful.In terms of the error, this can often be due to the Anti-Virus on the computer taking longer than expected to scan and verify the file, so it essentially "times out".However, since you have the most recent release installed, it updated OK. :-)
Hello, has anyone using the cloud version gotten the error message "Update loader not found: The automatic updater is missing. Nefsis cannot be updated."If so, how was this resolved?
Nefsis Customer Care