After upgrading MDT to 6.3.8443.1000 and ADK to 10.1.14393.0 the TS used to capture Windows stopped working properly. I checked the rules from CS.ini and nothing is changed, but now it seems the SkipCapture=NO is ignored and the capturing TS behaves like a deployment TS (the wizard doesn't display anymore the window where you can choose to capture, when you run theLiteTouch.vbs). I tried to create a new Capturing TS on the upgraded capturing share or a new capture share dedicated only to the capturing process (as the one that I upgraded) with a new TS but with the same result. If I uninstall MDT 8443 and install the previous version and create a new Capture Share and Capturing TS, the capturing process works again. So, I think the problem is with the new MDT update not with the CS.ini or ADK or TS and I couldn't find a fix for this. 

The deployment TSs seems to work ok, but I just upgraded today and I used them only for a short period of time, so I’ll see if I’ll discover anything wrong with them later.<o:p></o:p>

Does anyone encountered something similar with the new update of MDT? Do you have any suggestions regarding this?<o:p></o:p>

These are the rules from the CS.ini that I used to successfully capture Win 10 and 7, until I upgraded to the latest version of MDT:<o:p></o:p>

[Settings]
Priority=Default
Properties=MyCustomProperty

[Default]
OSInstall=Y
SkipCapture=NO
SkipAdminPassword=YES
SkipProductKey=YES<o:p></o:p>

Thank you! (This is not part of CS :))))  )<o:p></o:p>

I know this is a commonly asked question. I believe I've followed all the steps within this guide.

"https://social.technet.microsoft.com/Forums/en-US/3e083173-f5db-48e9-b744-f71b9ca6541c/how-to-debug-missing-drivers-in-mdt?forum=mdt"

The machine I'm trying to build is a Dell OptiPlex 7040, I've downloaded the cab file from the Dell Support page, and I've updated the Deployment Share, and then replaced the .wim file. 

I beg any help!!

I did a ref image in my mdt-build share, and imported the finished images with "hardinstalled" applications and fully updated, into my mdt-production share. And it applied just fine, but after I am getting:

My Rules looks like this, I guess it have nothing to do with the rules, but who knows..

I've got the newest Windows 10 WIM and am trying to slip stream a package into it. I keep getting an Error 50, To Service this Windows Image requires the latest version of DISM.  DISM version on my server is 6.3.9600.17031 and the one on my Win10 WIM is 10.0.14393.0.  So I've copied the DISM folder and Dism.exe from the mounted WIM back to my server and attempted to run DISM again but from my new DISM folder.  Still getting the error though.  The dism.log file shows:

2016-12-15 14:08:10, Info                  DISM   PID=6572 TID=12076 DismCore.dll version: 6.3.9600.17031 - CDISMManager::FinalConstruct

which appears to me that it is still trying to use the older version.  Do I need to register the newer dll before I can continue or is there something else that I'm missing?

Is there a Command Line/Powershell command I could have MDT do to prevent any non-administrator users from logging into a workstation until MDT successfully completes a deployment?

I tried googling around but keep getting flooded with unrelated results of what I'm looking for. The purpose is should staff/students power off a computer mid-task sequence, because it's on the domain students or staff can log into a computer that has not successfully completed the MDT task sequence and therefore are using an unsecured computer.

The first glimmer of hope was trying to use the 'deny local logon' security settings to allow only administrator accounts to log in at the interactive logon, however I can't seem to find any method to use Batch or Powershell scripts to lock it down when MDT starts, then remove the lock down when MDT successfully finishes.

I do not want to disable the mouse and keyboard as should MDT get interrupted, we need techs able to log in to see what went wrong. I also don't want to make the domain join be the last step in the task sequence as because we use Deep Freeze, I want the domain join early on so the computer has lots of time to download group policy and printer driver/settings.

Any idea how we could lock out staff and students from using a computer until MDT successfully completes a task sequence?

Zair

