Hi Jason
Thanks for replying.
I'm currently working on a PoC to move some POS devices from Windows XP to Windows 8.1 Ind with UWF enabled. When we apply monthly updates or application updates we need to stop the POS Application service before doing so. Using the inbuilt ConfigMgr
functionality to handle updates/application installs on write filter devices doesn't allow for the running of another program first before restarting into maintenance mode.
My thinking was to include exceptions in UWF for SCCM and then run a Task Sequence with the following steps:
Step 1 - Stop POS Application Service
Step 2- Disable UWF
Step 3 - Reboot
Step 4 - Install Application/Windows Updates
Step 5 - Reboot
Step 6 - Enable UWF
Step 7 - Reboot
Without the exceptions any information related to the progress of the Task Sequence is lost on the reboot at step 3. If I include the locations in the original post as exceptions I have some limited success in that information is retained such as the
_SMSTaskSequence folder and in Software Center the Task Sequence shows as installing but it never progresses to step 4. I've gone through the log files but they don't give any insight into the issue so I wanted to check if there is any other locations
that the ConfigMgr client may write to that are relevant to the Task Sequence status.
Hope this makes sense.