Hi ,

Is it possible to have more application bundlles in MDT and to have the option during the deployment tho choose one of those ?

Can i do this with dependencies ?

thnks

I'm looking for some help on getting my customsettings.ini configured to have Sections as machine models. To give an example we use Lenovo products in our environment and could have three slightly different machine models for a M73 desktop. All the models for the M73 start with 10AY so I would like a section called 10AY that will handle all the M73's we have. This would be the same for all the other Lenovo products we have. I am new to MDT and working with ini files so I might be shooting for things that are out of reach or might be making things harder on myself by doing it this way.

I have tried a couple of things but below is what I have currently for my driver structure and my customsetting.ini file. Any help or guidance you can give is greatly appreciated and if it helps I'm using MDT 2013 Update 1.

Driver Setup

Current CustomSettings.ini File

[Settings]
Priority=#Left("%Model%", 4)#, Init, ByLaptop, Default
Properties=MyCustomProperty

[10AY]
DriverGroup001=Windows 7\x32\Lenovo\M73
DriverGroup002=Windows 7\x64\Lenovo\M73

[Default]
OSInstall=Y
SkipCapture=YES
SkipAdminPassword=YES
SkipProductKey=YES
SkipComputerBackup=YES
SkipBitLocker=YES

I am using MDT 2013 Update 1 with W10 ADK.

I have two Task sequences 1 for Windows 7 and the other for Windows 10

I have two driver root folders in MDT. Note the root\x64 is for windows 7

Driver Root:x64 

Driver Root: Windows10\x64

Then under each root folder there is a sub-folder each model and the applicable drivers.

example: x64\Dell Precision M3800 and windows10\x64\Dell Precision M3800

I have setup selection profile for the each model...  Then created a deployment task sequence to set the driver variable and point it to the appropriate driver Root folder based on the OS (W7 or W10 task sequence).

My questions:

1) Is it necessary to set the selection profile to map the model to the driver folder, since I use a deployment task sequence to set the variable and path for the drivers? 

2) If it is necessary to map your selection profile to your driver folder how do I accommodate for two sets of drivers that are the same model? From testing it appears both the selection profile and the drivers folder have to match the Model name of the pc. Or is selection profile mappings not needed if the deployment task sequence points to the correct root driver folder (windows10\x64\%model% for W10)?

I'm trying to create a Windows 10 image based on build 1511.

I was very surprised when I found that Candy Crush was automatically installed and I have not been able to find a good solution to uninstall crapware completely from the computer.

When a new user logs on the crapware is installed.

Is their a way to create a base image without crapware?

Thanks

Hans  

Hi All,

I'd like to deploy Office 2013 with other pieces of software such as anti-virus.

Antivirus comes in .msi format and office comes in .exe format, other apps come in .exe format too.

I deploy each app as a single application in the task sequence, no bundles or anything like that for now.

The task sequence will wait for the .msi file to finish and then move to .exe files which are the next ones on the task sequence.

The problem I have is that it will execute .exe files and won't wait for them to finish so it will execute setup.exe in office 2013, then setup.exe in another software directory and then move to other task sequence which is reboot. This will cause none of the .exe apps to install. I guess it does that because .exe files generate another processes and then terminate themselves.

I tried start /wait in command line but no luck, same problem.

How do I configure the task sequence so it waits for all apps to install?

I found this which I think is applicable to my problem:

The install programs should not exit until all setup tasks have finished. If the setup program returns, yet there are still installation tasks being performed in the background, MDT has no way to determine this. So MDT may continue with the next installation, or perhaps a reboot thus causing conflicts with the installation running in the background.

For example, say you have two installation packages, A.Exe and B.Msi. A.Exe is just a Self Extracting Executable that expands A.MSI to the %temp% folder, and kicks offmsiexec.exe. However, A.Exe calls msiexec.exe and doesn’t wait, instead A.Exe promptly exits. MDT does not know what is running in the background, and instead continues installing the next package in the list B.Msi. However since A.Msi is running in the backgound, and MSIExec only allows one installation at a time, B.Msi will fail.

Instead A.Exe should wait until Msiexec.exe /i A.msi has finished.

