Sysprep is making a lot of problems for us. We get so many different error on Win 7 and I couldn't event start Sysprep on Win10

So I was thinking maybe I can continue the tasks without running sysprep ( On a captured wim image).

And also use some kind of a workaround to continue the task after the deployment of the wim.

After we deploy the image, the task stops at the logon screen with our local admin user (not Administrator) and cant continue from there. if I open the user then the tasks wont continue from where it stopped.

Is there a way to make it pass our local admin and then change the computer name and domain as we provided in the tasks?

Hi,

In my present network i have multiple branded PCs and few assembled system.

I am trying to deploy OS to 4 PCs all the 4 are different make and model, i have imported all the 4 Models Driver into my Deployment Tool-->Out of Box Drivers Like HP-15G , Lenovo V110, Intel DG61HK, Asus M5AG etc.

When i check manually the cmd

wmic csproduct get name

wmic csproduct get vendor

few motherboard shows "To Be Filled By O.E.M" error.

Can anybody suggest me how to deploy OS for multiple model System all at once.

Thanks in advance.

Mohammed...

Hello,

First of all, I would like to apologize for my very basic English.

I explain my problem, when capturing a Windows 7 x86 image installed on a Hyper-V VM via MDT, when creating the.wim, the VM restarts and displays the following prompt "An existing in-progress deployment was found but is not in an excepted state. Would you like to ignore this in-progress deployment and start a new one ?". 

So I click on no and the task sequence fails and gives me the following error codes :

"Error creating an image of drive D:, rc = 13"

"ZTI Error - Non-zero return code by ZTIBackup, rc = 13

I think I went all over the internet to find a solution but I didn't find anything. It seems I'm the only one who's had this problem on Earth. Did someone can help me please ?

So I have the MDT task sequence set to enable Bitlocker and put the recovery key into Active Directory for easy access by the Domain Admins.  When I tested it, everything seemed fine.  When I went to image a production machine, I found that the machine kept prompting the user for the recovery key.  I then went about trying to add a GPUpdate /force command into the task sequence thinking that it might just be a policy issue.  When I went to test this on one of our spare machines, I ended up getting a failure message at the end stating the task sequence had failed.  I have added a link to all of the log files from this attempt in order to allow you all to see what is going on.  I am not sure if I should just add in a reboot command to the system in order for it to make sure it gets all of the right GPO's applied to the system.  Any help on this issue would be appreciated.

https://1drv.ms/f/s!AnkJZ7azSrQpbwX5A61XdYP6aXs

I'm trying to capture a physical "D" drive through task sequence for Window 7 and I found some help online using this method

Add “Run Command Line” to the task sequence to capture D: with the following command line
"%DeployRoot%\Tools\X64\imagex" /capture D: "%ComputerBackupLocation%\D_Drive.wim" "D Drive"

I'm able to capture the images for C and D drive on my window 7 but I got some issue to deploy the images.

Add “Run Command Line” to the task sequence to deploy D: with the following command line
"%DeployRoot%\Tools\X64\imagex" /apply "%DeployRoot%\Operating Systems\D_Drive\XP_D_Drive.wim" 1 %DDrive%

The above command Line for deploy D there is a Variable %DDrive%. But I am deploying to a physical D Drive. can someone help me what is the Right Command to deploy to a physical D Drive. I am not using any task sequence to create a "Format and Partition Disk" with C and D drive and assign Variable to it. 

fyi: I have successful capture and deploy window 10 "D" drive using DISM capture command, but window 7 does not support the syntax for DISM Capture.  

Where can I find the MDT 6.3.8443 MSI? I cannot find it anywhere. Thank you for your help.

Nicholas

Hello everybody,

we have some problems with our deployment. The problems started when we upgraded the MDT to 8450 / ADK 1709. We installed a vm with 1709 and we customized it. After that we captured the image and added a task sequence to our deployment. While testing, we noticed that the task sequence stops right after rebooting the system (installation of operating system was successful). The system does the autologin (or i think it does; we had no password set) and stops continuing. There is no summary or anything else in the processes. When I try to launch the LiteTouch.vbs from the computer the task sequence starts and finishes the deployment successfully. We checked the other task sequences with earlier versions and they still work like expected. There are no error logs on the machine or on the deployment server which could be realted to our problem.

