I was attempting to re-order my list of applications in MDT 2013 using XML Notepad and the Applications.xml file.  Basically I moved the XML parts around to my desired order.  I then added a few more Applications.

NOW, upon running the Deployment Wizard, it does not show my updated order OR mynew applications that I have added either.  It seems that Applications.xml is no longer linked to the Deployment wizard somehow, yet it still shows the older applications and previous order.  They install fine.

The XML file appears to be error-free.

I need to be able to add new Applications again.  Re-ordering them has now become a side thought.

Thanks!

I keep getting errors when trying to deploy Windows 7 Pro x64 from the source files that I imported in MDT.  Below is a snippet of my smsts.log file.  It looks like it is having a problem saving the environment and that there may be a program issue.

Has anyone else had this problem?  If so, what did you do to get around this.  The only thing I can think of is that after importing windows 7 source files and going through the unattend.xml file, there are two deprecated entries in there by default.  I didn't remove them, but I also didn't think they would cause issues like this.  I'm not sure if in fact these deprecated values are the issue or not.

Failed to save environment to  (80070057)    TSManager    3/25/2010 4:46:15 PM    1404 (0x057C)
TS::Environment::SharedEnvironment.saveEnvironment(szPath), HRESULT=80070057 (e:\nts_sms_fre\sms\client\tasksequence\executionengine\executionenv.cxx,842)    TSManager    3/25/2010 4:46:15 PM    1404 (0x057C)
Failed to save the current environment block. This is usually caused by a problem with the program. Please check the Microsoft Knowledge Base to determine if this is a known issue or contact Microsoft Support Services for further assistance.
The parameter is incorrect. (Error: 80070057; Source: Windows)    TSManager    3/25/2010 4:46:15 PM    1404 (0x057C)
SaveEnvironment(), HRESULT=80070057 (e:\nts_sms_fre\sms\client\tasksequence\executionengine\executionenv.cxx,420)    TSManager    3/25/2010 4:46:15 PM    1404 (0x057C)
Failed to persist execution state. Error 0x(80070057)    TSManager    3/25/2010 4:46:15 PM    1404 (0x057C)
Failed to save execution state and environment to local hard disk    TSManager    3/25/2010 4:46:15 PM    1404 (0x057C)

I migrating Windows XP Desktop from Domain A to Domain B with Windows 7 OS. 

I need to Transfer the group administrator Membership of User A from Domain A to Domain B. 

Scenario: User A is part Domain A/Group A and Group A is part of Local Administrators Group in Windows XP. Group name is also not same across the laptops. 

Result Expect: User A should be added to Local Administrators Group In Window 7

Rgds, S Kannan

Hi,

We need to ship a USB key with a MDT image + Task Sequence to deploy Windows 7.

The issue is that it will be shipped to multiple regional offices some of which have network connection to our corporate domain and some of which who don't.

So i would like during the deployment to have a window to ask users "Do you want to join this computer to the domain (Answer Yes if the computer is connected to ACME's corporate Network, otherwise select NO").

Then depending on their selection, try or do not try a domain join.

How can i achieve this?

Thanks

Hello,
I have a problem with the appdiscovery from mdt 2013.

i use mdt with sccm 2012 r2 Integration.
In my UDI Tasksequence the appdiscovery only discover Software that are installed with msi.
Scripted Software installations are not discovered.
The WMI Application History in the appdiscovery.log is empty.

Thanks for help

What is the difference using drivergroup method to install drivers vs inject drivers & select all drivers from selection profile? 

OK, please can anyone offer any advice as I am staring down the barrel of 90 of these laptops and I cant image a single one.

