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

Application hanging on install - ZTI Heartbeat

$
0
0

Hi all,

I'm using MDT 2013 Update 1 to create a Windows Server 2012 R2 image with certain modifications including installing  a number of applications.

I'm having some issues whereby the deployment seems to hang for 5 - 60 minutes where it looks like nothing is happening.

The first time I encountered this is when I used the Cleanup_before_sysprep script created by Michael N. The build seemed to just hang for 15 - 30 minutes and then would crank back up and complete the build.

The next time I've encountered it is trying to install the Citrix VDAWorkstationsetup.exe. Again, the install seems to just hang until I interact with the OS and move a window around. Then it seems to wake up.

Has anyone come across this type of behaviour before? If so, is there a way to troubleshoot it to find out what's going on?

What log files am i looking for and where would they reside?

Thanks,

Mark


So, it seems there really is a bug with the Upgrade task sequence not finishing up.

$
0
0

I wanted to get some consensus around this. I have been working on our Windows 10 Upgrade task sequence, and it seems the only way for the task sequence to successfully complete is for an administrative user to login to the Windows 10 machine after it has been upgraded.

We are utilizing MDT monitoring (and have extended it quite a bit, actually) so we know when the deployment has properly finished. All of the steps listed in the task sequence editor are executed properly, but the deployment does not send the status message 41015 (which means a successful deployment) until a user with admin privileges logs in. Up until that point, the deployment is still in progress. This also means that you never see the summary screen until an admin user logs in.

This presents a problem for our desired upgrade strategy, which would be to silently upgrade batches of machines at night or on the weekends, since they will not be "finished" until an admin logs in to the machine.

Here is a shot from our monitoring that illustrate the issue:

So, is anyone else seeing this? How are we supposed to handle this? They way MS is pushing us to do Upgrades, I think this would be a significant issue?

"Wizard Error: You must be running with Administrator rights. The deployment cannot Proceed." after reboot of Windows 10 Upgrade

$
0
0

I am preparing to upgrade all machines in my environment from Windows 7 Enterprise to Windows 10 Enterprise using MDT 2013 Update 1 Build 8298. I am using the standard upgrade sequence template in MDT and running litetouch.vbs from a domain account with local administrative permissions on the box. The script does its thing and then goes to the Black screen saying Windows 10 is upgrading sit back and relax and the prograss circle with the %. Once the computer reboots and I log back in to Windows (now windows 10) as that same domain user with local administrative privileges I get the following error come up "Wizard Error: You must be running with Administrator rights. The deployment cannot Proceed."

I have tried disabling the Install Applications task as I am not using it at this point. I have also tried adding specific credentials for the tattoo task however to no avail. Each time I still get the error message. I have double check that my user is still part of the local administrator group on the machine, which he is so I'm unclear of what exactly is going wrong.

As you can see I don't have anything crazy setup in my task sequence:



Here is what I have setup in my customsettings.ini:

[Settings]
Priority=Default

[Default]
_SMSTSORGNAME=<CompanyName>
OSInstall=Y
SkipWizard=YES
SkipCapture=YES
SkipAdminPassword=YES
SkipApplications=YES
SkipProductKey=YES
SkipComputerBackup=YES
SkipBitLocker=YES
SkipBDDWelcome=YES
SkipTaskSequence=YES
TaskSequenceID=WIN10-X64-UPG
SkipSummary=YES
SkipFinalSummary=YES

And in Bootstrap.ini:

[Settings]
Priority=Default

[Default]
DeployRoot=\\<Server>\DeploymentShare$

UserID=MDT_BA
USerDomain=<MyDomain>
UserPassword=<MDT_BAPassword>

**Removed some identifying information

I'm trying to make this pretty much automated for the end user to just run LiteTouch.vbs and MDT do the rest however I must be missing something simple. Please help!


FAILURE ( 7706 ): ERROR! Drive D: was not found!

$
0
0

I was wondering if anybody run into this issue and could point me in the right direction.