We already tried to change the registry keys „FilterAdministratorToken“ and „EnableLUA“. Further we tried to create a new task sequence (we copied it before and changed the settings).

There is a second administrator account on the machine, while the administrator is disabled. I also tried to change the unattend.xml to login with the second administrator account, with no success.

Later I thought that it might be a problem with the custom image, so we installed another vm and captured it (at this time without a second administrator). The deployment process still stops after reboot and autologin.

for the sake of completeness, here are the logs from the computer: https://www.file-upload.net/download-13113110/smsts.log.html

Any suggestions?

thank you in advance.

Thanks for reading my post.  Our Imaging Server is running MDT ver. 8443 and ADK 1703 on a VMWare hosted Windows 2008 R2 Standard server.  Before I upgrade to the 1709 ADK I want to make sure the Capture and Deploy functions are working.  The Capture function is not working and I have not been able to determine why yet. The last time I captured an image of my reference computer was back in June or July and I have not touched this server since then. There have been a few Windows Security updates and one Cumulative update since then.

The reference computer I use is a VMWare hosted Windows 10 64bit 1703 VM hosted on a Windows 10 64bit Pro physical host. This is the same configuration I have been using for the past year+.  I have joined and disjoined this VM to/from our domain a few times this past year. 

When I connect to the MDT server's deployment share (scripts folder) to run the LiteTouch VBS script as I always do it pops up the usual prompt to log in to my network, then it runs what looks like the LTIGather script. Then abruptly finishes and produces no error messages indicating it is complete. But is is not complete, it does not run the entire set of scripts and does not capture an image.  I looked through the BDD log but cannot discern what the problem is.  I hope you can help me and appreciate your input.  I am including a link to the BDD log it produces.  If you cannot access would you please let me know? I can post it here too.

I appreciate your input.

https://colgov-my.sharepoint.com/:u:/g/personal/mike_hyland_lynchburgva_gov/EXilh36Svo1Opxcm9jwoPR8BOZwf-Ub7QXrjZAR8TciL5Q?e=xFrQ0S

Hello,

I'm trying to join a pc to an AD security group during a MDT 2012 Task Sequence with a VBS script. I'm running the script during the TS as another user. I'm getting error 0x80004005. I've run the script in Windows as another user the script just works.

I've tried several things, but I can't let it work.

I hope someone can help me

Thank you

Edward de Ruiter

Hi!

I'm having issues with something I thought should be very smart. The possiblity to choose in the start of a specific deployment if the computer should join our domain or just stay in a workgroup.

If I blank out every domain settings in [W10X64-1803] it will join the workgroup Ive specified, but if not, it will somewhere in postinstall join the domain with name as configured. I want it to stay in the workgroup.

I would also love a tip on how to set specific tasks in the TS for if the computer is in the domain or in the workgroup.

Anyone who has a solution for this?

Under you can see my two CustomSettings.ini files.

CustomSetting:
[Settings]
Priority=DefaultGateway, ByLaptopType, ByDesktopType, Model, SetAlias, Default
Properties=MyCustomProperty, ModelAlias, MakeAlias, MacAlias, SMBIOSBIOSVersion, ComputerLocationName, ComputerTypeName

[DefaultGateway]
10.247.10.1=NORWAY

[NORWAY]
ComputerLocationName=no

[ByLaptopType]
Subsection=Laptop-%IsLaptop%

[Laptop-True]
ComputerTypeName=lt

[ByDesktopType]
Subsection=Desktop-%IsDesktop%

[Desktop-True]
ComputerTypeName=ws

[HP Elite x2 1012 G1 Tablet]
ComputerTypeName=tablet

[Surface Pro 4]
ComputerTypeName=surface

