In my environment, we all boot to MDT using USB drives. Normally, it takes just a moment to get to the Bootstrap window, then the Wizard.hta window and then onto the credentials window. Once the credentials are entered it goes to the CustomSettings window, then the Deploy Menu to pick your image.

Since some changes made a while back, this process takes 4 -5 minutes to get to the Deploy Menu window. Ignoring the fact that we are still required to enter the user password while its stored in the INI, we type the p/w and move on. But for the cloning process to actually execute past all the initial windows, we're looking at roughly 5 minutes before we get to enter the p/w and pick the image.

I don't recall ever updating the deployment share as I've never had to, but something is causing the process to take a very long time. Any ideas on what to check/change? I know that any changes I make to the DShare will effect each user's USB and those will have to be manually updated as well.
Thanks

Ok, here goes my question.

I've followed the steps to create and deploy a Windows 10 installation to a Microsoft Surface 4 Pro using MDT.

https://technet.microsoft.com/en-us/itpro/surface/deploy-windows-10-to-surface-devices-with-mdt?f=255&MSPPError=-2147217396

https://technet.microsoft.com/en-us/itpro/windows/manage/mandatory-user-profile?f=255&MSPPError=-2147217396

I have successfully deployed an image, captured an image and installed applications using MDT LiteTouch, booted off of a USB.

Part of my configuration for these MS Surface's are to utilize a local Mandatory profiles (basically pointing the local path to the folder in C:\Users)

All of this worked like a charm. I had almost no issues. The Surface Drivers all installed, Win 10 LTSB 2016 works great, my mandatory profile does what its supposed to, and everything is great.

EXCEPT:

I don't want to have to manually create a mandatory profile on each device. I want to utilize MDT to capture the image complete with the working mandatory profile, and deploy it to other Surface's.

What I am finding is that MDT utilizes Sysprep -- there goes my mandatory profile -- So now I am back to square one.

Any suggestions or ideas?

----

Windows 10 Enterprise LTSB 1607
MDT 2013 Update 2
Surface's are not on the DOMAIN.

MVP Jesús Octavio Rdz http://blogs.itpro.es/octaviordz

We recently updated one of our MDT servers to MDT build 8443 that was just released.  Everything had been working fine until we went to sysprep and capture via a standalone Capture Task Sequence.  Basically what is happening is whether we boot to the MDT Deployment Share or manually kick off the LiteTouch script to start the Deployment Wizard, after we select the standalone Sysprep and Capture task sequence in the wizard we are not getting the Capture Screen in the wizard where you select to sysprep and capture and specify the file name / location, etc.  It just skips right to the computer name / domain join screen. 

We have verified that SkipCapture=NO in our customsettings.ini and have even created new sysprep and capture task sequences but nothing seems to work.    

Just wondering if anyone else has ran into this since updating to MDT build 8443 and has found a fix for it yet.

Thanks.

Hello,

I'm using USMT to capture a provisioning package from reference PC, then importing this package into Windows ICD to customize my image. Now so far everything works fine if I create a bootable USB and I would image same PC with no issues.

I'm deploying Windows 10 Ent. I was able to import my custom image in MDT, create Lite Touch boot.wim and import it in WDS. PC will boot straight and before it finish the installation it fails in (Install Operating System) step.

In my custom wim i configured the disk also skipped the oobe, also in choosing Standard Client TS and disabled (New Computer) step as I already formatted the disk.

How should I configure my TS in this case?

Thanks in advance.

this is a Lab environment with Standalone WDS and DHCP setup. 

My company has a setup guide for Windows 7 with various tweaks in it that I was hoping to integrate in to the deployment process. I have tried the following:

1. Create a LocalGPO pack - This worked for some of the settings but not all the settings. That and it prevented the user from making changes later.

2. Unattend.xml - I found a few tweaks that can be done here. Some of my changes stick, some do not.

3. Powershell script - I have spent hours isolating all the necessary registry keys to make the tweaks happen. Here is the script:

