Dear Colleagues,

I would like to ask for your assistance:

- I have a Windows Server 2012 R2. 1809 ADK, MDT 6.3.8456.1000, DISM 10.0.17763.1 + WinPE 1809 installed.

- Deploying Windows 10 1703 is always succeed.

- I have an alternate DeplymentShare on the same server and 1803 deployment is succeed. 

- Reference Image .wim file caputed with DISM 10.0.17763.1.

- But with the main DeploymentShare I am unable to deploy the OS. I receive the following error after extracting .wim (100%):

LTIApply.log

...

Error: 50 DISM does not support servicing a Windows Vista RTM or earlier operating system.

If the operating system us supported chech that SSShim.DLL is present.

...

Did any of you run into this issue?

Thank you in advance!

So I followed this site: https://deploymentresearch.com/Research/Post/1688/A-Geeks-Guide-for-upgrading-to-MDT-8456

I didn't have any deployment shares so I ignored that part.

The part where you create a dummy task sequence to update your MDT Toolkit, can I just delete the old toolkit I assume (files on file server as well as the package in SCCM?)?

I went in and changed the task sequence but on that site it shows that there is 5-7 changes per task sequence and the only change I had to make was to change it to use the latest toolkit??

My main issue is that I cannot add an image into SCCM that was created with MDT 8456. Below is the error I get and I thought updating the ADK/PE and boot image to 1809 and MDT to 8456 would  resolve this but it still hasnt.

Is there something I am missing? I can't figure out why this image is not allowed to be added when other images made before 1809 are still allowed to be added. I also captured a reference image with SCCM and was allowed to add that one. It's just the image that was captured using MDT is not working and it works when deploying with MDT and not SCCM.

(it is not a permissions issue, I have set to everyone full and it still doesnt work)

Hello,

I am having issues running my Litetouch.vbs remotely from the windows OS to upgrade. some unique items about the situation is that the WDS/MDT server is not added to the domain, but still connected.

the below errors occur during the first step in the task sequence.

Errors in Litetouch.log

RUN: regsvr32.exe /s "C:\Users\Workstation Admin\AppData\Local\Temp\Tools\x64\Microsoft.BDD.Utility.dll"

FAILURE (Err): 70: CreateObject(Microsoft.BDD.Utility) - Permission denied

I have been trying to resolve this for several days and have made nearly no progress.

Thank you for any assistance you provide.

Hello all. My customsettings.ini is setup to pull the Asset Tag from the BIOS and then add "D" for Desktop chassis (1234D) and "L" for Laptop chassis (5678L) to create a computer's hostname. This has worked successfully for many months for all desktops (IsDesktop=True), all laptops (IsLaptop=True) and for all Surface products we use (IsLaptop=True). Since I moved the DeploymentShare to a new location over the weekend (and generated a new boot WIM), the naming scheme no longer works for any Surface product, only. The desktops and laptops are still named correctly like before. The Surface products pull the correct asset tag number and IsLaptop still = True, but MDT does not add the "L" to its hostname. I've dumped the variables that LTI is using at the end of a load and see that the OSDComputerName is still set correctly (1234L), but the hostname ends up being 1234. Did I miss regenerating something in the move or somehow tweaked a setting? I don't understand why laptops are named correctly but Surface products are not when they share the same chassis type. Thanks in advance for any ideas.

Anthony

Hi all,

I want to use the SplitWim option in order to create a UEFI Media but when I set SkipWimSplit to False in my Settings.xml file I keep getting an error when I attempt to generate the Media.

I can see MDT splitting my wim file into swm pieces but it throws the error below and cancels the operation:

Starting MDT Media Update
Opened the media deployment share.

System.Management.Automation.CmdletInvocationException: Could not find file 'X:\MDTBuildProd\Operating Systems\REFW10-X64-001\REFW10-X64-001.wim'. ---> System.IO.FileNotFoundException: Could not find file 'X:\MDTBuildProd\Operating Systems\REFW10-X64-001\REFW10-X64-001.wim'.
   à System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
   à System.IO.FileInfo.get_Length()
   à Microsoft.BDD.PSSnapIn.GenerateMDTMedia.ProcessRecord()
   à System.Management.Automation.CommandProcessor.ProcessRecord()
   --- End of inner exception stack trace ---
   à System.Management.Automation.Runspaces.PipelineBase.Invoke(IEnumerable input)
   à Microsoft.BDD.Wizards.GenerateMediaProgress.WizardProcessing()
   à Microsoft.BDD.Wizards.WizardProgress.InitiateWizardProcessing()

