Deploying PSP via SWUPDATE...

[John Kramer]

When I try to do send out a application lunch task to install updated PSP's the task kicks off but then stops, if I logon to the console it's waiting for me to answer "yes" to the question about this driver or software not having a digital signature. There are several PSP that I have to say YES too. I suppose I could tell Windows 2000 to install unsigned drivers but should I have too? I have the agents all set to trust by server name.

[Neal Bowman]

Are you launching setup.exe? In the PSP, there is a cmd file that will run all components that are part of the package. It is typically named BP000xxx.CMD. Depending on the version of PSP you have downloaded or copied from CD, the xxx may vary. You can also use the setupc.exe with the /force switch- c:\ntcsp\setupc.exe /use-latest /f. Open setupc.hlp for more specifics on available switches for the SETUPC utility.

[John Kramer]

No I am sending the whole support pack version 6.2 as a task in Insight Manager. Using the SWUPDATE batch file and example in the Insight Manager documentation. That's why I can't have it prompt it should be an automated task.

[Mike Gentles]

Whenever I run a PSP update thru IM7 I always use a simple update software/firmware task. I dont bother with the batch file method.

This assumes that there is a functioning VCA on the servers, that there is the IM7 trust setup also. You can preconfig the insight management agents from within the VCRM, and push it out this way.

I have never had a problem with this before.

Mike Gentles

[Rob Buxton]

I've not seen the problem you're reporting but have had problems when updating multiple Servers. Admittedly these were when we had a range of old Agents all over the place.

Recently I've just pushed them from IM using the VC Agent Page with success.

[John Kramer]

How is your Windows 2000 server configuration setup to handle unsigned drivers? Is it set for Ignore, Warn or Block? I have to use the SWUPDATE task IF I do not have a working VCS agent on the server. Most of these servers have older or unconfigured agents on them. I am trying to send out a new 6.2 PSP with fully configured agents, and during the install process of the various components Windows 2000 is asking if It okay to install this unsigned component. I guess the real question should be why isn't all the PSP file digitally signed?

[John Kramer]

The same thing happens when I try to lunch an software update task that uses the VCS agent. I have two identical DL580G2's that both stopped updating on CP002928.exe. I get installation started in the VCS log then nothing. I see a CP002928.EXE process in the task manager just sitting there. I suspect there is a prompt that I cannot see that needs answered, with a "YES" to ignore the absense of a digital signature. But since the VCS agent runs as a background process in the SYSTEM context I have no why to get to this prompt to answer "YES"

CAN SOMEONE FROM COMPAQ PLEASE LET ME KNOW IF I HAVE TO HAVE DRIVER SIGNING VERIFICATION DISABLED IN WINDOWS 2000 TO GET THIS TO WORK.

Do most users have their Driver Signing policy set to ignore?

[Rob Buxton]

John,
I've made no changes to the default setup for Driver signing, mine is set to "warn".

[John Kramer]

How are the following too registry setting set, in your environment?

HKLM\software\microsoft\non-driver signing\policy=00
HKLM\software\microsoft\driver signing\policy=00

[John Kramer]

How are the following two registry setting set, in your environment?

HKLM\software\microsoft\non-driver signing\policy=00
HKLM\software\microsoft\driver signing\policy=00

[Rob Buxton]

John,

Difference in the Driver Signing Policy.
e.g.
HKLM\software\microsoft\non-driver signing\policy=00
HKLM\software\microsoft\driver signing\policy=01

Rob.