#Set-ExecutionPolicy Unrestricted

#Folder Options
New-ItemProperty -Path HKCU:\Software\Microsoft\Windows\CurrentVersion\Explorer\Advanced -Name HideFileExt -PropertyType Binary -Value 0 -Force
New-ItemProperty -Path HKCU:\Software\Microsoft\Windows\CurrentVersion\Explorer\Advanced -Name DontPrettyPath -PropertyType Binary -Value 0 -Force
New-ItemProperty -Path HKCU:\Software\Microsoft\Windows\CurrentVersion\Explorer\Advanced -Name AlwaysShowMenus -PropertyType Binary -Value 1 -Force
New-Item -Path HKCU:\Software\Microsoft\Windows\CurrentVersion\Explorer -Name CabinetState -Force
New-ItemProperty -Path HKCU:\Software\Microsoft\Windows\CurrentVersion\Explorer\CabinetState -Name FullPath -PropertyType Binary -Value 1 -Force

#Start Menu
New-ItemProperty -Path HKCU:\Software\Microsoft\Windows\CurrentVersion\Explorer\Advanced -Name Start_ShowDownloads -PropertyType Binary -Value 1 -Force
New-ItemProperty -Path HKCU:\Software\Microsoft\Windows\CurrentVersion\Explorer\Advanced -Name Start_NotifyNewApps -PropertyType Binary -Value 0 -Force
New-ItemProperty -Path HKCU:\Software\Microsoft\Windows\CurrentVersion\Explorer\Advanced -Name Start_ShowSetProgramAccessAndDefaults -PropertyType Binary -Value 0 -Force
New-ItemProperty -Path HKCU:\Software\Microsoft\Windows\CurrentVersion\Explorer\Advanced -Name Start_ShowMyMusic -PropertyType Binary -Value 0 -Force
New-ItemProperty -Path HKCU:\Software\Microsoft\Windows\CurrentVersion\Explorer\Advanced -Name Start_ShowRecentDocs -PropertyType Binary -Value 1 -Force
New-ItemProperty -Path HKCU:\Software\Microsoft\Windows\CurrentVersion\Explorer\Advanced -Name Start_ShowRun -PropertyType Binary -Value 1 -Force
New-ItemProperty -Path HKCU:\Software\Microsoft\Windows\CurrentVersion\Explorer\Advanced -Name Start_PowerButtonAction -PropertyType Binary -Value 2 -Force

#Notification Area and Action Center
New-ItemProperty -Path HKCU:\Software\Microsoft\Windows\CurrentVersion\Explorer -Name EnableAutoTray -PropertyType Binary -Value 0 -Force
New-Item -Path HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies -Name Explorer -Force
New-ItemProperty -Path HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\Explorer -Name HideSCAHealth -PropertyType Binary -Value 1 -Force

#Control Panel
New-Item -Path HKCU:\Software\Microsoft\Windows\CurrentVersion\Explorer -Name ControlPanel -Force
New-ItemProperty -Path HKCU:\Software\Microsoft\Windows\CurrentVersion\Explorer\ControlPanel -Name AllItemsIconView -PropertyType Binary -Value 1 -Force
New-ItemProperty -Path HKCU:\Software\Microsoft\Windows\CurrentVersion\Explorer\ControlPanel -Name StartupPage -PropertyType Binary -Value 1 -Force

#User Access Control
New-ItemProperty -Path HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System -Name ConsentPromptBehaviorAdmin -PropertyType Binary -Value 0 -Force
New-ItemProperty -Path HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System -Name EnableLUA -PropertyType Binary -Value 0 -Force
New-ItemProperty -Path HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System -Name PromptOnSecureDesktop -PropertyType Binary -Value 0 -Force