All the best,

Hi,

Does anyone know if it is possible to integrate the recently released Threshsold 2 update into a Windows 10 Enterprise build using that MDT task sequence?

Unfortunately my MDT environment does not have internet access so I can't use Windows Update to integrate the Threshold 2 update during the build creation process. Is there an offline re-distributable MSU file available for this update so that I can integrate it in the Packages section of the Deployment Workbench?

I'm aware that I could deploy the update via WSUS to Windows 10 PCs once they are on our corporate network, but it would be nice if the Threshold 2 update could be included in the build which we apply to new PCs.

Many thanks

I am having so much problems with creating a syspreped image, I figured I would try to create the sysprep image with WDT.  So I tried that, turned of UAC and tried creating an image.  Like with everything else I have done with MDT, nothing seems to work out. 

Here are the bdd.log 

BDD.log

Hi

I hope someone can advise.

I'm trying to build an offline ISO for windows 10 deployment. I am using MDT 2013 Update 1 (build 6.3.8298.1000).

The Selection Profile is created and I can run the Update Media Content wizard. It runs through the folder copy but it is then failing with a message that says

Unable to mount the WIM, so the update process cannot continue.

I have also had it give me dism errors whilst mounting or unmounting the wim file (during the Wizard process), and when this happens,  I need to go into a cmd prompt on the MDT Server and run this

dism /Get-MountedWimInfo

This returns an MDTUpdate.xxxx\Mount  dir with an image file of LiteTouchPE_x64.wim When this happens the only way I can continue is to run dism /unmount-Wim, and this fails to unmounts the wim, unless I have restarted the MDT server, if this is the case, I can unmounts the wim, otherwise I get a dism message saying that the process cannot continue because of a file lock, and I need to restart the MDT Server.

If I do not get the dismhost.exe crash message, the ISO file is created on completion of the wizard. If dism crashed, the iso file is not created.

I have not done any customising of the Offline Media rules, I want ot take it a step at a time and at least get a working iso file before I attempt to introduct some of the automation.

Has anyone seen this before, I can't find anything online about it?

Many Thanks

regards

John

Regards, John

Greetings,

Long time reader, first time poster.

My deployment server works fine.  However, recently I was tasked with deploying to sites where PXE is not allowed. 

I task option of deploying via USB.  This works with out issues depending the OU I select.

We have a few OUs where GPO is set to deny the use of storage devices.

If I deploy and select an OU without the GOP, the process completes without issues.

If I deploy and select an OU which has the GPO in place, shortly after the workstation is joined to the domain, the UBS is blocked.

On the screen the error is -> Please insert the media (CD, DVD or USB) needed to complete the deployment.

