Hi,

I have an Upgrade Task sequence set.  If left as default, no issues.  I added a new group, added Run Command using an msiexec uninstall script, then I added a RESTART.   

When the TASK sequence runs, the uninstall happens and then RESTARTS.  Upon reboot, I log back onto system, with same account that started the Litetouch.vbs but the Task Sequence never starts again.  Basically, any RESTARTS in the Task Sequence require me to run Litetouch.vbs again and again. 

Any ideas why the Task wont auto start after the RESTART?

thanks

Paul

Hi,

I recently migrated my MDT to new server and installed all software to the latest version. When I deployed windows 10, it always installed the OS and then jump out of the deployment, it ended up to boot to windows and look nothing wrong, but it didn't finish the whole procedure. When I checked the log, it turned out it jumped out of the deployment with no errors at all. the status stopped as running at 59%, just finished at the Postinstall and reboot, but never got into State Restore to install any application.

I tried to re-created a new Deployment share and started from scratch, but it still didn't fix it.

Anyone have any idea about this? I am really devastated about it.

I can upload the CustomSettings.ini and log files if needed.

Hi,

I'm looking for a solution to deploy office 365 with MDT, without share folders for Source installation.

I can install o365 from an share folder (share folder = SourcePath in the configuration xml).
If I copy my o365 source files from MDT to the client computer in a folder previously created in a script, it's working.
If in my o365 configuration xml file, I don't setup an SourcePath or leave it to blank, it's not working, because during the deployement I've got an 17100 error which is for o365 an path error.

Is there an other solution of copying o365 source files to the client computer on local folder before deploy o365??

regards

Hello!

I'm new in MDT, I was configuring a deployment for windows W7 and It was working great, but 1 mounth ago I recive a error message: "litetouch deployment failed return code -1073741819" just when the installation wizard should start to copy the file to the PC. The only information that i've found is about error -2147467259.

The client log didn't show any relevant information and I'm not sure but looks like there aren't any log in the server.

Any idea about what is happening???

Hi.

I'd like to include the ability to add a Computer Description during the deployment of Windows 7.  Ideally, both locally and within AD.  And I'm using MDT 2013 Update 1 (v6.3.8298.1000)

I've read a few articles online, most recently https://social.technet.microsoft.com/Forums/en-US/fcd979f1-9be8-4eac-80c1-9e3c504b555f/computer-description-in-the-mdt-2012-wizard?forum=mdt (specifically SJ3ff's post) and whilst I am now asked to include a Computer Description on the Computer Name page pre-deployment, it does not appear locally or within AD once the build has successfully deployed.

I have yet to find anything online which relates to MDT 2013 U1, it's mostly MDT 2010/2012 upgrade/2012.  Many thanks.

I went ahead and updated my MDT 2013 Update 1 to Update 2. I had issues upgrading the deploymentshare(s) themselves, but I was able to get through it; however now I am unable to create a new boot file from the deploymentshare itself.

below is the error that I get!

Hi,

I have WDS currently working to image Windows 10 images with a separate Task Sequence which installs perfectly fine. I also have another Task sequence created for Windows 8.1 Enterprise(With update). When i attempt to install the 8.1 image, i receive this very generic error code: mdt failure (5601): False: Verify OS guid error 0x80004005. I've tried troubleshooting by re-creating the Litetouch, checking logs both BDD.log and SMSTS.LOG, both don't say much, especially the SMSTS.LOG, which i'm not too sure why. But i have been very unsuccessful. Below are my logs.

SMSTS.LOG:

