Hi All

I am really struggling to get my USMT restore step working in my MDT 2012 Task Sequence.

• I manually run (from Windows 10 OS): \\MDTServer\deploymentshare$\Scripts\litetouch.vbs /SkipWizard:YES
• My UserData variables are:

LoadStateArgs: /uel:30 /UE:*\administrator /i:MigUser.xml
ScanStateArgs: /uel:30 /UE:*\administrator /i:MigUser.xml
UDDir: %OSDComputerName%
UDShare: %DeployRoot%\USMT-MIG
UserDataLocation: NETWORK
USMTConfigFile: config.xml

• The Capture User State task works perfectly. Note I can see C:\MININT\USMT\X64 copied to the local computer whilst its capturing
• MDT then restarts the PC and carries out the preinstall/install/postinstall and state restore phases.
• When the “restore user state” phase kicks, the deployment fails and I get an error:

“Checking for USMT Files in c:\minint\tools\x64\amd64

Failure (9705): Unable to find USMT files. Cannot capture/restore user state”

I am a bit baffled as what the issue is here. The path is completely different to the capture state. I have dug around the ZTIUserState.wsf and notice the following If Statement. Having checked BDD.log I can see that DeploymentMethod=SCCM in which case (based on the if statement) I am not sure how the sScanSateFolder would reflect the correct deployment share path (%DeployRoot%\Tools\x64\USMT). I could be going down a rabbit hole here but because I kicked the deployment off using litetouch over the network, shouldn't DeploymentMethod = UNC and therefore get the 'Else' on the if statement and get the correct scanstate path?

This was working fine a few weeks ago and I have no idea why is not working now.

		If oEnvironment.Item("DeploymentMethod") = "SCCM" then

			sScanStateFolder = oShell.CurrentDirectory & "\" & sUSMTArchitecture

			oLogging.CreateEntry "Checking for USMT Files in " & sScanStateFolder, LogTypeInfo
			If oFSO.FileExists (sScanStateFolder & "\scanstate.exe") then
				oLogging.CreateEntry "Found scanstate.exe version = " & oFSO.GetFileVersion(sScanStateFolder & "\scanstate.exe"), LogTypeInfo
				sUSMTVersion = "USMT5"	
				sUSMTPath = sScanStateFolder
			Else
				oLogging.ReportFailure "Unable to find USMT files, cannot capture/restore user state.", 9705
			End if	
		Else

			' Use the USMT files in the USMT5 folder (which can be a later version)
			
			sUSMTVersion = "USMT5"
			sScanStateFolder = oEnvironment.Item("DeployRoot") & "\Tools\" & sUSMTArchitecture & "\" & sUSMTVersion

			oLogging.CreateEntry "Checking for USMT Files in " & sScanStateFolder, LogTypeInfo
			If oFSO.FileExists(sScanStateFolder & "\ScanState.exe") then
				oLogging.CreateEntry "Found scanstate.exe version = " & oFSO.GetFileVersion(sScanStateFolder & "\scanstate.exe"), LogTypeInfo
				sUSMTPath = oEnvironment.Item("DeployRoot") & "\Tools\" & sUSMTArchitecture & "\" & sUSMTVersion
			Else
				oLogging.ReportFailure "Unable to find USMT files, cannot capture/restore user state.", 9705
			End if

		End If

Anyone have any suggestions? Im starting to go crazy

I am attempting to use the Deployment Research method because it seemed the most complete solution that matched my needs.

http://deploymentresearch.com/Research/Post/562/Moving-Computers-to-another-OU-during-deployment-Webservice-style

I got it all setup, tested it out and it worked fine from the website.  I then followed the instructions from the site to add the needed info to my CS.ini and TS.  As written this work fine to put a newly created computer object in the Staging OU, and then move it to the production OU at the end of the TS.  But I also need to move existing computer objects to the Staging OU.

So I copied the command to call the MOVE script, and added it to below the "Set Staging OU" variable under Initialization.  This works in both Windows and WinPE!  BUT... for some reason when this step is enabled at this point, the TS never progresses past the initial boot of Windows.  It does not auto-login, and never starts LiteTouch back up.

