Hi,
 
i have the problem with the MDT 2010 Sp1 during the installation of applications. The MDT is not restarting the computer,  although the installation script is returning a EXIT CODE of 3010. If i set the property for the application "Reboot the computer after installing this application" the reboot is forced and happend. But i would like to decide for myself in my installation script, when the restart is happend. But the MDT is not responding of the Exit Code 3010 with a restart. After a little debugging of the ZTIApplications.wsf Script i see that the Exit Code is not processed in the script. The Exit Code is in the variable iResult (he hase the value 3010) but i do not exactly know which Method/Property must be called/set, that the exit code is well interpreted from the MDT and the Computer restarted.
 
After that, i added the following line to the Script after Line Number 466
 
>>>> InstallApplication = iResult
 
With this line the application installation process is working as aspected, but i'm not sure is there a bug or i make a mistake in the configuration or may be i understand the use of the exit code wrong.
 
It would be nice, if someone can clarify that for me.

Thank you jens

I just setup a new server with Server 2012 to run MDT. The server has WDS installed on it for PXE booting. I have both 32 and 64bit boot images. In WDS properties, I have the 64bit image selected under Boot - Default boot image (optional). When I try to start MDT on a laptop it shows that the architecture is X64 but the TFTP Download points to boot\x86\wdsnbp.com on the boot screen. The laptop is capable of running 64bit. Why does it keep defaulting to 32bit?

Also, in my DHCP option, I have the option 067 Bootfile Name set to \Boot\x86\Wdsnbp.com.

It seems like I'm unable to create images with the following:

Windows Server 2012 R2

MDT 2013 Update 1 64-bit

ADK 10

I saved the output when I tried to update my deployment share.  FYI, this is a brand new install.

=== Making sure the deployment share has the latest x86 tools ===

=== Processing LiteTouchPE (x86) boot image ===

Building requested boot image profile.
Determining if any changes have been made in the boot image configuration.
No existing boot image profile found for platform x86 so a new image will be created.
Calculating hashes for requested content.
Changes have been made, boot image will be updated.
Windows PE WIM C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Windows Preinstallation Environment\x86\en-us\winpe.wim will be used.
Unable to mount the WIM, so the update process cannot continue.

=== Completed processing platform x86 ===

=== Making sure the deployment share has the latest x64 tools ===

=== Processing LiteTouchPE (x64) boot image ===

Building requested boot image profile.
Determining if any changes have been made in the boot image configuration.
No existing boot image profile found for platform x64 so a new image will be created.
Calculating hashes for requested content.
Changes have been made, boot image will be updated.
Windows PE WIM C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Windows Preinstallation Environment\amd64\en-us\winpe.wim will be used.
Unable to mount the WIM, so the update process cannot continue.

=== Completed processing platform x64 ===

=== Processing complete ===

Let me know if you folks know how to fix this.  Otherwise, I'll have to use MDT2013 with ADK8 instead.

I've tried the following suggestions from these blogs:

- http://blogs.technet.com/b/msdeployment/archive/2015/08/25/mdt-2013-update-1-release-notes-and-known-issues.aspx#pi47623=3

- https://graemebray.wordpress.com/2014/03/26/unable-to-mount-the-wimdism-was-unable-to-set-the-system-root/

- http://www.fastracktechnology.com.au/2011/06/24/mdt-2010-unable-to-update-deployment-share/

I have 2 iso file downloaded via the media creation app from Microsoft, one is en-gb and the other is en-us, they are both in x86 and x64 windows 10240.

My issue is when I try to import them into the operating system section of mdt, I am able to import en-gb successfully however when I import en-us I am told that the wim file can not be read. Is this due to the language setting of my computer or is there another reason for this.

I have tried importing with and without source files and not had any success. They are both from the Microsoft server so I can not see why other that the reason stated.

Any ideas.

Hi,

I got to upgrade my mdt server to 2012 and test deploying win10. Im wondering if you guys have any suggestions on how I can achieve this?

Is it also possibly to "test" deploy win10 without other users being able to pxe boot win10?

