Litetouch Deployment Failed

269 views

Skip to first unread message

Serafin Sonnier

unread,

Aug 3, 2024, 10:52:24 AM8/3/24

to cogsborgeoman

I have an HP Z420 Workstation with a single 500GB SATA drive that I spent all day imaging to Server 2012 R2. Part of the deployment process is selecting if you want to wipe the drive. I selected yes every time because the drive was blank. It failed numerous times with the error LiteTouch Deployment failed, Reason Code -214746259 0x80004005. I exited to a command prompt and ran these commands:

Then I restarted the deployment. Still failed. I checked and rechecked BIOS settings, and I saw nothing out of the ordinary, but I did see that the drive mode was set to IDE. I decided to enable AHCI to t ake advantage of the better features. The LiteTouch deployment went smoothly after that.

We are running MDT for some while now and when something changed the deployment failes every time. For short it had to do with joining the domain so i have edit the ltidomainjoin and 'out 2 lines according to info on the internet.
Joining domain is now ok but for some reason deployments failes and i cannot figure out what the problem is.
The message at the end in the screenshot. command completed, return code = -2147024891
litetouch deployment failed, return code -2147024891 0x800700005

Applications which are in the Task sequence at the line install applications between post windows update en past windows updates are running but commands at the end of the task sequence at state restore are not running.
The task sequence finishes but with the error and the minint is not removed. In the BDD.log it says that minint is beiing removed but this is not the case.

Problem when do the solution is that the machine is not in de right OU and gets no policy's, so some .ps1 files are only starting when the policy has run which copy's the right files to the local system.
When i try to run the ps1 files in MDT in stead of thru policy the error in the log is:

So it looks like when i put the client in the right OU it gets the domain policy's applied not all applications install good and i must put the client afterwards in the right OU.
When the client is not getting group policy applied so leaving the machineobject ou out of the customsettings then an application is not applied because it cannot find path. I do believe however that the path is accessible because it is the deploymentshare path.

Hi AllenLiu, i am braking my head for this problem cannot find a solution, even when i leave machineobjectOU out of the rules.ini still the deployment is goiing wrong. Maybe there are leftovers from previous attemts but there is no minint folder or _smstassequence anymore on the client.

I can see in the BDD.log that the applications which are between pre en post windows updates are started. The custom tasks and commands beneath state restore not. CAnnot find office or ps files which i start in the task sequence.
attached part of the task sequence where after the post windows update is goes wrong i think.

This is not only occuring when putting the OU's in the customsettings.ini so that the clients getting the gpo's but this is also happening when the client already excists in the right OU and then restoring the image to the client which is already in the domain in the right OU, then also the deployments failes.
When first deleting the client from the OU in the domain then deploy the client the installation all go wel and no fatal error occurs.

Here are the details. I'm trying to image and HP DeskPro 600 and I can get it to PXE boot but when the windows splash screen comes up it does not proceed to the MDT login screen to start the process. If I use a USB stick that has the boot IOS on it I can get through the complete script and start the imaging process but it hangs when it come to formatting the disk. I'm wondering it the issue might have something to do with UEFI. We do disable that function on our computers before we image and like I said it has worked in the past. Currently I'm moving WIM file to another server that has MDT 2013 installed and they seem to work fine on that server. So, do you thing an update from 2012 to 2013 would solve the issue I'm having? Or if someone has had this issue and has a fix for It I would appreciate some help in this area.

I'm having an issue currently with my Surface Pro 3 locking out mapping accounts for MDT. I'm wondering if anyone here has run into this as it's really confusing me at the moment. Here's what is currently happening -

1 - Device boots to MDT Share, tech enters UID/PW. -- Most times this works, though something seems to be getting cached somewhere, and domain is not accepting valid passwords from the device. Seems like auth is completely broken to the device.

I have a Surface Pro 3 in front of me currently, and it will not accept valid user/passwords. I have Surface Pro 1&2, Dell Venue 11, and Lenovo models all functioning properly from this deployshare, but this SP3 is killing me. Anyone here run into domain join accounts being locked out or MDT/WinPE locking out reference accounts? Any helps appreciated, thanks.

