How to retrieve the smstslogs During OSD

[Gregory B]

Hello,

 

This is my first topic, so I would like to share a simple way to retrieve the smstslogs automatically during an OSD TS.

 

Sometime, we can't stay in front of the computer during the TS, so, it's interesting to retrieve the logs on a share. We can do this by adding a group of tasks at the end of the TS like this :

 

 

Then, We are going to add a task in general category "Connect to Network Folder" :

 

 

You'll have to parameter the network folder path, the letter of the drive network path ("M:" in this example), and the account.

 

Next step, we are going to use the TS Variable %_SMSTSMachineName% to create a folder in the network folder. The folder will have the name of the computer we are deploying :

 

.

 

For the last step, we are going to copy the logs to the folder with the command : "cmd.exe /c copy %_SMSTSLogPath% M:\%_SMSTSMachineName%" :

 

 

Before to advertise the TS, we have to check that every groups of the TS have the option "Continue on error" checked.

 

At the end of your deployment (in error or not), you can check the logs.

 

Hope that will help you.

 

Gregory B

[anyweb]

nice post, i'll pin it ! keep it up

[Gregory B]

THX

[Peter33]

Make sure to use %OSDComputerName% instead of %_SMSTSMachineName%. Otherwise you will get a lot of MININT folder names.

[Peter van der Woude]

Make sure to use %OSDComputerName% instead of %_SMSTSMachineName%. Otherwise you will get a lot of MININT folder names.

Shouldn't be necessary, as _SMSTSMachineName just represends the up-to-date machinename through the whole task sequence...

 

Someting totally different, in case somebody just wants the logs of a failed task sequence, see: http://www.petervanderwoude.nl/post/copy-logs-from-a-failed-task-sequence-in-configmgr-2007/

[SRed]

Hmm, I've tried your steps, Gregory B, and I end up with a folder titled "%_SMTSMachineName%" in the network share I specified.

 

Did I do something wrong?

 

I linked the commands using an Ampersand operator like this

 

cmd.exe /c md M:\%_SMTSMachineName% & copy %_SMSTSLogPath% M:\%_SMSTSMachineName%

 

Furthermore, when I try the command manually from a diagnostic command prompt (I hit F8 while the Task Sequence is running), I don't see either %_SMSTSLogPath% or %_SMSTSMachineName% as Variables. They aren't listed under Set, and I can't expand them using Echo.

[Sameul]

sound like a good idea,have anyone do this experiment?

[ogeccut]

This is an old topic, but i am trying to use during in place upgrade TS and having some issues.

When i run this command:

cmd.exe /c robocopy /mir /z %_smstslogpath% m:\%_smstsmachinename% /copy:dt /NFL /NDL

The %_smstslogpath% is resolving to "c:\windows\sysWOW64\ccm\logs\Smstslog"

However that directory does not exists, I only have "c:\windows\sysWOW64\ccm\logs" at that point.

So my xcopy is failing with exit code 3. Is there any way to use that variable or should i hard code it to c:\windows\ccm\logs?

Thank you.

OSD PHASE	SMSTS.LOG LOCATION
WinPE, Before HD Format	x:\windows\temp\smstslog\smsts.log
WinPE, After HD Format	x:\smstslog\smsts.log
Windows, No SCCM Client Installed	c:\_SMSTaskSequence\Logs\Smstslog\smsts.log
Windows x86, SCCM Client Installed	c:\windows\system32\ccm\logs\Smstslog\smsts.log
Windows x64, SCCM Client Installed	c:\windows\sysWOW64\ccm\logs\Smstslog\smsts.log
Task Sequence Completed x86	c:\windows\system32\ccm\logs\smsts.log
Task Sequence Completed x64	c:\windows\sysWOW64\ccm\logs\smsts.log