hi all

i have a MDT Server in my Azure Location. Now my goal is, to create new Azure VM´s that run after creating automaticly a MDT Tasksequence without any interactions. Is that possible and when yes, how? i was not able to run a MDT Tasksequence without my interaction. For Testing i logged into a Azure VM what i have created before, and let than run the litetouch.vbs, and pick up my Task (Post Install Task), and than all is running fine. But i will do that when i create the Azure VM´s over Posh, but i dont know how i can do that fully automated. Is there a way?

Regards Frank

Hi Guys,

I have a new problem with my MDT 2012. Always appear in the Deployment Summary 2 errors:

ERROR: Invalid Task Sequence ID DEPLOY-WIN8 specified

FAILURE ( 5496 ): 1:LoadControl File.FindFile: DEPLOY-WIN8\TS.XML

I'm have searching of this errors on other sites / places but unfortunately not exist much information about this yet.

Anybody know why happens this errors or have any ideia how can i skip this?

Thank You!

Regards,

We recently implemented a new instance of ConfigMgr with MDT integration, and now my OSD task sequence hangs up after installing Office 2010. The Office 2010 package is configured (using OCT) with Reboot=Never but the system reboots anyway immediately after the Office install, and then whatever application is supposed to install next never installs and the whole task sequence hangs.  The task sequence ran without issue in the old ConfigMgr environment.

Old environment: SCCM 2012 R2, ADK 10.0.26624, MDT 2013 Update 2

New environment: CM 1710 w/hotfix rollup KB4086143 (v5.00.8577.1115), ADK 1709, MDT 8440.

Can anyone shed some light on why this is happening now?

Thanks,

David

I'm hope im posting this in the correct forum, I recently setup my wds and mdt and successfuly captured and deployed windows 10 images. I want to know how I can make a users credential tied to a task sequence. For example if theirs a username jsmith and hes in finance and he needs to reimage his laptop all he does is to connects to the internal network and pxe boot his machine to windows deployment wizard, now aside from him clicking on a task sequence to image his machine, how can i make it that a paticular user  group or a department can be tied to a task sequence meaning as soon as the credentials and password is entered the proper task sequence is run. like jsmith enters their credentials and Asanders enters their credentials and that users is in a different department both users get different task sequence that run and install automatically. Excuse my grammer errors english is my second lanaguage. Thank You

In the past I would create a bootable usb by doing the following:

Open Command Prompt as Administrator
Diskpart
List Disk
Select Disk x (X = the desired USB)
Clean
Create Partition Primary
Select Partition 1
Format fs=ntfs quick
active
assign
exit

Then I would copy over the necessary items onto the usb (boot folder, sources folder with the boot.wim and bootmgr) and go boot off of USB in legacy mode. Each machine I did this to would access the MDT server and I could image just find. If I go use the same USB in one of our custom labs and image but in UEFI mode they seem to work just fine (Asus motherboards). I now have a dell inspiron 7577, it won't even see the USB drive unless I put it in legacy. We are getting new machines and would like to start using UEFI, but we need to continue to image. Almost everyone gets dells, unless there are special circumstances. I need to know how to fix this. I even tried formatting the USB in fat32 because I read somewhere that it would help. Thank you in advance.

Hello,

We are deploying Windows 7 Professional images and are using Windows Server 2003 R2 using MDT.  We have one deployment share but that is giving us some problems when we upload new images.  So we decided to just start from scratch and create a new deployment share.  While testing the new one out, we get the following error at the end of the deployment: MDT Failure (5210): ValidateDeployRootWithRecovery: Cancel.

The old deployment share deploys images without this message.  The new share is located in the same location with the same permissions so I know it is not a permissions error.  I have also copied over the same WIM files that were working in the old share to the new, and copied the TS.xml files over too to assure the task sequence is the same.  That had failed too.  I believe it is some setting when I created the new deployment share.  I have checked the bootstrap.ini file and the Network (UNC) path in the properties of the deployment, and both point to the correct location.  I can't think of anything else.  Does anyone have any insight on this?

Ohh.  Here is some lines from the BDD.log from a deployed image from C:\Windows\Temp\DeploymentLogs.  If I didnt post enough, I can add more.  It's fairly long.

