NetChk Protect 7.6 Hotfix Available

This hotfix is available for download through the forum currently. See the list of resolved issues below and go to the Shavlik Forum and login to download the hotfix.

This hotfix will release as a deployable patch in NetChk Protect 7.6 in an upcoming XML release. It was not included in the November Patch Tuesday release.

Resolved issues:

• Resolved an issue where the ‘Item History’ report and the ‘Seat License Status’ report were not available in the report gallery.
• Scan fails to import properly due to file locking issue on the scan information importer.
• Resolved an issue where deployments would fail when deploying patches that could not be downloaded.
• Resolved an issue where scans would hang on importing new definitions: Error – ‘Object synchronization method was called from an unsynchronized block of code.’
• Resolved an issue where deployments fail when installing or upgrading to 7.6 on a disconnected network.

Chris Goettl
Agile Product Owner
Shavlik Technologies

2 Comments

Steve Mason

Posted November 19, 2010 at 6:37 pm
Permalink

I appreciate your mention of the patch, I missed it in the support forum. But…
Why is there never anything available when clicking help, check for program updates?

I sat at 7.5 for a while because I incorrectly assumed that this would work, then finally noticed people talking about 7.6 in the forum.

Chris Goettl

Posted November 29, 2010 at 1:16 pm
Permalink

Steve,

The updates feature is for major product versions and is typically set to the latest build that has the majority of customers running on it. A new version would go through Beta, Early Access, and General Availability. At some point usually at the same time or shortly after GA we will turn on the auto update feature for previous versions to go to the latest build. That change will be occuring shortly for 7.6.

Patches are a little different. Beta for a patch is more of a period where we may have an engineering drop we can put in place to confirm fixes for customers with open issues. Once confirmed we build the patch. That is given out to customers with known cases that are resolved and goes to the forum and blogs for others to download. Once those cases are confirmed closed we release the patch into XML. At this point it is scanned and deployed like a security patch to the Shavlik console. Again there is a point where we reach a critical mass of users successfully running on the patch and we turn on auto update for that release to automatically update to the patch.

Now each release may differ a little, but that should give you a general idea of what we try to do. This helps us to control delivery and quality of the product more closely.

Regards,
Chris Goettl
Agile Product Owner

Blog Authors

Steve Mason

Posted November 19, 2010 at 6:37 pm

I appreciate your mention of the patch, I missed it in the support forum. But…
Why is there never anything available when clicking help, check for program updates?

I sat at 7.5 for a while because I incorrectly assumed that this would work, then finally noticed people talking about 7.6 in the forum.
Chris Goettl

Posted November 29, 2010 at 1:16 pm

Steve,

The updates feature is for major product versions and is typically set to the latest build that has the majority of customers running on it. A new version would go through Beta, Early Access, and General Availability. At some point usually at the same time or shortly after GA we will turn on the auto update feature for previous versions to go to the latest build. That change will be occuring shortly for 7.6.

Patches are a little different. Beta for a patch is more of a period where we may have an engineering drop we can put in place to confirm fixes for customers with open issues. Once confirmed we build the patch. That is given out to customers with known cases that are resolved and goes to the forum and blogs for others to download. Once those cases are confirmed closed we release the patch into XML. At this point it is scanned and deployed like a security patch to the Shavlik console. Again there is a point where we reach a critical mass of users successfully running on the patch and we turn on auto update for that release to automatically update to the patch.

Now each release may differ a little, but that should give you a general idea of what we try to do. This helps us to control delivery and quality of the product more closely.

Regards,
Chris Goettl
Agile Product Owner