You got it! FYI, we require that on all our MSI installs. :)

Daniel Ratliff


From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On 
Behalf Of Jeff Poling
Sent: Wednesday, June 26, 2013 11:21 AM
To: mssms@lists.myitforum.com
Subject: Re: [mssms] MSI Logging from Task Sequence

<slaps forehead>.  Based on what you said, I could just add a /L*v to the 
package command line, right? Not sure why I did not think of that :)

On Wed, Jun 26, 2013 at 9:55 AM, Daniel Ratliff 
<dratl...@humana.com<mailto:dratl...@humana.com>> wrote:
Just have the MSI log to a path in the machine? As long as it's after the 
format you should be good. We do all our logging in c:\temp.

Daniel Ratliff

From: listsad...@lists.myitforum.com<mailto:listsad...@lists.myitforum.com> 
[mailto:listsad...@lists.myitforum.com<mailto:listsad...@lists.myitforum.com>] 
On Behalf Of Jeff Poling
Sent: Wednesday, June 26, 2013 10:52 AM
To: mssms@lists.myitforum.com<mailto:mssms@lists.myitforum.com>
Subject: [mssms] MSI Logging from Task Sequence

In a ConfigMgr 2007 environment, I have a OSD task sequence that is randomly 
failing.  The point at which it fails is during a package installation.  The 
package fails with a MSI 1603 error.  Under normal circumstances, I would 
enable verbose MSI logging, run the package, grab the log and find the specific 
point at which the MSI is failing.

During OSD, though, how do I get a verbose MSI log? My first thought would be 
to have an additional package that sets the proper reg values for verbose 
logging.  Any other thoughts or insight?

Thanks!

Jeff


The information transmitted is intended only for the person or entity to which 
it is addressed
and may contain CONFIDENTIAL material. If you receive this material/information 
in error,
please contact the sender and delete or destroy the material/information.




The information transmitted is intended only for the person or entity to which 
it is addressed
and may contain CONFIDENTIAL material.  If you receive this 
material/information in error,
please contact the sender and delete or destroy the material/information.


Reply via email to