none
Suppress Dialog During Deployment?

    Question

  • I am getting the following dialog during one of my task sequences, but not the other two (this is a three task sequence deployment; the user chooses one of three; this task sequence formats C: partition leaving the D: partition alone and deploys Windows to C:).

    The dialog reads: "The OEM image has been copied to the local machine. Now ready for replication. Press OK to shutdown (default automatic shutdown in 20 minutes)."

    Upon shutdown and reboot, the deployment continues and deploys successfully. Does anybody know why this dialog is appearing and how I can suppress it? I need it to skip this dialog and have it continue and complete the deployment without user interaction.

    Monday, July 01, 2013 12:49 PM

All replies

  • What task sequence template are you using for that task sequence.  It sounds like maybe you used the Litetouch OEM Task Sequence template when you really want the Standard Client Task Sequence...

    www.vaughnemiller.com

    Monday, July 01, 2013 1:13 PM
  • It's a Custom Task Sequence. The sequence uses two disks to copy a number of SWM files to the local drive, reassembles them and applies the WIM using imagex.exe.

    Here is a screen shot of the actual dialog I am experiencing:

    • Edited by greg.roberts Monday, July 01, 2013 4:21 PM Added screen shot
    Monday, July 01, 2013 1:19 PM
  • That's a result of bIsOEM = True and is caused by LiteTouch.wsf.  Is bIsOEM being forced to true somewhere with your custom scripts?

    David Coulter | http://DCtheGeek.blogspot.com | @DCtheGeek

    Monday, July 01, 2013 5:15 PM
    Answerer
  • That's a result of bIsOEM = True and is caused by LiteTouch.wsf.  Is bIsOEM being forced to true somewhere with your custom scripts?

    David Coulter | http://DCtheGeek.blogspot.com | @DCtheGeek

    The only place I see where bIsOEM being set to true in LiteTouch.wsf starts at line 921:

    If iRetVal = 0 then
    			
    	oLogging.CreateEvent 41015, LogTypeInfo, "LTI deployment completed successfully", Array("0")
    	If ucase(oEnvironment.Item("_DoNotCleanLiteTouch")) = "TRUE" then
    				
    	        bIsOEM = True
    		
            End if
    			
    Else
    			
    	oLogging.CreateEvent 41014, LogTypeError, "Litetouch deployment failed, Return Code = " & PrnErrValue ( iRetval ), Array(CStr(iRetVal))
    	oLogging.CreateEntry "For more information, consult the task sequencer log ...\SMSTS.LOG.", LogTypeInfo
    				
    End if
    You're thinking one of the custom scripts could be setting bIsOEM equal to True?

    Monday, July 01, 2013 5:55 PM
  • Yes, I think it's being set somewhere... as it's triggering that popup.  I'd parse through the bdd.log / smsts.log and see if it gets set somewhere or check your custom scripts.

    David Coulter | http://DCtheGeek.blogspot.com | @DCtheGeek

    Monday, July 01, 2013 6:06 PM
    Answerer
  • Yes, I think it's being set somewhere... as it's triggering that popup.  I'd parse through the bdd.log / smsts.log and see if it gets set somewhere or check your custom scripts.

    I've tried adding bIsOEM = False into the code right before that If statement, but now I'm getting another failure that I can't seem to resolve. This came out of nowhere. My tests are in a VM so there shouldn't be driver issues or "missing network adapter" issues.

    I've gone through BDD.log and SMSTS.log and they're complete gibberish to me. I never find anything useful in them after a failure.

    Someone just told me that bIsOEM gets set when DeploymentType gets set to NewComputer. Any idea if that's true?

    Monday, July 01, 2013 7:00 PM
  • Is your custom Task Sequence calling LTIOEM.wsf by any chance?  At the end of that, it sets _DoNotCleanLiteTouch, which is then used to set bIsOEM.

    If you want help with the logs, toss them up on SkyDrive somewhere and let me know and I'll try and dig through them.

    And no, bIsOEM does not get set when DeploymentType=NewComputer.


    David Coulter | http://DCtheGeek.blogspot.com | @DCtheGeek

    Monday, July 01, 2013 7:13 PM
    Answerer
  • I do not know. How can I find out if the task sequence is calling LTIOEM.wsf?

    I appreciate the offer. Here is a Skydrive link to the logs: https://skydrive.live.com/redir?resid=665A6CCB9533D5FF!255&authkey=!ANdpoN-fOZkTpYE
    Monday, July 01, 2013 8:48 PM
  • It just might be a step if it's being called.  I don't use it (not an OEM), so have never tried to call it.

    I looked at the logs... the bdd.log seems way to short (21 lines)... are you sure that's the whole file?  Your smsts.log shows that it skips Apply DriverApps WIM (due to condition) and is trying to do Export OS WIM and this is where it's failing:

    %DEPLOYROOT%\Tools\%ARCHITECTURE%\imagex.exe /ref %OSDisk%\DeployCache\SDC-3401-NIPR-x86*.swm /export %OSDisk%\DeployCache\SDC-3401-NIPR-x86.swm 1 "%OSDisk%\Deploy\Operating Systems\SDC-3401-NIPR-x86\SDC-3401-NIPR-x86.wim"

    Does this command work if you do it manually from WinPE?  If you can get the whole bdd.log, I might be able to spot more.

    David Coulter | http://DCtheGeek.blogspot.com | @DCtheGeek

    Monday, July 01, 2013 9:23 PM
    Answerer
  • p.s.  Download CMTrace.exe... it makes reading those logs a lot easier. : )

    http://www.microsoft.com/en-us/download/details.aspx?id=36213


    David Coulter | http://DCtheGeek.blogspot.com | @DCtheGeek

    Monday, July 01, 2013 9:27 PM
    Answerer
  • I was actually able to resolve the red screen failure. I recreated the deployment from scratch and it is now gone. I am still having the dialog problem. I will try tweaking LiteTouch.wsf in an attempt to suppress the dialog from coming up during deployment.
    Monday, July 01, 2013 9:31 PM
  • It just might be a step if it's being called.  I don't use it (not an OEM), so have never tried to call it.

    I looked at the logs... the bdd.log seems way to short (21 lines)... are you sure that's the whole file?  Your smsts.log shows that it skips Apply DriverApps WIM (due to condition) and is trying to do Export OS WIM and this is where it's failing:

    %DEPLOYROOT%\Tools\%ARCHITECTURE%\imagex.exe /ref %OSDisk%\DeployCache\SDC-3401-NIPR-x86*.swm /export %OSDisk%\DeployCache\SDC-3401-NIPR-x86.swm 1 "%OSDisk%\Deploy\Operating Systems\SDC-3401-NIPR-x86\SDC-3401-NIPR-x86.wim"

    Does this command work if you do it manually from WinPE?  If you can get the whole bdd.log, I might be able to spot more.

    David Coulter | http://DCtheGeek.blogspot.com | @DCtheGeek

    Is this in regard to the red screen issue? I was able to solve that by rebuilding the deployment. Something had happened to cause it, and since I didn't know what it was I just recreated the deployment from scratch. Doesn't take long, as many times as I've done this.

    Now I'm back to the dialog issue from above. I modified LiteTouch.wsf and commented out the section that creates the dialog to see if that suppresses it. It was explained to me by a Microsoft tech why someone might want that dialog in an OEM environment, but I don't want it. So I'm testing ways to simply bypass it. I actually commented out and then deleted the lines of code that create the dialog, but the dialog presented itself anyway. I don't understand how to get rid of that dialog.

    Also, that was the whole BDD.log. When the red screen failure hit, I pressed F8 to bring up a DOS prompt, navigated to where that file was, typed "notepad bdd.log" and did a Save As.. to a USB drive. From there I did a direct upload to the SkyDrive. I didn't modify the log file at all.

    CMTrace. Now that's a nice tool! Thanks for the recommendation on reading log files...


    Tuesday, July 02, 2013 12:35 PM
  • Sounds like you are on the path to success.  Let us know if it works or if you still need some assistance.

    David Coulter | http://DCtheGeek.blogspot.com | @DCtheGeek

    Tuesday, July 02, 2013 1:16 PM
    Answerer
  • I believe I have a 99.9% solution and working on the last .01 right now. I ended up having to make some edits to the LiteTouch.wsf file and updating the deployment to compile the scripts. I basically removed the code creating the dialogs I didn't want displayed to the user, so the deployment would move forward and complete.
    Tuesday, July 02, 2013 8:04 PM