I have been using MDT for over 4 years and last week was the first time that I have ever seen this "FAILURE ( 7706 ): ERROR! Drive D: was not found!" message. I'm running a MDT 2013 deployment server with AIK 8.1 and this error occured while imaging a Surface Pro 3.

We successfully imaged about  +10 Surface's with this MDT build however they all had 128GB SSD's and and 4GB of RAM this one that failed has a 256GB SSD and 8GB of RAM and the issue was replicated on another Surface with the exact same specs.

So far I have;

1) Tried another Surface Pro 3 of the same SKU and it had the exact same issue.

2) Successfully imaged this Surface with Windows 10 and with the Windows 8.1 Pro Surface Pro 3 recover image from Microsoft using USB media.

3) Updated my deployment share to MDT 2013 Update 1 and AIK 10 and tried both the original MDT 2013 standard deployment Task Sequence and the updated MDT 2013 standard deployment Task Sequence both modified for Surface Pro 3 (Driver Firmware, patches etc...)

4) Updated the Surface Pro 3 driver set with the very latest drivers but I noticed that even the latest drivers still uses the Intel ahci 8 driver from 2013 that the worked fine on the other 128GB SSD 4GB RAM Surface Pro 3 SKU's that we imaged before.

When looking at the BDD.log I can see that SSD drive is successfully cleared of any existing partition but it fails to create any partitions and after it fails in WinPE if you manually run Diskpart no drives seems to be available even though driver for the storage controller should still be loaded.

I have done a lot of research and I have found similar issues but none of the solution suggested has solved this issue and I'm running out of things to try.

Thanks in advanced.

Setting IE search provider from Unattend.xml

$
0
0
Deploying Windows 10 with IE11 via SCCM with MDT 2013. I read somewhere that it is possible to set Google rather than Bing as the default search provider by making changes to Unattend.xml - can this still be done with Windows 10?. I'd like also to set Edge homepage and search Engine - at present there are no policies to do this so again if could be done via unattend.xml would be good

Ian Burnell, London (UK)

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.

MOve the task to bind to active directory until all other tasks are complete

$
0
0

Hello

I the above possible?

We have our task sequence to bind to active directory, but i can see this binds way before all other install applications task start.

What is the task in the task sequence to move this to the end, if possible ?

Thanks

Where is the task sequence saved in offline media (file and path)

$
0
0

If I only change the task sequence (for example changing a value for a variable).

Which file should I copy over to my USB drive after updating the offline media?


Can not find C:\LTIBootstrap.vbs after a capture

$
0
0

Hi,

about this limitation mentioned here: http://blogs.technet.com/b/msdeployment/archive/2015/08/25/mdt-2013-update-1-release-notes-and-known-issues.aspx

LTI: Cleanup is not complete after image capture

After capturing an image and rebooting back to the drive, autologon is still configured and an error will appear about LTIBootstrap is not found. This is a minor, non-fatal error that does not affect the captured image.

Workaround: Script changes are possible but difficult and challenging, especially given the minor severity of the issue.

I did some tests and it seems due to the unattend.xml passed as parameter to sysprep command; this file contains the enablement of AutoLogon for the administrator account when machine reboots after the capture process and automatically reconfigures it; if I disable it, the popur error will disappear.

I still ignore why the same unattend.xml file, with AutoLogon enabled, does not raise the popup error if executed on a pure MDT 2013 environment (so two years old). Any clue about the root cause?

Thanks

MDT 2013 Update 2013 Build 8298 - Sysprep "disconnects" NIC

$
0
0

Hello Guys

We have upgraded our MDT 2013 to Update 1 build 8298.

And we have quite a few issues that we didn't have before.

We have some pretty simple task sequences we use to build images, one for each OS. Currently
Windows 7x64, Windows 8.1x64 and Windows 10x64. Each os has a separate virtual machine in our VMware environment. We don't capture the image in MDT since our deployment system requires and older WinPE to run (Capasystems.com).

I pick the Syspreb task so it does what needs to be done at the end of the build. Shutdown the machine when it's done, pxe boot into capa and then proceed to capture the image.

This is pretty basic and has worked in the past.

After the upgrade I boot from the litetouch ISO like we normally do and using a VMxnet3 driver make the connection to the share and this runs smoothly all the way to the sysprep part. 

