Quantcast
Channel: Microsoft Deployment Toolkit forum
Viewing all 11297 articles
Browse latest View live

Add updated WIM to existing Task Sequence

$
0
0

Hi,

I have an established Task Sequence to deploy Win8.1 using MDT 2013. The deployments are starting to take longer, because more and more updates need to be applied. So I have re-run the reference build and generated a new up to date WIM. My question is, what is the preferred method to import it? Should I import with or without the Operating system files?

In the import wizard, I select "Custom image file" and then browse to the new WIM. I select to move the files instead of copying them. On the next window, (Setup) what is best practice? To copy the OS files, or to not copy?

Is this documents in a blog anywhere?

Many Thanks

John


Regards, John


Feature Request for MDT / SCCM - Could you add in functionality to deploy WICD Provisioning Packs?

$
0
0
With windows 10 and the new adk and mdt it would be really nice if you could add a task sequence to deploy provisioning packs rather then having to DISM them into the wim that way if you are still testing out different options it would save a TON of time.

MDT 2013 Update 1 & Dell E7240 deployments failing

$
0
0

Getting this error message when trying to image a Dell Latitude E7240 with Windows 8.1 x64 image using MDT 2013 Update 1:

windows could not parse or process the unattend answer file for pass [specialize]. The settings specified in the answer file cannot be applied. The error was detected while processing settings for component [Microsoft-Windows-Shell-Setup].


The Panther\setuperr.log file is indicating the following:

SYSPRP SPPNP: Failed to enumerate PnP DRP files. Err = 0x5[gle=0x000003f0]

[setup.exe] [Action Queue] : Unattend action failed with exit code 4

[setup.exe] Execution of unattend GCs failed; hr = 0x0; pResults->hrResult = 0x8030000b


In the Panther\setupact.log, I'm seeing this:

[setup.exe] [Action Queue] : Executing command "C:\WINDOWS\SYSTEM32\RUNDLL32.EXE" shsetup.dll,SHUnattendedSetup specialize

[setup.exe] [Action Queue] : process exit code = 4

[setup.exe] [Action Queue] : Unattend action failed with exit code 4

[setup.exe] [Action Queue] : ProcessActionQueue finish (hr = 0x2c2000)

[setup.exe] Execution of unattend GCs failed; hr = 0x0; pResults->hrResult = 0x8030000b


In the Panther\UnattendGC\setuperr.log, I'm seeing this:

[Shell Unattend] CopyProfileDirectory from C:\Users\Administrator failed (0x8007012b) [gle=0x0000012b]

[Shell Unattend] _CopyToDefaultProfile failed (0x8007012b) [gle=0x0000012b]

[Shell Unattend] CopyProfile failed (0x8007012b) [gle=0x0000012b]

I'm not exactly sure what's causing this issue except for maybe a particular driver.  If I deploy the OS with any drivers, the deployment succeeds.  This is the only model machine we have that is having this issue (although I suppose that as soon as I get the E7250's that we'll have problems with those as well).

Any thoughts?


MDT LiteTouch not using the provided computer name

$
0
0

Hey guys,

I'm having an issue with MDT 2012 OS deployments that is driving me crazy. First off, I've taken over the system from the previous administrator, so I'm still learning how some of these things work. Before coming here, I've spend the better part of 2 days scouring Google and trying different recommendations, but I'm still stumped. 

Our 2 current (out of date) Win 7 images deploy without any issues. We go through the LTI prompts to choose the deployment task sequence for which image we are deploying, specify the computer name and domain information, choose whether or not to backup existing user information, then select from a checklist of applications to include. When we use these existing deployment sequences, the finished computer's hostname is set to what is specified in the MDT LTI dialog. However, when I try to deploy a new image that I created, it deploys fine, with all the extra applications and settings, but the hostname never gets set to what I specify in the Computer Name field. It ends up getting a hostname like [initials of our organization]-[random letters]. I've tried adding a step in the task sequence to specify the OSDComputerName value, but nothing ever changes. Why does MDT prompt for a computer name but then never use it? 

