Log for task sequence on client

Question

_{Thursday, January 19, 2017 10:25 AM}

Hi 

How can I see the install log for applications in my task sequence on the client ?

I have a powershell script which is working fine if I execute it from the package path on the server at the client, but it do not work when executed from the task sequence

I have looked at below path but ccm is empty

%windir%\sysWOW64\ccm\logs\smsts.log (64-bit)

Thanks in advance

All replies (3)

_{Thursday, January 19, 2017 12:11 PM}

First, the log directory is %windir%\ccm\logs.

Next, during task sequence execution (for a non-OSD task sequence), the current smsts.log is stored in a sub-folder called SMSTSLog.

Last, the normal Application logs are still used during a task sequence include AppEnforce.log and AppDiscovery.log.

Jason | http://blog.configmgrftw.com | @jasonsandys

_{Thursday, January 19, 2017 2:03 PM}

Thanks i found the %windir%\ccm\logs folder and the log for  AppEnforce.log. I am unable to find the SMSTSLog folder. Could you please point me in the right direction

_{Thursday, January 19, 2017 2:06 PM}

As noted, the folder only exists while the TS is running. If the TS is no longer running than smsts.log will be in the same folder %windir%\ccm\logs.

If the log is not there, then a TS has never run. You can check execmgr.log for possible reasons why the ts didn't get kicked off.

Jason | http://blog.configmgrftw.com | @jasonsandys