topic Re: VPM experiences in Server Management - Systems Insight Manager

VPM experiences

tintin31 — Wed, 05 Jan 2005 09:41:30 GMT

hello all,

I have installed a patch on CMS server and the server has rebooted itself.
Is it possible to control the reboot?
When I try to patch a W2K server with the wulnerability called MS04-044.
I have this result:
VPM Patch Date 05-Jan-2005, 14:52:23 Romance Standard Time
VPM Patch Details Advisory: MS04-044 Operation : Install Status : Not Applicable

So, I have downloaded the same patch from Microsoft site and I have installed it without no problem. So, why? Anybody have the same problem?

Is CMS server is able to manage any patch that they were installed before manually or by another product? If not, it is possible to indicate to CMS server that a group of patches have been already installed on a server?

I am waiting for further licensing to improve the tune and validate or not this product.

Please, share your experiences about this.

Re: VPM experiences

Deborah Kuznitz — Thu, 06 Jan 2005 13:16:12 GMT

The VPM patch agent validates whether the patch is truly applicable for the system. It is possible to download patches from Microsoft and install them, whether the system requires them or not.

The way patches that were previously installed are handled is through the Patch-Fix Based on a Scan function. The scan will identify security vulnerabilities and the patches that are needed to fix those vulnerabilities. If a patch has previously been applied for a security vulnerability, you will not be told that the patch is required.

Re: VPM experiences

tintin31 — Fri, 07 Jan 2005 03:48:01 GMT

I understand what you say but when I try to applied a patch identified by the security vulnerabilities scan, I should not have the Not Applicable Status, should I?

I try with another patch, it was the same result!!!
I just try a ssh command netstat on this W2K server, I have a red message saying :
No, does not support the SSH protocol.
Maybe, this is the problem?

Re: VPM experiences

tintin31 — Fri, 07 Jan 2005 09:18:00 GMT

Some news....
I have had someone from HP who told me that yes, SSH server must be installed on CMS server but also each Insight client must have the SSH client installed too. This one can be push from the Deploy menu from Insight console.

After having install SSH client, I try again to patch my W2K server and ....
I found again my first error: MxTmSIMSOAPWrapper.logon: ; nested exception is:
java.net.SocketException: Default SSL context init failed: Algorithm TrustAllX509 not available
Any idea????

I also a problem to configure a Domain user on the SSH server.
mkpasswd -d -u >> ...passwd works but when I use mxagentconfig, I always have a failed connection.
Just a precision, I have activated the trust certificate mode.
Please, help