Through all my Google searches, I've seen tons of people with similar VB scripts to set the variable name. That's not what I'm looking to do, since the built-in prompt already works for the older images. I've compared the task sequences from those working deployments to the one I created and nothing is different. Unfortunately, there is no documentation either from the previous admin. Please help! I've spent the majority of this week trying to figure out this issue.

Thanks!

Failure (5627) 8: Run DISM.exe | Litetouch deployment failed. Return Code = -2147467259 0x800040005

$
0
0

I am trying to load a MDT 2013 Windows 10 Enterprise Image onto Virtualbox, however it fails while applying unattend.xml. The two error messages are:

Failure (5627) 8: Run DISM.exe

Litetouch deployment failed. Return Code = -2147467259 0x800040005

This build works fine on physical hardware. Same error occurs when using VMWare Desktop 10. Any ideas on how to get this build to apply to a VDI?

 

All task sequence failing.

$
0
0

I had a working MDT server in windows 2008R2 with WDS installed for deployment. It was working fine. Later i had to install windows 2012r2 and copy the deployment share from the old server and install the necessary tools to get the MDT 2013 and wds working. Upgraded the deployment share and already created task Sequence were working fine(server name had changed)

Now my problem is any new task sequence i create to deploy windows 7 its fails at step 44 (install operating system) , but if i replace the wim file from the old task sequence with the one i want and do a deployment it works. bascially any new deployment is failing at step 44.

Error it get in the Deployment summary,

Failure (5627):- 2146498514 0x800f082e: Run DISM.exe

https://social.technet.microsoft.com/Forums/getfile/724847 

Kindly advice.


With Regards, Vinoy MCSE 2003,MCITP 2008,CCNA &ITIL V3


MDT2013 WSUS task Sequence very slow

$
0
0

Hello

I have setup my task sequence to include the Windows Update Post Application Install.

I have set my WsusServer in my customsettings.ini file to go to our internal WSUS server.

This works but it is very slow to install , it looks like it downloads fine at a speed i would expect but to install 50 updates took over 24hours.

I have google'd around and saw someone who said about a proxy etc, so i thought to give this task in the task sequence Run as rights. I entered my details which would have rights to run and now i get the error 

TI ERROR - Unhandled error returned by ZTIWindowsUpdate: Invalid root in registry key "HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate\AU\UseWUServer". (-2147024891  0x80070005)

If i remove the the run as rights the WSUS post application task works but is very slow as before.

So my question 

1. Why is this very slow to install?

2. Why i get the error when run as rights are entered in the Task Sequence?

Thanks

Installing applications with MDT 2013

$
0
0

Hi,

I have 2 applications users can decide which one to install during deployment. These two apps are Office 2013 x86 and Office 2013 x64. Right now they can mistakenly choose both so I am wondering if it is possible to avoid that? Is it possible if they choose 32-bit version that 64-bit is automatically unticked and cannot be choose and vice versa?

Thanks,


Computer restarts after booting

$
0
0

Hi,

Issue: Computer restart after booting, right before litetouch wizard starts.

We use only offline media. Everything worked pretty good on my own pc. But when I moved everything onto server it stopped.

Moved from: Windows 8.1, MDT2013  6.2.5019.0, ADK 8.1, winpe5.0 (drivers from dell for winPe5.0)

Moved to: Windows Server 2008 R2, MDT2013  6.3.8298.1000, winpe10.0 (tried winPe10.0, winPe5.0, winPe5.1 drivers)

Before, offline media was working on all computers even non dell. Now, on some models it works, but on other doesn't.

I've mix up winPE drivers, also tried winPE without any drivers.

Tried to separately generate x86 x64 images.

I disabled restore state in task sequence.

I can't even troubleshoot, cause I don't have any logs. It restarts itself, so there is no x: partition inside the memory.

What I can do?

MDT 2013 Update 1 default deployment share security settings

$
0
0
When I updated to MDT 2013 Update 1 I noticed that it locked down my deployment share. When I booted my first vm it hangs because it cannot access the deployment share with my admin credentials at all so I edited those security settings manually. Should this work out of the box? This was different with older MDT versions. 

Set time and timezone in WinPE

$
0
0

I need to set current local time and timezone information in WinPE. Does anyone know how to do this with task sequence?