//Pelle

Anyone suggest that Deploy different brand PCs with just one single image.

For example:

I use HP pc to capture a HP image.And I deploy it to a Lenovo PC.

I konw this can work,but is it the better way for deployment?and if it's not recommended,is there any officical statement about this?

Looked around for those with the same problem, only to find the only one that's resolved isn't relatable.

I'm trying to deploy a Windows 8.1 installation iso image (so not captured from a machine), and everything works as expected until near the end when the error "Cannot find the script file c:\ltibootstrap.vbs" shows, and it doesn't install the applications I've specified, so they have to be done manually. The operating system is working, however it automatically boots to the local administrator every time, and for the purpose of the machine this should not be happening.

Windows 7 deployment does not have this issue.

Hello All,

As recommended by a lot of SCCM experts I am creating a Win 8.1 reference image using MDT 2013. When I boot my reference VM using the MDT Build Lab x64.iso it gets stuck at "Processing Rules" as pictured below:

This is what my Rules look like:

[Settings]
Priority=Default

[Default]
_SMSTSORGNAME=Death Star Enterprises
UserDataLocation=NONE
DoCapture=YES
OSInstall=Y
AdminPassword=P@ssw0rd
TimeZoneName=Central Standard Time
JoinWorkgroup=WORKGROUP
HideShell=YES
FinishAction=SHUTDOWN
DoNotCreateExtraPartition=YES
WSUSServer=http://hv-host2.wolf.local:8530
ApplyGPOPack=NO
SLSHARE=\\HV-Host2\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

And in the Bootstrap.ini file this is how I have it configured

[Settings]
Priority=Default

[Default]
DeployRoot=\\HV-Host\MDTBuildLab$
UserDomain=Wolf
UserID=MDT_BA
UserPassword=P@ssw0rd

SkipBDDWelcome=YES

Phil Balderos

Having upgraded my MTD 2010 to MDT 2012 update 1,completely regenerate the boot images.I have seen similar errors but cant quite figure out what to do,

I get the following Errors

Cannot find script file "C:\MININT\Scripts\LTICleanup.wsf"

when i click ok to the above,i get the following in my  Deployment summary (with yellow background)

Operating System Deployment completed successfully.

i get a yellow back ground after deployment in completed successfully

During Deployment process, 0 errors and 1 warnings were reported.

Details>>

unable to locate the results.xml file needed to determine the deployment results. (This may be the result of mismatched script versions. Ensure all boot images have been updated)

Are the two errors linked to each other?this has not been the case in MDT 2010 set up prior to the upgrade??

Hi All,

I'm hoping someone can help with this issue, I will provide a little background before introducing the problem to try and make my situation as clear as possible.

Background

- I have recently upgraded MDT from 2010 to 2013 and integrated Windows Assessment and Deployment Kit for Windows 8.1

- My task sequences are split into two folders (x86 and x64), both of these folders contain a deployment image for our commonly purchased PCs. They have been created using a sysprep and capture which was working swimmingly.

- The first time I imaged two new 64x PCs since the upgrade, MDT went through the installation OK (it took all day which is unusual but it did complete), the speed of installation was going to be my next issue however I was faced with a bigger one.

Problem

We have received two new 64x PCs which I am trying to image, however the deployment wizard errors and cancels at the stage of 'Installing Operating System', with the following error:

Litetouch deployment failed, Return Code = -2147467259 0x80004005
Failed to run the action: Install Operating System.
Incorrect function. (Error: 00000001; Source Windows)
The execution of the group (Install) has failed and the execution has been aborted. An action failed.
Operation aborted (Error: 80004004; Source Windows)
Failed to run the last action: Install Operating System. Execution of task sequence failed.
Incorrect function. (Error: 00000001: Source Windows)
Task Sequence Engine Failed! Code: enExecutionFail
Task Sequence execution failed with error code 80004005
Error task sequence manager failed to execute task sequence. Code 0x80004005