<![LOG[FAILURE ( 5210 ): ValidateDeployRootWithRecovery: Cancel]LOG]!><time="09:13:26.000+000" date="02-12-2013" component="LiteTouch" context="" type="3" thread="" file="LiteTouch"><![LOG[ZTI Heartbeat: command has been running for 5 minutes (process ID 1544)]LOG]!><time="11:42:00.000+000" date="02-22-2013" component="LTIApply" context="" type="1" thread="" file="LTIApply"><![LOG[ZTI Heartbeat: command has been running for 10 minutes (process ID 1544)]LOG]!><time="11:47:00.000+000" date="02-22-2013" component="LTIApply" context="" type="1" thread="" file="LTIApply"><![LOG[ZTI Heartbeat: command has been running for 15 minutes (process ID 1544)]LOG]!><time="11:52:00.000+000" date="02-22-2013" component="LTIApply" context="" type="1" thread="" file="LTIApply"><![LOG[Return code from command = 0]LOG]!><time="11:52:30.000+000" date="02-22-2013" component="LTIApply" context="" type="1" thread="" file="LTIApply"><![LOG[Setup completed successfully.]LOG]!><time="11:52:30.000+000" date="02-22-2013" component="LTIApply" context="" type="1" thread="" file="LTIApply"><![LOG[LTIApply processing completed successfully.]LOG]!><time="11:52:30.000+000" date="02-22-2013" component="LTIApply" context="" type="1" thread="" file="LTIApply"><![LOG[Microsoft Deployment Toolkit version: 6.0.2223.0]LOG]!><time="11:52:31.000+000" date="02-22-2013" component="ZTINextPhase" context="" type="1" thread="" file="ZTINextPhase"><![LOG[The task sequencer log is located at X:\windows\TEMP\SMSTSLog\SMSTS.LOG.  For task sequence failures, please consult this log.]LOG]!><time="11:52:31.000+000" date="02-22-2013" component="ZTINextPhase" context="" type="1" thread="" file="ZTINextPhase">

I've did a search through this forum for this, but the methods I've found haven't worked out for me. Does anyone here do this currently in their MDT? If so can you please share how you are pulling this off. I found a .vbs script that will work if I run it manually from a command prompt with the same credentials I have set to run as in the TS. But I cannot get it to run during the task sequence. Below is the vbs script and showing how I have had it listed in the TS. I have it set to run under a service account that has domain rights to move to OUs. 

I have set it to run in the task sequence the following ways.

cscript.exe "%SCRIPTROOT%\MoveOU.vbs" "OU=TEST OU,DC=MYDOMAIN,DC=COM"

cscript.exe %SCRIPTROOT%\MoveOU.vbs "OU=TEST OU,DC=MYDOMAIN,DC=COM"

\\mdtserver\deployshare$\scripts\MoveOU.vbs "OU=TEST OU,DC=MYDOMAIN,DC=COM"

Here is the script.

' //***************************************************************************
' //***************************************************************************
' // ***** Script Header *****
' //
' // Solution:  ConfigMgr
' // File:      MoveComputerToCorrectOU.vbs
' // Author:Jakob Gottlieb Svendsen, Coretech A/S. http://blog.coretech.dk
' // Purpose:   Move computer to the correct OU that remains in variable MachineObjectOU
' //Run inside TS after install
' //
' // Usage:     MoveComputerToCorrectOU.vbs
' //
' //
' // CORETECH A/S History:
' // 0.0.1JGS 17/12/2009  Created initial version.
' // 0.0.2MIP 17/03/2009 Added feature to add argument to script
' // 0.0.3  JGS 02/12/2010  Changed to ADSystemInfo for the DN retrieval, instead of a homemade function.
' //Thanks to Nico_ at Technet Forums
' //
' // Customer History:
' //
' // ***** End Header *****
' //***************************************************************************
'//----------------------------------------------------------------------------
'//  Main routines
'//----------------------------------------------------------------------------

On Error Resume Next

'Get MachineObjectOU Value
Set wshNetwork = CreateObject("WScript.Network")
Set oFso = CreateObject("Scripting.FileSystemObject")
Set objSysInfo = CreateObject( "ADSystemInfo" )
Set ArgObj = WScript.Arguments

'Use first argument as target OU
strMachineObjectOU = ArgObj(0)
strComputerDN = objSysInfo.ComputerName

nComma = InStr(strComputerDN,",")
strCurrentOU = Mid(strComputerDN,nComma+1)
strComputerName = Left(strComputerDN,nComma - 1)

'If current ou is different than target OU. Move object
If UCase(strCurrentOU) <> UCase(strMachineObjectOU) Then
Set objNewOU = GetObject("LDAP://" & strMachineObjectOU)
Set objMoveComputer = objNewOU.MoveHere("LDAP://" & strComputerDN, strComputerName)
End If 