We have HP 250 G2 Notebook laptops (http://h10010.www1.hp.com/wwpc/pscmisc/vac/us/product_pdfs/HP_250_G2_Notebook_PC_DS.pdf)  The BIOS options are as follows with no seemingly way to enable 'legacy support' as with other HP models.

I boot to deployment wizard, selects my image and install then after 1st reboot I get this:

I've tried all possible combinations of BIOS Settings and have googled but found no answers.

One possibility I'm looking at is the version of Windows 7 I have is old, perhaps I should update the version of Windows 7 on my deployment share to Win7SP1 (Downloading right now) although I don't want to go through building my image again if I can help it.  I can comfortably image every other unit I have.

I'm out of ideas, never seen this before, can anyone help?

Regards JH

I'm trying to find a way to deploy a base OS VM from template and then call MDT to finish the config by running a post os task sequence. I'd like to be able to do this by either passing in paramaters or setting environment variables. I'd rather not get into the mess of using a database or having lots of sections in the customsettings.ini because this will be pretty dynamic. Is there any way to call a specific task sequence after an OS is on a system without using a database or customsettings.ini?

Thanks,
Rich

Hi,

  Good afternoon.Need help on this please

-Test laptops Iam using are 2 * E7440 and 1*E7240. One laptop of model E7440 has our image installed and other two (1*E7440 & 1*E7240) are shipped from Dell with default Win 7 64 bit OS.

-Test desktops Iam using are Dell Optiplex 3020 & Dell 3010 . Both models have our own images of Win 7 64 Bit.

-Laptops and desktops are on same network .

-For OS deployments we have MDT 2012.

-While there are no issues with desktops, all the laptops mentioned above don’t connect to MDT deployments share . The detailed error message I get when I run a litetouch ISO is ‘A connection to the deployment share could not be made. Connection OJ.Possible cause:invalid credentials. Retry : Try again to connect to the deployment share.’

-Have injected all possible network & storage drivers mentioned by Dell &  Intel into MDT boot image but the problem still persists. Still WinPE doesn’t detect network adapter wherein IPaddresses are not picked in WinPE mode.

-Have been testing each and every driver by manually loading them into Winpe mode to see if they pick up the IP addresses and I finally found one driver by name ‘e1d63x64.inf ‘ which I downloaded directly from Intel website. This one is picking IP Address in WinPE mode when loaded manually. Also have tested the connectivity to MDT server in WinPE mode with net use command and it was successful.

Have injected this driver into MDT Laptop deployment share, regenerated the ISO and tried again however Iam still unable to connect to the deployment share with litetouch ISO.

The above driver is very much part of set of network drivers on Dell website too.But it doesn’t work.

-Have also tried combination of network & storage drivers from Dell website  (along with the above one mentioned ) injecting them into the MDT laptop boot image but no luck.

-Every time I make changes to drivers in boot image,I update deployment share & recreate boot image .

-This very litetouch iso connects to  MDT deployments share for Dell desktop models 3010 & 3020 but have issues with laptop models E7440 & E7240. This means any connectivity or access issues can be ruled out. Also no problem with our image cause this happens even with brand new shipped laptops with your inbuild win 7 OS.

-Have tried all options suggested on internet,tested all the drivers suggested but no luck.

-For example I tried latest E7440 netwrok & storage drivers ,Dell Win PE drivers,drivers from Intel website,etc  individually as well as in combinations but the issue persists.

-If you google many express similar issues with these laptop models.

Though I used the drivers suggested by various bloggers,nothing worked for me.

Any help on this is appreciated.Thanks in advance.

I have been getting the error "ZTI ERROR - Unhandled error returned by ZTIWindowsUpdate: Object doesn't support this property or method (438)" when I use any task sequence with the Windows Update step enabled. This occurs when deploying any image, Windows XP, Server 2008(R2), Windows 7, or Windows 8.

I have updated to MDT 2012 Update 1 (6.1.2373.0). I have updated the WAIK to version 2.0(?) (not sure of the version number but, it is using the Windows 8 PE).

The troubleshooting information I have found to date states that this issue is related to the WSUS server not having the hotfix (KB2734608) installed to provide support for Windows 8/Server 2012. All WSUS 3.0 servers in the update environment have had this hotfix applied, restarted, and resync'd.

Even after all this has been done, I still am getting the same 438 error message when the task sequence gets to the Windows Update steps. The machine properly detects that it needs updates, downloads them to the target computer, then errors out when they try to install. Without fail, every machine that fails during the task sequence, will check in with the update server, download and install their required updates just like any other machine on the network. They just will not do this during the task sequence.

All of these issues did not occur until the current update of MDT 2012 was applied. Any ideas of what is happening here and what I might do to fix it?

Hello,

I am using MDT 2012 Update 1 with an almost vanilla Windows 8.1 and Windows 7 test box. I can deploy both images fine and get a success on my summary but both machines continue to auto login to the Administrator account. To my understanding, the Auto Login should be shutoff via the LTIcleanup script. When I double check the script for the reg keys that are added/deleted I can confirm that this is happening but the images still continue to auto login to the admin account.

Anyone have any ideas?

I just replaced one of the applications in my deployment share with a newer version.  What do I need to do now to update the deployment share.   If the answer is recompile, how do I do this? 

So here it is...I am deploying both Windows Server 2008 R2 and Windows 7 for an enterprise wide product.  To facilitate the build process, I've merged them into a single deployment share.  First, I loaded the W2K8R2 image into MDT 2012 and then imported the Win7 image into the same share.  I have setup the share with separate directories for each image in the appropriate places (i.e. Applications has a server directory and a client directory, as does Operating System and Task Manager).  I have set up two Selection Profiles one for the server and one for the client and assigned the directories accordingly.

While testing my client build, however, I run into a problem.  During deployment from an ISO, it can't seem to find my custom client task sequence and the deployment fails every time.  I've checked the ISO and the task sequence is there and the TaskSequenceGroups.xml and TaskSequence.xml files appear to have the correct info, but my task sequence is never read.  It appears to be looking for the old task sequence from its original share.  Any ideas?

Michael.

The problem I am about to describe doesn't exist with MDT 2010 update 1, MDT 2012, or MDT 2012 update 1 when using the either WAIK or ADK.  I have not attempted to reproduce this problem with older versions of MDT or pre-release versions of MDT 2013.  The problem definitely exists with MDT 2013 RTM.

This is the same problem as Inconsistent DISM.EXE error when applying unattend.xml during LTI deployment - Possible bug!, but this is more concise and provides details on how to reproduce the problem. 

Status as of 2014-01-08 (Previous workaround deemed unusable - core bug still present)

Keith Garner determined that DISM.EXE was failing while processing the <offlineServicing> section in the unattend.xml file.  Removing this section resolves the issue, but this section is needed to inject drivers into the image during WinPE and is needed  The presence of this section didn't cause any problems with previous releases of MDT/ADK - it is likely an interoperability bug within the DISM.EXE tool.  See replies below for details.

Problem:

When deploying Windows 7 Pro x64 w/SP1 and enabling/disabling features using unattend.xml, deployment often (almost 100% of the time) fails with this dialog:

Steps to reproduce ("bare-metal"):

1. Create a new, clean virtual machine (I used VMware Workstation)
2. Boot the VM with the Windows 7 x64 Pro w/SP1 Volume Licensing DVD
3. Install Windows with default options, OOBE choices:
   • User name = Tony
   • Computer name = Tony-PC
   • Password = tony
   • Windows Update = recommend settings
   • Time zone = Eastern
   • Location  = Work network
4. Install VMware Tools and reboot
5. Configure Internet Explorer using express settings
6. Configure Windows Update to get updates for other Microsoft products
7. Apply all available Windows Updates*
8. Install ADK for Windows 8.1 (http://www.microsoft.com/en-us/download/details.aspx?id=39982)
   • Installs .NET Framework 4.5 automatically
   • Accept all default installation choices
9. Install MDT 2013 x64 (http://www.microsoft.com/en-us/download/details.aspx?id=40796)
   • Accept all default installation choices
10. Apply all available Windows Updates again*

*When installing Windows Updates:

• Select all important updates, except Internet Explorer 11
• Select all optional updates, except Bing Bar, Bing Desktop, Security Essentials, and Silverlight.

Launch MDT Workbench:

1. Create a new deployment share
   • Accept all defaults:  C:\DeploymentShare, DeploymentShare$, etc.
2. Import Operating System:
   • Full set of source files
   • Source Directory = CD drive containing the Windows 7 x64 Pro w/SP1 Volume Licensing DVD.
   • Accept remaining defaults
3. Create a new task sequence:
   • ID = Test
   • Name = Test
   • Template = Standard Client Task Sequence
   • OS = Windows 7 Professional
   • Key = Do not specify at this time
   • Settings:
     • Full name = Tony
     • Organization = Tony
     • IE Home Page = about:blank
   • Admin password = tony
4. Update Deployment Share, and completely regenerate the boot images.

From another new, clean virtual machine:

1. Boot from the "C:\DeploymentShare\Boot\LiteTouchPE_x64.iso" file from MDT computer.
2. Run the Deployment Wizard, and enter credentials (tony, tony, . )
3. Launch the created Task Sequence (accept defaults, click keep clicking ‘next’):
   • Computer name = autogenerated
   • Join a workgroup = WORKGROUP
   • Do not move user data and settings
   • Do not restore user data  and settings
   • Locale and time = accept defaults
   • Do not capture an image

At this point, the deployment will succeed every time.

Now, edit the task sequence and edit the unattend.xml:

1. Add the Foundation Package to the answer file
2. Edit the foundation Package:
   • Disable MediaPlayback > MediaCenter
3. Save file and close task sequence.

Deploy the task sequence again using the directions above (for each attempt, I used a new, unused VM), and it will fail nearly every time!

Notes:

• Enabling/Disabling features via unattended.xml is a supported and documented process.
• I suspect a bug with DISM.EXE v6.3 while operating on Windows 6.1 images.
• I realize that adding"Install Roles and Features" and/or "Uninstall Roles and Features" task sequence items may be a workaround for this problem (I haven't tried it), but it is not asolution to the problem.

I have several images where the deployment task fails on the copy profile step.  Can anyone tell me which log will show exactly where it is failing in the copy profile process?  The latest image was created using a sysprep and capture sequence on a VM with a suspend in the middle to do the customizations.  I don't have the dreaded Adobe file permission issue or the IE10 Disable Welcome page problem.  It is clearly something else.  I didn't deprovision any apps.  Any help would be greatly appreciated.  I think my hair will all be gray by the time I get this fixed.

I'm attempting to deploy an image that I have recently captured with MDT.  I was able to capture the image without any problems and after capturing, it booted up properly.  But now when I go to deploy the image using a Standard Task Sequence it errors out.  It does boot into WinPE and gets to the installing operating system portion then spits out the following 8 errors:

(5624):2: Run ImageX: /apply "\\PDC31089\DeploymentShare$\Operating Systems\Win7_BUP_1-31-14\Win7_BUP_1-31-14.wim" 1 C:
Litetouch deployment failed, Return Code = -2147467259  0x80004005
Failed to run the action: Install Operating System. 
Unknown error (Error: 000015F8; Source: Unknown)
The execution of the group (Install) has failed and the execution has been aborted. An action failed.
Operation aborted (Error: 80004004; Source: Windows)
Failed to run the last action: Install Operating System. Execution of task sequence failed.
Unknown error (Error: 000015F8; Source: Unknown)
Task Sequence Engine failed! Code: enExecutionFail
Task sequence execution failed with error code 80004005
Error Task Sequence Manager failed to execute task sequence. Code 0x80004005
After I receive the error messages if I attempt to restart the computer and allow it to boot up it just comes up with:
"An operating system wasn't found.  Try disconnecting any drives that don't contain an operating system"

I have tried the following to resolve this issue:

• Create a new deployment share with only network drivers added and the one .WIM that was captured with MDT as well as one Task sequence.
• Update to MDT 2013
• Update Deployment share and completely regenerate Boot images
• Tried starting deployment from within Windows by mapping the drive and executing litetouch.vbs
• Also tried starting deployment using USB boot disk

I'm running out of ideas and seem to keep getting the same 8 error messages.  It's very aggravating and am hoping that someone can point me in the right direction.

I've included some log files on Skydrive at:  https://skydrive.live.com/redir?resid=6375A8F9E8089918%21105

I have been trying to capture a master image of Windows Thin PC we have prepared using MDT 2012 Update 1 but to no avail. When attempting the capture process using LiteTouch.vbs it syspreps and then reboots as it normally would and then it simply keeps rebooting over and over in a loop.

I am unsure of how to bypass this and correctly capture Windows Thin PC using MDT 2012 Update 1. If anyone has any advice or feedback they can offer I would greatly appreciate it. Thank you.

Hi everyone,

I've set up MS Deployment Toolkit, Assess and Deploy Kit, and Windows Deployment Service (all latest versions as of last week) on a Windows 2008 R2 server. I have a Windows 7 Enterprise reference system running under Hyper-V on my Windows 8 desktop. I took an image of the Windows 7 HV last week and deployed it to a new employee's computer. After they started, they got varcharmax error which told me I forgot to put SQL Native Client on the image. I went back to my reference HV and installed the sqlncli5_x64 patch and attempted to capture the image. Because this took so long the first time, I clicked 'Begin' and walked away, but was surprised that it was finished just a short time later. It wasn't until I attempted to import the capture into MDT that I realized nothing was captured. I rebooted everything and tried again, and found that the LiteTouch script prompts for paths and passwords and expected, but when you click begin a couple of screens with progress bars flash by the screen, then it shows the 'completed successfully' window without ever sysprep'ing or booting into PE for the actual capture. Thinking it was because I had already sysprep'ed the machine once, I rolled back to a snapshot I took before doing the first sysprep and capture, reapplied my update, and tried again. It still won't allow me to take a second image of the reference system. Am I missing something?

Thanks!