Forum.shavlik.com

These are release notes for version 6.5.3.

Installation:

Please see the “Requirements\" tab on http://www.shavlik.com/netchk-protect-6-5-requirements.aspx for a list of supported Operating Systems and other system requirements

Please note: version 6.5.3 cannot be installed on Windows Vista. (version 7 can be installed on Vista)

Upgrades:

Shavlik NetChk Protect 6.5.x can be installed on top of existing Shavlik NetChk Protect 5.9 and later installations.

What's New and What's Fixed in Shavlik NetChk Protect 6.5.3 and other releases:

Please see http://www.shavlik.com/support/protect-history.aspx#protect653

Error Codes for Shavlik NetChk Protect 6.5.x:

http://forum.shavlik.com/viewtopic.php?f=10&t=6266&start=0&hilit=6266


Shavlik NetChk Protect Offline Virtual Machine Image Quick Start Guide:

http://www.shavlik.com/documents/qsg-prt-6-1-offline_vm.pdf

Notes about scanning and patching offline VMware Workstation, Server, and ESX Server Images:

ESX 4.0 is not supported on versions of NetChk Protect previous to 7.1.

Only virtual machine images that are offline (powered off) can be mounted. A virtual machine image that is online (powered on) will fail to mount if scanned specifically as a virtual machine image. Online virtual machine images should be treated no differently than a regular machine.

Only the current state of the offline image can be scanned and patched.

Dual boot systems (for example, a virtual machine with two partitions, each containing a different operating system) are not supported.

In order to mount a VMware ESX Server through a virtual center server, you must be running VMware VirtualCenter 2.0 or later.

When scanning virtual machine images that are supported by VMware, please keep in mind the following:
You cannot mount encrypted virtual disks.
You cannot mount a virtual machine image if any of its .vmdk files are compressed or have read-only permissions.
You cannot mount a virtual machine image that is currently being used by a running or suspended virtual machine.
Linked clones, templates, template images, and compressed images are not supported.

The scanning function assumes that port 902 is open and available on the ESX Server being scanned

The offline scan configuration dialog allows you to change the default port number (443) for communicating with the ESX or VI Server, however, this release will only use port 443 regardless of what is entered in this box

Email capabilities for offline virtual images don't work at this time.

Patches are not executed on the virtual images until the images are powered on.

A virtual machine image is counted only once against the total number of license seats available, even if it is scanned both in online (powered on) mode and offline (powered off) mode.

Within a machine group, the Filter Machines in this Group by and the Ignore Items components do not apply to virtual machine images.

Shavlik NetChk Agent operations are not supported on offline virtual machine images.

If you install Shavlik NetChk Agent on an online virtual machine image and then later scan the image while it is in an offline state, Shavlik NetChk Protect may report the wrong agent status for that image. For example, it may show that the agent is not installed, or it may let you attempt to uninstall the agent. This occurs because Shavlik NetChk Agent operations are not supported on offline virtual machine images. The correct status will be reported once the image is brought back online and rescanned by Shavlik NetChk Protect.

The spyware management function is not supported. Performing a spyware scan of a machine group that consists only of offline virtual machine images will result in a spyware scan of the local console.

When using Windows 2000 as a console machine, offline images that are running on an x64 version of Windows are not supported. Windows 2000 cannot read x64 registries.

Scanning offline images of Windows NT systems is not currently supported.

Shavlik NetChk Tracker will show the installation status for VM images, however, the rescan after reboot may not succeed as the console may not have credentials to scan the online VM image (as only offline ESX credentials were supplied in the machine group).