We have media that has TS to deploy and configure device in OEM factory. TS shutdown the device after initial deployment of OS and other applications. Once device arrive on site, we boot the device and continue the deployment for doing the on site steps
like domain join etc.
We are trying to modify 1 step in the TS to add one more applications (same application is actually skipped in TS that is been handed over to OEM) but once we run the post staging using updated TS , it is skipping the new step for installing
application, I am not sure why? Looks like once device is shutdown at factory, it cache\store the details and even when we use the TS, it reads some old info and skipping the new application deployment. any pointers to deploy the app will be appreciated.
Does MDT stores some Guid\reference for TS somewhere ?
Are you using a Standard Client Task Sequence or a Post OS Installation Task Sequence to try and do the Post-Factory configuration? Is it the same Task Sequence ID as used in the Factory by the OEM, just with additional / different steps?
it sounds like it's reading old deployment instructions from the original TS. The folders C:\MININT, and C:\_smstasksequence act
as a cache for deployment information. If those folders are still present from the original deployment, it will continue to follow the old instructions.
When the deployment finishes, it's supposed to run LTICleanup.wsf to remove those folders. Have you checked to see if the folders are present?
Proposed as answer bygbilligWednesday, July 03, 2013 2:25 PM
Microsoft is conducting an online survey to understand your opinion of the Technet Web site. If you choose to participate, the online survey will be presented to you when you leave the Technet Web site.