after migrating (from windows XP to Win7) i just campared with 2 machines smsts log & smsts-20120523-011350 file seize is diffrent & in one machine application (ms-Office is not loaded). I am not sure how to troubleshoot

look for the Install software step which was responsible for installing Microsoft Office, what does it tell you ? Step by Step ConfigMgr 2007 Guides | Step by Step ConfigMgr 2012 Guides | I'm on Twitter > ncbrady

Troubleshooting and other Troubleshooting PXE and OSD Deployment problems Troubleshooting with the help of SMSTS.LOG and F8 How can I make troubleshooting failed deployments easier Adding additional functionality to your boot images Understanding SCCM Logs where are they, and what are they for Step by Step ConfigMgr 2007 Guides | Step by Step ConfigMgr 2012 Guides | I'm on Twitter > ncbrady

The smsts.log is indeed the one which gives information about what's going wrong during deployment. During installation the smsts.log file is located at different places. Everytime the device is booted again while the Task Sequence is still running, the smsts.log will be copied to a smsts--.log file, and a new smsts.log file will be created. That explains why you have multiple logfiles. The one with the date mentioned is used during deployment and will contain the most information. Open it with Trace32 (part of ConfigMgr 2007 toolkit) and have a look what's wrong with MS Office deployment.My blogs: Henk's blog and Virtuall | Follow Me on: Twitter | View My Profile on: LinkedIn

are you telling any specific log file. if yes how to find out

Troubleshooting and other Troubleshooting PXE and OSD Deployment problems Troubleshooting with the help of SMSTS.LOG and F8 How can I make troubleshooting failed deployments easier Adding additional functionality to your boot images Understanding SCCM Logs where are they, and what are they for Step by Step ConfigMgr 2007 Guides | Step by Step ConfigMgr 2012 Guides | I'm on Twitter > ncbrady