The BDD log shows (I don't have access to the logs to upload, however) ->

• Found existing task sequence state information in C:\_SMSTaskSequence, will continue
• Not running within WinPE.
• Unable to find media, prompting to have it reinserted

Would it complete if the move the domain join to the end as I read on forums ?

Is there another way to overcome this such as changing permissions to whatever it needs to be changed then undoing the change?

Is there another solution to my issue?

I have not tried using a USB SSD, however, the GPO does block anytype of storage USB CD so I don't think that will work either.

Thank you for your time

Hello everyone,

I am trying to add the Storage Cmdlets to an existing WInPE Image.

I mounted the boot.wim to C:\mount and run the command 

C:\Windows\system32>dism /add-package /image:C:\mount PackagePath:"C:\Program Files\Windows Kits\8.1\Assessment and Deployment Kit\Windows Preinstallation Environment\x86\WinPE_OCs\en-us\WinPE-StorageWMI_en-us.cab"

The Command Output is as follows:

Tool zur Abbildverwaltung für die Bereitstellung
Version: 6.1.7600.16385


Fehler: 0xc1510115

Das angegebene Abbild ist ungültig.
Heben Sie die Bereitstellung des Abbilds auf, oder bereinigen Sie WIM, und wiederholen Sie dann den Vorgang.

Die DISM-Protokolldatei befindet sich unter "C:\Windows\Logs\DISM\dism.log".

So it tells me that the image is invalid and that I have to unmount the image, clean the WIM and retry.

Can anybody tell me what could cause this error? The log is avaiable via OneDrive.

Thanks in advance!

Regards

Tobias

Hi,

I'm trying to deploy Windows 10 Enterprise x64 to the Dell OptiPlex 5040 Small Form Factor with MDT 2013 Update 1. My deployment task is successful in deploying the image to the computer, but after a series of successive reboots, the local administrator logs in and that's it. The part where the deployment should continue and install applications doesn't happen. The BDD.log file just halts at different steps. This will persist until the computer is manually restarted. Then, it will automatically log in as the administrator again and present the dirty deployment dialog box indicating a previous deployment had not finished etc... I opt to not start a new deployment, and it seems as if the original deployment restarts and finishes with the application installs. The end if the "Deployment Not Successful" screen, indicating that the deployment couldn't find the NIC and that it could not continue over wireless. The ethernet driver is installed throughout the entire deployment without error. Curiously, the NIC is listed as "Intel(R) Ethernet Connection (2)" Uninstalling/reinstalling the NIC doesn't change that designation. It is an Intel i219-V adapter. I checked for updated drivers from the Dell and Intel sites, but there are none. Could this be the issue? I can't find anything regarding it online. The last error from the "Deployment Unsuccessful" screen is about the SLShare having an invalid path. The path is correct and the log files are written there at the end. SLSDynamicLogging is enabled for the deployment share so I can see where the task is failing.

Any ideas?

Thanks

Jason

I've read though previous references to this error in this forum.  I can see the Application.xml file in ,\Deploy\Control folder.  I've looked through the BDD.log file but still can't pinpoint the issue.  It was working one day and received this error the next day.  Any further advice?

Thank you

<job id="Z-Sample"><script language="VBScript" src="ZTIUtility.vbs"/><script language="VBScript">

' //***************************************************************************
' // ***** Script Header *****
' //
' // Solution: Solution Accelerator for Microsoft Deployment
' // File: Z-Sample.wsf
' //
' // Purpose: Template
' //
' // Usage: cscript Z-Sample.wsf [/debug:true]
' //
' // Customer Build Version: 1.0.0
' // Customer Script Version: 1.0.0
' // Customer History:
' //
' // ***** End Header *****
' //***************************************************************************

'//----------------------------------------------------------------------------
'//
'// Global constant and variable declarations
'//
'//----------------------------------------------------------------------------

Option Explicit

Dim iRetVal

'//----------------------------------------------------------------------------
'// End declarations
'//----------------------------------------------------------------------------

'//----------------------------------------------------------------------------
'// Main routine
'//----------------------------------------------------------------------------

On Error Resume Next
iRetVal = ZTIProcess
ProcessResults iRetVal
On Error Goto 0

'//---------------------------------------------------------------------------
'//
'// Function: ZTIProcess()
'//
'// Input: None
'//
'// Return: Success - 0
'// Failure - non-zero
'//
'// Purpose: Perform main ZTI processing
'//
'//---------------------------------------------------------------------------

' To Delete a Registry Key Value
Function RegDelete( sRegValue )
    RegDelete = oShell.RegDelete ( sRegValue )
end Function

Function ZTIProcess()

     iRetVal = Success
     ZTIProcess = iRetval
        ' Call function and delete key
        Dim sRegDeleteValue, sRegKey
        sRegKey = "HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Windows\WindowsUpdate"
        oLogging.CreateEntry "Preparing to delete Registry key " & sRegKey, LogTypeInfo
        sRegDeleteValue=regDelete(sRegKey)
End Function</script></job>

Hi

I'm trying to do a build and capture of Windows 10 using MDT 2013 Update Preview 1. This worked fine on my workstation but since moving to a dedicated 2012 R2 server I am having problems trying to update the Deployment Share and generate my boot images.

The error output looks like this:

Copy: D:\Program Files\Microsoft Deployment Toolkit\Samples\Background.bmp to C:\Users\user\AppData\Local\Temp\MDTUpdate.3448\Mount\Windows\system32\winpe.bmp

ERROR: The process cannot access the file because it is being used by another process. 
Exit code = 1
REG LOAD failed, rc = 1.
System.Management.Automation.CmdletInvocationException: Unable to open the specified WIM file. ---> System.Exception: Unable to open the specified WIM file. ---> System.ComponentModel.Win32Exception: The operation completed successfully
   --- End of inner exception stack trace ---
   at Microsoft.BDD.Core.BDDWimFile..ctor(String wimPath, Boolean forUpdate)
   at Microsoft.BDD.PSSnapIn.UpdateDeploymentPoint.UpdateBootImage(String template, String platform, String dpPath, Boolean createISO, String isoName)
   at Microsoft.BDD.PSSnapIn.UpdateDeploymentPoint.ProcessRecord()
   at System.Management.Automation.CommandProcessor.ProcessRecord()
   --- End of inner exception stack trace ---
   at System.Management.Automation.Runspaces.PipelineBase.Invoke(IEnumerable input)
   at Microsoft.BDD.Wizards.UpdateProgress.WizardProcessing()
   at Microsoft.BDD.Wizards.WizardProgress.InitiateWizardProcessing()

Am I correct in saying its failing because the background.bmp file is in use by something else or barking up the wrong tree?

Thanks in advance,

Jonathan

Hi everyone. Im currently deploying Windows 7, 8.1 and 10 using a standard MDT setup. Since i dont have access to our DHCP server, im using a USB-stick with the boot image, and then connet to the deployment share. Everything have worked great for over a year.

Now i wanted to try to deploy images using UEFI. So i disabled lagcy boot in UEFI/BIOS and booted up on my Stick. No problem i got into the deployment wizard and i can do all my settings. The deployment starts and applys the OS. But when the image has been applied, i get the error: "5615: False: Boot Drive was not found, required?"

Ive done some googling and found several tips and i have tried several diffrent things without succsess. I have changed frpm MBR to GPT in the TS settings and i also tried to remove the USB key befor starting the deployment, with no success. I would really like some help on this. Anyone with any idees? Thank you

I have multiple applications in MDT that use batch files for installation. They all do not work anymore since we upgraded to MDT 2013 Update 1 (it was still working in the preview version).

I used Procmon and found that, when the installation command is "batchfile.cmd", BDD.EXE opens a process "c:\windows\system32\cmd.exe /c batchfile.cmd", and then that CMD process looks for

• C:\Windows\batchfile.cmd
• C:\Windows\System32\batchfile.cmd
• C:\Windows\System32\wbem\batchfile.cmd
• C:\Windows\System32\WindowsPowerShell\v1.0\batchfile.cmd

and then exits with error code 1.

Obviously CMD.EXE is executed in C:\Windows\System32, not in the specified working directory. It has been working in MDT 2012, MDT 2013, and MDT 2013 Update 1 Preview.

Hey guys,

I've been searching for this and haven't found an answer yet.

I started using a total-control method deploying my drivers and for the most part it's been great - But when trying to import my driver package to another deployment share, it reports tat it cannot copy files because there are duplicates.

I thought it might have just been complaining about the files itself (because MDT seems to manage the back end files on its own, as not to create duplicates, etc.) and still be copying all the links in my organized folders... but it isn't doing them either.

Has anybody found a solution for this?

Thanks,

I'm currently running MDT 2013 Update 1 on a Windows 2012 R2 with WDS. I imported the OS files, drivers for Surface and created Task Sequence. I boot Surface Pro 3 into PXE and select my task and all works fine, it even loads the OS but when it tries to capture the image as the second phase it always fails with "Expected image state is Image_State_Generalize_Reseal_to_OOBE, actual image state is Image_State_Complete, sysprep did not succeed. Failure 6192, Litetouch deployment failed, return code = -2147467259 0x80004005"

I try capturing the image using a Sysprep and capture, connected to Deployment share and ran LiteTouch.vbs and wizard comes up and it starts to run thru the task but it fails in the same error. Driving me nuts and not sure why it's happening. I need to complete this image ASAP and I'm wondering if I'm hitting a MDT 2013 bug.

thanks in advance.