Task Sequence not installing patches

Hi,
In order to automate the patching process for servers, I have a task sequence that runs at a specific time which triggers a wuauclt.exe scan to check for updates. I have a software update group created with the patches that we want to install. This time
around the patches were available in software center but were not installed. I just would like to clarify what I found as to what may be the reason for this. The task sequence that is deployed has an assignment schedule of 4/11/15 At 03:00 and will run for
a maximum of 120 minutes. Checking the software update group scheduling properties, the software available time is set to 4/11/15 At 12:00.
Would this be why the patches did not install because the software available time was after the task sequence was finished running?
TIA

Hi,
The Software update muse be available to install through a TS as well, that is what I have seen in the past as well.
Regards,
Jörgen
-- My System Center blog ccmexec.com -- Twitter
@ccmexec

Similar Messages

  • A custom task sequence to install software is always listed as Operating System on Software Center

    Hello,
    I have built several custom task sequences to install software in SCCM 2012 R2 CU1 environment, but the type of task sequence is always listed as Operating System on the Software Center. I tried creating a simple task sequence (Task Sequence 1) that contains
    a single restart computer step only and tried deploying it to a test machine. This task sequence is also listed as Operating System. This task sequence fails because this is not the one for OS install and I do not specify a boot image for this task sequence.
    All task sequences that I have created in SCCM 2012 RTM environment are working as expected. All task sequences that I create in SCCM 2012 R2 CU1 are listed as Operating System regardless of its actual type (I upgraded my environment from CM2012 RTM to CM2012
    R2 CU1 last month).
    Here is a test task sequence that contains a single step of restart computer. This is not Operating System install but listed as Operating System. Any thoughts?

    If you use OSD steps in your task sequence you will get this prompt.
    http://social.technet.microsoft.com/Forums/en-US/3eb7569c-0b5a-4b40-86c3-d4f092c70aca/task-sequence-warning?forum=configmanagerosd
    Per Mikko:
    Using any of following steps (and possibly others as well, I did not check all of them) will change the task sequence type from generic to OSD:
    General - Join Domain or Workgroup
    General - Restart Computer (Only "The boot image assigned to this task sequence" option)
    Disks - Format and Partition Disk
    User State - Request State Store
    User State - Release State Store
    Images - Apply Operating System Image
    Images - Setup Windows and ConfigMgr
    Daniel Ratliff | http://www.PotentEngineer.com

  • SCCM 2012 R2 Task Sequence Step "Install Package" downloads all content

    Hello,
    Task Sequence step "Install Package" I have several packages with multiple programs. When I use one of these packages with one of its programs it appears to download all the package content is there a workaround to stop this
    from happening?
    Regards!

    Hi,
    You could change it to run directly from the DP, then it will only use the files it needs and doesn't download anything at all. You will have to make sure that all the content needed by the task seqeunce is copied to the package share otherwise it will not
    work in a task sequence.
    The other would be to split up the package in multiple packages if that is possible.
    Regards,
    Jörgen
    -- My System Center blog ccmexec.com -- Twitter
    @ccmexec

  • Applications Installed through task sequence not showing up in Software Center

    In the task sequence we use for our OSD Windows 7 machine build, we have Custom-Install Application steps which install a number of of our Applications.  Each of these Applications has the "Allow this application to be installed from the Install
    Application task sequence action without being deployed" checkbox checked.  All of the Applications have the following properties set:
    Installation behavior: Install for system
    Logon requirement: Whether or not a user is logged in
    Installation program visibility: Hidden
    When a machine is built using this task sequence, all of the Applications install successfully - they show up in Control Panel\Programs and Features, and they run correctly. However, none of them show up in the Software Center. I'm not seeing anything in
    any of the logs that indicates a problem, and the Software Center remains empty even after running all the client evaluation cycle actions  
    Interestingly, if I add a couple of the newly build machines to a collection, then target deployments for the already installed Applications to that collection, after running the Machine Policy Retrieval and Evaluation Cycle the Applications immediately
    show up in Software Center as installed.
    Does anyone know if Applications installed through a task sequence do not show up in the Software Center by default, or could you give me some troubleshooting tips if this is not normal?
    Thanks for any suggestions!
    SCCM 2012 SP1, Single site, W7 clients

    Why you deploy applications through task sequences? Task sequences are built and meant to be used with OSD, not application deployment.
    To my knowledge, if you have application install step in a task sequence and you deploy that task sequence to a collection of machines, the software center on those machines only sees the task sequence itself, not the applications inside the task sequence.
    If you want your applications to be shown in the software center, change the method of deploying stuff and deploy applications as they're are meant to.

  • Error 16389 running a Task Sequence to install software

    We've run into multiple WinXPProSP3 computers generating error code 16389 when trying to run a TS.  After searching on Google, we found this, 
    http://blogs.technet.com/b/smsandmom/archive/2007/10/29/sccm-2007-task-sequence-fails-drive-letter-not-displayed.aspx
    , which led to another article to modify a RegKey,  HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{4D36E967-E325-11CE-BFC1-08002BE10318} , to add a key of UpperFilters, with a value of PartMgr.  The key WAS missing on the machines with
    the error, and, adding that key and value DOES fix the problem.  This key and value seem to be default for the OS.
    However, searching Google for that RegKey has a LOT of suggestions to delete that key and value, due to issues with USB Thumbdrives and iPods not being seen when plugged in--so, it seems that there may be a conflict.
    Does anyone know of a fix for Error 16389 without having to add that key, if it's going to cause other problems?
    Thanks.

    Hi,
    Will you please past the detailed errors in the smsts.log?
    From your description your are using TS to install software right?
    If so you should first make sure this software package meats the following requirement when it was deployed through TS:
    this program can be installed under local system account.
    this program can be installed without any user interaction (such as: press next button).
    this program will not force computer reboot, it allows sccm ts to manage the reboot.
    If your OSD TS return 16389 exit code, you can try to change the volume license keys. Because once i have seem this error and it was solved by changing the volume license key.
    Hope this will help.
    Thanks

  • 11.2.0.3.0 Required Postinstallation Tasks: Downloading and Installing Patches

    I installed 11.2.0.3.0 on AIX 7.1. The postinstallation tasks begin with downloading and installing patches. I am not sure which patches or PSU to install. Following the directions in the installation guide, I go to My Oracle Support, then to Patches and Updates and specify Oracle Database and IBM AIX 64-bit. For "release" do I select 11.2.0.3.0, or do I select the seven releases from 11.2.0.3.0 - 11.2.0.3.6? If I select all seven the search returns 1293 patches. The instructions are obviously not telling me to download and apply all 1293 patches. I next searched for the most recent PSU and see that PSU 11.2.0.3.6 was published on April 17, 2013. What is the right thing to apply? Should I download only PSU 11.2.0.3.6 and apply that, or should I do something else not described here?
    Thanks,
    Bill

    You should apply the latest 11.2.0.3 PSU (currently 11.2.0.3.6) - you do not have to apply all of the one-off patches
    See MOS Doc 753736.1
    HTH
    Srini

  • Error code 1603 While deploying symantec Endpoint protection through MDT Task sequence as Install a single Application

    Hi ,
    Am getting Error code 1603 (fatal error during installation) while deploying the SEP through MDT task sequence . am not getting such issue regularly but some time am getting and need to be fixed.
    Shailendra
    Shailendra Dev

    Hi,
    I am Chetan Savade from Symantec Technical Support Team.
    Logs can provide more detail info, as said earlier by MrBrooks provide SEP_Inst.log from the affected machine.
    Adding Windows defender related articles if they can help you:
    Keeping Windows Defender Enabled when Deploying and Installing Symantec Endpoint Protection Client package.
    http://www.symantec.com/docs/TECH168501
    Windows Defender startup type registry value is Manual instead of Disabled after installing Symantec Endpoint Protection
    http://www.symantec.com/docs/TECH206793
    How to prepare a Symantec Endpoint Protection 12.1.x client for cloning
    http://www.symantec.com/docs/HOWTO54706
    Best Regards,
    Chetan

  • MDT Capture Task Sequence not working correctly

    Hello All<o:p></o:p>
    I need some help to tell me what I am doing wrong. I am using Hyper V and trying to capture a image of Windows 7 x64. From within the OS I run the
    Litetouch.wsf from the deployment share. I get the normal MDT Wizard windows. I pick my capture task sequence and everything looks like it is running fine sys prep happens and I but back into windows PE I start to process the rules again and I am taken
    back to the Select task sequence screen in WinPE.  If I pick the capture task sequence again the deployment fails. <o:p></o:p>

    (posting for anyone else that found this page, this was my fix)
    I had the same problem as the initial poster apart from what I wanted to capture was a 'real' pc.  The reason my 'capture' task sequence wasn't booting into WinPE from the local disk and continuing on with the capture was because the local disk was
    being wiped when the boot wim - LiteTouchPE_x64.wim, was being run. 
    A few weeks prior to me wanting to capture a PC I'd been working out how to stop the occasional error when you boot a PC off the WDS server - “The Task Sequence Has Been Suspended”.  I was particularly interested in stopping this error as I want to
    remotely start a Win7 install on a PC, this error would stop the install happening but I wouldn't see this error and end up visiting the PC only to find the install hadn't really started.  After googling around, I found a page that explains how to edit
    the unattend.xml file in the boot image - LiteTouchPE_x64.wim, in the xml file to run the command wscript.exe X:\Deploy\Scripts\LTICleanup.wsf.  Sounded good so I done what the page said (myitforum.com/cs2/blogs/cnackers/archive/2010/10/20/microsoft-deployment-toolkit-lite-touch-lti-the-task-sequence-has-been-suspended.aspx)
    but it didn't stop the message appearing.  In the end I fixed this problem by adding the line 'SkipWizard=YES' in my customsettings.ini file.  I didn't remove the LTICleanup.wsf from unattend.xml, it didn't seem to do any harm, that was until I tried
    to capture a PC.
    When I ran though my 'sysprep and capture' task sequence, the PC would sysprep ok and then reboot, ready to capture it.  Instead of the 'capturing a WIM file' sequence I was expecting to see, I, like the original posted got shown the list of available
    task sequences window.  If you try again to run the capture sequence, it will fail as this has to be started in a running Windows environment, not in WinPE.  After several hours wondering what is going wrong, I dawned on me what was going wrong,
    the LTICleanup.wsf was being run when the boot image was being run and wiping my disk, a disk that was ready to run an existing task sequence, the capture sequence, no wonder it was failing.  Removing the LTICleanup.wsf command from within unattend.xml
    or rebuilding the boot image (by running 'Update Deployment Share' within MDT 2010) fixed the problem, the capture now worked.
    Hopefully this will help someone else like me who was wondering what was going wrong with a capture.

  • Orchestrator and SCCM 2012 integration: run task sequence and install assigned applications/packages?

    Dear,
    We do not have Orchestrator running in our SCCM 2012 R2 environment. Though I wonder if we could accomplish the following scenario with it:
    Task sequence Windows 7 => Orchestrator step which queries assigned installations to the computer object and installs them one by one.
    Could you advise?
    Kind regards,
    Stev.
    SteveWonB

    > > Define "assigned to computer objects". How is this done technically?
    Well, computer objects are members of collections via AD memberships, like the collection "W7-Google-Chrome" (exists of 100 computer objects).
    Deploy of packages is done to these collections. So a computer member of  "W7-Google-Chrome"  will automatically get Google Chrome.
    Some computers are member of 30 collections, some of 80.
    Goal is to have the task sequence run all applications/packages assigned (with their reboots if needed).
    Kind regards,
    Steven
    SteveWonB

  • MDT 2012 - Task Sequence Not Completing

    I'm a complete novice with MDT 2012, but I have had pretty good luck getting a deployment for Server 2008 R2.
    I have a reference system, and I do a very vanilla sysprep and capture using the template task sequence with no changes.
    My deployment has a few app installs and other configuration items, but nothing too exotic.
    My problem is this: during deployment, after applying the system from WinPE, I perform the final reboot. At this point, the expected action is for an autologon to take place, and for the local Administrator account to run c:\Litetouch.vbs, which does some final
    cleanup and a few tasks that require the target system to be running.
    This isn't happening on my system. And a look at the registry shows that the autologon stuff has not been set up, so it won't ever happen. It's not a matter of having an incorrect account, or a count of 0, none of the autologon registry keys are even present.
    In trying to solve this (I believe it worked when I first started!) I've stripped down my deployment to a pair of task sequences that have no customization
    at all in either the capture or the deployment task sequences, and still no luck. So I believe that something has changed in my reference system - but I unfortunately can't roll back.
    What is driving me a little nuts is that I can't tell when that autologon information is supposed to be inserted in the registry. There is code in Litetouch.wsf that appears to do it, in function PopulateAutoAdminLogon, but I can't come up with a scenario in
    which this function gets called. I am guessing that perhaps sysprep does it when creating the WIM, but I can't seem to find good information on that.
    I've done a lot of searching on this, and unfortunately the answer space is cluttered with people who have a similar sounding but completely different problem - they want their deployed system to do an autologon, and after deployment their system comes up with
    the logon screen instead of doing what they want. I've seen a few people post similar problems to mine, but nobody has received an answer. This one is pretty close, it suggest I might have a group policy item that disables the local admin account, but I don't
    think it hits the mark for me.
    http://social.technet.microsoft.com/Forums/en-US/mdt/thread/e625aa88-2415-4a2a-9e79-ac6b37119c27
    So in a nutshell: when deploying a system using MDT 2012, at what point do the autologon items from unattend.xml stuffed into the registry for use after state restore/reboot in the task sequence? And what can go wrong with that?
    - Mark

    Same here, can't find any solution though. Did you ever work it out? 

  • Format and Partition Task Sequence Not Working As Exprected When Using USB Media

    Task looks like this. 
    Had been working on PXE based task sequence, but when I use USB media, it only makes a single partition that is around the size of the USB thumb drive.
    How does this need to be changed so that it makes a C drive partition that is 80% of the total local disk space and a D drive that uses the remaining disk space when using USB boot media?

    If you choose to create a "custom" partition configuration like the one above, then you are responsible for creating any extra required partitions like a BitLocker boot partition.
    Additionally, if you are deploying on a uEFI machine, then you will also need to create the correct uEFI partitions.
    Generally I discourage creating extra partitions.
    Keith Garner - Principal Consultant [owner] -
    http://DeploymentLive.com

  • VBScript in Task Sequence not working

    Can someone let me know if I am doing this right or wrong?
    I have a vbscript that I packaged up. No program attached to it, just the folder itself.
    In the task sequence, I have a Run Command Line.
    I point it to the package & disable 64-bit file system redirection
    Command line: cscript outlook.vbs
    Is this correct or am I doing this wrong?

    check the SMSTS.log file on the client errors using the CMtrace log viewer.
    Cheers
    Paul | sccmentor.wordpress.com
    I don't see any errors.
    Parsing step node: Microsoft Outook 2013 Desktop Icon TSManager 8/5/2014 10:53:21 PM 2672 (0x0A70)
    Description: TSManager 8/5/2014 10:53:21 PM 2672 (0x0A70)
    ContinueOnError: TSManager 8/5/2014 10:53:21 PM 2672 (0x0A70)
    SuccessCodeList: 0 3010 TSManager 8/5/2014 10:53:21 PM 2672 (0x0A70)
    (__hrMethodRetVal == ((HRESULT)0L)) || (bFailIfMissing == false), HRESULT=80070002 (e:\NTS_SCCM_RELEASE\sms\common\inc\ccmxml.h,582) TSManager 8/5/2014 10:53:21 PM 2672 (0x0A70)
    No condition is associated with the step. TSManager 8/5/2014 10:53:21 PM 2672 (0x0A70)
    Disable: TSManager 8/5/2014 10:53:21 PM 2672 (0x0A70)
    Run in attribute: WinPEandFullOS TSManager 8/5/2014 10:53:21 PM 2672 (0x0A70)
    Timeout: TSManager 8/5/2014 10:53:21 PM 2672 (0x0A70)
    DefaultVarlist found TSManager 8/5/2014 10:53:21 PM 2672 (0x0A70)
    Variable name: SMSTSDisableWow64Redirection TSManager 8/5/2014 10:53:21 PM 2672 (0x0A70)
    Variable name: _SMSTSRunCommandLineAsUser TSManager 8/5/2014 10:53:21 PM 2672 (0x0A70)
    Action command line: smsswd.exe /run:JH100170 cscript outlook.vbs TSManager 8/5/2014 10:53:21 PM 2672 (0x0A70)
    Adding instruction at 131 TSManager 8/5/2014 10:53:21 PM 2672 (0x0A70)
    Processed all elements TSManager 8/5/2014 10:53:21 PM 2672 (0x0A70)
    Adding end group instruction at 132 TSManager 8/5/2014 10:53:21 PM 2672 (0x0A70)
    The next instruction after group will be at 133 TSManager 8/5/2014 10:53:21 PM 2672 (0x0A70)
    Parsing step node: Restore Groups TSManager 8/5/2014 10:53:21 PM 2672 (0x0A70)
    Description: TSManager 8/5/2014 10:53:21 PM 2672 (0x0A70)
    ContinueOnError: TSManager 8/5/2014 10:53:21 PM 2672 (0x0A70)
    SuccessCodeList: 0 3010 TSManager 8/5/2014 10:53:21 PM 2672 (0x0A70)
    A condition is associated with the step found TSManager 8/5/2014 10:53:21 PM 2672 (0x0A70)
    Found and operator. TSManager 8/5/2014 10:53:21 PM 2672 (0x0A70)
    There are 1 operands TSManager 8/5/2014 10:53:21 PM 2672 (0x0A70)
    **Processing expression node TSManager 8/5/2014 10:53:21 PM 2672 (0x0A70)

  • Task sequence not deploying the client

    Guys,
    I have a TS deploying an operating system.  This includes deploying the client via the Configuration Manager Client Package.
    I have noticed that the client is not being deployed at the end of the TS.  The Configuration Manager Client Package has been successfully deployed to my dp's .  Only thing I have noticed is that the package does not have any programs associated
    with it.
    Any thoughts ?

    Hi,
    As Peter mentioned, Maybe the log can give us some clues.
    Also, please refer to the link below:
    Setup Windows and ConfigMgr          
    http://technet.microsoft.com/en-us/library/hh846237.aspx#BKMK_SetupWindowsandConfigMgr
    We
    are trying to better understand customer views on social support experience, so your participation in this
    interview project would be greatly appreciated if you have time.
    Thanks for helping make community forums a great place.

  • Client not installing completing via OSD Task Sequence - Standalone Media

    Dear All,
    Facing this issue that i have made Standalone media for OS Deployment but after installing OS, SCCM Client doesn't install completely but when try to install from network with same Task Sequence Client installed successfully.
    One more thing while installing from media, machine is connected on LAN.
    For Further Reference Snapshots are attached.
    As in log its stat that installation was processed but there was no ccmsetup.exe in process neither its installed correctly
    ======>Begin Processing request: "2097152793", machine name: "WIN7VERIFY"
    SMS_CLIENT_CONFIG_MANAGER 11/10/2014 3:52:21 PM
    10472 (0x28E8)
    Execute query exec [sp_IsMPAvailable] N'KHI'
    SMS_CLIENT_CONFIG_MANAGER 11/10/2014 3:52:21 PM
    10472 (0x28E8)
    ---> Trying each entry in the SMS Client Remote Installation account list
    SMS_CLIENT_CONFIG_MANAGER 11/10/2014 3:52:21 PM
    10472 (0x28E8)
    ---> Attempting to connect to administrative share '\\WIN7VERIFY\admin$' using account ''
    SMS_CLIENT_CONFIG_MANAGER 11/10/2014 3:52:21 PM
    10472 (0x28E8)
    ---> Connected to administrative share on machine WIN7VERIFY using account 'uead\'
    SMS_CLIENT_CONFIG_MANAGER 11/10/2014 3:52:21 PM
    10472 (0x28E8)
    ---> Attempting to make IPC connection to share <\\WIN7VERIFY\IPC$>
    SMS_CLIENT_CONFIG_MANAGER 11/10/2014 3:52:21 PM
    10472 (0x28E8)
    ---> Searching for SMSClientInstall.* under '\\WIN7VERIFY\admin$\'
    SMS_CLIENT_CONFIG_MANAGER 11/10/2014 3:52:21 PM
    10472 (0x28E8)
    ---> System OS version string "6.1.7601" converted to 6.10
    SMS_CLIENT_CONFIG_MANAGER 11/10/2014 3:52:22 PM
    10472 (0x28E8)
    ---> Mobile client on the target machine has the same version, and 'forced' flag is not turned on. Not processing this CCR
    SMS_CLIENT_CONFIG_MANAGER 11/10/2014 3:52:22 PM
    10472 (0x28E8)
    ---> Deleting SMS Client Install Lock File '\\WIN7VERIFY\admin$\SMSClientInstall.KHI'
    SMS_CLIENT_CONFIG_MANAGER 11/10/2014 3:52:22 PM
    10472 (0x28E8)
    Execute query exec [sp_CP_SetLastErrorCode] 2097152793, 120
    SMS_CLIENT_CONFIG_MANAGER 11/10/2014 3:52:22 PM
    10472 (0x28E8)
    ---> Skipped request "2097152793", machine name "WIN7VERIFY".
    SMS_CLIENT_CONFIG_MANAGER 11/10/2014 3:52:22 PM
    10472 (0x28E8)
    Deleted request "2097152793", machine name "WIN7VERIFY"
    SMS_CLIENT_CONFIG_MANAGER 11/10/2014 3:52:22 PM
    10472 (0x28E8)
    Execute query exec [sp_CP_SetPushRequestMachineStatus] 2097152793, 3
    SMS_CLIENT_CONFIG_MANAGER 11/10/2014 3:52:22 PM
    10472 (0x28E8)
    Execute query exec [sp_CP_SetLatest] 2097152793, N'11/10/2014 10:52:22', 1
    SMS_CLIENT_CONFIG_MANAGER 11/10/2014 3:52:22 PM
    10472 (0x28E8)
    <======End request: "2097152793", machine name: "WIN7VERIFY".
    SMS_CLIENT_CONFIG_MANAGER 11/10/2014 3:52:22 PM
    10472 (0x28E8)
    REGARDS DANISH DANIE

    The attached log file is related to a client push, I'm not sure how that is related to your problem. When you're having problems with the client installation during a task sequence deployment, please check the smsts log file and, if available, the ccmsetup
    log file (these log files should be available on the client itself).
    My Blog: http://www.petervanderwoude.nl/
    Follow me on twitter: pvanderwoude

  • MDT - Custom Reference Image does not work with Task Sequence, normal Windows 7 Enterprise Iso media works fine.

    Hi,
    Our MDT server is acting strange!
    I have previously had this system running without problem - i could both capture and deploy computers as is and no changes have been made to mdt.
    But my latest capture does not work. When i capture my reference maching in my VM environment it completes without errors and i can import the latest wim file.
    When i deploy the tast sequence, it install the custom Wim image, but it ends up with "login" screen as the administrator i have entered for the capture/deploy sequence, but it goes to stop at this point and applications is not installed.
    If i change the ISO in the task sequence under Install OS step, to a clean Win7 install media then the capture completes and install applications.
    I have also tried to:
    Capture reference without password
    Capture reference without Windows updates
    Customsettings.ini, bootstrap, BDD.log and SMSTS.log to be found here: https://onedrive.live.com/redir?resid=ED5029A20300B814!365&authkey=!AALV1b2ubD0laEE&ithint=folder%2cini
    Hope you will be able to assist,
    Regards,
    Anders

    if you have noticed your smsts.log, there is same error multiple - 
    Executing in non SMS standalone mode. Ignoring send a task execution status message request
    TSManager 1/23/2015 12:50:37 PM
    1656 (0x0678)
    User did not specify local data drive TSManager
    1/23/2015 12:50:37 PM 1656 (0x0678)
    Volume A:\ is not a fixed hard drive TSManager
    1/23/2015 12:50:37 PM 1656 (0x0678)
    Volume D:\ is not a fixed hard drive TSManager
    1/23/2015 12:50:37 PM 1656 (0x0678)
    Volume X:\ is not a fixed hard drive TSManager
    1/23/2015 12:50:37 PM 1656 (0x0678)
    Volume Z:\ is not a fixed hard drive TSManager
    1/23/2015 12:50:37 PM 1656 (0x0678)
    TSM root drive = TSManager
    1/23/2015 12:50:37 PM 1656 (0x0678)
    We do not find an available volume to store the local data path
    TSManager 1/23/2015 12:50:37 PM
    1656 (0x0678)
    Set a global environment variable _SMSTSNextInstructionPointer=1
    TSManager 1/23/2015 12:50:37 PM
    1656 (0x0678)
    Set a TS execution environment variable _SMSTSNextInstructionPointer=1
    TSManager 1/23/2015 12:50:37 PM
    1656 (0x0678)
    Set a global environment variable _SMSTSInstructionStackString=0
    TSManager 1/23/2015 12:50:37 PM
    1656 (0x0678)
    Set a TS execution environment variable _SMSTSInstructionStackString=0
    TSManager 1/23/2015 12:50:37 PM
    1656 (0x0678)
    Save the current environment block TSManager
    1/23/2015 12:50:37 PM 1656 (0x0678)
    pszPath[0] != L'\0', HRESULT=80070057 (c:\qfe\nts_sms_fre\sms\framework\core\ccmcore\path.cpp,58)
    TSManager 1/23/2015 12:50:37 PM
    1656 (0x0678)
    Filesystem::Path::Add(sEnvPath, EnvDataFileName, sEnvPath), HRESULT=80070057 (e:\nts_sms_fre\sms\framework\tscore\environmentlib.cpp,639)
    TSManager 1/23/2015 12:50:37 PM
    1656 (0x0678)
    Failed to save environment to  (80070057)
    TSManager 1/23/2015 12:50:37 PM
    1656 (0x0678)
    TS::Environment::SharedEnvironment.saveEnvironment(szPath), HRESULT=80070057 (e:\nts_sms_fre\sms\client\tasksequence\executionengine\executionenv.cxx,842)
    TSManager 1/23/2015 12:50:37 PM
    1656 (0x0678)
    Failed to save the current environment block. This is usually caused by a problem with the program. Please check the Microsoft Knowledge Base to determine if this is a known issue or contact Microsoft Support Services for further assistance.
    The parameter is incorrect. (Error: 80070057; Source: Windows)
    TSManager 1/23/2015 12:50:37 PM
    1656 (0x0678)
    SaveEnvironment(), HRESULT=80070057 (e:\nts_sms_fre\sms\client\tasksequence\executionengine\executionenv.cxx,420)
    TSManager 1/23/2015 12:50:37 PM
    1656 (0x0678)
    Failed to persist execution state. Error 0x(80070057)
    TSManager 1/23/2015 12:50:37 PM
    1656 (0x0678)
    Failed to save execution state and environment to local hard disk
    TSManager 1/23/2015 12:50:37 PM
    1656 (0x0678)
    Start executing an instruciton. Instruction name: Gather local only. Instruction pointer: 1
    TSManager 1/23/2015 12:50:37 PM
    1656 (0x0678)
    Set a global environment variable _SMSTSCurrentActionName=Gather local only
    TSManager 1/23/2015 12:50:37 PM
    1656 (0x0678)
    Set a global environment variable _SMSTSNextInstructionPointer=1
    TSManager 1/23/2015 12:50:37 PM
    1656 (0x0678)
    what about the mass storage driver in your boot image, is it updated?
    Md.Waseem Please remember to click “Mark as Answer” on the post that helps you. Thank you.

Maybe you are looking for