Re: OSD Logs
- From: Johan Arwidmark <anonymous@xxxxxxxxxxxxxx>
- Date: Mon, 17 Jul 2006 20:57:36 +0200
OSDAgent.log is the primary log and should be the first place you look
to determine what step failed
OSDEnv.log indicates which OSD Environment variables are set
OSDInstallWizard.log logs startup operations when doing a bare metal
deployment
OSDShell.log launches the OSD Install Wizard
osdConnectToUNCPath.log logs Connect to UNC operations
If using ZTI you also have the ZTI Logs (copied to the \\server\logs
folder after each phase). You can also turn on ZTI debug mode by
adding /debug:true to the command line,
OSD logs will log verbose info if a file named c:\osd.debug is
present. OSD will keep the logs if a file named
c:\minint\archive_osd.sms is present. (adding debug to ZTI
automatically creates these files
Regarding batchfiles you can run them as a custom action either by
just calling the batchfile itself or by cmd /c batchfile.cmd.
Having batchfiles as software packages for the restore phase SWD
program action is a different story since there are issues with how
UNC paths is handled.
John Clark recently posted a nice solution in this forum to issues
with running SWD programs contaning batch files in the state restore
phase.
regards
Johan Arwidmark
Microsoft MVP - Setup/Deployment
On 17 Jul 2006 10:18:24 -0700, anliko.lowman@xxxxxxxxx wrote:
Can anyone tell me which log(s) are about the pre-install phase? Also
can someone also tell me how to properly execute a batch file through a
custom action. Thanks
.
- References:
- OSD Logs
- From: anliko . lowman
- OSD Logs
- Prev by Date: Re: OSD Error, please Help Me
- Previous by thread: OSD Logs
- Next by thread: Re: OSD Error, please Help Me
- Index(es):
Relevant Pages
|
Loading