[SetAlias]
UserExit=AliasUserExit.vbs
MakeAlias=#SetMakeAlias()#
ModelAlias=#SetModelAlias()#
SMBIOSBIOSVersion=#SetSMBIOSBIOSVersion()#
MacAlias=#SetMacAlias()#

[MAKE]
DriverSelectionProfile=Nothing
DriverGroup001=%Model%

[Default]
OSDComputername=%ComputerLocationName%-%ComputerTypeName%-
_SMSTSORGNAME=DOMAIN - %TaskSequenceID% on %OSDComputername%

BitsPerPel=32
VRefresh=60
XResolution=1
YResolution=1
OSInstall=Y
SkipBDDWelcome=YES
KeyboardLocale=nb-NO
UserLocale=nb-NO
UILanguage=nb-NO
AdminPassword=P@ssw0rd
SkipAppsOnUpgrade=NO
SkipAdminPassword=YES
SkipProductKey=YES
SkipComputerName=NO
SkipUserData=YES
SkipLocaleSelection=YES
SkipTaskSequence=NO
SkipTimeZone=YES
SkipBitLocker=YES
SkipSummary=YES
SkipCapture=YES
SkipApplications=YES
DoCapture=NO
ComputerBackupLocation=\\MDTSERVER\MDTProduction$\captures

SkipFinalSummary=YES
TimeZone=110
TimeZoneName=W. Europe Standard Time
WSUSServer=http://MDTSERVER.DOMAIN.com:8530

Home_page=http://www.DOMAIN.no
EventService=http://MDTSERVER:9800

CustomSettingWG.ini:
[Settings]
Priority=DefaultGateway, ByLaptopType, ByDesktopType, TaskSequenceID, Model, Default
Properties=MyCustomProperty, ComputerLocationName, ComputerTypeName

[Default]
SkipDomainMembership=YES
JoinDomain=DOMAIN.com
DomainAdmin=%ComputerLocationName%-MDT_join 
DomainAdminPassword=P@ssw0rd
DomainAdminDomain=DOMAIN.com
MachineObjectOU=ou=MDT,ou=%ComputerLocationName%,ou=Corp,dc=DOMAIN,dc=com

[W10X64-1803O]
SkipDomainMembership=YES
JoinDomain=DOMAIN.com
DomainAdmin=%ComputerLocationName%-MDT_join 
DomainAdminPassword=P@ssw0rd
DomainAdminDomain=DOMAIN.com
MachineObjectOU=ou=MDT,ou=%ComputerLocationName%,ou=Corp,dc=DOMAIN,dc=com

[W10X64-1803]
SkipDomainMembership=NO
JoinDomain=DOMAIN.com
DomainAdmin=%ComputerLocationName%-MDT_join 
DomainAdminPassword=P@ssw0rd
DomainAdminDomain=DOMAIN.com
MachineObjectOU=ou=MDT,ou=%ComputerLocationName%,ou=Corp,dc=DOMAIN,dc=com
JoinWorkGroup=WORKGROUPNAME

Some screendumpts:

Hello,

i want a automatic installation of Office 2019 deployed with MDT (as application).

With earlier versions of MS Office i did by : setup.exe /config proplus.ww\config.xml

I think this is not possible anymore with Office 2019.

Until now i can deploy office 2019 with the setup.exe and configuration-Office365-x64.xml

My xml-file is:

With this setup, the volume licensing version is downloaded, and installed.

Problem:

After starting an Office Application, office must still be activated with the same key.

Anybody having a (better?) solution for the deploying Office 2019 with mdt?

Anybody having a solution for the activation-problem?

Thx

It's decided that, for now, we will use GPO to govern our MS Updates via the internet.
One issue is that device-specific drivers are being replaced during the updates. When I check online for GPO settings to prevent this, all I see are settings to prevent the admin/user from installing any drivers, at any time.

What I'm hoping to find is the GPO setting to prevent driver updates/replacements during the "Check for Updates" when we run this manually. It's obvious several drivers get updated during this.
Thanks!

Hi @ all

wie have updated our Litetouch boot image using DISM and know we try to update the deploymentshare but we get the following error.  

=== Making sure the deployment share has the latest x86 tools ===

