Deploying Apps in MDT 2013

I am trying to deploy apps using MDT 2013 on clients machines but keep getting the
following bdd.log error. Please note I can image,
deploy drivers and packages in MDT with no issues except when I
try to deploy apps:
I have added all the applications in their
individual folder in MDT, then i created a task sequence to install
application. Each app gets their own "install application" command. Then on the client machine i run the following cmd with
elevated privillege: cscript.exe
\\ORS-WDS\DeploymentShare\Scripts\LiteTouch.WSF. The script runs after selecting the task but then disappeared and i get this bdd.log on the client:
https://onedrive.live.com/redir?resid=8D6242F28512FDE3!564&authkey=!AFojuxXjHaKXl0I&ithint=file%2ctxt

These are not the correct bdd.log files. Make sure you include the right ones. Also check the c:\windows\temp\... folder.
From the error above:
C:\windows\system32>err 0x8007051B
# as an HRESULT: Severity: FAILURE (1), Facility: 0x7, Code 0x51b
# for hex 0x51b / decimal 1307 :
ecNotRitpMaster ec.h
ERROR_INVALID_OWNER winerror.h
# This security ID may not be assigned as the owner of this
# object.
# 2 matches found for "0x8007051B"
This would suggest that you are still having permission/elevation problems.
Keith Garner - Principal Consultant [owner] -
http://DeploymentLive.com

Similar Messages

Error at the time of deploying App for SP 2013

When I try to deploy any App created using VS 2012, giving error below. Please provide some help to resolve it.
Build started: Project: FleetManagementApp, Configuration: Debug Any CPU ------
------ Deploy started: Project: FleetManagementApp, Configuration: Debug Any CPU ------
Active Deployment Configuration: Deploy App for SharePoint
Skipping deployment step because a pre-deployment command is not specified.
Skipping the uninstall step because the app for SharePoint is not installed on the server.
Install app for SharePoint:
Uploading the app for SharePoint...
Error occurred in deployment step 'Install app for SharePoint': We're sorry, we weren't able to complete the operation, please try again in a few minutes.
If you see this message repeatedly, contact your administrator.
========== Build: 1 succeeded or up-to-date, 0 failed, 0 skipped ==========
========== Deploy: 0 succeeded, 1 failed, 0 skipped ==========

Hi,
Please check the link below, it about the simialr issue.
https://social.msdn.microsoft.com/Forums/vstudio/en-US/c8eb6c92-e1b2-45a9-840e-c782bdc933ec/error-occurred-in-deployment-step-install-app-for-sharepoint-were-sorry-we-werent-able-to?forum=sharepointdevelopment
Best Regards
Dennis Guo
TechNet Community Support

Using MDT 2013 for deploying Software from MDT Server to PC Client automatically and silently ?

I have a trouble about deploying software from MDT 2013 server to PC Client , Can we using MDT 2013 for deploying software automatically and silently , that Users/Clients don't have to click "next,next" to install software ?
If you have a solutions to deploying it , please share me about that solutions ?
Thanks.

you can make software silently with boot opción:
with chocolatey opensource.
or make software with switches
here link to help you:
http://blogs.itpro.es/octaviordz/2014/05/29/instalando-aplicaciones-con-chocolatey
http://blogs.itpro.es/octaviordz/2014/06/05/integrando-chocolatey-a-mdt-2013-e-instalando-aplicaciones-de-forma-desatendida-en-windows-8-1/
http://blogs.itpro.es/octaviordz/2014/10/31/probando-chocolatey-en-windows-10
http://blogs.itpro.es/octaviordz/2012/07/10/aplicaciones-desatendidas
MVP Jesús Octavio Rdz http://blogs.itpro.es/octaviordz

Upgraded to MDT 2013 - old deployments not working - parse error - copyprofile error

I upgraded from MDT 2012 U1 and Waik to MDT 2013 and ADK 8.1. My windows 7 deployments quit working after the upgrade. I installed ADK 8.1 and upgraded 2012 to 2013 then upgraded the deployment share. Since the upgrade I am getting copyprofile errors
when MDT is trying to sysprep the machine then I am in a reboot loop. Not sure what changed. The error is "windows could not
parse or process the unattend answer file for pass [specialize]. The settings specified in the answer file
cannot be applied." In the setup log files it says the copyprofile could not be done. The deployments all worked before the upgrade. Any ideas? Thanks.