Hi everybody,

I would like to stop using the default compact database to an actual DB stored in SQL server. What would be the best approach? Create an other one? Convert the existing one? Is that even possible?

Thanks all for your help!

All,

I have constructed a test environment following the steps laid out in this excellent video from Micheal Beaver:

https://www.youtube.com/watch?v=QOgvECpIsAI

The only difference between Micheal's setup and mine is that I do not have a AD/Domain environment and I want to deploy my images via a local WORKGROUP scenario.

My MDT server is called SRV-DS01. I am using MDT 2013 Update 2 on Windows Server 2012 R2. I have WSUS setup and fully synced and here are the contents of my CustomSettings.ini:

[Settings]
Priority=Default
[Default]
_SMSTSORGNAME=MDT Build
UserDataLocation=NONE
DoCapture=YES
OSInstall=Y
AdminPassword=MyAdminPW
TimeZoneName=Mountain Standard Time
JoinWorkgroup=WORKGROUP
HideShell=YES
FinishAction=SHUTDOWN
DoNotCreateExtraPartition=YES

WSUSServer= http://SRV-DS01:8530

ApplyGPOPack=NO

SLShare=\\SRV-DS01\DeploymentLogs$
SLShareDynamicLogging=\\SRV-DS01\DeploymentLogs$

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=NO

And my Bootstrap.ini settings

Q: Is the UserDomain field causing an issue by placing the computer name there? I have found a ton of conflicting reports on what needs to be there. From the computer name to a period "." or something else?

Settings]
Priority=Default

[Default]
DeployRoot=\\SRV-DS01\MDTBuild$

UserDomain=SRV-DS01
UserID=MDT_BA
UserPassword=P@ssw0rd

SkipBDDWelcome=YES

I have spent probably a good hour modifying share permissions and security permissions on the MDT Build share. I have checked and rechecked the Task sequence and other settings. I have built and rebuilt the LiteTouch iso and replaced it in WDS several times.

But everytime I spark up a client VM to test - PXE boot is fine, accessing/downloading wim is fine, MDT screen appears, looks like it rolls thru the Rules section (or maybe not?) and then hangs on the Processing Bootstrap Settings and says Processing rules....for like ever.

What am I missing here?

Appreciate some sort of tip to get past the madness :)

B

I'm having a very strange problem which was not happening one day, and then was happening the next. 

I have a web service which is accessed via a vbscript during the rules processing stage of an MDT deployment (MDT 2012 Update1).  The script now returns the error "The supplied certificate is invalid"

The important parts of the code are as follows:

Dim oHTTP2, oXML
Set oHTTP2 = CreateObject("MSXML2.ServerXMLHTTP")
Set oXML = CreateObject("MSXML2.DOMDocument")
oXML.setProperty "SelectionLanguage", "XPath"
oHTTP2.open "POST", "https://<fqdn>:446/DesktopImagingSvc/DesktopImagingSvc.asmx/<Method>, False,"<domain/userID>","<password>"
oHTTP2.setRequestHeader "Content-Type", "application/x-www-form-urlencoded"
oHTTP2.SetOption 2, 13056   ' supposed to ignore certificate errors, but doesn't work
oHTTP2.send sEnvelope    'send the envelope

The send method produces the error even though the SetOption 2,13056 is supposed to ignore errors. 

This script works fine in Windows, just not in WinPE.  I've tried the following:

- rebuilding my PE media

- using newer versions of WinPE (up to Win10)

- Using MDT standard scripts (ZTIDataAccess.vbs)

- Using different versions of the ServerXMLHTTP object (6.0)

According to a coworker some of our certificates were replaced recently and since our code has never changed the problem must be on the server side.  I don't know what else to try.

Any suggestions would be greatly appreciated.

Woody

i am using MDT offline task sequence to install application on Windows 10 computer

Note : I am not using MDT task sequence  OS...Our Hardware Vendor install OS and give to Us ...then we install MDT task sequence to install applications only..