Investigating I found that LTIBootloader is present at C:\, but there is no shortcut created in Startup to launch it.  If I manually launch LTIBootloader the TS resumes and finishes normally.

I can't find any errors or significant messages in BDD or any other log generated.  The last entry is LiteTouch kicking off the restart.

(If you want to know how I got to this point, otherwise you can ignore the rest of this)

Running into yet another GPO issue with MDT, I finally resigned to configuring a 
Staging OU with inheritance blocked.

Configuring new computers to be added to the staging OU worked fine.

For moving computers, I tried multiple scripts.  PS, VB, and WSF scripts.  The VB 
and WSF's would work fine at the end of the TS to move the computer to the production OU.  
(PS issues since I didn't want to load RSAT on my WIMs)  But I couldn't get any script to 
work in WinPE to move an existing computer object from the production OU to the staging 
OU, BEFORE the computer would run into an issue with Group Policy.  I could run the scripts 
manually or through Task Sequences with only the scripts added, but not in or before the 
early Post Install phase of a OS deploy TS.

I gave up and decided to try using a Web Service.  

Thanks,

-Matt

There's no place like 127.0.0.1

Hi,

I have a problem with PXE boot for UEFI enabled machine DELL 5480.

In legacy mode no problem. PXE responds correctly.

To confirm the issue with UEFI, HP machine that doesn't have Legacy support was tested. It has the same issue with PXE boot.

- WDS run on Server 2012 R2, fully patched (June Rollup supposed to fix PXE issue included).

- WDS is on the same subnet with machines to be deployed (deployment shop, so DHCP options are not involved)

- files: wdsmgfw.efi   and  wgl4_boot.ttf are in appropriate directories of WDS installation.

- NetBIOS over TCP/IP server's NIC is disabled

- Enable Variable Windows Extension is unchecked under TFTP tab

For now I use USB key with Light Touch from my MDT 8456.

 I checked couple of blogs at spiceworks forums for confirming all the points mentioned above that were suggested for troubleshooting.

https://community.spiceworks.com/topic/2217808-wds-pxe-boot-not-working-for-uefi?page=1

The final solution is a bit strange ... The OP says that after using WireShark, that showed no problem, he disabled Wireshark loopback adapter and it worked on the next boot!

So, looks like in order to make work PXE, Wireshark should be installed. Funny... but it "fixed" the issue...

Any other idea?

--- When you hit a wrong note its the next note that makes it good or bad. --- Miles Davis

I have been having some issues with trying to deploy some of our older hardware.

We use WDS / MDT to deploy our laptops. Some of our older laptops will no longer deploy, it seems this change happened after we updated Windows 10 ADK to 1903.

The machine goes through the deployment process, PXE boots and loads the boot wim. It even installs the Operating System but when it goes to reboot after deployment we are greeted with the can't find winload.efi error.

I have tried a varying degree of different configurations UEFI, Legacy, Secure Boot on, Secure boot off and neither seem to work.

Windows 10 drivers are available for the model in question a Dell E5540 and have been added to MDT and also the WinPE boot image.

Is there anything I have potentially missed or could try to get this machine to boot to its OS after it has been deployed?

Thanks

HI folks, I need your help.

We are starting to look forward to W10 upgrade, and therefore i setup a Build Lab, to create a W10 image.
However, it stops during "Processing Bootstrap Settings - Processing rules.", it works fine on Win 7 ?

Using MDT 2013 U2 on Server 2012R2 and ADK W10

When looking in the logs on the deploy client in hyperv client (F8 -> X:\MININT\SMSOSD\OSDLOGS\BDD.log) i can see that it says:

ERROR - rule Priority key not set in section [Settings]
ERROR proccessing Ini settings. No further processing.
ZTI ERROR - Non-zero return code by ZTIGather, rc =1
Command completed, return code = 1
FAILURE: 1: Running wscript.exe "X:\Deploy\Scripts\ZTIGather.wsf" /inifile:Bootstrap.ini

In the TS [ Initialization - Gather local only ] is set to gather local data and process rules: customsettings.ini

Customsettings.ini rule:

[Settings]
Priority=Default
Properties=MyCustomProperty
[Default]
_SMSTSORGNAME=DOMAIN
UserDataLocation=NONE
DoCapture=YES
OSInstall=Y
AdminPassword=********
TimeZoneName=Romance Standard Time
JoinWorkgroup=WORKGROUP
HideShell=YES
FinishAction=SHUTDOWN
DoNotCreateExtraPartition=YES
WSUSServer=http://SERVER:8530
ApplyGPOPack=NO
SLSHARE=\\SERVER\e\MDTBuildLab\Logs$
SkipAdminPassword=YES
SkipProductKey=YES
SkipComputerName=YES
SkipDomainMembership=YES
SkipUserData=YES
SkipLocaleSelection=YES
SkipTaskSequence=NO
SkipTimeZone=YES
SkipApplications=YES
SkipBitLocker=YES
SkipSummary=YES
SkipRoles=YES
SkipCapture=NO
SkipFinalSummary=YES
EventService=http://SERVER:9800
[Settings]

Bootstrap.ini

[Default]
DeployRoot=\\SERVER\MDTBuildLab	
UserID=deployuser
UserDomain=DOMAIN.DN
UserPassword=*****************
SkipBDDWelcome=YES

I am having problems with Microsoft Deployment Toolkit (MDT) Windows 10 1903.

·        I first upgraded my MDT to 8456 (6.3.8456.1000).

·        Then uninstalled the old Windows ADK, and PE from the server.

·        I then installed Windows ADK (10.1.18362.1), and Windows ADK PE (10.1.18362.1).  

·        I then applied Windows System Image Manager (WSIM) 1903 update (which replaces ImgMgr.exe, and ImageCat.exe)

·        I then downloaded the 1903 iso image from Microsoft’s Volume license website (SW_DVD9_Win_Pro_10_1903_64BIT_English_Pro_Ent_EDU_N_MLF_X22-02890.ISO)

·        Add the OS to my deployment share

·        Updated the deployment share to create a new boot image

·        After the boot image completed, I added it in Windows Deployment Services, and named it accordingly.

·        Now when I attempt to image a workstation I boots the LiteTouchPE_x64-(19).wim

·        Then I get the following error:

·         

Windows Boot Manager (Server IP: 10.2.24.19) 

Windows failed to start. A recent hardware or software change might be the cause. To fix the problem:  

1. Insert your Windows installation disc and restart your computer.

2. Choose your language settings, and then click “Next.”

3. Click “Repair your computer.” 

If you do not have this disc, contact your system administrator or computer manufacturer for assistance. 

File: \Windows\System32\boot\winload.efi 

Status: 0xc000000f 

Info: The application or operating system couldn’t be loaded because a required file is missing or contains errors.

Not sure what to do from here………..

• Please go through the  Link  for accessing the Guide

Hello,

I have seen a few other posts of this and the solutions they provided have not helped my situation.

This is what I am looking at. I checked the BDD.log and this was what pulled up:

**Full disclosure I pulled these pictures from another post because they match my issues. I use a system called Secure Host Baseline (SHB) to run my windows deployment which makes my rules very long and convoluted. Being that my MDT is on a secure network **I can't copy over information unless I type it by hand**

I have checked to make sure I have no repeating "[Default]" or "[Settings]" throughout my rules. I confirmed that it is calling out the correct task sequence. I have verified everything that I can think of. All I am trying to do is build a WIM file for my Reference image to call out for my deployment build. So, this MDT is getting stuck in a virtual machine....

Any help would be greatly appreciated!

Hi

I am upgrading from W7 to W10, but some computers give hardware compatibility error (eg Intel (R) HD Graphics 520) which is not so because it is fully compatible and the task fails and does not continue.

If I launch the upgrade with the W10 DVD, the same message comes out but leave the option to "confirm" and move on.

Is it possible to skip that message in the MDT sequence?

Thanks!

So I've had MDT working fine for years but on the latest media build I've come across a strange problem.  My PE drivers are not loading.  I use the same drivers when updating my MDT share and they load fine, I can see we debugView from systernals the calls to inject drivers into the mounted PE wim, yet when updating my media, it does not make the calls to inject the drivers.  I thought it may be my media so I created a new one with all defaults, and pointed to my PE drivers selection profile.  Still no calls to inject drivers.  I tried forcing all drivers within the profile instead of only network and storage, still no dice.  I thought maybe my drivers.xml was corrupted so i limited the profile to only 1 set of drivers, still nothing.  I'm running build 8450 and about to update to the latest but wanted to see if anyone's come across the problem and if there's a fix. 

Thanks

Unfortunately I am still struggling with MDT to get the priority to work based on the TaskSequence ID.
I really need this for my project which I am working on at the moment, as we have several VM Setups.

I have tried the file "DeployWiz_SelectTS.vbs" in the zipfile Wiz_SelectTSMDT8843.7z from Ward Visser, but no luck.

http://www.wardvissers.nl/2016/04/25/mdt-2013-update-2-automatically-move-computers-to-the-right-ou/

It does execute another gather when I click on any tasksequence in the wizard, but it doesn't prioritize the tasksequence first over the model or the default setting. I have tried this on a VM machine. However when removing the VM model I still don't get the expected result to set the computername for tasksequence [W81-100] when clicking on the corresponding tasksequence in the wizard.

Is there something wrong in my ini file?

I have the Gather step in the TS set to read from the rule file "%DeployRoot%\Control\CustomSettings.ini"

Which is posted below.

Any suggestions?

[Settings]
Priority=TaskSequenceID, Model, Default
Properties=MyCustomProperty

[W81-100]
MachineObjectOU=OU=VMware_Computers,OU=Computers,OU=XXX,DC=TMG,DC=XXX
OSDComputerName=APPLEVMXXXX
SkipComputerName=NO

[W10-100]
MachineObjectOU=OU=VM-W10,OU=Computers 2.0,OU=XXX,DC=XXX,DC=XXX
OSDComputerName=MBP-VM#right("%UUID%",4)#
SkipComputerName=NO

[HP COMPAQ 8200 ELITE SFF]
MachineObjectOU=OU=T3C,OU=Computers,OU=TMG,DC=TMG,DC=XX
OSDComputerName=XXX_AMS_WSXXX
SkipComputerName=NO

[HP COMPAQ 8200 ELITE SMALL FORM FACTOR]
MachineObjectOU=OU=T3C,OU=Computers,OU=TMG,DC=TMG,DC=WAN
OSDComputerName=XXX_AMS_WSXXX
SkipComputerName=NO

[VMware Virtual Platform]
MachineObjectOU=OU=VM-V10,OU=Computers 2.0,OU=XXX,DC=XXX,DC=XXX
OSDComputerName=XXXAPPLEVMXXXX

[Default]
_SMSTSORGNAME=XXX
OSInstall=Y
UserDataLocation=NONE
AdminPassword=XXX
TimeZoneName=W. Europe Standard Time
JoinDomain=XXX
DomainAdmin=XXXX\XXX
DomainAdminPassword=123456
ApplyGPOPack=NO
HideShell=YES
WSUSServer=http://XXXX:1234
SLSHARE=\\XXX
EventShare=%DeployRoot%\Events
SkipAdminPassword=YES
SkipProductKey=YES
MachineObjectOU=OU=VM-W10,OU=Computers 2.0,OU=XXX,DC=XXX,DC=XXX
OSDComputerName=XXX-MBP-VM#right("%UUID%",4)#
SkipComputerName=YES
SkipDomainMembership=YES
SkipUserData=YES
SkipLocaleSelection=YES
SkipTaskSequence=NO
SkipTimeZone=YES
SkipApplications=YES
SkipBitLocker=YES
;SkipSummary=YES
SkipRoles=YES
SkipFinalSummary=YES
FinishAction=REBOOT
SkipPackageDisplay=YES
KeyboardLocale=nl-us;0413:00020409
UILanguage=nl-nl
UserLocale=nl-us

SkipCapture=NO
SkipSummary=NO
DoCapture=YES
ComputerBackupLocation=NETWORK
BackupShare=\\XXX\MDT$
BackupDir=Captures
BackupFile=%TaskSequenceID%_#month(date) & "-" & day(date) & "-" & year(date)#.wim

EventService=http://XXXX:9800

Hello MDT experts,
I have a MDT setup here which worked fine until I updated the Windows image to 1903 recently.

Now the PXE boot on clients fails with error "0xc000000f" about missing boot configuration data files in the folder Tmp\ of the remote installation share. File names are "<architecture>{<some UUID>}.bcd", e.g. "x64uefi{ABC-XYZ-...}.bcd".

Screenshot will follow when I can post images.

MDT somhow seems to need those files in order to boot, the problem is that they're deleted periodically and if they're missing PXE boot will fail with above error.

Also after e.g. replacing the boot images in the MDT configuration, these files are regenerated. The same happens when restarting the MDT services. I also should add that the I've set up a distributed environment and the remote installation folder is replicated to other servers via DFS-R. That shouldn't be a problem though.

What could be the cause of this? I couldn't find anything in the configuration, nor while searching the web.

Thanks in advance for any help.

Cheers

Edit: Even after completely reconfiguring the MDT server settings and Remote Installation share, the same error occurs.

Hello MDT experts,
I have a MDT setup here which worked fine until I updated the Windows image to 1903 recently.

Now the PXE boot on clients fails with error "0xc000000f" about missing boot configuration data files in the folder Tmp\ of the remote installation share. File names are "<architecture>{<some UUID>}.bcd", e.g. "x64uefi{ABC-XYZ-...}.bcd".

Screenshot will follow when I can post images.

MDT somhow seems to need those files in order to boot, the problem is that they're deleted periodically and if they're missing PXE boot will fail with above error.

Also after e.g. replacing the boot images in the MDT configuration, these files are regenerated. The same happens when restarting the MDT services. I also should add that the I've set up a distributed environment and the remote installation folder is replicated to other servers via DFS-R. That shouldn't be a problem though.

What could be the cause of this? I couldn't find anything in the configuration, nor while searching the web.

Thanks in advance for any help.

Cheers

Edit: Even after completely reconfiguring the MDT server settings and Remote Installation share, the same error occurs.

Hi there,

One of my clients asked me about integration of MDT (Probably from the newest versions) & SCCM 2012. The thing is they want use these products in OS deployment stage. I don't believe it's possible but I need to be sure. Here is the senario;

MDT and SCCM servers are not on the same server. Their SCCM site is in another country and they cannot even use the admin console effectively because of some sort of slowness, I suspect it's about network speed. Because of this issue, they decided to set up MDT server in their local site and their OS deployments are generally deployed under 1h. 

The trick is that there is a group of computer named Audit which needs about 50-60 TS created in SCCM in their local site. So, they want to learn if this integration makes it possible to create an OS package (from MDT) + 50-60 TS (from SCCM). 

By the way, PXE is not enabled in their DP. It's being used on MDT.

I think, on the worst case, these TS' will be created on MDT or they will need an MP on their local side.

I just need to make sure if it's possible or is there an option to export SCCM TS and import to MDT.

Thanks 

Melih

Hi there,

I have a small issue with an MDT 2010 deployment of Windows 7.  When I am logged into the machine that we will be upgrading as administrator and run litetouch.vbs from the command prompt the program will open a new command prompt window briefly and then close the window without opening the task sequence selector.  I am also having trouble locating where the log files are kept for the process and am really stuck.

Regards,

Hello,

Hoping for some assistance as i cannot seem to figure this out. I've inherited and MDT environment (i normally just use sccm). 

To make a long story short:

When i burn my ISO created from MDT, the DEPLOY folder within contains some customization's in a custom folder. I've been having to copy over an additional folder manually into this deploy folder because i dont know how to automate this.

How does one automatically as part of the process get a folder in the DEPLOY folder within the burned the ISO?

Thanks in advance!

Sean

Vmware 6.7
Virtual Windows 10 1903 x64  - vmxnet3 nic

Virtual Server - WDS and MDT 8456 on same Server 2019

Trying to figure out why loading the WIM file for a VMware VM in EFI mode takes ~8 minutes while the same VM as BIOS works in seconds?

I've tried adjusting the TFTP packet size in WDS and even doing the BCD edit directly to decrease the time, but havent found anything that actually works. 

Bcdedit -store pathto:\default.bcd -set {68d9e51c-a129-4ee1-9725-2ab00a957daf} ramdisktftpblocksize 16384

Just looking for suggestions. Thanks