<![LOG[Used smsts.ini to set logging settings.]LOG]!><time="13:58:52.738+480" date="09-22-2016" component="TSMBootstrap" context="" type="1" thread="1904" file="tslogging.cpp:1457">
<![LOG[==============================[ TSMBootStrap.exe ]==============================]LOG]!><time="13:58:52.738+480" date="09-22-2016" component="TSMBootstrap" context="" type="1" thread="1904" file="tsmbootstrap.cpp:1185">
<![LOG[Command line: "X:\Deploy\Tools\X64\TsmBootstrap.exe"  /env:SAStart]LOG]!><time="13:58:52.738+480" date="09-22-2016" component="TSMBootstrap" context="" type="0" thread="1904" file="tsmbootstrap.cpp:1186">
<![LOG[Current OS version is 10.0.10240.0]LOG]!><time="13:58:52.785+480" date="09-22-2016" component="TSMBootstrap" context="" type="1" thread="1904" file="util.cpp:3203">
<![LOG[Running Task Sequence in standalone.]LOG]!><time="13:58:52.801+480" date="09-22-2016" component="TSMBootstrap" context="" type="0" thread="1904" file="tsmbootstrap.cpp:523">
<![LOG[Environment scope successfully created: Global\{51A016B6-F0DE-4752-B97C-54E6F386A912}]LOG]!><time="13:58:52.801+480" date="09-22-2016" component="TSMBootstrap" context="" type="1" thread="1904" file="environmentscope.cpp:623">
<![LOG[Environment scope successfully created: Global\{BA3A3900-CA6D-4ac1-8C28-5073AFC22B03}]LOG]!><time="13:58:52.801+480" date="09-22-2016" component="TSMBootstrap" context="" type="1" thread="1904" file="environmentscope.cpp:623">
<![LOG[Loading the Environment Variables from "X:\Deploy\Tools\X64\variables.dat".]LOG]!><time="13:58:52.848+480" date="09-22-2016" component="TSMBootstrap" context="" type="1" thread="1904" file="tsmbootstrap.cpp:549">
<![LOG[D:\_SMSTaskSequence does not exist]LOG]!><time="13:58:52.895+480" date="09-22-2016" component="TSMBootstrap" context="" type="1" thread="1904" file="utils.cpp:1851">
<![LOG[Updated security on object D:\_SMSTaskSequence.]LOG]!><time="13:58:52.895+480" date="09-22-2016" component="TSMBootstrap" context="" type="1" thread="1904" file="utils.cpp:1815">
<![LOG[Updating the local data path in the Task Sequencing Environment.]LOG]!><time="13:58:52.895+480" date="09-22-2016" component="TSMBootstrap" context="" type="1" thread="1904" file="tsmbootstrap.cpp:659">
<![LOG[Reading  logging settings from TS environment to set TS logging]LOG]!><time="13:58:52.895+480" date="09-22-2016" component="TSMBootstrap" context="" type="1" thread="1904" file="tslogging.cpp:2555">
<![LOG[Process completed with exit code 2147500037]LOG]!><time="14:00:18.989+480" date="09-22-2016" component="TSMBootstrap" context="" type="1" thread="1904" file="commandline.cpp:1124">
<![LOG[Exiting with return code 0x80004005]LOG]!><time="14:00:18.989+480" date="09-22-2016" component="TSMBootstrap" context="" type="1" thread="1904" file="tsmbootstrap.cpp:1258">
<![LOG[Used smsts.ini to set logging settings.]LOG]!><time="14:00:19.067+480" date="09-22-2016" component="TsProgressUI" context="" type="1" thread="680" file="tslogging.cpp:1457">
<![LOG[==========[ TsProgressUI started in process 1000 ]==========]LOG]!><time="14:00:19.067+480" date="09-22-2016" component="TsProgressUI" context="" type="1" thread="680" file="winmain.cpp:330">
<![LOG[Unregistering COM classes]LOG]!><time="14:00:19.067+480" date="09-22-2016" component="TsProgressUI" context="" type="1" thread="680" file="winmain.cpp:204">
<![LOG[Shutdown complete.]LOG]!><time="14:00:19.067+480" date="09-22-2016" component="TsProgressUI" context="" type="1" thread="680" file="winmain.cpp:512">

BDD FILE:
BDD.Log

Update: I created a new task sequence & used "Standard Client Task Sequence" but that did not help... I've also checked the bios for the time, I've made sure i have the right CD key, injected the right drivers... I'm really confused what is going on. Why would Windows 10 work flawlessly but Win 8.1 is having issues. Not sure that it matters but I'm using the same scripts for W10 as W8.1...

Hello!

I recently upgraded MDT to 2013 Sp2 and ADK for Windows 10 1607 and after that I experience problem connection to the MDT deployment share.