=== Processing LiteTouchPE (x86) boot image ===

Building requested boot image profile.

System.Management.Automation.CmdletInvocationException: Unable to open the specified WIM file. ---> System.Exception: Unable to open the specified WIM file. ---> System.ComponentModel.Win32Exception: The system cannot find the file specified
   --- 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.Internal.PipelineProcessor.SynchronousExecuteEnumerate(Object input, Hashtable errorResults, Boolean enumerate)
   at System.Management.Automation.Runspaces.LocalPipeline.InvokeHelper()
   at System.Management.Automation.Runspaces.LocalPipeline.InvokeThreadProc()

Unable to open the specified WIM file? The image ist is stil in the boot folder.

Anybody an idea or an solution for that problem?

Thank's

Adrian

Hello;

I'm using MDT 2013, build 8450, with Windows 10 1709 ADK installed.

From an Windows 10 client in build 1607, I'm trying to execute an upgrade task sequence to upgrade my windows 10 client version to 1709, all drivers injected is good, during the task sequence, it starting to Upgrade the OS, but not finish this step.

Here is my BDD.log

<![LOG[Property TaskSequenceID is now = 012]LOG]!><time="14:34:18.000+000" date="01-24-2018" component="Wizard" context="" type="1" thread="" file="Wizard"><![LOG[Property TaskSequenceName is now = Udpate-Win10-1709]LOG]!><time="14:34:18.000+000" date="01-24-2018" component="Wizard" context="" type="1" thread="" file="Wizard"><![LOG[File C:\MININT\Scripts\LTIBootstrap.vbs already exists in Target]LOG]!><time="14:35:42.000+000" date="01-24-2018" component="LTICopyScripts" context="" type="1" thread="" file="LTICopyScripts"><![LOG[LTICopyScripts processing completed successfully.]LOG]!><time="14:35:42.000+000" date="01-24-2018" component="LTICopyScripts" context="" type="1" thread="" file="LTICopyScripts"><![LOG[Property SourcePath is now = \\192.168.0.3\DeploymentShare$\Operating Systems\Windows10-1709-V2]LOG]!><time="14:35:42.000+000" date="01-24-2018" component="LTIApply" context="" type="1" thread="" file="LTIApply"><![LOG[LTI upgrade OS using  \\192.168.0.3\DeploymentShare$\Operating Systems\Windows10-1709-V2]LOG]!><time="14:35:42.000+000" date="01-24-2018" component="LTIApply" context="" type="1" thread="" file="LTIApply"><![LOG[New ZTIDiskPartition : \\LAPS-PC1\root\cimv2:Win32_LogicalDisk.DeviceID="C:"    \\LAPS-PC1\root\cimv2:Win32_DiskPartition.DeviceID="Disk #0, Partition #1"]LOG]!><time="14:35:43.000+000" date="01-24-2018" component="LTIApply" context="" type="1" thread="" file="LTIApply"><![LOG[Upgrading from \\192.168.0.3\DeploymentShare$\Operating Systems\Windows10-1709-V2\setup.exe using command: "\\192.168.0.3\DeploymentShare$\Operating Systems\Windows10-1709-V2\setup.exe" /auto Upgrade /Quiet /NoReboot /PostOobe C:\MININT\Scripts\SetupComplete.cmd /PostRollback C:\MININT\Scripts\SetupRollback.cmd /InstallDrivers C:\MININT\Drivers /DynamicUpdate Disable /ImageIndex 5 /compat IgnoreWarning]LOG]!><time="14:35:43.000+000" date="01-24-2018" component="LTIApply" context="" type="1" thread="" file="LTIApply"><![LOG[About to run command: "\\192.168.0.3\DeploymentShare$\Operating Systems\Windows10-1709-V2\setup.exe" /auto Upgrade /Quiet /NoReboot /PostOobe C:\MININT\Scripts\SetupComplete.cmd /PostRollback C:\MININT\Scripts\SetupRollback.cmd /InstallDrivers C:\MININT\Drivers /DynamicUpdate Disable /ImageIndex 5 /compat IgnoreWarning]LOG]!><time="14:35:43.000+000" date="01-24-2018" component="LTIApply" context="" type="1" thread="" file="LTIApply"><![LOG[Command has been started (process ID 5860)]LOG]!><time="14:35:43.000+000" date="01-24-2018" component="LTIApply" context="" type="1" thread="" file="LTIApply"><![LOG[ZTI Heartbeat: command has been running for 0 minutes (process ID 5860)]LOG]!><time="14:35:43.000+000" date="01-24-2018" component="LTIApply" context="" type="1" thread="" file="LTIApply"><![LOG[Return code from command = -1047526908]LOG]!><time="14:37:18.000+000" date="01-24-2018" component="LTIApply" context="" type="1" thread="" file="LTIApply"><![LOG[Setup failed to upgrade OS from  \\192.168.0.3\DeploymentShare$\Operating Systems\Windows10-1709-V2\setup.exe, rc = -1047526908]LOG]!><time="14:37:18.000+000" date="01-24-2018" component="LTIApply" context="" type="3" thread="" file="LTIApply"><![LOG[ZTI ERROR - Non-zero return code by LTIApply, rc = 1]LOG]!><time="14:37:18.000+000" date="01-24-2018" component="LTIApply" context="" type="3" thread="" file="LTIApply"><![LOG[Command completed, return code = -2147467259]LOG]!><time="14:37:18.000+000" date="01-24-2018" component="LiteTouch" context="" type="1" thread="" file="LiteTouch"><![LOG[Litetouch deployment failed, Return Code = -2147467259  0x80004005]LOG]!><time="14:37:18.000+000" date="01-24-2018" component="LiteTouch" context="" type="3" thread="" file="LiteTouch"><![LOG[For more information, consult the task sequencer log ...\SMSTS.LOG.]LOG]!><time="14:37:18.000+000" date="01-24-2018" component="LiteTouch" context="" type="1" thread="" file="LiteTouch"><![LOG[Property RetVal is now = -2147467259]LOG]!><time="14:37:18.000+000" date="01-24-2018" component="LiteTouch" context="" type="1" thread="" file="LiteTouch"><![LOG[Unable to copy log to the network as no SLShare value was specified.]LOG]!><time="14:37:18.000+000" date="01-24-2018" component="LiteTouch" context="" type="1" thread="" file="LiteTouch"><![LOG[CleanStartItems Complete]LOG]!><time="14:37:18.000+000" date="01-24-2018" component="LiteTouch" context="" type="1" thread="" file="LiteTouch"><![LOG[Unregistering TSCore.dll.]LOG]!><time="14:37:18.000+000" date="01-24-2018" component="LiteTouch" context="" type="1" thread="" file="LiteTouch"><![LOG[About to run command: wscript.exe "\\svcdc-test\deploymentshare$\Scripts\LTICleanup.wsf"]LOG]!><time="14:37:18.000+000" date="01-24-2018" component="LiteTouch" context="" type="1" thread="" file="LiteTouch"><![LOG[Microsoft Deployment Toolkit version: 6.3.8450.1000]LOG]!><time="14:37:18.000+000" date="01-24-2018" component="LTICleanup" context="" type="1" thread="" file="LTICleanup"><![LOG[Removing AutoAdminLogon registry entries]LOG]!><time="14:37:19.000+000" date="01-24-2018" component="LTICleanup" context="" type="1" thread="" file="LTICleanup"><![LOG[Re-enabling UAC for built-in Administrator account]LOG]!><time="14:37:19.000+000" date="01-24-2018" component="LTICleanup" context="" type="1" thread="" file="LTICleanup"><![LOG[Removing Windows 10 Upgrade registry entry]LOG]!><time="14:37:19.000+000" date="01-24-2018" component="LTICleanup" context="" type="1" thread="" file="LTICleanup"><![LOG[VSSMaxSize not specified using 5% of volume.]LOG]!><time="14:37:19.000+000" date="01-24-2018" component="LTICleanup" context="" type="1" thread="" file="LTICleanup"><![LOG[Logs contained 43 errors and 10 warnings.]LOG]!><time="14:37:19.000+000" date="01-24-2018" component="LTICleanup" context="" type="1" thread="" file="LTICleanup"><![LOG[No Windows PE image to delete.]LOG]!><time="14:37:19.000+000" date="01-24-2018" component="LTICleanup" context="" type="1" thread="" file="LTICleanup"><![LOG[Checking mapped network drive.]LOG]!><time="14:37:19.000+000" date="01-24-2018" component="LTICleanup" context="" type="1" thread="" file="LTICleanup"><![LOG[testing drive Z: mapped to \\svcdc-test\deploymentshare$]LOG]!><time="14:37:19.000+000" date="01-24-2018" component="LTICleanup" context="" type="1" thread="" file="LTICleanup"><![LOG[testing drive Y: mapped to \\192.168.0.3\DeploymentShare$]LOG]!><time="14:37:19.000+000" date="01-24-2018" component="LTICleanup" context="" type="1" thread="" file="LTICleanup"><![LOG[Disconnecting drive Y: mapped to \\192.168.0.3\DeploymentShare$]LOG]!><time="14:37:19.000+000" date="01-24-2018" component="LTICleanup" context="" type="1" thread="" file="LTICleanup"><![LOG[Cleaning up C:\MININT directory.]LOG]!><time="14:37:19.000+000" date="01-24-2018" component="LTICleanup" context="" type="1" thread="" file="LTICleanup"><![LOG[Cleaning up TOOLS, SCRIPTS, and PACKAGES directories.]LOG]!><time="14:37:19.000+000" date="01-24-2018" component="LTICleanup" context="" type="1" thread="" file="LTICleanup">

