pcyosis

New Member
Joined
Jun 7, 2010
Messages
2
Hi,

I really hope someone can help since this has been driving me mad.
I have a number of issues but this is the first one, and the one thats stopping me progressing.

I am using a USB stick to boot the PE environment and it goes through no problems. The machine joins the domain when in windows and i select "Work"
Windows doesn't seem to activate itself, but will work if i do it manually.

Now i don't see any other window coming up to install any apps. I don't get a ZTIApplication.log file generated in the c:\windows\temp\deployment folder.
I know there is the SMSTS.log, but this doesn't appear on the local machine, there is a copy that it writes to x:\windows....but thats no good since its on the USB stick's PE environment which is not available.

In WDT I have left the deploy applications task step and just added a simple install application for adobe acrobat straight after. I gather this is the correct way.
I can provide more detail as people ask.

I guess first question: how do i see the log file then any other reasons it won't work.

Thanks
 

Last edited:
It seems like you're encountering some challenges with your Windows deployment process using a USB stick to boot the PE environment. Let's address the issues you've described:

Logging Concerns:​

  1. ZTIApplication.log: You mentioned that the ZTIApplication.log file is not generated in the C:\Windows\Temp\Deployment folder. This log typically records information related to Application deployment in MDT (Microsoft Deployment Toolkit). If it's not being generated, there could be an issue with the application deployment process itself.
  2. SMSTS.log: The SMSTS.log file is crucial in SCCM (System Center Configuration Manager) deployments. It's strange that you're not seeing it on the local machine but only on the X: drive in the USB stick's PE environment. The absence of this log locally might indicate that logs are not properly stored during the deployment process.

    Activation Issue:​

    • You mentioned that Windows doesn't activate itself automatically but works when done manually. This might be related to how the activation process is configured in your deployment task sequence.

      Application Installation:​

    • It's good practice to add an "Install Application" step after the "Deploy Applications" task in your MDT task sequence to ensure applications are installed post-deployment. Adding Adobe Acrobat as a test application in this step is a correct approach.

      Troubleshooting Steps:​

    []Log File Visibility: To view log files, especially the missing SMSTS.log, you might need to troubleshoot why it's not being stored locally. Ensuring proper logging configurations in your deployment settings is crucial. []Activation Troubleshooting: Review your Windows activation configuration in the task sequence. Ensure proper licensing and activation settings are in place. []Application Installation: Check the application deployment settings in the MDT task sequence. Ensure dependencies and conditions are correctly configured, and the application installation step is targeting the right machines. []Manual Log Collection: If logs are not being stored as expected, manually collecting logs during the deployment process might provide insight into where the issue lies. For further assistance, providing more detailed information about your MDT task sequence configurations and deployment settings would be helpful in diagnosing and resolving the issues you're facing. Feel free to share additional details for more targeted assistance.
 

Back
Top