Re: Leftover junk prevents new installation in MDT 2010

Hi,

I belive deleting the content on minint or some such folder used to allow the next installation. I dont remember the exact name but when the Old installation which had crashed or stopped in middle used to keep the folder and not remove the content. The Folder is created on the server in the root folder of OS or under deploymenst share.

Johan please correct me if I am wrong.

I did not see such folder being created in 2012 beta.

Thanks

Re: Leftover junk prevents new installation in MDT 2010

Sorry to write the above but if you read the content of the script file attached in Johan's post does the same thing.
'Delete any existing C:\MININT directory
Johan nice work - Your book helped me out to understand a lot - Fundamental Vol 1
Thanks

Re: Leftover junk prevents new installation in MDT 2010

Thank you for this blog. Do i need to edit Unattend_PE_x86.xml in the "C:\Program Files\Microsoft Deployment Toolkit\Templates" and then recreate the boot disk?
Thank you.

Re: Leftover junk prevents new installation in MDT 2010

One more question? Just to make sure. ZTICleanSetupInprogress.vbs has to be in the \\server\deploymentsgare$\scripts folder?
Thank you.

Re: Leftover junk prevents new installation in MDT 2010

Hi Ogeccut,

I did not have to modify unattend_pe_x86.xml to get it running. I could insert as needed in the unattend.xml in the control folder with your specific task sequence number eg: c:\deplymentshare\control\1 (When 1 is my task sequence number) Also it needs to be in the 1 in the unattend.xml as we need it to execute it before our Litetouch.wsf
and yes the ZTICleanSetupInProgress.vbs needs to be under the scripts folder as that is mapped to x:\deply\scripts.

Thanks

Re: Leftover junk prevents new installation in MDT 2010

Hi Johan,

I just ran a test over this. I crashed my VHD deploy and i have a unattend.xml modified and the ZTICleanSetup script which cured my leftovers.

Can you explain this more - as below
"If you want to automate, you can do this via the UpdateExit.vbs built-in sample. But again, make sure to ONLY update the wim on your PXE server. Do NOT modify the wim's inside the Boot folder.
"

Re: Leftover junk prevents new installation in MDT 2010

Hello,

I have an issue with a previously functioning OS Deployment Task Sequence (deploying a 32-bit Windows 7 captured image, via WDS and MDT2010 on 2008 R2). When deploying the OS, I get failure messages related to commands in the task sequence that are no longer there. Meaning, the task sequence failure message references items I since removed (and also tried creating a new task sequence to deploy the same image), But the failures still show tasks no longer there. I stumbled across this posting, but also tried it (inseted the clean script in my image file),but I still get the same issue. no matter if I disable all commands in the task sequnce, there is still some reference somewhere to these tasks which I cant find. I have looked at the smsts.log, bdd.log, litetouch.log, and all I see is the same line that shows in the GUI failure box which is the following:

Litetouch deployment failed, Return Code = -2147467259 0x80004005

Messages from the task sequence engine:

Failed to run the action: Run Windows Updates: 1st Pass. [NOTE: This is the name of one of the task sequnce items that is no longer there]
The environment is incorrect. (Error: 0000000A; Source Windows)
The execution engine ignored the failure of the action (Run Windows Updates: 1st Pass) and continues execution [NOTE: it does not proceed on]

after this there is another identical set of lines referencing a second non-existent task sequence item

Also, I have attempted disabling these items when they were still in the sequence, and get the same messages. Tried creating new sequence with no commands other than OS deploy, still get the same. I cant find where it is pulling this stuck info.

Any help would be great.

Thanks

Re: Leftover junk prevents new installation in MDT 2010

I’m trying to migrate from Win XP to Win 7 (REFRESH). I searched Google, found the below url but the last one is similar to my issue which is un-answered till now. Below are steps followed,Why the migration is not success @ first trigger of litetouch.vbs? Am i missing something?

social.technet.microsoft.com/Forums/ar/mdt/thread/a80bdbb2-4090-446b-959e-a8dad39420d1?prof=required

• I ran the LiteTouch.VBS Script from USB drive after logging into the Windows XP laptop with domain user ID which is a Local Administrator rights.
• The PC ran the script successfully to Applying Win PE and additional other processes to Restarting PC.
• The PC rebooted back to the Win XP log-in screen
• I logged in again with same domain user ID and restarted the LiteTouch.VBS script again. The script ran to Capture User State. Almost immediately I received below error message
------------------------------------------------------------------------
ZTI ERROR - Non-zero return code by Litetouch, rc=-2147467259 0x80004005
ZTI ERROR - Non zero return code from Scan state, RC = 27
Failed to run the action: Capture User State
Node creation failure in DNS. (Error: 000025E7;Source:Windows)
The execution of the group(State capture) has failed and the execution has been aborted.
An action failed.
------------------------------------------------------------------------
• I clicked Finish and rebooted the machine
• Again I logged in with same domain user ID ran the LiteTouch.VBS Script. The script ran to completion and the PC restarted
• On restart, the full migration took place.