'//----------------------------------------------------------------------------
'//  End Script
'//--------------------------------------------

I have a working XML which sets all preferred tabs on the Start Menu. Works great!
I've been reading about adding taskbar choices in the XML and setting them both during deployment.

I'm working with 1703.

I found many, many sample XML's which combine the Start Menu and Taskbar. After tweaking a few, I finally got to a white summary screen. However, the taskbar was right but the Start Menu had ALL buttons on it.
While working on the XML, it would fail saying that the XML was not valid. I created the initial XML with PS and use a PS script to import it in my TS. As I said, it works applying the Start Menu if all I have in my XML is for the Menu. Adding the taskbar info, that part works and the Start Menu doesn't. Below is the combined XML for both settings:

I will reply to this post and paste in just the Start Menu text which works as a stand-alone

<?xml version="1.0" encoding="utf-8"?>
<LayoutModificationTemplate
    xmlns="http://schemas.microsoft.com/Start/2014/LayoutModification"
    xmlns:defaultlayout="http://schemas.microsoft.com/Start/2014/FullDefaultLayout"
    xmlns:start="http://schemas.microsoft.com/Start/2014/StartLayout"
    xmlns:taskbar="http://schemas.microsoft.com/Start/2014/TaskbarLayout"
    Version="1">
  <LayoutOptions StartTileGroupCellWidth="6" />
  <DefaultLayoutOverride>
    <StartLayoutCollection>
      <defaultlayout:StartLayout GroupCellWidth="6" xmlns:defaultlayout="http://schemas.microsoft.com/Start/2014/FullDefaultLayout">
        <start:Group Name="Apps" xmlns:start="http://schemas.microsoft.com/Start/2014/StartLayout">
          <start:Tile Size="2x2" Column="2" Row="0" AppUserModelID="Microsoft.BingWeather_8wekyb3d8bbwe!App" />
          <start:Tile Size="2x2" Column="0" Row="0" AppUserModelID="Microsoft.WindowsStore_8wekyb3d8bbwe!App" />
        </start:Group>
    <start:Group Name="Office 365" xmlns:start="http://schemas.microsoft.com/Start/2014/StartLayout">
          <start:DesktopApplicationTile Size="2x2" Column="0" Row="0" DesktopApplicationLinkPath="%ALLUSERSPROFILE%\Microsoft\Windows\Start Menu\Programs\Outlook 2016.lnk" />
          <start:DesktopApplicationTile Size="2x2" Column="2" Row="0" DesktopApplicationLinkPath="%ALLUSERSPROFILE%\Microsoft\Windows\Start Menu\Programs\Word 2016.lnk" />
          <start:DesktopApplicationTile Size="2x2" Column="4" Row="0" DesktopApplicationLinkPath="%ALLUSERSPROFILE%\Microsoft\Windows\Start Menu\Programs\Excel 2016.lnk" />
        </start:Group>
        <start:Group Name="LanDesk Management" xmlns:start="http://schemas.microsoft.com/Start/2014/StartLayout">
          <start:DesktopApplicationTile Size="2x2" Column="0" Row="0" DesktopApplicationLinkPath="%ALLUSERSPROFILE%\Microsoft\Windows\Start Menu\Programs\LANDESK Management\Security Scan.lnk" />
          <start:DesktopApplicationTile Size="2x2" Column="2" Row="0" DesktopApplicationLinkPath="%ALLUSERSPROFILE%\Microsoft\Windows\Start Menu\Programs\LANDESK Management\Inventory Scan.lnk" />
        </start:Group>
      </defaultlayout:StartLayout>
    </StartLayoutCollection>
  </DefaultLayoutOverride>
    <CustomTaskbarLayoutCollection>
      <defaultlayout:TaskbarLayout>
        <taskbar:TaskbarPinList>
          <taskbar:DesktopApp DesktopApplicationLinkPath="%APPDATA%\Microsoft\Windows\Start Menu\Programs\System Tools\File Explorer.lnk" />
      <taskbar:DesktopApp DesktopApplicationLinkPath="%APPDATA%\Microsoft\Windows\Start Menu\Programs\Accessories\Internet Explorer.lnk" />
      <taskbar:UWA AppUserModelID=Microsoft.WindowsStore_8wekyb3d8bbwe!App" />
        </taskbar:TaskbarPinList>
      </defaultlayout:TaskbarLayout>
    </CustomTaskbarLayoutCollection>
</LayoutModificationTemplate>

Hi all,

