We have had a task sequence in place for well over a year now. It has worked fine for updating, sysprepping and capturing an image. Once the capture creates the .wim file we create another task sequence off of that for deployment.
Now for some reason the sysprep and capture is failing.
I've tried the following: -created a new task sequence -duplicated the issue from another reference PC. -Verified that we are running the litetouch script from the reference PC and not from within PE environment.
I have included SMSTS.log file. I can see that the syspep is failing because of a missing file but not sure what file it is. I apologize in advance if there is an obvious answer for this. I was kind of just thrown into this as an after thought after a previous employee left our organization.
We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.
We have had a task sequence in place for well over a year now. It has worked fine for updating, sysprepping and capturing an image. Once the capture creates the .wim file we create another task sequence off of that for deployment.
Now for some reason the sysprep and capture is failing.
I've tried the following:
-created a new task sequence
-duplicated the issue from another reference PC.
-Verified that we are running the litetouch script from the reference PC and not from within PE environment.
I have included SMSTS.log file. I can see that the syspep is failing because of a missing file but not sure what file it is. I apologize in advance if there is an obvious answer for this. I was kind of just thrown into this as an after thought after a previous employee left our organization.
smsts.log
Share this post
Link to post
Share on other sites