Windows 7 deployment slow after upgrading from MDT 2013 to MDT 2013 update 1

$
0
0

we have been running a MDT 2013 server for system deployment before and just upgrade to MDT 2013 update1 recently.

now we found a strange problem, it's very slow to install windows 7 after upgrade. not only the DISM process but also for applying image and application installation process. it will take more time to finish a deployment than before  (twice)

but looks normal for windows 8 and windows 10 deployment. I didn't modify too much on task sequence for all of these systems. and no idea why give us so different result? anyone has any idea?  

How to get started with Push Button Reset?

$
0
0

According to the OEM agreement, we cannot ship systems with Windows 10 unless they are configured with Push Button Reset. Having never implemented this feature, I'm at a loss. I can't find any good guidance on it either. Can someone point me to the right place?

We've got MDT 2013 Update 1 Second Edition and Windows 10 is deploying splendidly. I've worked through the OEM customizations and Push Button Reset is the last hurdle to clear.


Link for MDT 2013 (not update 1) download?

$
0
0

Anyone have a link to download the original MDT 2013 x64 installer (not Update 1)?  The link on Microsoft's site is broken and I haven't had much luck googling it.  Thanks.

MDT and WSUS : cut the job

$
0
0

Hi,

I work with Windows 7 and when I capture my custom image WSUS add 207 items to my Windows 7 Enterprise with SP1 iso from Microsoft vlsc.

And now I got an error befor it finished : Not enough memory

Is it possible to modifiy the ZTIWindowsUpdate.wsf to cut the job in , for example, 50 items ?

Thank you for your help.

Ludovic.


Removing Windows 10 built in Apps

$
0
0

Hello,

I created and captured a Windows 10 Reference Build. During my build process I removed some of the Windows 10 built in Apps using a PS command. I made some changes to the profile. When I bring down the image I am seeing the profile changes are there but the built in Apps are back! I was unable to find a place in the unattended file to remove these apps. So does that mean I need to remove these apps each time I build new computer or do I need to do it a different way?<o:p></o:p>

Thanks


Update to Update 1

$
0
0

I've seen all sorts of articles about MDT 2013 Update 1 which all start with how to set up MDT. What I haven't seen is anything on updating an existing MDT 2013 installation to Update 1.

I presume you just run the Update 1 msi on the current MDT machine and it's intelligent enough to work out what it needs to do without breaking existing Deployment Share setups. But I'd like to be sure. Can anyone confirm that this is all we need to do?

After an image capture, unattend.xml file not cleaned about AutoLogon,FirstLogonCommands and UserAccounts/LocalAccounts nodes

$
0
0

Hi,

I checked that popup error about missing LTIBootstrap.vbs file has been fixed in build 8298.

However, I'm wondering if the string used to query the nodes works because if I try to run a Xpath query against one of the sample unattend.xml files that are stored in MDT 2013 u1 build 8298 (they are at C:\Program Files\Microsoft Deployment Toolkit\Templates\) the query does not return any nodes.

This is the query in the script LTICleanup.wsf:

Set oNode = oUnattend.selectSingleNode("//unattend:settings[@pass='oobeSystem']/unattend:component[@name='Microsoft-Windows-Shell-Setup']/unattend:AutoLogon")
If not (oNode is Nothing) then
oNode.parentNode.removeChild oNode
oLogging.CreateEntry "Removed AutoLogon settings.", LogTypeInfo
End if

The query runs against a xml file, like the templates in MDT installation, which contains the section as below. If I remove "unattend:" from the query string, match is found about AutoLogon,FirstLogonCommands, UserAccounts and LocalAccounts nodes. Can you please tell me if it is a problem about the unattend.xml or a bug in the query?

Thanks a lot in advance

