i'm trying to figure out a way of preserving the MSI log information from install to install without creating a single HUGE history log file.
we've developed a CA that attempts to truncate the MSI log but we're finding out that the MSI log is locked during the Execution Sequence.
is there a way of renaming the MSI log during install?
is there a way of generating a unique log everytime an install happens?
any suggestions on managing the MSI log?
i would like to preserve previous install logs without ending up with one huge log file.
This is a ready-only archive of the InstallSite Forum. You cannot post any new content here. / Dies ist ein Archiv des InstallSite Forums. Hier können keine neuen Beiträge veröffentlicht werden.
MSI Log file
Started by
dtasanas
, Jan 04 2005 18:56
2 replies to this topic
Posted 04 January 2005 - 21:31
http://www.msifaq.com/a/1022.htm
You can use the registry setting described there (or the equivalent group policy) to generate log files with unique (random) names in the TEMP folder.
You can use the registry setting described there (or the equivalent group policy) to generate log files with unique (random) names in the TEMP folder.
Stefan Krüger
InstallSite.org twitter facebook
Posted 11 January 2005 - 00:15
thanks Stefan
but pre-setting the registry isn't very practical on customer machines. great for the test lab.
i think i'm going to have to deal with the fact that i'm only going to be able to keep one log of the latest install information.
but pre-setting the registry isn't very practical on customer machines. great for the test lab.
i think i'm going to have to deal with the fact that i'm only going to be able to keep one log of the latest install information.
Don Tasanasanta[br]Configuration/Installation Eng