There is only one OS in my console (and in the OperatingSystem.xml) and I renamed it with the .WIM extension, no clue:

Windows_10_Enterprise_x64_v1607_FR_Production_Image.WIM

I had a look at the thread below but the answer did not solve my issue, I even tried to create a new test selection profile...

Offline Media creation Fails If Split WIM is attempted

I know Rufus can create a UEFI bootable USB key with NTFS support but you have to disable Secure Boot to boot with keys generated with this tool.

Any help would be much appreciated.

I am using MDT 8443 and ADK1703 (it didn't work with 1607 either).

Viadeo: Mathieu Ait Azzouzene | Linkedin: Mathieu Ait Azzouzene

I have a RunOnce working on Panasonic units to turn off Numlock for each user who signs on. I configure it under the Default user with a VB script and place it in the registry under RunOnce.

What I'd like to do now is set permissions on a folder under the user\appdata\local location for a folder that gets created for each user who signs on. I am not sure if I can copy the permissions/folder from an existing pc and use that somehow.

The standing issue is that the appdata\local folder had a folder in it that has to have authenticated users having full control, but for each user who signs on. We manually do this, but it gets skipped by some techs during the manual setup, so I'd like to have this happen during imaging if possible. I can't modify the installer because I don't even know what software was used to build the application.

Could I please pick the hivemind brain I have a reference image that is a HOT topic in my company but since changing to 8456. Everytime I try to do a sysprep and capture the capture portion never pops up.

 As I said this is a HOT TOPIC and a lot of eyes are looking at me.

Thank you

Robert D. Allsup

Information Technology NetOps Lab

Imaging Support Coordinator

ThyssenKrupp Elevator Americas

3965 S. Mendenhall Rd. Suite 13 Dock B

Memphis, TN 38115

Phone: (901) 365-5692

Cell: (901) 315-0546

My configuration:  Stand alone laptop.  No WSUS server.  No network connections.  No System Center Configuration Manager.

Objective: Create offline deployment media that can be used to create a virtual machine that can be used to create a reference machine and capture an image.

Status: I have a deployment share created.  I can create the offline deployment media (bootable ISO).  I can create the vmware virtual machine.  When I get to the Windows Deployment Wizard and select "Capture an image of this reference computer.", I am prompted for User Credentials.  I enter my login name and password for my laptop and I get "Invalid credentials.  The network name cannot be found.". 

What am i missing?

My customsettings.ini

;------------------------------------------------------------------------------------------
;Customsettings.ini - This file has been generated with MDT Profile Generator
;------------------------------------------------------------------------------------------
[Settings]
Priority=DeploymentShareDefault
Properties=MyCustomProperty


[DeploymentShareDefault]
_SMSTSORGNAME=*********************
AdminPassword=***************
;TaskSequenceID=W10_2018_09
TaskSequenceID=Test1
ProductKey=******************

;SkipFinalSummary=NO
;SkipSummary=YES
;FinishAction=LOGOFF
;Hiding the Shell prevents the Windows task bar from being displayed at the bottom of the window while the installation is going on.
;HideShell=YES
;DoCapture=YES

;------------------------------------------------------------------------------------------
;NETWORK SELECTION
;------------------------------------------------------------------------------------------
;OSDAdapterCount=1
;OSDAdapter0EnableDHCP=TRUE

;------------------------------------------------------------------------------------------
;BACKUP SELECTION - CAPTURE AND COMPUTER BACKUP PART
;------------------------------------------------------------------------------------------
:JSP 3-28-19 DeploymentType=NEWCOMPUTER
DeploymentType=REFRESH
:JSP 3-28-2019 DoCapture=NO
DoCapture=YES
ComputerBackupLocation=NONE

;------------------------------------------------------------------------------------------
;BACKUP SELECTION - RESTORE USER DATA PART
;------------------------------------------------------------------------------------------

;------------------------------------------------------------------------------------------
;BACKUP SELECTION - RESTORE USER DATA PART
;------------------------------------------------------------------------------------------
UserDataLocation=NONE

;------------------------------------------------------------------------------------------
;DOMAIN/WORKGROUP SELECTION
;------------------------------------------------------------------------------------------
;JoinWorkGroup=WorkGroup

;------------------------------------------------------------------------------------------
;LOCALE AND TIME SELECTION
;------------------------------------------------------------------------------------------
;LanguagePacks1=
;UILanguage=en-US
;TimeZoneName=Coordinated Universal Time
;KeyboardLocale=00000409
;UserLocale=en-US

;------------------------------------------------------------------------------------------
;APPLICATION SELECTION
;------------------------------------------------------------------------------------------
;No applications selected

;------------------------------------------------------------------------------------------
;WIZARD SELECTION
;------------------------------------------------------------------------------------------
;SkipBDDWelcome=YES
SkipWizard=YES
SkipTaskSequence=YES
SkipProductKey=YES
;SkipComputerBackup=YES
;SkipDomainMembership=YES
;SkipUserData=YES
;SkipAdminPassword=YES
;SkipApplications=YES
;SkipCapture=NO
;SkipBitLocker=YES
;SkipLocaleSelection=YES
;SkipTimeZone=YES
;SkipPackageDisplay=YES
;SkipComputerName=YES

;------------------------------------------------------------------------------------------
;OTHER PART
;------------------------------------------------------------------------------------------
;ApplyGPOPack=NO
[Default]
EventService=******************

So I installed MDT and ADK, installed a base image of Win10 Pro, installed all the apps I needed, then went to take a capture and sysprep failed. Here's the setuperr log

2017-11-28 14:19:10, Error                 SYSPRP Package Microsoft.BingNews_4.21.2212.0_x64__8wekyb3d8bbwe was installed for a user, but not provisioned for all users. This package will not function properly in the sysprep image.

2017-11-28 14:19:10, Error                 SYSPRP Failed to remove apps for the current user: 0x80073cf2.

2017-11-28 14:19:10, Error                 SYSPRP Exit code of RemoveAllApps thread was 0x3cf2.

2017-11-28 14:19:10, Error      [0x0f0082] SYSPRP ActionPlatform::LaunchModule: Failure occurred while executing 'SysprepGeneralizeValidate' from C:\Windows\System32\AppxSysprep.dll; dwRet = 0x3cf2
2017-11-28 14:19:10, Error                 SYSPRP SysprepSession::Validate: Error in validating actions from C:\Windows\System32\Sysprep\ActionFiles\Generalize.xml; dwRet = 0x3cf2
2017-11-28 14:19:10, Error                 SYSPRP RunPlatformActions:Failed while validating SysprepSession actions; dwRet = 0x3cf2
2017-11-28 14:19:10, Error      [0x0f0070] SYSPRP RunExternalDlls:An error occurred while running registry sysprep DLLs, halting sysprep execution. dwRet = 0x3cf2
2017-11-28 14:19:10, Error      [0x0f00d8] SYSPRP WinMain:Hit failure while pre-validate sysprep generalize internal providers; hr = 0x80073cf2

It seems to be an issue that has happened before, for a while now. I've read some of the fixes that do not seem to work, without breaking something else, but why should I have to jump through hoops when it was a Microsoft installed problem? This is just really poor customer service. One of your Noobs created a Appx package incorrectly and then you pushed it out to the world. Why don't you fix it Microsoft? BTW, your software scanned my network without my permission, saw my Toshiba printers, then also installed Toshiba updates that are also misconfigured, and install the same way a Bing News.

Sit back and relax. This post will be lengthy. I have been racking my brain on this for over a week, and I desperately need a hero. Let me start with the scenario. We use a combination of MDT\WDS to deploy our images (we also have an SCCM environment that is not integrated with MDT). We are in the middle of using MDT's refresh capability to replace our Windows 7 bitlockered OS' with Windows 10. The refresh process goes like this:

1. Litetouch.vbs is executed from within a running Windows 7 OS that has Bitlocker enabled.
2. Task sequence is executed, and performs the following key steps: (a) backs up user profiles via USMT, (b) disables BDE protectors, (c) applies Windows PE, (d) reboots to MDT to continue the task sequence
3. Once the PC has booted into the MDT environment, the task sequence continues on like this (key elements only): (a) applies the WIM, (b) converts the bios to UEFI via Dell CCTK, (c) converts the MBR to GPT via the Microsoft MBR2GPT utility, (d) reboots to load Windows 10 for the first time.

This last reboot is where the issue lies. As soon as the task sequence hits that 'Restart' task, it blue screens with an 'fvevol.sys' error, and a 'DRIVER IRQL NOT LESS OR EQUAL' error, and it just sits there until the power is cycled. Now once you cycle the power, the task sequence continues without error, but we kick these off remotely. So our only option right now is to either have the end user cycle the power, or be physically present at the workstation.

Now...with the previous iteration of WinPE, we were still getting this blue, but it would at least reboot automatically, and continue on with the task sequence. I have scoured the internet, and cannot find anything related to this. I find it hard to believe that no one is encountering this, as it happens on EVERY machine of ours (not a random thing). Here is what I have tried so far:

1. Removed the built-in 'Disable BDE protectors' task in MDT, and replaced it with a script of my own (no change).
2. Mounted the 'LiteTouchPE_x64.wim' and edited the registry entry "AutoReboot" value from 0 to 1. This change causes the PC to shutdown after the bluescreen instead of rebooting.
3. Mounted the 'LiteTouchPE_x64.wim' and edited the registry so that it does not load fvevol.sys (a bitlocker driver). This causes the PC to boot straight to the MDT menu (task sequence does not continue), as it can no longer read the scripts from the drive due to encryption. I thought this was rather strange since the bde protectors get disabled before it reboots to WinPE. This tells me that WinPE is possibly re-enabling bitlocker.

The only thing I have not tried is fully decrypting the drive. I suspect this would work, but I shouldn't have to do this. Also, this issue does not occur if we boot straight to MDT using a 'New Computer' deployment type scenario.

I would greatly appreciate any feedback on this! Thanks to all in advance!

Bonjour,

La migration vers windows 10 n'étant prévu que pour l'année prochaine apres test de compatibilité

 de nos logiciels métiers, je suis encore obligé de déployer Windows 7. Or sur les nouveaux pc équipés de processeurs intel de 7ieme et 8ieme génération, le déploiement échoue. Ce qui n'était pas le cas avec les anciens processeurs. Même une installation classique (installation sur clé usb) échoue, car le clavier et souris usb ne sont pas gérés.

Quelles sont les solutions que vous voyez, car je suis en panne d'inspiration. j'ai tenté l'injection des drivers dans l'image, aussi bien sur MDT que sur l'installation par clé usb. Mais rien n'y fait.

Une installation de Windows 10 par clé, fonctionne .

Merci de vos réponses.

A+ JJ

Hi everyone,

I'm trying to debug a powershell script in an active tasksequence, so I created a 'pause tasksequence' task and I'm trying to debug the script. The first problem I run into is that I'm unable to load the ZTIUtitlity module. I get lot's of errors but it all starts with a failure to load a dll. It's a server 2012 R2 VM and the errors I get are these:

PS C:\Users\Administrator> Import-Module ztiutility
Microsoft Deployment Toolkit version: 6.2.5019.0
Import Microsoft.BDD.TaskSequenceModule
Import-Module : Could not load file or assembly 'file:///Z:\Tools\Modules\Microsoft.BDD.TaskSequen
ceModule\Microsoft.BDD.TaskSequenceModule.dll' or one of its dependencies. Operation is not suppor
ted. (Exception from HRESULT: 0x80131515)
At Z:\Tools\Modules\ztiutility\ztiutility.psm1:47 char:2+     Import-Module Microsoft.BDD.TaskSequenceModule -Global+     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~+ CategoryInfo          : NotSpecified: (:) [Import-Module], FileLoadException+ FullyQualifiedErrorId : System.IO.FileLoadException,Microsoft.PowerShell.Commands.ImportMod 
   uleCommand
Task Sequence Module did not load
At Z:\Tools\Modules\ztiutility\ztiutility.psm1:51 char:3+         throw "Task Sequence Module did not load"+         ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~+ CategoryInfo          : OperationStopped: (Task Sequence Module did not load:String) [], Ru 
   ntimeException+ FullyQualifiedErrorId : Task Sequence Module did not load
Microsoft Deployment Toolkit version: 6.2.5019.0
Import Microsoft.BDD.TaskSequenceModule
Import-Module : Could not load file or assembly 'file:///Z:\Tools\Modules\Microsoft.BDD.TaskSequen
ceModule\Microsoft.BDD.TaskSequenceModule.dll' or one of its dependencies. Operation is not suppor
ted. (Exception from HRESULT: 0x80131515)
At C:\MININT\Modules\ztiutility\ztiutility.psm1:47 char:2+     Import-Module Microsoft.BDD.TaskSequenceModule -Global+     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~+ CategoryInfo          : NotSpecified: (:) [Import-Module], FileLoadException+ FullyQualifiedErrorId : System.IO.FileLoadException,Microsoft.PowerShell.Commands.ImportMod 
   uleCommand
Task Sequence Module did not load
At C:\MININT\Modules\ztiutility\ztiutility.psm1:51 char:3+         throw "Task Sequence Module did not load"+         ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~+ CategoryInfo          : OperationStopped: (Task Sequence Module did not load:String) [], Ru 
   ntimeException+ FullyQualifiedErrorId : Task Sequence Module did not load
Import-Module : The specified module 'ztiutility' was not loaded because no valid module file was 
found in any module directory.
At line:1 char:1+ Import-Module ztiutility+ ~~~~~~~~~~~~~~~~~~~~~~~~+ CategoryInfo          : ResourceUnavailable: (ztiutility:String) [Import-Module], FileNotFo 
   undException+ FullyQualifiedErrorId : Modules_ModuleNotFound,Microsoft.PowerShell.Commands.ImportModuleCo 
   mmand

Clues anyone? Thanks in advance.

MicaH.

Hi Team,

We are trying to deploy Windows 10 Image using MDT and currently stuck on one of unwanted display.

We have selected option to install multiple application to select Office and OS Language Pack while starting the deployment. However we can also see the folders which have been created in Application Folder to select from. We do not want the highlighted folders to be visible to deployment team:



How do me make these folders hidden or remove them from deployment page. Any leads will be appreciated.

Thanks,

Aakash Saxena

Aakash Saxena

Getting error messages: ZTIOSRolePS.ps1 

ArgumentNotValid: The role, role service, or feature name is not valid: 'Web-DAV-Publishin'.  The name was not found.

This same error happens with Web-Http-Error, 

When I checked Windows 2016 Roles/Features, these names are not correct.

Where do I go to modify the roles for Windows 2016?  Version 8443 is said to be compatible with Windows 2016: MDT https://blogs.technet.microsoft.com/msdeployment/2016/11/14/microsoft-deployment-toolkit-8443-now-available/

Consultant

Hi all, I am on MDT 8456 and I am trying to install some additional language packs as part of OSD of win10 1809. I have done the following:

1. Imported language packs to the deployment share under the packages folder
2. Created a selection profile and assigned them to the language packs folder
3. Configure the customsettings.ini with SkipPackageDisplay=NO (it did not work when set to Yes either)
4. created an array for the language packs: LanguagePacks001={guid}
5. in the task sequence selected the selection profile for the Apply Patches task (even when set to ALL Packages, it did not work)

Doing all that is still not making the wizard appear so I can select a package. Aside from that, the language packs are not getting installed. Please help, and thanks in advance.

Good Afternoon, 

 I am reaching out because I am trying to install Adobe DC reader. Here is the syntax I am currently using:

msiexec /i AcroRdrDCUpd1901020098.msi /qn

It is returning a 1639 error however. Had anyone seen this before and can help?

Thanks everyone!

SC

I'm trying to capture a client machine and receive the following error when I run LiteTouch.vbs

A connection to the deployment share could not be made.  Connection OK.  Possible cause: invalid credentials.

Note that I'm using IP addresses in bootstrap.ini, customesettings.ini, and I'm using an IP address from the client machine to connect to the Deployment Share.

Also note that I'm not using PXE or a thumb drive to boot into the client machine.  I'm booting into Windows on the client machine and then trying to run the LiteTouch.vbs script from the Deployment Share.

Hi there,

We have an MDT 2010 server which worked fine until a couple of weeks ago. Suddenly every time we press F12 and launch the WinPE we get an error stating that "The Deployment Wizard was cancelled or did not complete successfully. The deployment will not proceed."

Here is the full contents of both the BDD and Litetouch log files:

<![LOG[FAILURE ( 5206 ): The Deployment Wizard was cancelled or did not complete successfully.  The deployment will not proceed.]LOG]!><time="11:04:32.000+000" date="05-11-2011" component="LiteTouch" context="" type="3" thread="" file="LiteTouch">

Any ideas?

Thanks