We noticed lot of time to install language pack in out task sequence

we are using DISM command to install the language pack CAB file

Is it possible to use any other method to install language pack...I think DISM is taking lot of time...any other way to speed up the language pack installation in MDT tasksequece ?

verification

Hi All,

First of all, some history behind my issue:

We had fully working MDT 8443 release, with Windows ADK for Windows 10, version 1511.

We then decided to roll out the anniversary update of Windows 10 v1607, and due to this, we replaced ADK 1511 with 1607.

We have added new Windows 10 OS v1607, along side with a newly created package which includes the latest CU for this Windows 10 OS version (kb3200970).

When we try to update the deployment share or completely regenerate the image, it fails every time with the following error (attached below) after injecting a package with the latest CU for Windows 10. I also tried to reboot this server several times to see if that fixes the problem, however no luck. Same issue after the reboot.

As a part of this troubleshooting, I've also disabled Microsoft Data Access Components (MDAC/ADO) support under Features for x86/x64 for this deployment share.
----------------------------------------------------------------------------------------------------------------------------

Error: 1726

The remote procedure call failed.
An error occurred closing a servicing component in the image.
Wait a few minutes and try running the command again.

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

Exit code = 1726

DISM /Add-Package failed, rc = 1726.
Injected package Package_for_RollupFix neutral amd64 14393.447.1.5
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 process cannot access the file because it is being used by another process
   --- 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()

----------------------------------------------------------------------------------------------------------------------------

When then we removed the update package from the MDT, and image generated just fine so must be something related to this package.

I tried removing the package and adding it again but no luck. While it's on 'Injecting package Package_for_RollupFix neutral amd64 14393.447.1.5, I will receive a window saying 'Dism Host Servicing Process has stopped working' with the following error details and 'Close the program' button.

----------------------------------------------------------------------------------------------------------------------------

Problem signature:
  Problem Event Name:    APPCRASH
  Application Name:    dismhost.exe
  Application Version:    10.0.14393.0
  Application Timestamp:    57899b20
  Fault Module Name:    cmifw.dll
  Fault Module Version:    10.0.14393.0
  Fault Module Timestamp:    57899838
  Exception Code:    c0000005
  Exception Offset:    0000000000006caa
  OS Version:    6.3.9600.2.0.0.272.7
  Locale ID:    2057
  Additional Information 1:    b613
  Additional Information 2:    b6130c53ab7c1f5795a469873fb1d675
  Additional Information 3:    5fe4
  Additional Information 4:    5fe4b80a1967253d1918c64f42947e5c

Read our privacy statement online:
  http://go.microsoft.com/fwlink/?linkid=280262

If the online privacy statement is not available, please read our privacy statement offline:
  C:\Windows\system32\en-US\erofflps.txt

----------------------------------------------------------------------------------------------------------------------------

Anyone, any ideas on this issue?

Your help would be greatly appreciated!

Thanks

Hello everybody,

For my W10 MDT deployement I want inject last cumulative update for Windows 10 1607 :
https://support.microsoft.com/en-us/kb/3201845

I use DISM V10 for inject cab in WIM :
.\DISM /Mount-Wim /WimFile:install.wim /index:1 /Mountdir:TempWim
.\DISM /image:TempWim /Add-Package /Packagepath:KB.cab
.\DISM /Unmount-Wim /Mountdir:TempWim /commit

But in WSUS MDT task sequence the KB3201845 are download again and re-apply !
It's take less time of full install but I don't understand :(

Why the KB are download and install again while it is already included in the install.wim ?

Thanks :)

Hi Everybody, I was wondering whether you could help me out with something? I just need to know where USMT stores the data from user profiles when deploying a new OS. I am working with offline media for this as we do not have the networking capabilities to run deployments over our network.

My question is does it store it on the HDD somewhere or on the USB I am using to deploy?

Many thanks,

Liam  