When the machine is done syspreping it completely "drops all network connections" and the build "fails". 

I'm having a hard time figuring out why this happens - Any ideas?


Tried with different drivers, old and new. Even tried running it on hyper-v but it yields the same results. Every task sequence was built from scratch since the format part was changed.


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.

Failure (5627) 50: Run DISM.exe

$
0
0

Whenever I try to deploy Windows 10 from my MDT 2013 Update 1 server, I get this series of errors during "Installing Operating System." I couldn't find any issues in BDD.log. 

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

Any idea how to get past this? I checked and it looks like it's partitioning everything correctly. 


Below is the smsts.log

Expand a string: WinPEandFullOS	TSManager	9/24/2015 11:55:17 AM	1536 (0x0600)
Executing command line: cscript.exe "%SCRIPTROOT%\LTIApply.wsf"	TSManager	9/24/2015 11:55:17 AM	1536 (0x0600)
Process completed with exit code 5627	TSManager	9/24/2015 12:00:04 PM	1536 (0x0600)
!--------------------------------------------------------------------------------------------!	TSManager	9/24/2015 12:00:04 PM	1536 (0x0600)
Failed to run the action: Install Operating System.
Unknown error (Error: 000015FB; Source: Unknown)	TSManager	9/24/2015 12:00:04 PM	1536 (0x0600)
Sending status message . . .	TSManager	9/24/2015 12:00:04 PM	1536 (0x0600)
Executing in non SMS standalone mode. Ignoring send a task execution status message request	TSManager	9/24/2015 12:00:04 PM	1536 (0x0600)
Set a global environment variable _SMSTSLastActionRetCode=5627	TSManager	9/24/2015 12:00:04 PM	1536 (0x0600)
Set a global environment variable _SMSTSLastActionSucceeded=false	TSManager	9/24/2015 12:00:04 PM	1536 (0x0600)
Clear local default environment	TSManager	9/24/2015 12:00:04 PM	1536 (0x0600)
Let the parent group (Install) decides whether to continue execution	TSManager	9/24/2015 12:00:04 PM	1536 (0x0600)
The execution of the group (Install) has failed and the execution has been aborted. An action failed.
Operation aborted (Error: 80004004; Source: Windows)	TSManager	9/24/2015 12:00:04 PM	1536 (0x0600)
Failed to run the last action: Install Operating System. Execution of task sequence failed.
Unknown error (Error: 000015FB; Source: Unknown)	TSManager	9/24/2015 12:00:04 PM	1536 (0x0600)
Sending status message . . .	TSManager	9/24/2015 12:00:04 PM	1536 (0x0600)
Executing in non SMS standalone mode. Ignoring send a task execution status message request	TSManager	9/24/2015 12:00:04 PM	1536 (0x0600)
Execution::enExecutionFail != m_eExecutionResult, HRESULT=80004005 (e:\nts_sms_fre\sms\client\tasksequence\tsmanager\tsmanager.cpp,767)	TSManager	9/24/2015 12:00:04 PM	1536 (0x0600)
Task Sequence Engine failed! Code: enExecutionFail	TSManager	9/24/2015 12:00:04 PM	1536 (0x0600)
****************************************************************************	TSManager	9/24/2015 12:00:04 PM	1536 (0x0600)
Task sequence execution failed with error code 80004005	TSManager	9/24/2015 12:00:04 PM	1536 (0x0600)
Cleaning Up. Removing Authenticator	TSManager	9/24/2015 12:00:04 PM	1536 (0x0600)
Cleaning up task sequence folder	TSManager	9/24/2015 12:00:04 PM	1536 (0x0600)


Driver Selection Profile Not Working

$
0
0

We are using selection profiles for our imaging. We are using Johan's Added Predictability and has been working great. We used DISM to perform a windows offline update and created a new task sequence for the updated .wim file. Now we find the drivers, especially the video, are not being installed. Can anyone provide any guidance as to why this would occur when the only thing that changed was updating windows?

Any assistance is appreciated.


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?  

Force windows to install on C-drive