Trying to deploy Windows 10 to a Hyper V VM with MDT. It gets to "Install Operating System" in the Task Sequence and then fails. 

BDD.log is saying this:

FAILURE ( 5624 ): 13: Run DISM:  /Apply-Image /ImageFile:"\\mdtserver\DeploymentShare$\Operating Systems\Windows 10 Pro x64 1803\WIN10PRO.wim" /Index:1 /ApplyDir:D:

Litetouch deployment failed, Return Code = -2147467259  0x80004005

It is a 50 GB Virtual Drive and the TS looks to be partitioning it correctly so I don't believe it's a partitioning issue. 

The VM has 4GB of RAM.

DISM.log is saying this:

2018-05-02 11:20:00, Error                 DISM   DISM WIM Provider: PID=1788 TID=1768 onecore\base\ntsetup\opktools\dism\providers\wimprovider\dll\wimmanager.cpp:991 - CWimManager::Apply(hr:0x8007000d)

2018-05-02 11:20:00, Error                 DISM   DISM Imaging Provider: PID=1788 TID=1768 onecore\base\ntsetup\opktools\dism\providers\imagingprovider\dll\genericimagingmanager.cpp:2813 - CGenericImagingManager::InternalCmdWimApply(hr:0x8007000d)

2018-05-02 11:20:00, Error                 DISM   DISM Imaging Provider: PID=1788 TID=1768 onecore\base\ntsetup\opktools\dism\providers\imagingprovider\dll\genericimagingmanager.cpp:547 - CGenericImagingManager::ExecuteCmdLine(hr:0x8007000d)

Any  ideas?

Hello, Well i have tried many things before logging this but i have been unable to Sysprep and capture a Windows 10 1803 build installed on a VM using vmware.

Each time i run litetouch.wsf from the command line , i select the TS of capture which is the standard Sysprep and Capture TS (no changes).

This then shows the next screen where normally when i have captured of windows 10 build im able to select Capture and select a location of where to save the wim to. However now the default selection is to DO Not Capture an Image.

Anyway i have tried changing this to Capture (the top most selection on the screen) and select a location of where to save the wim file to. This then proceeds and and starts its sysprep, now before i upgraded to the latest mdt 8450 version i was getting the error before reboot of can not find the script lticleanup but now after the 8450 update i do not get that error the system restarts and i get the windows setup , then once finished i get can not find ltibootstrap and no capture has taken place.

I have a feeling i need to update the windows ADK but as i have already updated mdt i dont want to make things not work for my existing deployments.

Has anyone updated Windows ADK after MDT and are there things that need to be re-done to MDT after the ADK update, like update the deploy share?

Thanks 

I recently created a new task sequence in the latest version of MDT 8450 to do an in-place upgrade to Windows 10 Pro (1709) where it injects drivers for specific models of newer hardware that we still have Windows 7 running on. Running it off of the server works flawlessly and upgrades every time I do it. We have close to 1,000 machines that have to be upgraded to Windows 10 so it would not be feasible to bring them into the main office and upgrade so I decided to make offline media to upgrade. I followed the same steps I did to make the offline media that I use to actually deploy Windows on a machine at a remote site (which works with no issues) but it is hanging on the action "Upgrade Windows" where the progress bar is sitting about 3/4 the way across on both lines and doesn't move. I have went into the log files on the machine and it looks like it is hanging on the  LTIApply and the log file shows the following:

<![LOG[ZTI Heartbeat: command has been running for 1035 minutes (process ID 4496)]LOG]!><time="07:19:00.000+000" date="09-20-2018" component="LTIApply" context="" type="1" thread="" file="LTIApply">

This is the last line in the log file before I made a copy of it, and I am totally lost on what could be doing this. It does it if the network is plugged in, or not plugged in. Everything else seems to work fine, it injects the drivers as it should but never finishes the upgrade.

Thanks.

I upgraded MDT to 6.3.8450.1000 and I am seeing a new, sporadic problem. I am doing a new computer implementation. The BDD logs displays this message: Task Sequence contains a LTIApply.wsf step, and is not running within WinPE. The following line in in the log is: Property DeploymentType is now = REFRESH.  This causes the task sequence selection screen to reappear. The technician selects the same task sequence and then completes successfully. This does not happen on every machine. This is happening on the task sequence step Post-Apply Cleanup, which executes this command: cscript.exe "%SCRIPTROOT%\LTIApply.wsf" /post

Any ideas where I can look to figure out what is causing this?

Thanks in advance. 