#Windows Updates
New-Item -Path HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion -Name WindowsUpdate -Force
New-Item -Path HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate -Name "Auto Update" -Force
New-ItemProperty -Path "HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\Auto Update" -Name AUOptions -PropertyType Binary -Value 3 -Force
New-Item -Path "HKLM:\SOFTWARE\Policies\Microsoft\Windows" -Name WindowsUpdate -Force
New-ItemProperty -Path "HKLM:\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate\Auto Update" -Name ScheduledInstallDay -PropertyType Binary -Value 0 -Force
New-ItemProperty -Path "HKLM:\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate\Auto Update" -Name ScheduledInstallTime -PropertyType Binary -Value 9 -Force

#Remote Desktop
New-ItemProperty -Path "HKLM:\SYSTEM\ControlSet001\Control\Terminal Server" -Name fDenyTSConnections -PropertyType Binary -Value 0 -Force
New-ItemProperty -Path "HKLM:\SYSTEM\ControlSet001\Control\Terminal Server\WinStations\RDP-Tcp" -Name UserAuthentication -PropertyType Binary -Value 1 -Force
New-ItemProperty -Path "HKLM:\SYSTEM\ControlSet001\Control\Terminal Server" -Name fAllowToGetHelp -PropertyType Binary -Value 0 -Force
New-ItemProperty -Path "HKLM:\SYSTEM\ControlSet002\Control\Terminal Server" -Name fAllowToGetHelp -PropertyType Binary -Value 0 -Force
New-ItemProperty -Path "HKLM:\SYSTEM\CurrentControlSet\Control\Terminal Server" -Name fAllowToGetHelp -PropertyType Binary -Value 0 -Force
New-ItemProperty -Path "HKLM:\SYSTEM\CurrentControlSet\Control\Remote Assistance" -Name fAllowToGetHelp -PropertyType Binary -Value 0 -Force
New-ItemProperty -Path "HKLM:\SYSTEM\ControlSet001\Control\Remote Assistance" -Name fAllowToGetHelp -PropertyType Binary -Value 0 -Force
New-ItemProperty -Path "HKLM:\SYSTEM\ControlSet002\Control\Remote Assistance" -Name fAllowToGetHelp -PropertyType Binary -Value 0 -Force

#Windows Firewall
New-Item -Path HKLM:\SOFTWARE\Policies\Microsoft -Name WindowsFirewall -Force
New-Item -Path HKLM:\SOFTWARE\Policies\Microsoft\WindowsFirewall -Name StandardProfiles -Force
New-Item -Path HKLM:\SOFTWARE\Policies\Microsoft\WindowsFirewall -Name DomainProfiles -Force
New-Item -Path HKLM:\SOFTWARE\Policies\Microsoft\WindowsFirewall -Name PublicProfiles -Force
New-Item -Path HKLM:\SOFTWARE\Policies\Microsoft\WindowsFirewall -Name PrivateProfiles -Force
New-ItemProperty -Path HKLM:\SOFTWARE\Policies\Microsoft\WindowsFirewall\StandardProfiles -Name EnableFirewall -PropertyType Binary -Value 0 -Force
New-ItemProperty -Path HKLM:\SOFTWARE\Policies\Microsoft\WindowsFirewall\DomainProfiles -Name EnableFirewall -PropertyType Binary -Value 0 -Force
New-ItemProperty -Path HKLM:\SOFTWARE\Policies\Microsoft\WindowsFirewall\PublicProfiles -Name EnableFirewall -PropertyType Binary -Value 0 -Force
New-ItemProperty -Path HKLM:\SOFTWARE\Policies\Microsoft\WindowsFirewall\PrivateProfiles -Name EnableFirewall -PropertyType Binary -Value 0 -Force