This seemed strange as I haven't touched anything since the last successful image. I've been researching the following error and the first thing that I initially tried was to Completely Regenerate the Boot Images when updating the deployment share. Since then I can no longer PXE boot to the 64x WDS, instead it eventually brings up command prompt with X:\windows\system32 that sits on top of the Microsoft Solution Accelorator background, nothing else happens at this point. If I boot to the 32x WDS if does load the deployment wizard where I can actually see the 64 bit task sequence, if however I try to run this I'm prompted with that exact same error above.

The second thing I tried was disabling 'Injecting the drivers' as I thought that the network driver may have been causing a problem and disconnecting me from the deployment share, this however didn't work either.

I'm totally baffled now to be honest and would appreciate anyone helping me out?

Many thanks in advance,

Ad

Hi,

I followed this article in order to create TS to upgrade OS to Windows 10 with MDT:

https://technet.microsoft.com/en-us/library/mt426643(v=vs.85).aspx

Environment:

OS: Windows 8.1

PC: VM (Hyper-V)

However, when I run Litetouch.vbs deployment starts (Running action: Upgrade Windows) but after few minutes also stops without any error. In logs I can see this:

I manually ran Windows 10 setup.exe from Operating System folder in Deployment Share and OS was installed properly. 

Kind Regards,

Hi,

We have upgraded our MDT environment to MDT 2013 Update 1 and ADK W10. Only, now when recreating the boot image we get this message for each NIC driver:

Deployment Image Servicing and Management tool
Version: 10.0.10240.16384

Image Version: 10.0.10240.16384

Found 1 driver package(s) to install.
Installing 1 of 1 - F:\MDT\DeploymentShare\Out-of-box Drivers\Net\e1s6432_12.13.27.0_3C8E49543EA41CDD4D6777E8B710FE430FBAF23C\e1s6432.inf: 
INFO: DISM has skipped driver signature check because the version of running OS and that of target OS do not match.
Error - An error occurred. The driver package could not be installed. 
For more information, check for log files in the <windir>\inf folder of the target image.

Error: 5

Access is denied.

The DISM log file can be found at C:\Windows\Logs\DISM\dism.log

Exit code = 5

DISM /Add-Driver failed, rc = 5.
Injected driver Intel Net e1s6432.inf 12.13.27.0

The strange thing is, that it actually seems that the driver is injected (since MDT WinPE with NIC works just fine). Does anybody has an idea how this message comes and what do about it?

Best,
Steven

<IEWelcomeMsg>false</IEWelcomeMsg>

I have multiple deployment shares setup (Production, Development, International, etc.) and I am trying to use one boot environment for all. I have followed to the documentation about LocationServer.xml, removing the DeployRoot property from Bootstrap.ini, placed the custom LocationServer.xml in \\Share$\Extra Files\Deploy\Control, added Extra Files to the PE settings, and updated the Deployment Share to create a new iso and wim. When the deployment wizard launches it correctly displays the location wizard with the deployment shares' friendly names in the drop down list. But when I try to connect any share it prompts for credentials, which are defined in the Bootstrap.ini. I cannot find any documentation for how to define the deployment share user credentials within the LocationServer.xml file to automate this portion. If I cannot automate the user credentials, then the LocationServer.xml function is pretty much useless for me.

Any thoughts or suggestions?

Thanks,

Wayne C.

When Trying to create a new virtual network I end up getting.

What's going on here

Hello,

I am trying to install Office using MDT but the installation of Office just fails immediately. The OS and other applications install successfully. I get a window with the following:

------------------------------------------
Microsoft Setup Bootstrapper
Problem signature:
Problem Event Name: OfficeClassicSetup
SETUP EXE VERSION: 15.0.4454.1000
SETUP DLL NAME: OSETUP.DLL
SETUP DLL VERSION: 15.0.4569.1503
ERROR CODE: MSIInstallationFailure
MSI HRESULT: Unspecified
ERROR DETAILS: 30D23146
FIRST ERROR CODE: MSIInstallationFailure
OS Version: 6.1.7601.2.1.0.256.48
------------------------------------------

