none
Install Windows 10 1803 RRS feed

  • Question

  • I just download and imported windows 10 1803 into our sccm and then attched that wim to existing TS but for some reason its not fully building the PC. It doesnt fails, it does get successfully install the OS but no application or driver/app remove pwershell runs.

    The step (Dell Latitude 3490 Drivers) must be running in WinPE    TSManager    18/10/2018 17:22:59    4920 (0x1338)
    !--------------------------------------------------------------------------------------------!    TSManager    18/10/2018 17:22:59    4920 (0x1338)
    Failed to run the action: Dell Latitude 3490 Drivers.
    The request is not supported. (Error: 80070032; Source: Windows)    TSManager    18/10/2018 17:22:59    4920 (0x1338)
    Not in SSL    TSManager    18/10/2018 17:22:59    4920 (0x1338)
    Set a global environment variable _SMSTSLastActionRetCode=50    TSManager    18/10/2018 17:22:59    4920 (0x1338)
    Set a global environment variable _SMSTSLastActionSucceeded=false    TSManager    18/10/2018 17:22:59    4920 (0x1338)
    Clear local default environment    TSManager    18/10/2018 17:22:59    4920 (0x1338)
    Let the parent group (Dell) decides whether to continue execution    TSManager    18/10/2018 17:22:59    4920 (0x1338)
    Let the parent group (Driver Management) decide whether to continue execution    TSManager    18/10/2018 17:22:59    4920 (0x1338)
    Let the parent group (Setup Operating System) decide whether to continue execution    TSManager    18/10/2018 17:22:59    4920 (0x1338)
    The execution of the group (Setup Operating System) has failed and the execution has been aborted. An action failed.
    Operation aborted (Error: 80004004; Source: Windows)    TSManager    18/10/2018 17:22:59    4920 (0x1338)
    Failed to run the last action: Dell Latitude 3490 Drivers. Execution of task sequence failed.
    The request is not supported. (Error: 00000032; Source: Windows)    TSManager    18/10/2018 17:22:59    4920 (0x1338)
    Not in SSL    TSManager    18/10/2018 17:22:59    4920 (0x1338)
    Task Sequence Engine failed! Code: enExecutionFail    TSManager    18/10/2018 17:37:59    4920 (0x1338)
    ****************************************************************************    TSManager    18/10/2018 17:37:59    4920 (0x1338)
    Task sequence execution failed with error code 80004005    TSManager    18/10/2018 17:37:59    4920 (0x1338)
    Cleaning Up.    TSManager    18/10/2018 17:37:59    4920 (0x1338)
    Removing Authenticator    TSManager    18/10/2018 17:37:59    4920 (0x1338)
    Cleaning up task sequence folder    TSManager    18/10/2018 17:37:59    4920 (0x1338)
    Unable to delete file C:\_SMSTaskSequence\TSEnv.dat (0x80070005). Continuing.    TSManager    18/10/2018 17:37:59    4920 (0x1338)
    Failed to delete directory 'C:\_SMSTaskSequence'    TSManager    18/10/2018 17:37:59    4920 (0x1338)
    SetNamedSecurityInfo() failed.    TSManager    18/10/2018 17:37:59    4920 (0x1338)
    SetObjectOwner() failed. 0x80070005.    TSManager    18/10/2018 17:37:59    4920 (0x1338)
    RemoveFile() failed for C:\_SMSTaskSequence\TSEnv.dat. 0x80070005.    TSManager    18/10/2018 17:37:59    4920 (0x1338)
    RemoveDirectoryW failed (0x80070091) for C:\_SMSTaskSequence    TSManager    18/10/2018 17:37:59    4920 (0x1338)
    Deleting volume ID file C:\_SMSTSVolumeID.7159644d-f741-45d5-ab29-0ad8aa4771ca ...    TSManager    18/10/2018 17:37:59    4920 (0x1338)
    Successfully unregistered Task Sequencing Environment COM Interface.    TSManager    18/10/2018 17:37:59    4920 (0x1338)

    Removed 1 instance of SMS_MaintenanceTaskRequests for tasksequence.    TSManager    18/10/2018 17:37:59    4920 (0x1338)
    Failed to delete registry value HKLM\Software\Microsoft\SMS\Task Sequence\Package. Error code 0x80070002    TSManager    18/10/2018 17:38:06    4920 (0x1338)
    Start to cleanup TS policy    TSManager    18/10/2018 17:38:06    4920 (0x1338)
    End Task Sequence policy cleanup    TSManager    18/10/2018 17:38:06    4920 (0x1338)
    Start to evaluate TS policy with lock    TSManager    18/10/2018 17:38:06    4920 (0x1338)
    Updating settings in \\.\root\ccm\policy\machine\actualconfig    TSManager    18/10/2018 17:38:06    4920 (0x1338)
    Total RequestedConfig policy instance(s) : 526    TSManager    18/10/2018 17:38:06    4920 (0x1338)
    New/Changed ActualConfig policy instance(s) : 1    TSManager    18/10/2018 17:38:06    4920 (0x1338)
    Raising event:
    instance of CCM_PolicyAgent_SettingsEvaluationComplete
    {
        ClientID = "GUID:7b1c980f-8682-478c-8966-26339291b4c9";
        DateTime = "20181018163806.355000+000";
        PolicyNamespace = "\\\\.\\root\\ccm\\policy\\machine\\actualconfig";
        ProcessID = 900;
        ThreadID = 4920;
    };
        TSManager    18/10/2018 17:38:06    4920 (0x1338)
    Status Agent hasn't been initialized yet. Attempting to create pending event.    TSManager    18/10/2018 17:38:06    4920 (0x1338)
    Raising pending event:
    instance of CCM_PolicyAgent_SettingsEvaluationComplete
    {
        ClientID = "GUID:7b1c980f-8682-478c-8966-26339291b4c9";
        DateTime = "20181018163806.355000+000";
        PolicyNamespace = "\\\\.\\root\\ccm\\policy\\machine\\actualconfig";
        ProcessID = 900;
        ThreadID = 4920;
    };
        TSManager    18/10/2018 17:38:06    4920 (0x1338)
    Successfully submitted pending event to WMI.    TSManager    18/10/2018 17:38:06    4920 (0x1338)
    End TS policy evaluation    TSManager    18/10/2018 17:38:06    4920 (0x1338)
    Policy evaluation initiated    TSManager    18/10/2018 17:38:06    4920 (0x1338)
    RegQueryValueExW is unsuccessful for Software\Microsoft\SMS\Task Sequence, SMSTSEndProgram    TSManager    18/10/2018 17:38:06    4920 (0x1338)
    GetTsRegValue() is unsuccessful. 0x80070002.    TSManager    18/10/2018 17:38:06    4920 (0x1338)
    End program:     TSManager    18/10/2018 17:38:06    4920 (0x1338)
    Error Task Sequence Manager failed to execute task sequence. Code 0x80004005    TSManager    18/10/2018 17:38:06    4920 (0x1338)
    Sending error status message    TSManager    18/10/2018 17:38:06    4920 (0x1338)
    Not in SSL    TSManager    18/10/2018 17:38:06    4920 (0x1338)
    Finalize logging request ignored from process 900    TSManager    18/10/2018 17:38:06    4920 (0x1338)
    Waiting for CcmExec service to be fully operational    TSManager    18/10/2018 17:38:06    4920 (0x1338)
    CcmExec service is up and fully operational    TSManager    18/10/2018 17:39:26    4920 (0x1338)
    Current Assigned Management Point is SCCM.Domian.local with Version 8692 and Capabilities: <Capabilities SchemaVersion="1.0"><Property Name="SSLState" Value="0"/></Capabilities>    ClientLocation    18/10/2018 17:39:26    4920 (0x1338)
    Successfully connected to MP SCCM.Domian.local:80    TSManager    18/10/2018 17:39:26    4920 (0x1338)
    Attempting to release request using {1BC1A3B9-EDEE-4E86-AEAE-35CCFE84A400}    TSManager    18/10/2018 17:39:26    4920 (0x1338)
    ReleaseRequest failed with error code 0x87d00317    TSManager    18/10/2018 17:39:26    4920 (0x1338)
    Task Sequence Manager could not release active TS request. code 87D00317    TSManager    18/10/2018 17:39:26    4920 (0x1338)
    Process completed with exit code 2147500037    TSMBootstrap    18/10/2018 17:39:26    2472 (0x09A8)


    • Edited by lalaJee Thursday, October 18, 2018 5:00 PM
    Thursday, October 18, 2018 4:59 PM