Some info about the environment:

I have created a completely new deployment share just to make sure that there is not a settings that is creating these errors.

The problem:

When i boot (Not using PXE) up on the boot image the client is getting a ip adress from the DHCP,  after a while i get an error that the client could not contact the MDT server. If i check ipconfig everything seems to be working good, but if I ping the MDT server via ip adress or dns name i get "Request timed out". The strange thing is if i wait for like 10min with the client running it suddenly can ping the MDT server without any problems and if retry to reconnect to the MDT share it shows an error regaring wrong credentials instead.

The really strange thing is that i can ping other clients on the network even if im not is able to ping the MDT server.

Any help or suggestions is very appreciated!

Kind regards,

Anthon

I am attempting to run a Sysprep and Capture task sequence, it is kicking back multiple errors.

The only errors I see are:

-Unable to find sysprep.inf, image deployment may not be automated.

-FAILURE (6101):False: Check for file %DeploymentShare%\Operating systems\windows 10 pro X64\Support\Tools\Deploy.cab

-Litetouch deployment failed.  Return Code = -2147467259 0x80004005

Things of note:

-This is Windows 10 x64

-I have the source files for the OS uploaded and imported into the Deployment Share

-I have successfully created a custom WIM for Windows 7, and am attempting to do so for Windows 10.

Let me know if there is any other information I can help with. 

Hello everyone,

Here is the deal. I made a Windows 7 Pro gold image with updates in it. When I deploy it in english, everything works fine. The problem is when I deploy it and add a language pack with MDT, the deployment works just fine, although, after a reboot, windows install 75 updates, then reboot to a black screen with a cursor (before login). The problem only occurs when I am installing the french language pack with MDT (installed using the package option with MDT), after the deployment has completed. It also only happen if I wait a "long" time after deploying and first reboot. If I reboot quickly and manually install windows update before it reboots, it does not seem to have the problem.

Additional information:

1. CTRL+ALT+DELETE or CTRL+SHIFT+ESC does not open task manager
2. Safe mode also comes to black screen
3. Enabling debug mode does not give any interesting data
4. Using "last known good configuration" does not work
5. The problem occurs on many different hardware, and only when using language packs, so it is not driver related
6. Using startup repair works, but it is completely useless because I am trying to do a deployment

The setup:

1. Windows 7 Pro SP1 x64 with all updates up to a month ago.
2. Installed in English
3. Powershell 5
4. .net 4.6.1
5. Gold image was done in a virtualbox VM with 4GB ram, 2 cores, 100gb hdd with 3d hardware acceleration enabled
6. MDT 2013 update 2 (build 8330)
7. Language packs (lp.cab) are installed using the package section in MDT. I would like to avoid injecting them in the WIM for flexibility reasons.
8. I have removed the content of %windir%/Software Distribution/Download to save space in the WIM, although leaving them there does not fix the problem.

How does the problem occurs:

1. Deploy with MDT, select french language pack
2. Leave office for one hour or two, deployment takes around 20 minutes.
3. After deployment, move computer in proper OU to trigger windows updates (updates are disabled in the gold image)
4. Reboot
5. Black screen

I've been hitting the Microsoft wall for two weeks now, with no solution. I've tried to create 2 different gold images, different hardware; I always end up with the same problem.

Any help, insight or other would be much appreciated.

Hello all,

i have this new Dell's laptop (Latitude E7470) that I'm trying to deploy. when deploy starts, right after I click on "Run the depoyment wizard to install a new computer deployment",  it immediately shout on missing drivers (PCI\VEN_8086&DEV_156F&SUBSYS_06DC1028&REV_21 which is the Intel(R) Ethernet Connection I219-LM device).