#IE Settings not handled by unattended.xml
New-Item -Path "HKCU:\Software\Microsoft\Internet Explorer\SearchScopes" -Name "{E654518E-3688-45C9-A3F3-0FD51CADB782}" -Force
New-ItemProperty -Path "HKCU:\Software\Microsoft\Internet Explorer\SearchScopes" -Name DefaultScope -PropertyType String -Value "{E654518E-3688-45C9-A3F3-0FD51CADB782}" -Force
New-ItemProperty -Path "HKCU:\Software\Microsoft\Internet Explorer\SearchScopes\{E654518E-3688-45C9-A3F3-0FD51CADB782}" -Name DisplayName -PropertyType String -Value "Google" -Force
New-ItemProperty -Path "HKCU:\Software\Microsoft\Internet Explorer\SearchScopes\{E654518E-3688-45C9-A3F3-0FD51CADB782}" -Name URL -PropertyType String -Value "http://www.google.com/search?q={searchTerms}&sourceid=ie7&rls=com.microsoft:{language}:{referrer:source}&ie={inputEncoding?}&oe={outputEncoding?}" -Force
New-ItemProperty -Path "HKCU:\Software\Microsoft\Internet Explorer\SearchScopes\{E654518E-3688-45C9-A3F3-0FD51CADB782}" -Name ShowSearchSuggestions -PropertyType Binary -Value 1 -Force
New-ItemProperty -Path "HKCU:\Software\Microsoft\Internet Explorer\SearchScopes\{E654518E-3688-45C9-A3F3-0FD51CADB782}" -Name SuggestionsURL -PropertyType String -Value "http://clients5.google.com/complete/search?q={searchTerms}&client=ie8&mw={ie:maxWidth}&sh={ie:sectionHeight}&rh={ie:rowHeight}&inputencoding={inputEncoding}&outputencoding={outputEncoding}" -Force
New-ItemProperty -Path "HKCU:\Software\Microsoft\Internet Explorer\SearchScopes\{E654518E-3688-45C9-A3F3-0FD51CADB782}" -Name OSDFileURL -PropertyType String -Value "http://www.iegallery.com/en-us/AddOns/DownloadAddOn?resourceId=813" -Force
New-ItemProperty -Path "HKCU:\Software\Microsoft\Internet Explorer\SearchScopes\{E654518E-3688-45C9-A3F3-0FD51CADB782}" -Name FaviconURL -PropertyType String -Value "http://www.google.com/favicon.ico" -Force
New-ItemProperty -Path "HKCU:\Software\Microsoft\Internet Explorer\SearchScopes\{E654518E-3688-45C9-A3F3-0FD51CADB782}" -Name FaviconPath -PropertyType String -Value "C:\Users\Administrator\AppData\LocalLow\Microsoft\Internet Explorer\Services\search_{E654518E-3688-45C9-A3F3-0FD51CADB782}.ico" -Force

#Windows Media Player
New-Item -Path HKCU:\Software\Microsoft\MediaPlayer\Setup -Name UserOptions -Force
New-ItemProperty HKCU:\Software\Microsoft\MediaPlayer\Setup\UserOptions -Name DesktopShortcut -PropertyType String -Value "no" -Force
New-ItemProperty HKCU:\Software\Microsoft\MediaPlayer\Preferences -Name EnableWMPDMR -PropertyType Binary -Value 0 -Force
New-ItemProperty HKCU:\Software\Microsoft\MediaPlayer\Preferences -Name FirstRun -PropertyType Binary -Value 1 -Force
New-ItemProperty HKCU:\Software\Microsoft\MediaPlayer\Preferences -Name ShowAppTitlebarVTen -PropertyType Binary -Value 1 -Force
New-ItemProperty HKCU:\Software\Microsoft\MediaPlayer\Preferences -Name AcceptedPrivacyStatement -PropertyType Binary -Value 1 -Force
New-ItemProperty HKCU:\Software\Microsoft\MediaPlayer\Preferences -Name UseUDP -PropertyType Binary -Value 0 -Force
New-ItemProperty HKCU:\Software\Microsoft\MediaPlayer\Preferences -Name UseMulticast -PropertyType Binary -Value 1 -Force
New-ItemProperty HKCU:\Software\Microsoft\MediaPlayer\Preferences -Name UseTCP -PropertyType Binary -Value 0 -Force
New-ItemProperty HKCU:\Software\Microsoft\MediaPlayer\Preferences -Name UseHTTP -PropertyType Binary -Value 1 -Force
New-Item HKCU:\Software\Microsoft\MediaPlayer\Setup -Name UserOptions -Force
New-ItemProperty HKCU:\Software\Microsoft\MediaPlayer\Setup\UserOptions -Name DesktopShortcut -PropertyType String -Value "no" -Force