All replies

  • The first line of your included snippet shows an error:

    > The step (Dell Latitude 3490 Drivers) must be running in WinPE

    You need to apply the drivers from within WinPE before rebooting to the "currently installed OS" for the Setup Windows and ConfigMgr step.


    Nathan Ziehnert
    Senior Lead Consultant | Catapult Systems

    Blog | @theznerd | LinkedIn

    Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.


    • Edited by The Z-Nerd Thursday, October 18, 2018 5:07 PM
    Thursday, October 18, 2018 5:06 PM
  • Hi Nathan, I'm not reboot after the os.

    Saturday, October 20, 2018 9:50 AM
  • Your Driver Steps are after the "Setup Windows and Configuration Manager" Step but they have to be before this step because this is the WinPE Phase.
    Saturday, October 20, 2018 2:01 PM
  • I should apply drivers after "Apply Network Settings" and then do all of the software or modify the system.


    Saturday, October 20, 2018 7:00 PM
  • Apply drivers after applying OS and before “Setup Windows and Configuration manager” steps, add reboot to installed OS before the Setup Windows step.

    Nathan Ziehnert
    Senior Lead Consultant | Catapult Systems

    Blog | @theznerd | LinkedIn

    Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.

    Saturday, October 20, 2018 7:03 PM
  • I made changes to TS but still its not install any of the application/bitlocker/bios/custimise windows

    Monday, October 22, 2018 12:29 PM
  • Successfully completed the action (Setup Windows and Configuration Manager) with the exit win32 code 0    TSManager    22/10/2018 10:56:48    6016 (0x1780)
    Not in SSL    TSManager    22/10/2018 10:56:48    6016 (0x1780)
    Set a global environment variable _SMSTSLastActionRetCode=0    TSManager    22/10/2018 10:56:48    6016 (0x1780)
    Set a global environment variable _SMSTSLastActionSucceeded=true    TSManager    22/10/2018 10:56:48    6016 (0x1780)
    Clear local default environment    TSManager    22/10/2018 10:56:48    6016 (0x1780)
    Updated security on object C:\_SMSTaskSequence.    TSManager    22/10/2018 10:56:48    6016 (0x1780)
    Set a global environment variable _SMSTSNextInstructionPointer=65    TSManager    22/10/2018 10:56:48    6016 (0x1780)
    Set a TS execution environment variable _SMSTSNextInstructionPointer=65    TSManager    22/10/2018 10:56:48    6016 (0x1780)
    Set a global environment variable _SMSTSInstructionStackString=53    TSManager    22/10/2018 10:56:48    6016 (0x1780)
    Set a TS execution environment variable _SMSTSInstructionStackString=53    TSManager    22/10/2018 10:56:48    6016 (0x1780)
    Save the current environment block    TSManager    22/10/2018 10:56:48    6016 (0x1780)
    Set a global environment variable _SMSTSLastActionRetryCount=0    TSManager    22/10/2018 10:56:48    6016 (0x1780)
    Start executing an instruction. Instruction name: Dell Configuration. Instruction pointer: 65    TSManager    22/10/2018 10:56:48    6016 (0x1780)
    Set a global environment variable _SMSTSCurrentActionName=Dell Configuration    TSManager    22/10/2018 10:56:48    6016 (0x1780)
    Set a global environment variable _SMSTSNextInstructionPointer=65    TSManager    22/10/2018 10:56:48    6016 (0x1780)
    Evaluating an AND expression    TSManager    22/10/2018 10:56:48    6016 (0x1780)
    Evaluating a WMI condition expression    TSManager    22/10/2018 10:56:48    6016 (0x1780)
    Expand a string: root\cimv2    TSManager    22/10/2018 10:56:48    6016 (0x1780)
    Expand a string: SELECT * FROM Win32_ComputerSystem WHERE Manufacturer like ‘%DELL%’    TSManager    22/10/2018 10:56:48    6016 (0x1780)
    Error enumerating WMI instances returned from WQL query.
    Invalid query (Error: 80041017; Source: WMI)    TSManager    22/10/2018 10:56:48    6016 (0x1780)
    Failed to evaluate a WMI expression. Error 0x(80041017)    TSManager    22/10/2018 10:56:48    6016 (0x1780)
    Failed to evaluate an expression. Error 0x(80041017)    TSManager    22/10/2018 10:56:48    6016 (0x1780)
    Failed to evaluate an AND expression. Error 0x(80041017)    TSManager    22/10/2018 10:56:48    6016 (0x1780)
    Failed to evaluate an expression. Error 0x(80041017)    TSManager    22/10/2018 10:56:48    6016 (0x1780)
    Error 0x80041017 in evaluating the condition for the group (Dell Configuration)    TSManager    22/10/2018 10:56:48    6016 (0x1780)
    Not in SSL    TSManager    22/10/2018 10:56:48    6016 (0x1780)
    Let the parent group (Setup Operating System) decide whether to continue execution    TSManager    22/10/2018 10:56:48    6016 (0x1780)
    The execution of the group (Setup Operating System) has failed and the execution has been aborted. An action failed.
    Operation aborted (Error: 80004004; Source: Windows)    TSManager    22/10/2018 10:56:48    6016 (0x1780)
    Failed to run the last action: Dell Configuration. Execution of task sequence failed.
    The operation completed successfully. (Error: 00000000; Source: Windows)    TSManager    22/10/2018 10:56:48    6016 (0x1780)
    Not in SSL    TSManager    22/10/2018 10:56:48    6016 (0x1780)
    Task Sequence Engine failed! Code: enExecutionFail    TSManager    22/10/2018 11:11:51    6016 (0x1780)
    ****************************************************************************    TSManager    22/10/2018 11:11:51    6016 (0x1780)
    Task sequence execution failed with error code 80004005    TSManager    22/10/2018 11:11:51    6016 (0x1780)
    Cleaning Up.    TSManager    22/10/2018 11:11:51    6016 (0x1780)
    Removing Authenticator    TSManager    22/10/2018 11:11:51    6016 (0x1780)
    Cleaning up task sequence folder    TSManager    22/10/2018 11:11:51    6016 (0x1780)
    Unable to delete file C:\_SMSTaskSequence\TSEnv.dat (0x80070005). Continuing.    TSManager    22/10/2018 11:11:52    6016 (0x1780)
    Failed to delete directory 'C:\_SMSTaskSequence'    TSManager    22/10/2018 11:11:52    6016 (0x1780)
    SetNamedSecurityInfo() failed.    TSManager    22/10/2018 11:11:52    6016 (0x1780)
    SetObjectOwner() failed. 0x80070005.    TSManager    22/10/2018 11:11:52    6016 (0x1780)
    RemoveFile() failed for C:\_SMSTaskSequence\TSEnv.dat. 0x80070005.    TSManager    22/10/2018 11:11:52    6016 (0x1780)
    RemoveDirectoryW failed (0x80070091) for C:\_SMSTaskSequence    TSManager    22/10/2018 11:11:52    6016 (0x1780)
    Deleting volume ID file C:\_SMSTSVolumeID.7159644d-f741-45d5-ab29-0ad8aa4771ca ...    TSManager    22/10/2018 11:11:52    6016 (0x1780)
    Successfully unregistered Task Sequencing Environment COM Interface.    TSManager    22/10/2018 11:11:52    6016 (0x1780)
    Executing command line: "C:\WINDOWS\CCM\TsProgressUI.exe" /Unregister    TSManager    22/10/2018 11:11:52    6016 (0x1780)
    ==========[ TsProgressUI started in process 788 ]==========    TsProgressUI    22/10/2018 11:11:52    3316 (0x0CF4)
    Command line: "C:\WINDOWS\CCM\TsProgressUI.exe" /Unregister    TsProgressUI    22/10/2018 11:11:52    3316 (0x0CF4)
    Unregistering COM classes    TsProgressUI    22/10/2018 11:11:52    3316 (0x0CF4)
    Unregistering class objects    TsProgressUI    22/10/2018 11:11:52    3316 (0x0CF4)
    Shutdown complete.    TsProgressUI    22/10/2018 11:11:52    3316 (0x0CF4)
    Process completed with exit code 0    TSManager    22/10/2018 11:11:52    6016 (0x1780)
    Successfully unregistered TS Progress UI.    TSManager    22/10/2018 11:11:52    6016 (0x1780)
    Trying to restore client to the state it can be managed    TSManager    22/10/2018 11:11:52    6016 (0x1780)
    CCMExec service startup type is set to enabled    TSManager    22/10/2018 11:11:52    6016 (0x1780)
    Modifying CCMExec Service to auto start.    TSManager    22/10/2018 11:11:52    6016 (0x1780)
    CCMExec Service started    TSManager    22/10/2018 11:11:52    6016 (0x1780)
    Waiting for CcmExec service to be fully operational    TSManager    22/10/2018 11:11:52    6016 (0x1780)
    CcmExec service is up and fully operational    TSManager    22/10/2018 11:11:52    6016 (0x1780)
    Current Assigned Management Point is sccm.Domian.local with Version 8692 and Capabilities: <Capabilities SchemaVersion="1.0"><Property Name="SSLState" Value="0"/></Capabilities>    ClientLocation    22/10/2018 11:11:52    6016 (0x1780)
    Successfully connected to MP sccm.Domian.local:80    TSManager    22/10/2018 11:11:52    6016 (0x1780)
    Cleaning up any active TS requests in WMI.    TSManager    22/10/2018 11:11:52    6016 (0x1780)
    No instances of CCM_TSExecutionRequest found.    TSManager    22/10/2018 11:11:52    6016 (0x1780)
    Cleaning up any maintenance task requests in WMI.    TSManager    22/10/2018 11:11:52    6016 (0x1780)
    Deleting SMS_MaintenanceTaskRequests instance: SMS_MaintenanceTaskRequests.TaskID="{7EA6FB90-5D67-46D0-B844-0BE013687C09}".    TSManager    22/10/2018 11:11:52    6016 (0x1780)
    Removed 1 instance of SMS_MaintenanceTaskRequests for tasksequence.    TSManager    22/10/2018 11:11:52    6016 (0x1780)
    Failed to delete registry value HKLM\Software\Microsoft\SMS\Task Sequence\Package. Error code 0x80070002    TSManager    22/10/2018 11:11:54    6016 (0x1780)
    Start to cleanup TS policy    TSManager    22/10/2018 11:11:54    6016 (0x1780)
    End Task Sequence policy cleanup    TSManager    22/10/2018 11:11:54    6016 (0x1780)
    Start to evaluate TS policy with lock    TSManager    22/10/2018 11:11:54    6016 (0x1780)
    Updating settings in \\.\root\ccm\policy\machine\actualconfig    TSManager    22/10/2018 11:11:54    6016 (0x1780)
    Total RequestedConfig policy instance(s) : 526    TSManager    22/10/2018 11:11:54    6016 (0x1780)
    New/Changed ActualConfig policy instance(s) : 1    TSManager    22/10/2018 11:11:54    6016 (0x1780)
    Raising event:
    instance of CCM_PolicyAgent_SettingsEvaluationComplete
    {
        ClientID = "GUID:7b1c980f-8682-478c-8966-26339291b4c9";
        DateTime = "20181022101154.761000+000";
        PolicyNamespace = "\\\\.\\root\\ccm\\policy\\machine\\actualconfig";
        ProcessID = 5888;
        ThreadID = 6016;
    };
        TSManager    22/10/2018 11:11:54    6016 (0x1780)
    Status Agent hasn't been initialized yet. Attempting to create pending event.    TSManager    22/10/2018 11:11:54    6016 (0x1780)
    Raising pending event:
    instance of CCM_PolicyAgent_SettingsEvaluationComplete
    {
        ClientID = "GUID:7b1c980f-8682-478c-8966-26339291b4c9";
        DateTime = "20181022101154.761000+000";
        PolicyNamespace = "\\\\.\\root\\ccm\\policy\\machine\\actualconfig";
        ProcessID = 5888;
        ThreadID = 6016;
    };
        TSManager    22/10/2018 11:11:54    6016 (0x1780)
    Successfully submitted pending event to WMI.    TSManager    22/10/2018 11:11:54    6016 (0x1780)
    End TS policy evaluation    TSManager    22/10/2018 11:11:54    6016 (0x1780)
    Policy evaluation initiated    TSManager    22/10/2018 11:11:54    6016 (0x1780)
    RegQueryValueExW is unsuccessful for Software\Microsoft\SMS\Task Sequence, SMSTSEndProgram    TSManager    22/10/2018 11:11:54    6016 (0x1780)
    GetTsRegValue() is unsuccessful. 0x80070002.    TSManager    22/10/2018 11:11:54    6016 (0x1780)
    End program:     TSManager    22/10/2018 11:11:54    6016 (0x1780)
    Error Task Sequence Manager failed to execute task sequence. Code 0x80004005    TSManager    22/10/2018 11:11:54    6016 (0x1780)
    Sending error status message    TSManager    22/10/2018 11:11:54    6016 (0x1780)
    Not in SSL    TSManager    22/10/2018 11:11:54    6016 (0x1780)
    Finalize logging request ignored from process 5888    TSManager    22/10/2018 11:11:54    6016 (0x1780)
    Waiting for CcmExec service to be fully operational    TSManager    22/10/2018 11:11:54    6016 (0x1780)
    CcmExec service is up and fully operational    TSManager    22/10/2018 11:13:22    6016 (0x1780)
    Current Assigned Management Point is sccm.Domian.local with Version 8692 and Capabilities: <Capabilities SchemaVersion="1.0"><Property Name="SSLState" Value="0"/></Capabilities>    ClientLocation    22/10/2018 11:13:23    6016 (0x1780)
    Successfully connected to MP sccm.Domian.local:80    TSManager    22/10/2018 11:13:23    6016 (0x1780)
    Attempting to release request using {7EA6FB90-5D67-46D0-B844-0BE013687C09}    TSManager    22/10/2018 11:13:23    6016 (0x1780)
    ReleaseRequest failed with error code 0x87d00317    TSManager    22/10/2018 11:13:23    6016 (0x1780)
    Task Sequence Manager could not release active TS request. code 87D00317    TSManager    22/10/2018 11:13:23    6016 (0x1780)
    Process completed with exit code 2147500037    TSMBootstrap    22/10/2018 11:13:23    5632 (0x1600)
    Exiting with return code 0x80004005    TSMBootstrap    22/10/2018 11:13:23    5632 (0x1600)
    Process completed with exit code 2147500037    OSDSetupHook    22/10/2018 11:13:23    5392 (0x1510)
    Task sequence completed 0x80004005    OSDSetupHook    22/10/2018 11:13:23    5392 (0x1510)
    Restoring original desktop wallpaper.    OSDSetupHook    22/10/2018 11:13:23    5392 (0x1510)
    Resume SCCM Client.    OSDSetupHook    22/10/2018 11:13:23    5392 (0x1510)
    CCMExec service startup type is set to enabled    OSDSetupHook    22/10/2018 11:13:23    5392 (0x1510)
    Modifying CCMExec Service to auto start.    OSDSetupHook    22/10/2018 11:13:23    5392 (0x1510)
    CCMExec Service started    OSDSetupHook    22/10/2018 11:13:23    5392 (0x1510)
    Waiting for CcmExec service to be fully operational    OSDSetupHook    22/10/2018 11:13:23    5392 (0x1510)
    CcmExec service is up and fully operational    OSDSetupHook    22/10/2018 11:13:23    5392 (0x1510)
    Successfully connected to MP sccm.Domian.local:80    OSDSetupHook    22/10/2018 11:13:23    5392 (0x1510)
    Cleaning up any active TS requests in WMI.    OSDSetupHook    22/10/2018 11:13:23    5392 (0x1510)
    No instances of CCM_TSExecutionRequest found.    OSDSetupHook    22/10/2018 11:13:23    5392 (0x1510)
    Cleaning up any maintenance task requests in WMI.    OSDSetupHook    22/10/2018 11:13:23    5392 (0x1510)
    No instances of SMS_MaintenanceTaskRequests found.    OSDSetupHook    22/10/2018 11:13:23    5392 (0x1510)
    Exiting SetClientProvisioningMode 0x00000000    OSDSetupHook    22/10/2018 11:13:25    5392 (0x1510)
    Uninstalling Setup Hook    OSDSetupHook    22/10/2018 11:13:25    5392 (0x1510)
    Removing setup hook from registry.    OSDSetupHook    22/10/2018 11:13:25    5392 (0x1510)
    Successfully removed C:\WINDOWS\system32\OSDGINA.DLL    OSDSetupHook    22/10/2018 11:13:25    5392 (0x1510)
    Could not delete the file C:\WINDOWS\system32\OSDSETUPHOOK.EXE. Error code 5    OSDSetupHook    22/10/2018 11:13:25    5392 (0x1510)
    Marking the file C:\WINDOWS\system32\OSDSETUPHOOK.EXE for deletion on Reboot    OSDSetupHook    22/10/2018 11:13:25    5392 (0x1510)
    Successfully removed C:\WINDOWS\system32\OSDSETUPHOOK.EXE    OSDSetupHook    22/10/2018 11:13:25    5392 (0x1510)
    Successfully removed C:\WINDOWS\system32\_SMSOSDSetup    OSDSetupHook    22/10/2018 11:13:25    5392 (0x1510)
    ::RegQueryValueExW(hSubKey, szReg, NULL, NULL, NULL, &dwSize), HRESULT=80070002 (..\utils.cpp,844)    OSDSetupHook    22/10/2018 11:13:25    5392 (0x1510)
    RegQueryValueExW is unsuccessful for Software\Microsoft\SMS\Task Sequence, SMSTSEndProgram    OSDSetupHook    22/10/2018 11:13:25    5392 (0x1510)
    GetTsRegValue() is unsuccessful. 0x80070002.    OSDSetupHook    22/10/2018 11:13:25    5392 (0x1510)
    End program:     OSDSetupHook    22/10/2018 11:13:25    5392 (0x1510)
    Finalizing logging from process 5388    OSDSetupHook    22/10/2018 11:13:25    5392 (0x1510)
    Successfully finalized logs to SMS client log directory from C:\WINDOWS\CCM\Logs    OSDSetupHook    22/10/2018 11:13:25    5392 (0x1510)
     with exit code 0]LOG]!><time="19:45:09.965-60" date="10-22-2018" component="OSDDriverClient" context="" type="1" thread="1048" file="CommandLine.cpp:1115">         01/01/1601 00:00:00    0 (0x0000)
    Dism successfully added drivers to the offline driver store.    OSDDriverClient    22/10/2018 19:45:09    1048 (0x0418)
    Successfully added "C:\_SMSTaskSequence\Packages\PPD00178\5A973292-8460-4F3C-B038-F8320F4B39D7" to the Windows driver store.    OSDDriverClient    22/10/2018 19:45:09    1048 (0x0418)
    Adding "C:\_SMSTaskSequence\Packages\PPD00178\5C0A4470-D818-40B2-B434-16A05236A6E3" to Windows driver store.    OSDDriverClient    22/10/2018 19:45:09    1048 (0x0418)
    Setting %SystemRoot% to "C:\WINDOWS"    OSDDriverClient    22/10/2018 19:45:09    1048 (0x0418)
    Getting namespace "Microsoft-Windows-PnpCustomizationsNonWinPE" for architecture "amd64"    OSDDriverClient    22/10/2018 19:45:10    1048 (0x0418)
    Added list item with key value '1'    OSDDriverClient    22/10/2018 19:45:10    1048 (0x0418)
    Writing configuration information to C:\_SMSTaskSequence\PkgMgrTemp\drivers.xml    OSDDriverClient    22/10/2018 19:45:10    1048 (0x0418)
    Successfully saved configuration information to C:\_SMSTaskSequence\PkgMgrTemp\drivers.xml    OSDDriverClient    22/10/2018 19:45:10    1048 (0x0418)
    Setting temporary directory to 'C:\_SMSTaskSequence\PkgMgrTemp'.    OSDDriverClient    22/10/2018 19:45:10    1048 (0x0418)
    Calling Package manager to add drivers to the offline driver store.    OSDDriverClient    22/10/2018 19:45:10    1048 (0x0418)
    Command line for extension .exe is "%1" %*    OSDDriverClient    22/10/2018 19:45:10    1048 (0x0418)
    Set command line: "X:\windows\system32\dism.exe" /image:"C:" /windir:"WINDOWS" /apply-unattend:"C:\_SMSTaskSequence\PkgMgrTemp\drivers.xml" /logpath:"C:\_SMSTaskSequence\PkgMgrTemp\dism.log"    OSDDriverClient    22/10/2018 19:45:10    1048 (0x0418)
    Executing command line: "X:\windows\system32\dism.exe" /image:"C:" /windir:"WINDOWS" /apply-unattend:"C:\_SMSTaskSequence\PkgMgrTemp\drivers.xml" /logpath:"C:\_SMSTaskSequence\PkgMgrTemp\dism.log"    OSDDriverClient    22/10/2018 19:45:10    1048 (0x0418)
    Process completed with exit code 0    OSDDriverClient    22/10/2018 19:45:15    1048 (0x0418)
    Dism successfully added drivers to the offline driver store.    OSDDriverClient    22/10/2018 19:45:15    1048 (0x0418)
    Successfully added "C:\_SMSTaskSequence\Packages\PPD00178\5C0A4470-D818-40B2-B434-16A05236A6E3" to the Windows driver store.    OSDDriverClient    22/10/2018 19:45:15    1048 (0x0418)
    Adding "C:\_SMSTaskSequence\Packages\PPD00178\61B28FA3-A9FB-45B6-931A-3F683496E87D" to Windows driver store.    OSDDriverClient    22/10/2018 19:45:15    1048 (0x0418)
    Setting %SystemRoot% to "C:\WINDOWS"    OSDDriverClient    22/10/2018 19:45:15    1048 (0x0418)
    Getting namespace "Microsoft-Windows-PnpCustomizationsNonWinPE" for architecture "amd64"    OSDDriverClient    22/10/2018 19:45:15    1048 (0x0418)
    Added list item with key value '1'    OSDDriverClient    22/10/2018 19:45:15    1048 (0x0418)
    Writing configuration information to C:\_SMSTaskSequence\PkgMgrTemp\drivers.xml    OSDDriverClient    22/10/2018 19:45:15    1048 (0x0418)
    Successfully saved configuration information to C:\_SMSTaskSequence\PkgMgrTemp\drivers.xml    OSDDriverClient    22/10/2018 19:45:15    1048 (0x0418)
    Setting temporary directory to 'C:\_SMSTaskSequence\PkgMgrTemp'.    OSDDriverClient    22/10/2018 19:45:15    1048 (0x0418)
    Calling Package manager to add drivers to the offline driver store.    OSDDriverClient    22/10/2018 19:45:15    1048 (0x0418)
    Command line for extension .exe is "%1" %*    OSDDriverClient    22/10/2018 19:45:15   
    Monday, October 22, 2018 12:33 PM
  • Expand a string: SELECT * FROM Win32_ComputerSystem WHERE Manufacturer like ‘%DELL%’    TSManager    22/10/2018 10:56:48    6016 (0x1780)
    Error enumerating WMI instances returned from WQL query.
    Invalid query (Error: 80041017; Source: WMI)    TSManager    22/10/2018 10:56:48    6016 (0x1780)
    Failed to evaluate a WMI expression. Error 0x(80041017)    TSManager    22/10/2018 10:56:48    6016 (0x1780)   
    Your query on that group has an error. Replace the quotes surrounding %DELL% with the non-angled single quotes. ' instead of ‘ and ’

    Nathan Ziehnert
    Senior Lead Consultant | Catapult Systems

    Blog | @theznerd | LinkedIn

    Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.

    Monday, October 22, 2018 2:28 PM
  • This the query which does have correct single quote "  SELECT * FROM Win32_ComputerSystem WHERE Manufacturer like '%DELL%'  "
    Tuesday, October 23, 2018 7:18 AM
  • The error message in the SMSTS log file indicates otherwise. The TS is failing because of a bad WMI query.

    Nathan Ziehnert
    Senior Lead Consultant | Catapult Systems

    Blog | @theznerd | LinkedIn

    Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.

    Tuesday, October 23, 2018 2:20 PM