Hi,

I've got a couple hundred Win7 boxes to upgrade to Win10 180X in the next few months and they're going much slower than I expected. After this line in LTIApply.log...

9:35:41 AM About to run command: "\\[server]\[productionshare$]\Operating Systems\W10v1803x64-DEF\setup.exe" /auto Upgrade /Quiet /NoReboot /PostOobe C:\MININT\Scripts\SetupComplete.cmd /PostRollback C:\MININT\Scripts\SetupRollback.cmd /InstallDrivers C:\MININT\Drivers /DynamicUpdate Disable /ImageIndex 3 /compat IgnoreWarning

...it takes about an hour to finish. i.e....

10:45:00 AM Event 41003 sent: ZTI Heartbeat: command has been running for 70 minutes (process ID 9748)
10:48:58 AM Return code from command = 0
10:48:58 AM Setup completed successfully.

So, that's the big time gap that I expected, but I'm unsure if there's anything I can do about it. LiteTouch.log shows another big gap between...

10:49:05 AM Property BootPE is now = [it's blank] [and...]
11:39:19 AM Microsoft Deployment Toolkit version: 6.3.8450.1000
11:39:20 AM ZTIUtility!GetAllFixedDrives (False)

Looking at BDD, the other big gap is between:

12:22:44 PM Event 41001 sent: ZTIWindowsUpdate processing completed successfully. [ZTIWindows Update] [and...]
2:03:03 PM  Command completed, return code = 0 [LiteTouch]

If anyone has any advice on how I can speed up the In-Place Upgrade TS by eliminating these gaps, or by anything else I should check out, please let me know! Thank you. -G

I am new to using MDT/WDS and have followed the directions "https://docs.microsoft.com/en-us/windows/deployment/deploy-windows-mdt/prepare-for-windows-deployment-with-mdt" to setup and deploy Microsoft Windows 10 and everything is working great but when I try to add new OS's either Windows 8.1 or Windows 7 both Pro versions with their separate Task Sequences and separate drivers I keep getting the nice pink screen stating "Failure (5627) -2146498547 0x800F080D Run Dism.exe /Litetouch Deployment Failed / Failed to run the action: Install Operating Systems. Operation aborted (error: 80004004; Source: Windows Failed to run last action"

I'm using Server 2012 and MDT 2013.

Any assistance would be greatly appreciated.