Details are:
- Office Professional Plus 2013 SP1 32-bit VL
- Windows 7 Pro SP1 x64, captured using MDT capture task with all Windows updates as of 9/2015
- MDT 2013 (6.2.5019.0) / ADK 8.1 / WDS running on 2012 R2 server

Troubleshooting done:
- Re-downloaded the Office ISO to rule out potential corruption and recreated the application completely
- Removed OCT file and only using the customization settings within the Office Products tab
- When double clicking setup.exe on a normal OS installation completes successfully

Does anyone know why this may be happening? Thanks in advance

I volunteer at a community computer center. It has one HP server running Server 2012 R2 and 20 workstations (10 running Windows 7 and another 10 Windows 8.1). I'm using MDT 2013 for LTI deployment to the workstations

I found online how to tweak MDT so I could differentiate task sequences in my custom.ini file. My custom.ini provides for two task sequence IDs: WIN7_INSTALL and WIN8_INSTALL. The operator is prompted for which task sequence to run. The properties below are common to both install sequences.

Timezone worked correctly until a month or two back. Then only Win 7 installed as CST. The Win 8.1 machines now install as Pacific Standard Time. (The rest of Win 8.1 properties install correctly)

Why does Timezone keep installing as PST, not CST, for Win 8.1? I've also tried editing the Win8_INSTALL unattend.xml file to define Timezone in every possible spot it's used to no avail.

Any suggestions / insight appreciated.

; Locale and Time Page
SkipLocaleSelection=YES
SkipTimeZone=YES
UILanguage=en-US
UserLocale=en-US
Systemlocale=en-US
KeyboardLocale=0409:00000409
TimeZone=020
TimeZoneName=Central Standard Time

Maybe someone has already done this. I have two Dell application packages made with Dell Command Configure, one turns on TPM and the other Activates it. I’m trying to set it so that the application will only run if it meets the right condition. I’ve gotten this to work for installing Dell's Command Update, it runs a WMI query for certain models and installs the software if the is that model.

For some reason I just can’t figure out what kind of query to make for TPM. If I make a query from the command line I get “no instance(s) available” if TPM is not on. If TPM is on but not activated it'll return a False answer.

Here's what I have

Dell Enable TPM.
Added the following conditions to this application:

If any conditions are true

WMI namespace:root\cimv2\security\microsofttpm
WMI query:SELECT * FROM Win32_Tpm WHERE IsEnabled_InitialValue IS FALSE

WMI namespace: root\cimv2\security\microsofttpm
WMI query:SELECT * FROM Win32_Tpm WHERE IsEnabled_InitialValue LIKE “%No Instance%”

If this post is helpful please vote it as Helpful or click Mark for answer.

I have a very simple unattend.xml that I am copying into a sysprepped Windows Server 2012 R2 VHDX file that I use for deploying my VMs.  I basically want it to set the admin password, hide the EULA, set the locale, and then assign the computer a name.  The first three work just fine.  But the computer name is not getting set.  It's gotta be something simple, but I have not been able to find what I am doing wrong.  Assistance greatly appreciated.  (You can readily tell I am not using MDT to create the file, but I figured the unattend.xml experts would be here.)

<?xml version="1.0" encoding="utf-8"?><unattend xmlns="urn:schemas-microsoft-com:unattend"><settings pass="oobeSystem"><component name="Microsoft-Windows-Shell-Setup" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral"

versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"><UserAccounts><AdministratorPassword><Value>localAdminPwd</Value><PlainText>true</PlainText></AdministratorPassword></UserAccounts><OOBE><HideEULAPage>true</HideEULAPage></OOBE></component><component name="Microsoft-Windows-International-Core" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral"

versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"><InputLocale>en-US</InputLocale><SystemLocale>en-US</SystemLocale><UILanguage>en-US</UILanguage><UserLocale>en-US</UserLocale></component></settings><settings pass="specialize"><component name="Microsoft-Windows-Shell-Setup" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35"
language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"><ComputerName>computerName</ComputerName></component></settings></unattend>

. : | : . : | : . tim