Thanks for your reply. My DISM file doesnt tell me anything. It is not at the location after the system reboots. The exact message I get is
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.
I get this message from all of my windows 7 images when trying to apply them. These were okay until I updated the deployment share for MDT 2013. Under the shell setup in the unattend.xml I have
BluetoothTaskbarIconEnabled (blank)
ComputerName (blank)
CopyProfile True
DisableAutoDaylightTime false
DoNotCleanTaskBar True
ProductKey (blank)
RegisteredOrganization CompanyName
RegisterOwner CompanyUser
ShowWindowsLive false
StartPanelOff (blank)
TimeZone Central Standard Time
Something in the unattend.xml that 2013 doesnt like perhaps?
Thanks..

MDT 2013, Deploying Windows 8.1 on Surface and Dell Venue Tablets

I'm having numerous issues with Capturing Images and Deploying to Windows 8.1 Tablets. We are currently using Surface Pro 1, 2, and Dell Venue 11 Pro tablets. I am using a Windows Server 2012 computer with MDT 2013 installed. I can't get the tablets
to:
1-sysprep and capture using MDT 2013
2-Deploy a Task Sequence with a WIM and other applications attached. (I've tried using the simple standard task seq option with no luck)
3-I found another way to get a WIM (using imagex) but when i deploy task sequence it ignores my selection of applications to install outside the WIM and only installs the WIM (WIM 14gb = Win 8.1 Ent, Office 2013 x32, MS Updates)
Any help would be greatly appreciated. Everything is being performed within the LAN and with USB 2.0 thumbdrives for media.

Hi altimav8,
Are you trying to find out how to deploy Surface Pro method? Before capture the Surface pro image please download the latest drivers for the surface and made sure that they
were the only drivers that were going to be deployed. There have a specific MDT deploy support forum more about the MDT deploy related issue you can ask in MDT support forum.
MDT support
forum:
https://social.technet.microsoft.com/Forums/en-US/home?forum=mdt
The related guide:
Surface Pro - Enterprise Deployment Quick Start Guide
http://download.microsoft.com/download/2/0/7/2073C22F-2F31-4F4A-8059-E54C91C564A9/Surface%20Pro%20-%20Enterprise%20Deployment%20Quick%20Start%20Guide.pdf
Thanks for your understanding and support
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

MDT 2013 - A Connection to the deployment share could not be made - DHCP Lease was not obtained

First, let me give you some context:
Framework: MDT 2013 with MS SDK 7.1
Task Sequence: Standard Client TS with sysprep and capture.
Target workstation (build workstation): VM Guest on ESX 5.5 host, 8 vCPU, 8GB RAM, LSI Logic SAS Controller, E1000 NIC, SSD DAS
Behavior: The VM loads and installs the OS fine in PE, VM boots into OS successfully and resumes the TS, after the first system reboot, the error message occurs and it reads:
A connection to the deployment share (\\*********\DeploymentShare$) could not be made. DHCP Lease was not obtained for any Networking device! Possible Cause: Check physical connection. Retry:...... Cancel:.....
While observing this error, I didn't notice the NIC hadn't completely initialized and obtained an IP yet (network adapter icon in systray), additionally hitting retry after the NIC was initialized resumed the TS.
This behavior reoccurs with several subsequent reboots until a few more applications (Citrix Receiver, VMware Tools) with services are installed which seem to then slow the system boot-up time and then allows the TS to start after the NIC has initialized.
From several posts I've read on this forum, this particular behavior was alleviated by a "wait for IP lease" mechanism built into the TS engine which was introduced in MDT 2010 SP1, I wasn't able to find any other confirmation whether
this mechanism is still in effect with MDT 2013. Another point worth mentioning from several other posts I was able to find is that this behavior appears to manifested itself on target workstations with SSDs, which would somewhat explain the faster
TS load time vs waiting for an IP lease. I've also tried to replicate this behavior in a non-SSD and low-performance VM environment and I wasn't able to replicate it.
My question: Does anyone else have experienced this behavior with MDT 2013 and if so, how did you resolve it? Or is this a bug?

I have this issue intermittently as well. For us, it coincided with the deployment of IP phones, which meant PoE switches all around. However, the problem persisted even after we turned off PoE to the ethernet ports from which we normally PXE
boot.
As this issue has been intermittent, I've backburnered it. When it does happen, I just wait for the lease to arrive then rerun the wizard.
Thanks for the feedback, that's true the TS can be resumed manually once the lease has occured but it defeats the purpose of an automated TS if I have to keep an eye on it and intervene if I need to.
The network guys here recommended putting wireshark or network monitor on it and figuring out just what the heck is going on. Basically, what Keith Garner said. They also disabled PortFast awhile back to see if that made any difference, and it did
not.

MDT 2013 deploying OS from USB Flashdrive failed - need to click OK everytime

We are using MDT 2013 with ADK 8.1 and deploying Windows 7 x64 using media (USB Flashdrive). We can successfully deploy Windows 7 x64b using ethernet cabel but not via USB-Flashdrive. This problem appears on all our HP EliteBook
Series, old as new computers series. We can boot into WinPE 64 bit and start the proper task sequence, all image is applied then after restart, after the logon screen appears there is an error saying that cannot find "USB media?".
But after clicking "OK" it works fine until next reboot, same thing again, but the drive is recognized!
I downloaded all USB drivers from HP website that holds USB 2.0 and 3.0 and drivers that contains open driver files like .inf and .dll files and injected them with the "Profile" that contains all drivers and packages.
It seems like it needs a timeout because of the script is trying to early to find the USB-flashdrive.
Any ideas?
Sorry for language, but you get the Point.
Best regards

Hi,
I would like you to clarify following questions with me:
1. Did you keep the USB plugged in during the restarting?
2. Have you make any task sequence to install applications after log in? If so, have them been installed properly?
Then, please help to collect a boot trace to let me know the details:
How to collect a good boot trace on Windows 7
http://blogs.technet.com/b/jeff_stokes/archive/2012/09/17/how-to-collect-a-good-boot-trace-on-windows-7.aspx
Please upload them to a file sharing service like Onedrive or "Rapidshare" and put a link to them in your reply.
Kate Li
TechNet Community Support

Deploy UDI Windows 10 with SCCM 2012 R2 and MDT 2013 Update 1

Hi,
Trying use "User-Driven Installation" with
SCCM 2012
R2 CU4 and MDT
2013 Update 1 for deploy Windows
10.
Created MDT Task Sequences with
template "Client Task sequence"
and Deployment Method "User-Driven Installation".
When I try to deploy I have error like:
Failed to run the last action: Error in the task sequence. Execution of task sequence failed.
The operation cannot be completed because other resources are dependent on this resource. (Error: 00001389; Source: Windows)
ZTI deployment failed, Return Code = 5001 InstallSoftware 22.04.2015 11:36:57 1740 (0x06CC)
Unable to create WebService class InstallSoftware 22.04.2015 11:36:57 1740 (0x06CC)
Command line returned 5001 InstallSoftware 22.04.2015 11:36:57 1740 (0x06CC)
Process completed with exit code 5001 TSManager 22.04.2015 11:36:57 1160 (0x0488)
Part smsts.log
!--------------------------------------------------------------------------------------------! TSManager 22.04.2015 11:36:57 1160 (0x0488)
Expand a string: WinPEandFullOS TSManager 22.04.2015 11:36:57 1160 (0x0488)
Executing command line: smsswd.exe /run: cscript "%deployroot%\scripts\ztierrormsg.wsf" TSManager 22.04.2015 11:36:57 1160 (0x0488)
[ smsswd.exe ] InstallSoftware 22.04.2015 11:36:57 1740 (0x06CC)
PackageID = '' InstallSoftware 22.04.2015 11:36:57 1740 (0x06CC)
BaseVar = '', ContinueOnError='' InstallSoftware 22.04.2015 11:36:57 1740 (0x06CC)
ProgramName = 'cscript "C:\_SMSTaskSequence\WDPackage\scripts\ztierrormsg.wsf"' InstallSoftware 22.04.2015 11:36:57 1740 (0x06CC)
SwdAction = '0001' InstallSoftware 22.04.2015 11:36:57 1740 (0x06CC)
Set command line: Run command line InstallSoftware 22.04.2015 11:36:57 1740 (0x06CC)
Working dir 'not set' InstallSoftware 22.04.2015 11:36:57 1740 (0x06CC)
Executing command line: Run command line InstallSoftware 22.04.2015 11:36:57 1740 (0x06CC)
Process completed with exit code 5001 InstallSoftware 22.04.2015 11:36:57 1740 (0x06CC)
Microsoft (R) Windows Script Host Version 5.12 InstallSoftware 22.04.2015 11:36:57 1740 (0x06CC)
Copyright (C) Microsoft Corporation. All rights reserved. InstallSoftware 22.04.2015 11:36:57 1740 (0x06CC)
InstallSoftware 22.04.2015 11:36:57 1740 (0x06CC)
Microsoft Deployment Toolkit version: 6.3.8216.1000 InstallSoftware 22.04.2015 11:36:57 1740 (0x06CC)
The task sequencer log is located at X:\WINDOWS\TEMP\SMSTSLog\SMSTS.LOG. For task sequence failures, please consult this log. InstallSoftware 22.04.2015 11:36:57 1740 (0x06CC)
ZTI deployment failed, Return Code = 5001 InstallSoftware 22.04.2015 11:36:57 1740 (0x06CC)
Unable to create WebService class InstallSoftware 22.04.2015 11:36:57 1740 (0x06CC)
Command line returned 5001 InstallSoftware 22.04.2015 11:36:57 1740 (0x06CC)
Process completed with exit code 5001 TSManager 22.04.2015 11:36:57 1160 (0x0488)
!--------------------------------------------------------------------------------------------! TSManager 22.04.2015 11:36:57 1160 (0x0488)
Failed to run the action: Error in the task sequence.
The operation cannot be completed because other resources are dependent on this resource. (Error: 00001389; Source: Windows) TSManager 22.04.2015 11:36:57 1160 (0x0488)
MP server http://sccm.domain.com. Ports 80,443. CRL=false. TSManager 22.04.2015 11:36:57 1160 (0x0488)
Setting authenticator TSManager 22.04.2015 11:36:57 1160 (0x0488)
Set authenticator in transport TSManager 22.04.2015 11:36:57 1160 (0x0488)
Sending StatusMessage TSManager 22.04.2015 11:36:57 1160 (0x0488)
Setting message signatures. TSManager 22.04.2015 11:36:57 1160 (0x0488)
Setting the authenticator. TSManager 22.04.2015 11:36:57 1160 (0x0488)
CLibSMSMessageWinHttpTransport::Send: URL: sccm.domain.com:80 CCM_POST /ccm_system/request TSManager 22.04.2015 11:36:57 1160 (0x0488)
Request was successful. TSManager 22.04.2015 11:36:57 1160 (0x0488)
Set a global environment variable _SMSTSLastActionRetCode=5001 TSManager 22.04.2015 11:36:57 1160 (0x0488)
Set a global environment variable _SMSTSLastActionSucceeded=false TSManager 22.04.2015 11:36:57 1160 (0x0488)
Clear local default environment TSManager 22.04.2015 11:36:57 1160 (0x0488)
Let the parent group (Gather Logs and StateStore on Failure) decides whether to continue execution TSManager 22.04.2015 11:36:57 1160 (0x0488)
The execution of the group (Gather Logs and StateStore on Failure) has failed and the execution has been aborted. An action failed.
Operation aborted (Error: 80004004; Source: Windows) TSManager 22.04.2015 11:36:57 1160 (0x0488)
Failed to run the last action: Error in the task sequence. Execution of task sequence failed.
The operation cannot be completed because other resources are dependent on this resource. (Error: 00001389; Source: Windows) TSManager 22.04.2015 11:36:57 1160 (0x0488)
MP server http://sccm.domain.com. Ports 80,443. CRL=false. TSManager 22.04.2015 11:36:57 1160 (0x0488)
Setting authenticator TSManager 22.04.2015 11:36:57 1160 (0x0488)
Set authenticator in transport TSManager 22.04.2015 11:36:57 1160 (0x0488)
Sending StatusMessage TSManager 22.04.2015 11:36:57 1160 (0x0488)
Setting message signatures. TSManager 22.04.2015 11:36:57 1160 (0x0488)
Setting the authenticator. TSManager 22.04.2015 11:36:57 1160 (0x0488)
CLibSMSMessageWinHttpTransport::Send: URL: sccm.domain.com:80 CCM_POST /ccm_system/request TSManager 22.04.2015 11:36:57 1160 (0x0488)
Request was successful. TSManager 22.04.2015 11:36:57 1160 (0x0488)
Executing command line: X:\WINDOWS\system32\cmd.exe /k TSBootShell 22.04.2015 11:37:31 696 (0x02B8)
The command completed successfully. TSBootShell 22.04.2015 11:37:31 696 (0x02B8)
Successfully launched command shell. TSBootShell 22.04.2015 11:37:31 696 (0x02B8)

MDT Updates for Windows 10 Technical Preview Build 10041
Если Вам помог чей-либо ответ, пожалуйста, не забывайте жать на кнопку "Предложить как ответ" или "Пометить как ответ".
http://zalozny.com.ua

Deploy Office 365 Pro Plus using MDT 2013

Hello,
I'm currently evaluating O365 E3 and am specifically looking into what my options are for deploying Office 2013 Pro Plus when rolling out a new PC image. Currently I use MDT 2013 to deploy the image to new PCs and install Office 2010 along with other
applications. Can I use C2R with a config file pointing to a local repository of the installation files with MDT 2013?

Hi
This blog post by Rens will help you:
http://renshollanders.nl/2014/02/office-365-automatic-deployment-of-office-365-with-mdt/

Error when deploying LiteTouch image using MDT 2013 Media Flashdrive

Please help! I have created a media flash drive (drive capacity: 64Gb) to deploy LiteTouch x86 and x64 images (Win7 and Win8, 8.1) to PCs but getting error for the 3rd time. I am using the following tools in my environment: i am using MDT 2013 on a Windows
2k8 WDS server. PXE boot works fine deploying images but i keep getting this error after creating the Media flash drive). I first got the same failure with 14 errors but recreated the media on the WorkBench using a different selection profile but now i am
getting this error: (by the way where is the BDD.LOG?)
"Deployment Summary
During the deployment process, 8 errors and 0 warnings were reported.
Details...
Failure ( 5456): Unable to determine destination disk, partition, and/or drive. See BDD.LOG for more information.
Litetouch deployment failed, return code = -2147467259 0x80004005
Failed to run the action: inject drivers.
Unknown error (error: 00001550; source: unknown)
The execution of the group (preinstall) has failed and the execution has been aborted. An acton failed.
Operation aborted (error: 80004004; xource: 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

I am planning to build a WDS with Win2k12 and MDT2013 and perhaps will be lucky to create a successful media. I created one with my WDS Win2k8 it works on a HP laptop but failed on other machines like Dell...
Did you get driver injection in configuration WDS and MDT?
Considering if the incompatible drivers cause your issue.
If you can post back the MDT log during the deployment on DELL computers, it would be helpful for us to determine your issue.
Kate Li
TechNet Community Support

Deploy Embedded features of WE81IP using MDT 2013

I would like to deploy Windows Embedded 8.1 Industry Pro and configure the embedded features using MDT 2013 as described in this Windows Embedded
blog post. I've imported the WE81IP image and created a task sequence but the Install Embedded Features tasks are not available. What do I need to do to make those tasks show up as shown in this image?
Software Hardware Systems

I would recommended using Windows System Image Manager (SIM) instead. When you import the WIM file into SIM, you get access to the Embedded Features.
My book has the details: http://www.annabooks.com/Book_SGSIM.html
www.annabooks.com / www.seanliming.com / Book Author - Pro Guide to WE8S, Pro Guide to WES 7, Pro Guide to POS for .NET

Keep extra partition on deployment with MDT 2013

hello all,
I am using MDT 2013 to make the
deployment of some workstations in the company,
however they all have an extra
partition (D: \),
doing some testing I noticed that the
MDT does clean the entire
disk, not just on the C:\ drive.
Is it possible to get the MDT format
just drive the system keeping
the extra drive (D:\)?
Thank you.
Eduardo Sena | Microsoft Certified Professional | Embaixador Windows 8 | MVP Windows-Expert IT Pro | [email protected] Blog - www.eduardosena.com.br

if you are just replacing the OS, then I recommend the "Refresh" scenario. Refresh will take an existing Machine and refresh it to a new OS version, persisting the existing partition configuration.
Keith Garner - Principal Consultant [owner] -
http://DeploymentLive.com

Dart tool not added in MDT 2013 deployment workbench

Hi, I have MDT 2013 installed, copied tools.cab for Dart 6.5 in the C:\Program Files\Microsoft Deployment Toolkit\Templates\Distribution\Tools\x86 and C:\Program Files\Microsoft Deployment Toolkit\Templates\Distribution\Tools\x64 folders. x86 version
can in x86 folder and x64 in x64 folder. However, I don't see dart tools in the WINPE Features packs in the deployment share properties. I need to deploy Windows 7. Can someone suggest what is wrong? I have tried copying the dart tools.cab files for dart 6.5
7.0 and 8.1 without success.

Finally i fixed it. I created a new deployment share and the dart components appeared in winpe feature packs list but still they did not the appear in already existing old deployment share properties. I check the folders tools\x86 folder and there was
no tools.cab even though i copied the cabs under C:\Program Files\Microsoft Deployment Toolkit\Templates\Distribution\Tools\x64
folders. So for some reason mdt was not copying the tools.cab into existing deployment share. I am not sure this is by default or issue with my environment. Anyways, i copied the relevent tools.cab in tools\x64 and tool\x86 folders of existing deployment
share and not am able to see the dart tools in winpe feature packs.

MDT 2013 deploying images

Hello,
I am having issues with finishing the deployment of my image. Okay, so I downloaded all the drivers and I placed them in the out-of-box drivers in MDT 2013. I updated the deployment share and then I went to WDS and added the new .WIM file with the additional
drivers. I am able to image the computer, but when the computer boots up for me to activate Windows, I skip that because it cannot find the driver.
What am I doing wrong?

See in your device manager if all drivers are installed. If this is not the case, retrieve the missing driver from looking at the hardware id from the device, and match it against the
pcidatabase.com this should reveal which drivers you are missing.
Import the driver and you are good to go. By the way, updating your deployment share and regenerating your boot images is only necessary when you have modified your bootstrap.ini or have new drivers that need to be embedded in your boot image.
Cheers!
If this post is helpful please click "Mark for answer", thanks! Kind regards

Synaptics Pointting device Driver installs on an Desktop machine while deploying Windows 7X64 using MDT 2013 Update 1

I am deploying Windows 7X64 on Dell OptiPlex 990 and other desktops. Deployment goes fine but the Synaptics pointing device driver gets installed after the deployment is complete. Also after applying operating system I get a prompt to Run the Synaptics Pointing
Driver setup twice. If I don't click yes to install the TS wont proceed. Its gets worse when I uninstall the Synaptics Device Driver from Appwiz.Cpl and reboot the machine the Keyboard fails with the error Code:29. Above is the screenshot of what I get after
Applying Operating System step. Thanks in Advance.

I have also encountered this in MDT 2013 Lite Touch deployments for Windows 8.1 and I am researching it.
I noted that the Synaptics driver was installed for "SmBus" in Device Manager for a motherboard with an Intel 7 Cxxx Series chipset (Dell Optiplex desktop). The HardwareID's are all PCI\VEN8086...
We use %Model% in our task sequence and have a folder for each model such as "Optiplex 7010" in Out-of-Box Drivers.

Deploying Apps in MDT 2013

Similar Messages

Maybe you are looking for