<?xml version="1.0" encoding="utf-8"?>
<unattend xmlns:unattend="urn:schemas-microsoft-com:unattend">
    ........
    .........
    <settings pass="oobeSystem">
        <component name="Microsoft-Windows-Shell-Setup" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State">
            <UserAccounts>
                <AdministratorPassword>
                    <Value></Value>
                    <PlainText>true</PlainText>
                </AdministratorPassword>
            </UserAccounts>
            <AutoLogon>
                <Enabled>true</Enabled>
                <Username>Administrator</Username>
                <Domain>.</Domain>
                <Password>
                    <Value></Value>
                    <PlainText>true</PlainText>
                </Password>
                <LogonCount>999</LogonCount>
            </AutoLogon>
            <Display>
                <ColorDepth>32</ColorDepth>
                <HorizontalResolution>1024</HorizontalResolution>
                <RefreshRate>60</RefreshRate>
                <VerticalResolution>768</VerticalResolution>
            </Display>
            <FirstLogonCommands>
                <SynchronousCommand wcm:action="add">
                    <CommandLine>wscript.exe %SystemDrive%\LTIBootstrap.vbs</CommandLine>
                    <Description>Lite Touch new OS</Description>
                    <Order>1</Order>
                </SynchronousCommand>
            </FirstLogonCommands>
            <OOBE>
                <HideEULAPage>true</HideEULAPage>
                <NetworkLocation>Work</NetworkLocation>
                <ProtectYourPC>1</ProtectYourPC>
            </OOBE>
            <RegisteredOrganization></RegisteredOrganization>
            <RegisteredOwner></RegisteredOwner>
            <TimeZone></TimeZone>
        </component>
        <component name="Microsoft-Windows-International-Core" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
            <InputLocale>0409:00000409</InputLocale>
            <SystemLocale>en-US</SystemLocale>
            <UILanguage>en-US</UILanguage>
            <UserLocale>en-US</UserLocale>
        </component>
    </settings>
...................
</unattend>

MDT Issue

$
0
0

Hi All,

I'm hoping someone can help with this issue, I will provide a little background before introducing the problem to try and make my situation as clear as possible.

Background

- I have recently upgraded MDT from 2010 to 2013 and integrated Windows Assessment and Deployment Kit for Windows 8.1

- My task sequences are split into two folders (x86 and x64), both of these folders contain a deployment image for our commonly purchased PCs. They have been created using a sysprep and capture which was working swimmingly.

- The first time I imaged two new 64x PCs since the upgrade, MDT went through the installation OK (it took all day which is unusual but it did complete), the speed of installation was going to be my next issue however I was faced with a bigger one.

Problem

We have received two new 64x PCs which I am trying to image, however the deployment wizard errors and cancels at the stage of 'Installing Operating System', with the following error:

Litetouch deployment failed, Return Code = -2147467259 0x80004005
Failed to run the action: Install Operating System.
Incorrect function. (Error: 00000001; Source Windows)
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.
Incorrect function. (Error: 00000001: Source Windows)
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

This seemed strange as I haven't touched anything since the last successful image. I've been researching the following error and the first thing that I initially tried was to Completely Regenerate the Boot Images when updating the deployment share. Since then I can no longer PXE boot to the 64x WDS, instead it eventually brings up command prompt with X:\windows\system32 that sits on top of the Microsoft Solution Accelorator background, nothing else happens at this point. If I boot to the 32x WDS if does load the deployment wizard where I can actually see the 64 bit task sequence, if however I try to run this I'm prompted with that exact same error above.

The second thing I tried was disabling 'Injecting the drivers' as I thought that the network driver may have been causing a problem and disconnecting me from the deployment share, this however didn't work either.

I'm totally baffled now to be honest and would appreciate anyone helping me out?

Many thanks in advance,

Ad

Surface 3 WDS boot issues

$
0
0
I have 21 new Surface 3 (not pro) and I am trying to image them from a WDS / MDT server. I have used same equipment / setup to image 60+ Surface Pro 3 and 100+ other laptops. When I try to image Surface 3 I can get 4 of 14 I have tried so far to boot properly. The other 10 get to screen where you press enter to boot image and freeze forever. I know machines work since I can boot image they were shipped with and use keyboards. I don't know what to try since it is a UEFI issue it seems. I can't believe the machines are all faulty but I am at a loss for what else to try? I know this isn't exactly a MDT issue but I don't know where else to ask.

Brian Hoyt

Viewing all 11297 articles
Browse latest View live


<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>