Software Deployment

1. Welcome to WPS. I can understand the maths here, actually. Your example shows a conflict between just 2 packages. However, there could be conflicts with 20: how would you display the number of conflicts?

2. No.

Hello,

The conflictlist should contain one unique key, and in Conflict Details list you see all the applciations that conflict it.
Like key: ..\{4EF6..................9993}\<Default> should be there just 1 time.

Bert

You're more than welcome to post a feature request to Altiris. Just don't expect anything to happen in your lifetime. Or your grandchildren's... :-)

Hello VBScab,

I had contact with (Altiris) Sysmantec, and I found out what the problem was.

Normally I there is one unique registry key, lets say:
..\{4EF6..................9993}\<Default>

But when I check the MSI with Orca I saw, that there are 2 of those keys and it is because there are 2 merge modules, with the same key.

So lets say the problem is solved.

That isn't what I'm seeing in your screen shot. I'm seeing the same registry key with different component GUIDs, one for 'PDFCreator' and one for 'Wise Package Studio'. Why is WPS in the SMD? Do you distribute that to your estate? Bizarre...

Different GUIDs is because, Wise has his own regisrtykeys and PDFcreator uses Merge Modules.

One, how does that square with this assertion which you say was from Wise:it is because there are 2 merge modules, with the same key.As far as I can recall, the standard Wise install doesn't have any MMs.

Two, again, why do you have WPS in the database at all? You won't be distributing it to your estate so you don't need to know if it conflicts with any other applications.

Three, why not align the component IDs and have done with it?

and two, again, why do you have WPS in the database at all? You won't be distributing it to your estate so you don't need to know if it conflicts with any other applications.

Thats because we repackage almost every thing. And we don't want Wise stuff in our package. So its just for a check.

Sorry, but that doesn't make any sense. What Wise "stuff" would get into your packages? There are the usual Wise-specific tables but they won't mess with anything else, since they don't directly affect files or registry data. All you're going to get is a bunch of spurious "conflicts" which won't actually cause any issues on your user's workstations.

Anyway, I'm going to stop bashing my head against this particular wall: I have other, equally pointless things to be getting on with. Anyone interested in an XCopy/RoboCopy clone in HTA form?

Add the merge module to the database and the wsi instead of the msi to exclude merge modules conflicts.

However; as Ian also pointed out, can't understand why you want to conflict WPS with the rest of the packages.
WPS should only be installed to a clean machine when performing capture, for manually creating packages or just editing with wps no clean is "required".

@ VBScab and AngelD,

I just added Wise, just 2 be sure that there aren't any Wise regkeys, files being add to a new repacked program.
But maybe you guys are right, but I thought we repackage on a clean machine, with Wise. So there is an option that there a Wise keys in a new packaged program.

So VbScab, don't worry. Don't Bash youre head anymore. I just thought it's usefull !

Bert