Hi all,

I'm brand new to packaging so please bear with me if I post/do anything stupid :-)

I used the information nheim's post (port #5) in this thread: http://itninja.com/question/how-do-you-roll-out-new-machines?4199 to build a MST to deploy mms.cfg along with Adobe Flash, for depoyment via Group Policy.

Essentially I followed his instructions with the following exceptions: used InstEd instead of ORCA, installing Flash v10 instead of v9, and didn't put mms.cfg into a cab, just deployed it from the original file.

The package installs fine and the settings in mms.cfg appear to work, however if I remove the package again (via Group Policy) mms.cfg does NOT get removed along with Flash. Flash goes, but %windir%\System32\Macromed\Flash\mms.cfg remains.

This isn't really an issue, but for my own curiousity's sake - and in case I ever run into this in the future - can anyone suggest why mms.cfg is not being removed properly?

Cheers,
Matt
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Answers

0
Hi Matt,
interesting...
What does the log file tell you?
Regards, Nick
Answered 03/12/2009 by: nheim
Tenth Degree Black Belt

Please log in to comment
0
Hi mattjk,

Check the attribute of the component in which mms.cfg file is been kept it should be 0.If it is marked as 24(Permanent) change it to 0.I hope the file is geeting installed through FIle table and not through any custom action.

Regards,
Answered 03/12/2009 by: anks_09
Orange Senior Belt

Please log in to comment
0
If it is marked as 24(Permanent) change it to 0

Just for info - 16 is Permanent - 8 is SharedDllRefCount (24 meaning both bit flags are set)

So it's likely to be 16 - which you should still set to 0

Regards,
Rob.
Answered 03/12/2009 by: MSIPackager
Third Degree Black Belt

Please log in to comment
0
interesting...
What does the log file tell you?


Which log file would that be? Sorry, as I said in my OP, I'm new to this :-)

Check the attribute of the component in which mms.cfg file is been kept it should be 0.If it is marked as 24(Permanent) change it to 0.I hope the file is geeting installed through FIle table and not through any custom action.

Yep, the component's attributes are set to 0.

The file is being deployed by:
1) Create new entry in File table for my mms.cfg file
2) Create new entry in Components table referencing my custom File entry
3) Create new entry in FeatureComponents table with same Feature as the rest of the package, but Component referencing my custom Component

Cheers,
Matt
Answered 03/12/2009 by: mattjk
Yellow Belt

Please log in to comment
0
Which log file would that be?If you use a command line call to MSIExec, rather than going through 'Add/Remove Programs' or double-clicking the MSI, you can specify a log file in which all the steps of the install/uninstall will be recorded:

........MSIExec /x {ProductCode}_or_PathToAndNameOfMSI /L*V PathToAndNameOfLogFile.LOG
Answered 03/13/2009 by: VBScab
Red Belt

Please log in to comment
Answer this question or Comment on this question for clarity