I may be late with this but it's for my reference more than anything. SCCM OSD can be a hair tearing process at the bet of times. Should you ever need to troubleshoot it MS don't exactly make it easy finding the files either.
He is where you will find the log files at various points throughout the whole OSD process as they do move dependant on which stage you are up to...
WindowsPE, before HDD format: x:\windows\temp\smstslog\smsts.log
WindowsPE, after HDD format: x:\smstslog\smsts.log
Windows, SCCM agent not installed: c:\_SMSTaskSequence\Logs\Smstslog\smsts.log
Windows, SCCM agent installed: c:\windows\system32\ccm\logs\Smstslog\smsts.log
Windows x64, SCCM agent installed: c:\windows\sysWOW64\ccm\logs\Smstslog\smsts.log
Task Sequence completed: c:\windows\system32\ccm\logs\smsts.log
Task Sequence completed x64: c:\windows\sysWOW64\ccm\logs\smsts.log
Don't forget - use Trace32 to view these log files - it makes it miles easier....
These are the ramblings of a 30 something (going on 60) year old disgruntled IT Professional. This is gradually evolving into a Windows SCCM blog but there's a bit of "me stuff" in here too as I like to write so have a look at some of my work. Please feel free to leave a comment...
Showing posts with label log. Show all posts
Showing posts with label log. Show all posts
Friday, 17 May 2013
Tuesday, 25 September 2012
Turn on logging for MSI installs
If you ever install from MSI's (which I'm sure you do) it can be handy to turn on logging so you can see the outcome - particularly handy if the install is failing.
Use the following code after your package.MSI and then a log file will be generated at the location you choose:
Use the following code after your package.MSI and then a log file will be generated at the location you choose:
msiexec /i Packagename.msi /l*v c:\logname.log
Subscribe to:
Posts (Atom)