We just recently setup our WDS and MDT server and everything seems to be working great. The one issue I am having is with an installed application (VBS script). The script creates a few folders and run an .exe which all works great. The issue I am having is with the script calling a .reg file that is in our DeploymentShare directory. The script will run fine after the imaging process and does exactly what it needs to. However, it always skips this step during imaging. Any suggestions?

I had originally had this in a separate batch file to call the registry setting, but I had troubles with it working. So I thought I would just add it to the current VBS script since it installs the program first, then this is the configuration.

Can someone tell me what I'm doing wrong? I just cleaned installed Server 2012 R2, Windows 8.1 ADK, MDT 2013. Everything is working fine from a server standpoint, I can PXE boot in the WinPE enviroment, ect. I then created my VM of Windows 7 (Audit Mode), disabled system restore, disabled UAC, made some view tweaks, installed all updates, deleted the fax/xps printers, and just a few other minor tweaks. I created my TS to sysprep and capture, then within windows 7 went to run, typed \\wds\deploymentshare$. Navigated to the scripts section, ran litetouch.vbs, it processed rules ect, typed in my credentials, saw my capture/sysprep TS, nothing out of the ordinary compared to MDT 2010 or MDT 2012.

My problem is as soon as I run my sysprep and capture TS, it starts, but within like 5 seconds it finishes. No logs, no minnit folder, no errors, nothing. Everything finishes as if it's completed. I checked the Panther folder to see if anything is going on, nothing. I checked the TEMP folder in windows and see my logs and everything I'm looking at almost shows as being successful. It is not executing sysprep and booting into the PE enviroment to capture my WIM. Is there somthing I'm doing wrong? My rules are exactly as they were in MDT 2010, and MDT 2012.

Disabled the default Format and partiton step with the property DONOTFORMATANDPARTITION=YES just to get rid of errors at the end, i have alos tried to remove the Volume entries in this step with out the above mentioned property.
In this step i have also set the Disk type to GPT and checked the Create Extra 'Active' Partition

Changed the default Install Operating System step to install on disk 0 partition 4.

All seems to work fine until the computer reboots and i should start windows to continue with the deploy.
Instead of booting windows it boots into OSX.
I've tried to change the start disk with the OS utility, but it gives the error "The bless tool was unable to set the current boot disk."

We cannot get our product key to work in our unattend file. Below is the unattend file (the product key portion). Anyone notice anything wrong, or have any suggestions? I have also tried adding the product key into the custom.ini settings and that didn't work either. I know the product key works and I have double check to make sure I didn't fat finger anything. We are imaging Windows 7 Professional Computers using a Windows Server 2012 WDS/MDT server.

WDS boots the litetouch WIM (32 or 64 bit) and Lite Touch takes over. I select the Task sequence (Windows 7 x86) and it goes through with formatting and apples the install image (Imported from Windows 7 DVD). After it finishes applying the image it immediately fails the installation saying this:

We're using MDT 2010 U1 integrated with SCCM 2012 SP1 (I think it's CU3 but I'm not 100% positive). I've created a ZTI for our lab machines so that our lab techs can launch and forget and don't have to touch every computer in the lab when they need refreshed. Right now this is in development mode as I'm new to the department (coming from a lab tech position I was flabbergasted that they were making the techs go through every step of the UDI deployment when a system or lab needed imaged).

However, I've noticed that the USMT process is firing when launched out of Software Center and so some files are carrying over every time I test the ZTI on my test VM. Is there an easy way in either the customsettings.ini or in the task sequence itself to skip the capture and restore of the user data as on a lab machine there's no need to save this data? I did try adding "SkipUserData=YES" and UserDataLocation=NONE to the customsettings.ini but that just caused an error (reading the MDT help files pointed out that this is meant for an LTI deployment).

I've added som eapplications that are optional. I've added a taks sequence step "Install Application"/"Install Multiple applications" that functions correctly. users are able to select the applications they need from the wizard.