I placed the "Run Powershell script item in my task list under State Restore, just before Imaging. I also added a Restart Computer item just before Imaging.  Here is the actual call:

Powershell Script
\\deploy\deploymentshare$\CustomScripts\RegKeys.ps1

Parameters
-ExecutionPolicy Unrestricted -NoProfile

I check the logs and everything runs with no errors, some of the settings seem to apply but others do not. The keys get inserted but they don't seem to take effect.
Things that I set but don't work

1. Disable UAC

2. Disable Remote Assistance (This I don't get it is turned off in unattend.xml and my script!)

3. Windows Update settings

4. Show all notifications

5. Disable Action Center

6. Show Control Panel list as small icons

Anyone have any advice? How are you setting up your default profile. It stinks that MS took away the ease of setting up the Default Profile.

First of all I apologize for my lack of knowledge but I have inherited a situation that is driving me nuts especially as I don't have any in-depth experience of MDT deployments etc.

The problem I am seeing is when trying to deploy Windows 7 Enterprise with MDT2013 with WDS deployment shares via the PXE boot process.

This morning I attempted the PXE image of a Lenovo T450S laptop with a valid AD account with the required permissions and it worked. After entering the credentials it went into the automated deployment process. At this stage I stopped the process.

Ten minutes later I attempted the same process, on the same laptop, connected to the same LAN cable and port, using the same user id. It failed.

I compared the BDD.LOG files from the successful and failed re-image processes and close to the end of the log from the successful process there are two differences from the failed logs.

Firstly there is the entry as follows which does NOT appear in the log file from the failed process:<![LOG[ERROR: Invalid OS GUID {5eb3bb25-c967-4d45-803f-f126f004eae9} specified for task sequence W76402K specified]LOG]!><time="10:40:38.000+000" date="12-05-2016" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">

Then a few lines later I see this which does NOT appear in the log file from the failed process:

<![LOG[Property TSGuid is now = {f797a4d6-5767-4dc1-aa63-024e2ce2ddb2}]LOG]!><time="10:40:40.000+000" date="12-05-2016" component="Wizard" context="" type="1" thread="" file="Wizard">

To my uneducated mind it would make more sense if theInvalid OS GUID error appeared in the logs when the process fails but it actually appears when it succeeds.

The way the problem manifests itself is when the process fails it drops out to a manual intervention at the Task Sequence stage as shown in the image below:

If the process succeeds we see the same screen but without the labels (Computer Details, Product Key etc) under the Task Sequence label.

Initially I thought the problem was happening when the computer already had a record in AD from when it was previously re-imaged. I went through a series of tests last week where I re-imaged successfully, tried the process again with the AD record in place and it failed. I then had the AD computer record deleted (waited for the ad to sync), and tried the re-image process again and it worked. I repeated this test at least 5 times with predictable results.

However, the fact that the re-image process worked this morning and then failed 10 minutes later (without touching the AD computer record) on the exact same machine and config has completely thrown me a curve ball.

Could anyone help me else to look to find the cause of this problem as I am now totally stumped.

Thanks

Hi there,

Novice MDT user so apologies if the answer is obvious, but I've been having issues with MDT failing to install some applications during my task sequence. The return code I'm getting with these applications is 1603 which suggests access issues (either through permissions, or file in use).

After a lot of troubleshooting, I've determined the following:

• This only occurs on machines that have not yet been joined to the domain. If I re-image a machine or create the computer account manually in AD beforehand, it works fine. This includes if I image the same machine immediately after it fails, it will always work the second time.
• Can confirm it happens on multiple machine models, which (I think) rules out driver issues.
• Have confirmed permissions are correct, the service account used full access on the whole deployment share (despite only needing read access I believe).
• The Cisco VPN app gives another error, saying the windows installer service couldn't be accessed. I thought it could relate to a single application install not working properly, which then caused issues for following installs, but I've tried removing each application and running the TS with no change in result.
• Some applications are installing fine. I can not see any inconsistencies between the ones that are working and the ones that are not.
• This worked fine for a long time. It seemed to come up out of nowhere, obviously there was a change somewhere, but there was no obvious change that I can see. It was only picked up when we got a new batch of laptops in.

It really sounds like some sort of permissions access somewhere, as mentioned I've confirmed the deployment share permissions, so I'm not too sure where else I could look? Alternatively, as we are a global company with some global enforced policies, is it possible something's been pushed out globally that is causing an issue with non domain computers accessing the share?

Just wondering if there's anything obvious I'm missing, any suggestions or ideas would be greatly appreciated. Please let me know if there's any other info I can provide.

Hello, I am doing an implementation of Windows 7 SP1 to Windows 10, the problem is that I was previously using the following code in virtual machines and this was ok here the linkhttp://blogs.itpro.es/octaviordz/2015/11/30/migrar-de-windows-7-a-windows-10-en-un-dominio-con-mdt-2013-u1/
Now after some time I want to re-implement but in production with a physical machine through the network, which is not capturing the information of the users and mark error and cut the installation process.

customsettings.ini

[Settings]
Priority=Default
Properties=MyCustomProperty

[Default]
OSInstall=YES
SkipAdminPassword=YES
SkipApplications=YES
SkipAppsOnUpgrade=YES
SkipBDDWelcome=YES
SkipBitLocker=YES
SkipCapture=YES
SkipComputerName=NO
SkipComputerBackup=NO
ComputerBackupLocation=AUTO
SkipDeploymentType=NO
SkipDomainMembership=YES
JoinDomain=xxxxxxxxxx
DomainAdmin=Administrador
DomainAdminDomain=xxxxxxxxxx
DomainAdminPassword=xxxxxxxxxx
SkipFinalSummary=NO
SkipLocaleSelection=YES
KeyboardLocale=en-US
UserLocale=en-US
UILanguage=en-US
SkipPackageDisplay=YES
SkipProductKey=YES
SkipSummary=NO
SkipTaskSequence=YES
TaskSequenceID=W8
SkipTimeZone=YES
TimeZoneName=Central Standard Time
SkipUserData=NO
UserDataLocation=AUTO

MVP Jesús Octavio Rdz http://blogs.itpro.es/octaviordz

yaro

Dear fellow forum users,

Does anyone know how to use powershell to extract custom MDT variables from the database, during installation of an x64 system, for a custom script.

It seems that many people are reporting that calling and using the:

$tsenv = New-Object -COMObject Microsoft.SMS.TSEnvironment

does not work in x64 environments. 

Is there another method of doing this with Powershell?

I have a setup.exe file that I want to use to install a Dell Webcam application.
The switch is as follows:
setup.exe /s
Simple.
When I add the files to MDT and run the setup.exe /s nothing happens, and no error
in the Final Summary screen.
I decided to instead first copy the folder over to C: on the target machine, then run the setup.
It copies the folder, and then MDT finishes with zero errors. If I then go to that folder and run the setup.exe /s in a run box, it runs silently as it should, but it will not copy and run the file.

Here is the text in my batch file:

@echo on

robocopy \\mdtserver\share\Dell_Webcam C:\DellWebcam /e /np /nfl /ndl /njh /njs /nc /ns
cd C:\DellWebcam
START C:\DellWebcam\setup.exe /s

Also, /S or     /S /v/qn works, manually. I can't get it to run through MDT. I only know of batch files and am not familiar at all the Powershell or any other methods to run exe files. I use this above method for copying and installing other setups just fine. Am I missing something here?

Hi All,

Two weeks ago we upgraded our environment to the latest MDT version 8443. What happens now after deploying our Windows 7 image is after the first automatically log in MDT shows this message.

"Unable to find the SMS Task Sequence - The deployment will not proceed"

I can click OK and reboot the computer and the deployment proceed without any problem until the final notice.

I suspect this message is related to the MDT upgrade. Nothing else was changed in the deployment process for this task.

Any hint is highly appreciated.

Thanks,

Edy

Edy from Switzerland

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?

I am running an in-place upgrade. I have not changed any of the default Task Sequence except add a step right after the upgrade runs to install a PPKG file below.

DISM.exe /Image=%OSDisk% /Add-ProvisioningPackage /PackagePath:%DeployRoot%\Applications\SomeApp\Some.ppkg

I have HIDESHELL=YES set so I am still seeing the 100% message from Setup.exe onscreen.

This step causes an error(From BDD Log):

Litetouch deployment failed, Return Code = -2147467259  0x80004005

My question is can I apply a ppkg file during an in-place upgrade using DISM to install? If not, is there anther command line method it install it? My fear is that to apply a ppkg file via command line I need to be booted in WinPE.

I previously had MDT 2013 Update 2 installed, and upgraded to MDT 8443. I'm using ADK Win10 1607 with Windows 10 as the file server. This has been working for over a year now.

I upgraded the MDT software and updated my deployment share and litetouch WIM. I deployed my litetouch WIM to our WDS and booted off it.

Now, no matter what Task Sequence I select, after the "Ready to begin" screen, I get the following error:

Deployment Error
"Invalid DeploymentType value "" specified. The deployment will not proceed."
[OK]

I've tried every Task Sequence, I even built a new Task Sequence, I get thesame issue. I've tried manually specifying the "DeploymentType" various in both my bootstrap and in the Task Sequence itself, with no improvement.

I am currently completely down and unable to image systems.

==RULES==

[Settings]
Priority=Default
Properties=MyCustomProperty

[Default]
SkipBDDWelcome=YES
OSInstall=Y
SkipCapture=YES
SkipAdminPassword=YES
SkipDomainMembership=NO
JoinDomain=domain.com
EventService=http://computer:9800

==BOOTSTRAP.INI==

I'm trying to deploy Win7 & Win8.1 sysprep images using update 2.  These .wim's have been used in my production environment for over a year on multiple servers and have been deployed/redeployed well over 20K times without issue.  Using update 2 I've tried every combination (upgrading MDTU1 to U2, clean U2 install, creating new sysprep images, multiple deployment servers...) except for the correct one.

My last attempt was with a fresh deployment share using only the default scripts and minimal modifications (cs.ini & bootstrap.ini).  The task sequence only includes the following default items under State Restore;

Gather local only, Post-Apply Cleanup, Recover From Domain, Tattoo, Install Applications, Custom Tasks (folder), Restore Groups

same result.  The only errors/failures in the smsts.log are TSManager components;

• Failed to delete directory 'C:\_SMSTaskSequence'
• SetNamedSecurityInfo() failed.
• SetObjectOwner() failed. 0x80070005.
• RemoveFile() failed for C:\_SMSTaskSequence\TSEnv.dat. 0x80070005.
• RemoveDirectoryW failed (0x80070091) for C:\_SMSTaskSequence
• RegQueryValueExW is unsuccessful for Software\Microsoft\SMS\Task Sequence, SMSTSEndProgram
• GetTsRegValue() is unsuccessful. 0x80070002.

Because of the limited amount of hair I have left I'm reluctant to pull it out, so any useful MDT recommendations would be greatly appreciated.

Still fairly new to MDT but am learning. I am trying to add a Reg delete to the task sequence. The command line I have is:

reg.exe delete HKLM\Software\Policies\Microsoft\Windows\WindowsUpdate /f

This does not work but if I enter it in the command prompt afterwards it works fine.

I have tried looking through the logs and searching for reg.exe but cannot find any trace of it. Everything else in my TS works fine but this. Do I have to specify C:\Windows\System32? I thought I had tried that but could try it again. I just didn't know if there was anything obvious I am missing.

Where can I look for my problem at?

Thanks,

Scott