i followed this forum guide (http://en.community.dell.com/support-forums/laptop/f/3518/p/19676051/20898909?rfsh=1460360493687) which basically direct me to download the Intel driver from there site and extract it, and added all of the 32 and 64-bit drivers to their respective driver management locations (both their regular install folders and the winpe folder for the boot images).

For that i follow this guy guide (http://deploymentresearch.com/Research/Post/325/MDT-2013-Lite-Touch-Driver-Management) which basically tell me to create 1 folder under out of the box drivers for windows 7 drivers and 2 additional folders for WinPE 64 and WinPE 86. then make 2 selection profiles, 1 for the x64 and 1 for x86 and direct them to their designated folders under out of the box...

then i went to MDT Deployment share properties and at the Windows PE tab go to the Drivers and Patches and there configure for each platform which selection profile to use.

when booting for deployment i still have the same error.

under MDT Deployment share properties i went to Windows PE and under General tab i changed the background bitmap. when boot again i still getting the default bitmap and not what i choose. So i start thinking whether my new setup is working or not.

the strange thing is that i'm using VM to mount my basic windows installation and to patch it with new microsoft updates and then recapture it, for this I disjoin from the domain, and net use to the deploymentshare$ folder and run the litetouch.vbs.when doing this i do see the bitmap file I configured.

can any1 help pls? why when booting from WinPE and do not pull the MDT Deployment share properties and when running the litetouch.vbs it does.

Thanks a lot for your help.

Using MDT 2013 Update 2 In Place Upgrade task sequence to upgrade machines to Windows 10. The installation progress window that is usually persistent throughout the deployment process for all other types of task sequences does not appear after the actual OS upgrades. All the tasks still occur as usual and can be followed along in bdd.log but the progress window is no where to be seen

Have any of you been able to see the progress window during a W10 in place upgrade at this point? I've read on another forum about this issue but overall there is not much information on it. It is likely an MDT bug.

This occurs on every machine tested, VMs included, Windows 7 upgrade and Windows 8.1 upgrade. The log files do not seem to yield anything of value but let me know if there is a specific one I should post. 

Thanks

MDT 2013 update 2   : ADK 10.1.14393.0 - Installed on Windows server 2012 R2 - MDT Share with DFS : Windows 10 (1607)

Hi all,

   I am getting following message after post installation.

So far I have tried Diskpart (clean), remove all osd files from c: drive (Minint), re-added all drivers, no luck. Same tasksequence works on Dell Latitude E7250 but doesn’t work on Surface Pro 3 and OptiPlex 5040.

I also have tried this solutionshttp://tinyurl.com/jsxpq72 with no luck.

Since 5040 has M.2 SSD drives, I added offline WIM driverIntel® Rapid Storage Technology (Intel® RST) RAID Driver from

https://downloadcenter.intel.com/download/25165/Intel-Rapid-Storage-Technology-Intel-RST-RAID-Driver?product=55005  no luck

here are my log files:

https://1drv.ms/f/s!AvrwFkn-ASCWgj9liIVgSk1ygf-n

orion

I honestly have no idea what happened. All the drivers are gone in the toolkit, however looking at the DeploymentShare there are 20+gb's of driver files.

I have restarted the server many times, closed and reopened the share, completely re-add the drivers to a couple computer folders. Yet it still doesn't work... I even am checking for updated from microsoft, if it will even help..

I am running blind trying to fix this, as this is our only deployment server.

Any help would be greatly appreciated!

(screenshots coming after my account is verified)

I am getting these error at the end of my deployment:

FAILURE (Err): 53: Copy File: C:\MININT\unattend.xml to C:\Windows\Panther\Unattend.xml - File not found

After tracing BDD, LTIApply, ZTIConfigure and comparing it with deployments with no errors, I realised that in ZTIConfigure, the script looks for unattend.xml and it found one in C:\Windows\Panther and it assigns it to OSDAnswerFilePath. It doesnt even grab from the deployment share.

This is from the deployment that has issue.

Found existing unattend.xml at C:\Windows\Panther\unattend\unattend.xml	ZTIConfigure	23/9/2016 10:00:19 AM	0 (0x0000)
Property OSDAnswerFilePath is now = C:\Windows\Panther\unattend\unattend.xml	ZTIConfigure	23/9/2016 10:00:19 AM	0 (0x0000)
Loaded C:\Windows\Panther\unattend\unattend.xml	ZTIConfigure	23/9/2016 10:00:19 AM	0 (0x0000)
Merging \\<host>\DeploymentShare$\Control\HP430G3\Unattend.xml into C:\Windows\Panther\unattend\unattend.xml	ZTIConfigure	23/9/2016 10:00:19 AM	0 (0x0000)
Loaded \\<host>\DeploymentShare$\Control\HP430G3\Unattend.xml for merging	ZTIConfigure	23/9/2016 10:00:19 AM	0 (0x0000)

This should be the correct behaviour.

Found unattend.xml at \\VM-DC\DeploymentShare$\Control\W10_1\Unattend.xml, will copy to W:\MININT\Unattend.xml	ZTIConfigure	19/9/2016 9:53:02 PM	0 (0x0000)
Copied \\VM-DC\DeploymentShare$\Control\W10_1\Unattend.xml to W:\MININT\Unattend.xml	ZTIConfigure	19/9/2016 9:53:02 PM	0 (0x0000)
Property OSDAnswerFilePath is now = W:\MININT\Unattend.xml	ZTIConfigure	19/9/2016 9:53:02 PM	0 (0x0000)

*Ignore the different drive letter and differences in TS-ID.

BTW, W: and C: refer to the same location. They both refer to OSDISK and target partition where the wim will be applied to.

At the end of the day, LTIApply only grabs the unattend from %OSDISK%\MININT

Copy File: C:\MININT\unattend.xml to C:\Windows\Panther\Unattend.xml	LTIApply	23/9/2016 10:14:39 AM	0 (0x0000)
FAILURE (Err): 53: Copy File: C:\MININT\unattend.xml to C:\Windows\Panther\Unattend.xml - File not found	LTIApply	23/9/2016 10:14:39 AM	0 (0x0000)

How do i force it to always grab the unattend file from the deployment share and copy to %OSDISK%\MININT?

Hi Everyone,

I have recently tried to run a Capture task sequence for a Golden Windows 10 Build 1607 computer.

I have my Rules setup with:

[Settings]
Priority=Default
;CSettings, CPackages, CApps, CAdmins, CRoles, Locations, LSettings, LPackages, LApps, LAdmins, LRoles, MMSettings, MMPackages, MMApps, MMAdmins, MMRoles, RSettings, RPackages, RApps, RAdmins
Properties=MyCustomProperty
[Default]
OSInstall=Y
SkipCapture=NO
DoCapture=YES
AdminPassword=temp
TimeZoneName=E. Australia Standard Time
TimeZone=260
UILanguage=en-US
UserLocale=en-AU
KeyboardLocale=en-AU
JoinDomain=temp
WSUSServer=http://srv-wsus2:8530
_SMSTSORGNAME=temp

SkipAdminPassword=NO
SkipProductKey=NO
SkipComputerName=NO
SkipDomainMembership=NO
SkipUserData=NO
SkipLocaleSelection=NO
SkipTaskSequence=NO
SkipTimeZone=NO
SkipApplications=NO
SkipBitLocker=YES
SkipSummary=NO
SkipRoles=NO
;DoCapture=YES
;SkipWizard=NO
;SkipAppsOnUpgrade=NO
;SkipDeploymentType=NO
;SkipComputerBackup=NO
;SkipPackageDisplay=NO
;SkipCredentials=NO

;SkipCapture=NO
;SkipProductKey=NO
;SkipAdminPassword=NO

However, I am unable to / can not when I select the Task Sequence to get any capture options.

Any ideas???

Originally this worked when I was using Windows 10 Build 1511, and I could capture my Golden Image, but now I am trying to do this for a Windows 10 Build 1607, the capture options do not appear in Windows Deployment Wizard.

Also, as a second question, if I change the MDT Deployment Share properties, mainly the Rule (Custom Settings) do I have to rebuild / update the whole Deployment Share each time?

Thanks for any help, much appreciated.

Please let me know if I may have forgot any steps, etc?

Cheers,
Anthony

When you create a offline media MDT doesn't copy applications to media automatically.  Is this a bug or am I missing something? Using the latest MDT. Currently I will manually copy the applications to offline media before building the ISO file

Sometimes with certain laptop models we have problems with automatic MDT Bitlocker provisioning during OSD. I'm not sure what causes this. When you manually enable Bitlocker from OS afterwards it works fine.

FAILURE ( 6739 ): False: Check to see if TPM is enabled