Now that you have a copy of SMSTS.log log file, you can examine its content and identify the cause of your Task Sequence Deployment failure. To copy all the folder content, you need to specify the location using this format Folder_Path\*.* (Example: x:\windows\temp\SMSTSLog\*.*)) and is the destination folder you would like to use to copy the logs (Simply use the mapped drive of your USB drive or the network share as destination). It is better to copy the parent folder instead of copying only SMSTS.log file as you might find other useful logs inside.
The command to use is xcopy where is the folder where the log resides (You can refer to the previous table to get the log file location.
#Sccm mdt copy log files to network share software#
Import it into your deployment software (MDT, SCCM), or put it on the installation drive (rename the file to install. If you plug a USB drive then make sure that it is mapped (usually it is mapped as E:\ drive so make sure that you can access the drive from the command prompt windows). Copy the wim Image file from a local disk.Click on F8 when the Task Sequence fails to display the command prompt window.When a Task Sequence Deployment fails with an error, proceed as the following to extract the required log files: This Wiki shares with you how you can copy SMSTS.log to a USB key or a network share.
X:\smstslog\smsts.log and copied to c:\_SMSTaskSequence\Logs\Smstslog\smsts.logĬ:\_SMSTaskSequence\Logs\Smstslog\smsts.log copy the boot and root files to a folder in our NFS share ipxe is an ipxe. SMSTS.log is a log file which is generated to allow the troubleshooting of operating system related Task Sequence failures.ĭepending on the deployment phase, SMSTS.log will have the location shared in the following table: LOG With Ironic we get the flexibility of cloud with bare metal Digital Rebar.