none
MDT/OSD Deployment Page Not showing up corrrectly -MDT 2013 Update2 RRS feed

  • Question

  • About 95% of the time, the final MDT/OSD Deployment Complete page is only showing up after logging in as an admin.

    It usually shows up after last reboot. Here is the complete error:

    The task sequence execution engine failed executing the action (Scan Installed Apps) in the group (OSD Results and Branding) with the error code 1
    Action output: [ smsswd.exe ]
    PackageID = ''
    BaseVar = '', ContinueOnError=''
    ProgramName = 'cmd /c "cscript //nologo C:\WINDOWS\UDI\OSD_InstalledAppsLookUp.vbs > C:\WINDOWS\UDI\OSD_InstalledAppsLookUp.log"'
    SwdAction = '0001'
    Set command line: Run command line
    Working dir 'not set'
    Executing command line: Run command line
    Process completed with exit code 1
    Command line returned 1. The operating system reported error 1: Incorrect function. 

    _____________________________________________________________

    Second error:

    The task sequence execution engine failed executing the action (Parse Base Variable) in the group (OSD Results and Branding) with the error code 200
    Action output: [ smsswd.exe ]
    PackageID = ''
    BaseVar = '', ContinueOnError=''
    ProgramName = 'cscript.exe //nologo "C:\_SMSTaskSequence\WDPackage\Scripts\OSD_BaseVariables.vbs"'
    SwdAction = '0001'
    Command line for extension .exe is "%1" %*
    Set command line: Run command line
    Working dir 'not set'
    Executing command line: Run command line
    Process completed with exit code 200
    --------------------------------
    Initializing Objects
    --------------------------------

    --------------------------------
    Extracting TS Base Variable
    --------------------------------

    Reading OSD variable: [_SMSTSTaskSequence]
    Loading XML from variable string content...
    Using XPATH to query for [BaseVariableName]
    Failed to read XPATH query value, or value is empty.
    --------------------------------
     Exiting with [200]
    --------------------------------
    Command line returned 200. The operating system reported error 200: The code segment cannot be greater than or equal to 64K. 

    The only thing I see out there is this: http://www.myitforum.com/forums/MDT-2012-UDI-OSD-Results-Window-Installed-Applications-Unknown-m235557.aspx

    But there has to be a better way to make sure this works correctly all of the time.

    Using SCCM 2012 R2 SP2 CU2

    Thanks.

    Monday, March 14, 2016 4:28 PM

All replies

  • So, by commenting out the parts referring to the XPATH, I get rid of the errors that show up in the logs. But, it still only appears after logging into the machine as an admin.  This has worked fin in the past, just not sure what may have broken this functionality.
    Tuesday, March 15, 2016 4:57 PM
  • Did you ever figure out what caused this?
    Friday, November 9, 2018 9:42 AM
  • I faced with the same problem on Surface devices. But investigation showed that it was not an issue, but it was a feature of the OSD_InstallOSDResults.vbs script. Actually the script has 2 ways to configure startup for the "Deployment Complete" window (via Scheduled task or RunOnce registry hive). Those scenarios depend on pointing devices available in the system. The script checks them via WMI (select * from Win32_PointingDevice) and using IsTouchEnabled.exe application.

    1. Scheduled task (appears right after deployment). In case if there are more than 1 pointing devices available in the system considers that it OK to show scheduled task right after deployment. In case if there is only one pointing device, but it is not a touch screen (for example, mouse plugged in to a Desktop) it allows to use scheduled tasks as well.

       2. RunOnce registry hive (appears after login as an admin). In case if there is only one pointing device and this device is a touch screen.

    And it goes with 2nd scenario even if a surface keyboard with touchpad is attached (I have no clue why, probably it is registered in the system under other class). To resolve your problem it is enough to just plug a USB mouse in to a device and deploy OS with it. Also you can remove a condition in the script (But trick with mouse is easier).

     


    Tuesday, July 2, 2019 1:08 PM