I have several remote deployment shares on my network. I have monitoring turned on and is pointing to my central MDT server. We are a large enterprise and image thousands of computers each year. MDT meets our needs without spending the money for SCCM.

Is there a way to look at an active session and see what deployment share is doing the deployment? 

If not, here's a suggestion for for the future! Maybe even add the user who is doing the deployment?

Hi Community,

For a customer we need to create a rather unique boot device for offline installation and we're having unexplainable errors.

Goal:
To provide  bootable USB pendrive with pre-configured Windows 10 x64 uefi and Windows 7 x86 bios operating systems.

Environment:
Server 2016 build: 14393.2368
MDT build: 6.3.8450.1000
W10 X64 build: 16299.192 (1709) UEFI
W7 SP1 x86 BIOS

Situation:
We've set the settings.xml file to split the .wim image files to fit on a fat32 drive, and if we build a USB pendrive for either one OS this goes as designed.

The issue:
If we create the multi-OS USB pendrive, MDT stops at different places;
- Cannot find the x86 image
- File already exist (with no further explanation)
- Cannot find the x64 image

We looked at the working directories for MDT and saw that the %appdata%\temp directory is used sometimes and causes the 'file already exist' error, but we cannot explain why MDT is splitting the wim image in the same directory as the deploymentshare\Operating Systems folder (and sometimes removing the original wim file.

What are we missing or did we stumble across a bug in MDT?

We are in the position to support both solutions (if possible on one device)

Thanks in advance!

Dear Sir, 

We have purchased paper licence for our office, i have tried to activate windows 7 as we have paper licence but we unable to activate after doing setting twice of date and time and as well as also check time in BIOS. 

Windows 7 Activation Key Error - 0x80072f8f

Please help us to resolve this issue. 

Hi all,

I've got a bit of a weird annoyance with installing Windows 10 on the above model of machine where it will, using MDT, install the O/S, but will then drop to a command prompt instead of restarting and continuing the build. If I restart the PC manually it all carries on and completes with no issues.

I've tried updating the drivers in MDT with the latest available from HP and intel etc, but it makes no difference.

We build several different models and this only seems to affect the elitebook 840s.

It's an issue deploying Windows 10 1709 and 1803 at least, using a standard client task sequence.

Any ideas?

Thanks

I created LiteTouch iso image and deployed by booting with a USB hard drive (iso contents copied to the HD, select the USB HD to boot via BIOS). The deployment seems started ok, but it prompted me to "Specify which deployment share to use" with 'X:\Deploy' filled.

This is a HD deployment, why was I asked for this? Are there any other "deployment share" available during the process?

How can I avoid this prompt?

Thanks!

I am seriously inexperienced with MDT but I am trying to build an image which has everything within the ISO image itself. I have accomplished importing applications and getting them to install silently. I am now trying to find a way of skipping certain aspects of welcome stage when you have to choose things like Bitlocker, admin password and things like that.

At the moment the rules i have set will not take effect and skip the specified options. I am wondering whether this is due to the bootstrap.ini attempting to connect the my deployment share, which i do not want to happen.

Currently this is what the Bootstrap.ini looks like.

[Settings]
Priority=Default

[Default]
DeployRoot=\\DESKTOP-AGSIBB9\MDTBuildLab$

I do not want any connection at all between the PC i am installing windows on and the deployment share. I would like it completely separate and for it too take everything from the USB it is booting from.

This is the Customsettings.ini which i want it too use.[Settings]
Priority=Default
Properties=MyCustomProperty

[Default]
OSInstall=Y

SkipAppsOnUpgrade=YES
SkipCapture=YES
SkipAdminPassword=YES
SkipProductKey=YES

SkipDeploymentType=YES
DeploymentType=NEWPC

SkipDomainMembership=YES

SkipTaskSequence=YES
TaskSequenceID=TEST

SkipComputerName=YES
OSDComputerName=%INTLON0001%

SkipPackageDisplay=YES
LanguagePacks001={3af4e3ce-8122-41a2-9cf9-892145521660}
LanguagePacks002={84fc70d4-db4b-40dc-a660-d546a50bf226}

SkipLocaleSelection=YES
UILanguage=en-GB
UserLocale=en-GB
KeyboardLocale=0809:00000809

SkipTimeZone=YES
TimeZoneName=GMT Standard Time

I am skipping domain membership for the moment while testing aswell as Bitlocker and several other aspects which require connection to the network. 

I hope this has explained well enough. I would appreciate any help as I have been pulling my hair out over this.

Many thanks,

Liam