Clean Build versus Update Problem

[Guest]

I am evaluating XPSP2 on an enterprise image. In a clean build from original
select media with SP2 slip streamed Diskeeper and Symantec Antivirus refuse
to work. In an updated build applying XPSP2 to an existing image the same
programs work fine.

I cannot identify the root of the problem.

XPSP1 with SP2 added, AD domain membership and applications already in place
and working, Diskeeper 8 and SAV8.0 Corporate with Autoupdate.

XPSP2 clean build, AD domain membership and same SMS wrapped packages
installed. Diskeeper installs but when opening up the MMC console it dies
with a message about not be able to contact the "remote" machine. SAV
installs and appears to work but it will not connect to the corporate update
servers and cannot be forced to do an autoupdate. WF is turned off by
default on the local LAN.

Any ideas? I have searched the forums for both vendors with no good hits.

 

[Shenan Stanley]

I am evaluating XPSP2 on an enterprise image. In a clean build from
original select media with SP2 slip streamed Diskeeper and Symantec
Antivirus refuse to work. In an updated build applying XPSP2 to an
existing image the same programs work fine.

I cannot identify the root of the problem.

XPSP1 with SP2 added, AD domain membership and applications already
in place and working, Diskeeper 8 and SAV8.0 Corporate with
Autoupdate.

XPSP2 clean build, AD domain membership and same SMS wrapped packages
installed. Diskeeper installs but when opening up the MMC console it
dies with a message about not be able to contact the "remote"
machine. SAV installs and appears to work but it will not connect to
the corporate update servers and cannot be forced to do an
autoupdate. WF is turned off by default on the local LAN.

Any ideas? I have searched the forums for both vendors with no good
hits.

So you are installing DisKeeper using an SMS package or clean?

 

[Guest]

SMS package. We wrap everything here for enterprise deployment. There are
no problems with the package. It has been in production for a year. Updates
to the packages happen about every six months for configuration purposes.

 

[Shenan Stanley]

SMS package. We wrap everything here for enterprise deployment.
There are no problems with the package. It has been in production for
a year. Updates to the packages happen about every six months for
configuration purposes.

.... and if you install it without using the package?
.... or recreate the package with SP2?

 

[Guest]

The original source is usually not available in our environment. I can try
getting the source and installing that.

What do you mean by building the package under XPSP2?

We use MS SMS Installer as our standard packaging program. Are you
suggesting I run the installer on a SP2 machine to build the packages?