I currently have MDT 2013 Update 2 (8330) installed and just found out that 8443 was issued in November. I already have the correct ADK installed and was wondering about the correct sequence of events to move from MDT 8330 to 8443?

Do I install right over top of 8330? Uninstall one and reinstall the new one?

Will my current deployment share and task sequences etc remain operable and usable?

Appreciate any tips

Cheers!

B

Hi,

How do i add/replace and install.wim to an ISO file?

Can i do it with Dism or imagex?  

should i extract/export the content of image out to a folder then repackage it?

Hello,

I'm deploying Win 10 Enterprise on standalone machines using MDT and trying to enable Bitlocker during my deployment to encrypt OS drive (the only partition I have), TPM is enable in BIOS, and i'm trying to store recovery keys on the deployment share, here is my cs.ini :

SkipBitLocker=YES

BDEInstall=TPM

BDEInstallSuppress=NO

BDEDriveSize=300  ------- i tried 2000 as well ---

BDEWaitForEncryption=False

BDERecoveryKey=AD

BDEKeyLocation=\\SERVER\DeploymentShare\Recoverykeys

TPMOwnerPassword=XXXXX ------- tried with and without this line --------

I left the BitLocker step enable in TS (default). the deployment is finishes and never initiate the encryption.  

hint:  enable Bitlocker manually is working fine. Machines are Intel NUC kit. 

Any ideas ? thanks in advance. 

At this moment i am creating a new task sequence in MDT to deploy Windows 10 Enterprise x64 (build 1607).

I created a task where i deploy a custom Windows start menu. This is what i already did.

1) I created internet shortcuts (.url files) and copied them into the startmenu/programms folder.
2) I right clicked these shortcuts which appear in the startmenu and selected "Pin to start". Now they appear as tiles.
3) I exported the menu with Powershell using Export-Startlayout –path C:\Startmenu.xml
4) I copied the startmenu.xml and the shortcuts to my MDT script folder.
5) In MDT i created a task to copy the layout file to the local machine during deployment usingcmd.exe /c copy %SCRIPTROOT%\startmenu\LayoutStartMenu.xml c:\Windows\Temp
6) In MDT i created a task to copy the URL file to the local machine during the deployment using:cmd.exe /c copy %SCRIPTROOT%\startmenu\theurlfile.url "C:\ProgramData\Microsoft\Windows\Start Menu\Programs"
7) In MDT i created a "Run Powershell Script" task where i run a powershell script that imports the menu in Windows 10 during the deployment using:%SCRIPTROOT%\startmenu-win10\ApplyCustomMenu.ps1
 - (The script: Import-StartLayout –LayoutPath C:\Windows\Temp\LayoutStartMenu.xml -MountPath $env:SystemDrive\)

The problem:

When i restart the computer and I login as a user i can see that the custom menu appears. All the groups and select program tiles are there but not the URL tiles. The spaces are empty but no tiles are shown. The .URL are copied over and can be found in the startmenu/programs folder. I just have to click them again and select pin to start.

Does someone has an idea what i do or goes wrong?

Good morning,

i'm running a seperate build system and for my build task sequence i stick to Johan Arwidmarks Tutorial: http://deploymentresearch.com/Research/Post/521/Back-to-Basics-Building-a-Windows-7-SP1-Reference-Image-using-MDT-2013-Update-2

I've set up a Hyper-V VM which runs once a month from a task schedule and starts my Windows 7 Build Task Sequence (via CS.ini and Machine ID).

Yesterday i've run this Task Sequence for testing multiple times, and every time my captured .wim File gets about 500 MB bigger ???

- First run ~ 5GB (it took about 2 hours)
- Next run ~ 5,5 GB
- Next run ~ 6 GB

and so on....

It's always the same TS, same Updates installed, same Applications. Every time the VM starts i delete the old disk and create a new one. So why is my .wim image size growing??? I have no idea...

Greetings from Germany :-)