Dell KACE
AppDeploy
AppDeploy.com

 

Log In | Log Out | Register | Search | Member Ratings | My Forums | My Settings | RSS Feeds


SOLVED: Wise ConflictManager exclude MergeModule

Click here to associate this thread with a Package KB article. 		Logged in as: Guest
Users viewing this topic: none
  Printable Version
All Forums >> [AppDeploy Forums] >> Package Development >> SOLVED: Wise ConflictManager exclude MergeModule Page: [1]
Login
Message << Older Topic   Newer Topic >>
SOLVED: Wise ConflictManager exclude MergeModule - 7/22/2010 3:05:34 AM   
bertman

 

Posts: 12
Score: 0
Joined: 6/17/2006
From: Netherlands
Status: offline 		Hello,

I have 2 questions over the Wise ConflictManager

1. When I have a conflict with 2 applications he will show both keys and say that there are 12 conflicts, but in there are only 6 conflicts (in my example).


2. Is there an option to exclude the Merge Module in Wise Software Manager / Conflictmanager ?

< Message edited by bertman -- 7/30/2010 1:54:41 AM >
Post #: 1
RE: Wise ConflictManager exclude MergeModule - 7/22/2010 3:20:41 AM   
VBScab


Posts: 6634
Score: 192
Joined: 9/5/2006
From: London, UK
Status: online 		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.


_____________________________

- Don't know why 'x' happened? Want to know why 'y' happened? ProcMon will tell you.
- Try using http://www.google.com before posting.
- I answer questions only via forums. PMs and personal emails will be ignored.

(in reply to bertman)
Post #: 2
RE: Wise ConflictManager exclude MergeModule - 7/22/2010 4:09:50 AM   
bertman

 

Posts: 12
Score: 0
Joined: 6/17/2006
From: Netherlands
Status: offline 		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

(in reply to VBScab)
Post #: 3
RE: Wise ConflictManager exclude MergeModule - 7/22/2010 5:38:27 AM   
VBScab


Posts: 6634
Score: 192
Joined: 9/5/2006
From: London, UK
Status: online 		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... :-)

_____________________________

- Don't know why 'x' happened? Want to know why 'y' happened? ProcMon will tell you.
- Try using http://www.google.com before posting.
- I answer questions only via forums. PMs and personal emails will be ignored.

(in reply to bertman)
Post #: 4
RE: Wise ConflictManager exclude MergeModule - 7/30/2010 1:54:14 AM   
bertman

 

Posts: 12
Score: 0
Joined: 6/17/2006
From: Netherlands
Status: offline 		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.

(in reply to VBScab)
Post #: 5
RE: Wise ConflictManager exclude MergeModule - 7/30/2010 3:31:04 AM   
VBScab


Posts: 6634
Score: 192
Joined: 9/5/2006
From: London, UK
Status: online 		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...

_____________________________

- Don't know why 'x' happened? Want to know why 'y' happened? ProcMon will tell you.
- Try using http://www.google.com before posting.
- I answer questions only via forums. PMs and personal emails will be ignored.

(in reply to bertman)
Post #: 6
RE: Wise ConflictManager exclude MergeModule - 7/30/2010 8:34:10 AM   
bertman

 

Posts: 12
Score: 0
Joined: 6/17/2006
From: Netherlands
Status: offline 		Different GUIDs is because, Wise has his own regisrtykeys and PDFcreator uses Merge Modules.

(in reply to VBScab)
Post #: 7
RE: Wise ConflictManager exclude MergeModule - 7/30/2010 9:24:04 AM   
VBScab


Posts: 6634
Score: 192
Joined: 9/5/2006
From: London, UK
Status: online 		One, how does that square with this assertion which you say was from Wise:
quote:

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?


< Message edited by VBScab -- 7/30/2010 9:26:31 AM >

_____________________________

- Don't know why 'x' happened? Want to know why 'y' happened? ProcMon will tell you.
- Try using http://www.google.com before posting.
- I answer questions only via forums. PMs and personal emails will be ignored.

(in reply to bertman)
Post #: 8
RE: Wise ConflictManager exclude MergeModule - 7/30/2010 9:27:17 AM   
bertman

 

Posts: 12
Score: 0
Joined: 6/17/2006
From: Netherlands
Status: offline
quote:

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.

(in reply to VBScab)
Post #: 9
RE: Wise ConflictManager exclude MergeModule - 7/30/2010 9:52:59 AM   
VBScab


Posts: 6634
Score: 192
Joined: 9/5/2006
From: London, UK
Status: online 		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?


_____________________________

- Don't know why 'x' happened? Want to know why 'y' happened? ProcMon will tell you.
- Try using http://www.google.com before posting.
- I answer questions only via forums. PMs and personal emails will be ignored.

(in reply to bertman)
Post #: 10
RE: SOLVED: Wise ConflictManager exclude MergeModule - 7/30/2010 10:05:46 AM   
AngelD

 

Posts: 2937
Score: 102
Joined: 6/9/2004
From: Sweden
Status: offline 		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".

(in reply to bertman)
Post #: 11
RE: SOLVED: Wise ConflictManager exclude MergeModule - 8/1/2010 5:34:55 AM   
bertman

 

Posts: 12
Score: 0
Joined: 6/17/2006
From: Netherlands
Status: offline 		@ 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

(in reply to AngelD)
Post #: 12
Page:   [1]
All Forums >> [AppDeploy Forums] >> Package Development >> SOLVED: Wise ConflictManager exclude MergeModule Page: [1]
Jump to:





New Messages No New Messages
Hot Topic w/ New Messages Hot Topic w/o New Messages
Locked w/ New Messages Locked w/o New Messages
 Post New Thread
 Reply to Message
 Post New Poll
 Submit Vote
 Delete My Own Post
 Delete My Own Thread
 Rate Posts


Forum Software © ASPPlayground.NET Advanced Edition 2.4.5 ANSI

0.063