locked
Black Screen w/Mouse Pointer or Immensely Long Login Times RRS feed

  • Question

  • Hi,

    I'm trying to deploy Windows 10 Enterprise LTSB and my deployment task fails in several areas. The built-in administrator account shows nothing when logged in but a black screen and a mouse pointer. Logging in as another local user sees the log in process hang on "Preparing Windows" or just take a ridiculously long time >10 minutes to arrive at that same black screen. 10 minutes for a default user profile that is 29MB in size. What is making it take so long. LTSB doesn't have any of the useless Windows Store crap (that's why we chose it), so it cannot be setting that up. No Cortana, so what is it doing? The domain-join part of the task sequence failed, the computer didn't even get the name I specified in the wizard. 


    Jason

    Monday, March 28, 2016 9:08 PM

All replies

  • What is in the logs?  Netsetup.log will be interesting for the domain join issue.

    Logs are very important. https://keithga.wordpress.com/2014/10/24/video-mdt-2013-log-files-basics-bdd-log-and-smsts-log/ Mention any customizations you have made.

    Monday, March 28, 2016 11:18 PM
  • Here's the CS.ini. Pretty stock with nothing unusual in place.

    [Settings]
    Priority=Default

    [Default]
    _SMSTSORGNAME=Company.com
    _SMSTSpackageName=%TaskSequenceName%
    OSInstall=YES
    UserDataLocation=AUTO
    TimeZoneName=Eastern Standard Time
    AdminPassword=password
    ;JoinDomain=domain.com
    ;DomainAdmin=DOMAIN\mdt_user
    ;DomainAdminPassword=password
    ;MachineObjectOU=OU=Classrooms,DC=domain,DC=com
    SLShare=%DeployRoot%\Captures\Logs
    BitsPerPel=32
    VRefresh=60
    XResolution=1
    YResolution=1
    HideShell=YES
    ApplyGPOPack=NO
    ;WSUSServer=http://update.domain.com
    SkipAppsOnUpgrade=NO
    SkipAdminPassword=YES
    SkipProductKey=YES
    SkipComputerName=NO
    SkipDomainMembership=YES
    SkipUserData=YES
    SkipLocaleSelection=YES
    SkipTaskSequence=NO
    SkipTimeZone=YES
    SkipApplications=NO
    SkipBitLocker=YES
    SkipSummary=YES
    SkipCapture=YES
    SkipFinalSummary=NO

    The entries with semicolons are commented out, but do not seem to be ignored. a ' for a quote doesn't seem to work either. The MDT server is not joined to the target domain. Could that be why the domain join part fails? The log entry for that indicates success.

    Event 41001 sent: ZTIDomainJoin processing completed successfully.

    The SMSTS log is full of non-descript errors that really do not point to anything specific.

    Failed to run the action: Enter Windows 10 Product Key.
    Incorrect function. (Error: 00000001; Source: Windows)    TSManager    3/28/2016 5:43:04 PM    2884 (0x0B44)
    Executing in non SMS standalone mode. Ignoring send a task execution status message request    TSManager    3/28/2016 5:43:04 PM    2884 (0x0B44)
    Set a global environment variable _SMSTSLastActionRetCode=1    TSManager    3/28/2016 5:43:04 PM    2884 (0x0B44)
    Set a global environment variable _SMSTSLastActionSucceeded=false    TSManager    3/28/2016 5:43:04 PM    2884 (0x0B44)
    Clear local default environment    TSManager    3/28/2016 5:43:04 PM    2884 (0x0B44)
    Let the parent group (Custom Tasks) decides whether to continue execution    TSManager    3/28/2016 5:43:04 PM    2884 (0x0B44)
    Let the parent group (State Restore) decide whether to continue execution    TSManager    3/28/2016 5:43:04 PM    2884 (0x0B44)
    The execution of the group (State Restore) has failed and the execution has been aborted. An action failed.
    Operation aborted (Error: 80004004; Source: Windows)    TSManager    3/28/2016 5:43:04 PM    2884 (0x0B44)
    Failed to run the last action: Enter Windows 10 Product Key. Execution of task sequence failed.
    Incorrect function. (Error: 00000001; Source: Windows)    TSManager    3/28/2016 5:43:04 PM    2884 (0x0B44)
    Executing in non SMS standalone mode. Ignoring send a task execution status message request    TSManager    3/28/2016 5:43:04 PM    2884 (0x0B44)
    Task Sequence Engine failed! Code: enExecutionFail    TSManager    3/28/2016 5:43:04 PM    2884 (0x0B44)
    ****************************************************************************    TSManager    3/28/2016 5:43:04 PM    2884 (0x0B44)
    Task sequence execution failed with error code 80004005    TSManager    3/28/2016 5:43:04 PM    2884 (0x0B44)
    Cleaning Up.    TSManager    3/28/2016 5:43:04 PM    2884 (0x0B44)
    Removing Authenticator    TSManager    3/28/2016 5:43:04 PM    2884 (0x0B44)
    Cleaning up task sequence folder    TSManager    3/28/2016 5:43:04 PM    2884 (0x0B44)
    Unable to delete file C:\_SMSTaskSequence\TSEnv.dat (0x80070005). Continuing.    TSManager    3/28/2016 5:43:04 PM    2884 (0x0B44)
    Failed to delete directory 'C:\_SMSTaskSequence'    TSManager    3/28/2016 5:43:04 PM    2884 (0x0B44)
    SetNamedSecurityInfo() failed.    TSManager    3/28/2016 5:43:04 PM    2884 (0x0B44)
    SetObjectOwner() failed. 0x80070005.    TSManager    3/28/2016 5:43:04 PM    2884 (0x0B44)
    RemoveFile() failed for C:\_SMSTaskSequence\TSEnv.dat. 0x80070005.    TSManager    3/28/2016 5:43:04 PM    2884 (0x0B44)
    RemoveDirectoryW failed (0x80070091) for C:\_SMSTaskSequence    TSManager    3/28/2016 5:43:04 PM    2884 (0x0B44)
    Deleting volume ID file C:\_SMSTSVolumeID.7159644d-f741-45d5-ab29-0ad8aa4771ca ...    TSManager    3/28/2016 5:43:04 PM    2884 (0x0B44)
    Successfully unregistered Task Sequencing Environment COM Interface.    TSManager    3/28/2016 5:43:04 PM    2884 (0x0B44)
    Executing command line: "C:\MININT\Tools\X64\TsProgressUI.exe" /Unregister    TSManager    3/28/2016 5:43:04 PM    2884 (0x0B44)
    ==========[ TsProgressUI started in process 2864 ]==========    TsProgressUI    3/28/2016 5:43:04 PM    4612 (0x1204)
    Unregistering COM classes    TsProgressUI    3/28/2016 5:43:04 PM    4612 (0x1204)
    Shutdown complete.    TsProgressUI    3/28/2016 5:43:04 PM    4612 (0x1204)
    Process completed with exit code 0    TSManager    3/28/2016 5:43:04 PM    2884 (0x0B44)
    Successfully unregistered TS Progress UI.    TSManager    3/28/2016 5:43:04 PM    2884 (0x0B44)
    RegQueryValueExW is unsuccessful for Software\Microsoft\SMS\Task Sequence, SMSTSEndProgram    TSManager    3/28/2016 5:43:04 PM    2884 (0x0B44)
    GetTsRegValue() is unsuccessful. 0x80070002.    TSManager    3/28/2016 5:43:04 PM    2884 (0x0B44)
    End program:     TSManager    3/28/2016 5:43:04 PM    2884 (0x0B44)
    Error Task Sequence Manager failed to execute task sequence. Code 0x80004005    TSManager    3/28/2016 5:43:04 PM    2884 (0x0B44)
    Sending error status message    TSManager    3/28/2016 5:43:04 PM    2884 (0x0B44)
    In non SMS staqndalone mode.Ignoring SendStatusMessage request    TSManager    3/28/2016 5:43:04 PM    2884 (0x0B44)
    LOGGING: Setting log directory to "C:\Users\ADMINI~1\AppData\Local\Temp\".    TSManager    3/28/2016 5:43:04 PM    2884 (0x0B44)
    Process completed with exit code 2147500037    TSMBootstrap    3/28/2016 5:43:04 PM    3624 (0x0E28)
    Exiting with return code 0x80004005    TSMBootstrap    3/28/2016 5:43:04 PM    3624 (0x0E28)
    Used smsts.ini to set logging settings.    TsProgressUI    3/28/2016 5:43:05 PM    3004 (0x0BBC)

    Is there a log for deciphering MDT errors?


    Jason

    Tuesday, March 29, 2016 1:19 PM
  • Regarding the OU where the computer is placed after it is joined to the domain: is there a group policy linked to that OU for desktop redirection? Desktop redirection will cause long initial login times. I would ensure that whatever OU the computers are placed in after joining the domain have a minimal amount of group policies. Our setup has GPs that designate local admins and setup firewall rules, but not much else.
    Monday, April 4, 2016 12:45 PM
  • We have some basic GPOs in place on the OU, but we usually image to an OU that has no GPOs, other than the default domain GPO, which is un-configured. Same deal. Any way to speed this up? I have to make a decision whether or not to deploy 250+ copies of Windows 10 to replace Windows 7. If it takes > 1 minute to log on for each user, Windows 10 won't fly. Right now, with Windows 7, it is under 30 seconds.

    Jason

    Tuesday, April 5, 2016 3:03 PM
  • At this point your issue is likely far outside the MDT realm. To really troubleshoot this however you would need to do some tracing. The following article is close but, using older ADK tools.

    http://social.technet.microsoft.com/wiki/contents/articles/10128.tools-for-troubleshooting-slow-boots-and-slow-logons-sbsl.aspx


    Logs are very important. https://keithga.wordpress.com/2014/10/24/video-mdt-2013-log-files-basics-bdd-log-and-smsts-log/ Mention any customizations you have made.


    • Edited by Ty Glander Tuesday, April 5, 2016 6:05 PM
    Tuesday, April 5, 2016 6:02 PM
  • Thanks. Still not much luck with getting faster logins on Windows 10. We may have to nix the idea all together and stay with 7.

    Jason

    Thursday, April 21, 2016 2:00 PM