$
0
0

hi,

I can't succeed in deploying windows 7 to the C-drive.

Can someone please advice how to be able to install windows to the C-drive?

I'am using the following config:

OS:Windows 7

MDT version: MDT 2013 Update 1

Image: install.wim from original ISO source

I have added the variable OSDPreserveDriveLetter=False right before the step "Install Operating System"

The "Install Operating System" step has the following option: location: Specific Logical Drive Letter - Drive Letter: C:

The format and partition Disk step (both Bios and UEFI) are unchanged.

The device I'm deploying to is an UEFI device.

Many Thanks in advance


MDT 2013 capture image and windows updates

$
0
0

Hello,

I am trying to capture an image .wim using MDT 2013 and get all windows updates and then import the .wim into SCCM 2012 R2 SP1 for later deployment. WSUS is installed as well. My question is: How can I get the Windows Updates in the MDT capture process? I have tried deploying windows updates to the "unknown computers" collection but the updates log says there are no updates available and none get installed. I have read in some forums that I might need to enable automatic approval in WSUS but I have also read that you are not supposed to configure anything in WSUS and use SCCM for configuration.

Please help.

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


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 2012 / Windows 7 SP1 / ZTIWIndowsUpdates.wsf SVCHOST.EXE 2 Hour Delay

$
0
0
Hi Guys,


i have a strange problem while image creation in MDT 2012.
We start from scratch (Windows 7 Professional with SP1 X64 and X86 ISO). Boot up two VM's in VSPHERE with 4GB RAM.
Then using the WindowsUpdate.wsf to poll internal WSUS-Server.
The Machines are stressed my svchost.exe for like 90-120 minutes before the Download and Installation Progress begin.
Machines are connected with 10GBIT/s.

The problem happends here:

2015-09-25      12:20:38:522       808      a0c      Handler      Using CBS interface ICbsSession7
2015-09-25      12:20:38:584       808      a0c      Handler      Using CBS interface ICbsSession7
2015-09-25      12:20:40:097       808      a0c      PT      +++++++++++  PT: Synchronizing extended update info  +++++++++++
2015-09-25      12:20:40:097       808      a0c      PT        + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7},

line removed
2015-09-25      12:33:55:745      2108      b4c      Misc      ===========  Logging initialized (build: 7.6.7601.18847, tz: +0200)  ===========
2015-09-25      12:33:55:745      2108      b4c      Misc        = Process: c:\program files\windows defender\MpCmdRun.exe
2015-09-25      12:33:55:745      2108      b4c      Misc        = Module: C:\Windows\system32\wuapi.dll
2015-09-25      12:33:55:745      2108      b4c      COMAPI      Registered OnCompleted callback in GIT, cookie=256
2015-09-25      12:33:55:761      2108      b4c      COMAPI      -------------
2015-09-25      12:33:55:761      2108      b4c      COMAPI      -- START --  COMAPI: Search [ClientId = Windows Defender]
2015-09-25      12:33:55:761      2108      b4c      COMAPI      ---------
2015-09-25      12:33:55:761      2108      b4c      COMAPI      <<-- SUBMITTED -- COMAPI: Search [ClientId = Windows Defender]
2015-09-25      14:03:05:400       808      a0c      Agent      Update {A9134E4A-3B6F-4633-AA8F-9520F188FBF8}.101 is pruned out due to potential supersedence


See the Full Log here:

REMOVED.. NO LINKS ALLOWED FOR ME...


We already updated to latest Windows Update Client und patched WSUS-Server ...

The WSUS-Report is generated at 14:04:00

There are about 300 Updates to install...


Any Suggestions? I have no idea what to do further.


Thanks

MDT cannot install network drivers

$
0
0

When MDT trys to connect Share,it gives a error "The  PCI\VEN_8086&DEV_15A3&SUBSYS_222717AA&REV_03 is not installed".

But I have imported the driver into MDT,and in the drivers.xml its name is "PCI\VEN_8086&DEV_15A3$SUBSYS_222717AA"

So what's the problem? 





Viewing all 11297 articles
Browse latest View live


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