MDT 2013 - Install Application in Task Sequence Stuck

I am running an application installation within my task sequence during my deployment. One of the applications prompts a user response to click yes to continue. Otherwise the task is stuck at that step. It appears to be stuck during my Java 7U51
installation running this command. It works on several machines but I get this once in a while on a few workstations when trying to deploy. any ideas?
About to run command: \\xxxxxxxxxxxxxxxxxxx\xxxxxxxxxx\Tools\X64\bddrun.exe jre-7u51-windows-i586.exe /s /v"/norestart /AUTOUPDATE=0 JAVAUPDATE=0 JU=O"

first try to install java with
MDT if any one you are using and then
run the programyou want to post an example
here
http://mdtguy.wordpress.com/2014/02/17/installing-the-latest-java-re-msi-with-mdt-2013/
Freelance-IT http://www.freelance-it.com.mx

Similar Messages

MDT 2013: Wizard Pages by Task Sequence

Hi,
I believe what I am trying to do is not possible from previous readings on this forum, BUT then I see something in my MDT 2013 OSD wizard that seems to indicate there might be a way to get it done. So here goes.
For my own demos, I am trying to develop a deployment share that is much like Johan Arwidmark's hydration kit. Some machines, like a domain controller or a SQL cluster are all well-defined: computer names, IP addresses, etc. are fixed and can be set
in customsettings.ini or in the Task Sequence with variables. However, I would also like the ability to have to deploy a "generic" machine where I can select roles, applications, etc.
This would require having different wizard pages shown for different task sequences. From what I've read, this may not be possible without developing a custom wizard (and that might be too much effort). However, I currently have two task sequences and depending
on which one I select, I see a different number of steps to complete? See screenshots. I don't know what I have currently configured that makes it like that.
(when I select "Domain Controller 01" task sequence) (Task sequence ID "DC01")
(when I select the "generic" task sequence)
Below is my customsettings.ini [the only rules file I have].
[Settings]
Priority=TaskSequence,Default
[Default]
_SMSTSORGNAME=Demo Deployment
OSInstall=Y
SkipCapture=YES
SkipAdminPassword=YES
AdminPassword=P@ssw0rd!
SkipProductKey=YES
SkipComputerBackup=YES
SkipBitLocker=YES
EventService=http://192.168.232.1:9800
SkipUserData=YES
SkipTaskSequence=NO
SkipTimeZone=YES
SkipBitLocker=YES
SkipSummary=YES
SkipFinalSummary=NO
FinishAction=SHUTDOWN
SkipLocaleSelection=YES
HideShell=YES
[DC01]
_SMSTSORGNAME=DC01 Deployment
SkipComputerName=YES
OSDComputerName=DC01
SkipDomainMembership=YES
JoinWorkgroup=DEMO
SkipRoles=YES
I would expect the settings for task sequence "DC01" to be applied after I select that task sequence in the wizard. That doesn't seem to work. The first task in the sequence is a "Gather" task that gathers local data and processes customsettings.ini.
I understand I can't override most settings from [Default] because they would have already been processed but as you can see, that's not what I am actually trying.
I am not opposed to having multiple rules files if that would work. However, it seems like that doesn't make much difference when it comes to actually seeing different wizard steps active. I've tried adding a second customsettings_dc01.ini file and having
a Gather step that specifically references that file in the "Initialize" group.
I've considered some alternatives to making it work this way, such as having multiple deployment shares and "linking" them (although I haven't done this before) so I wouldn't have to copy all the applications.
I would also set the computer name and all in the task sequence using variables, but that still doesn't address the problem.
Any insight is appreciated,
SA.

SpeedBird186 - There are several assumptions going on here.
1. by default MDT processes the CS.ini file *before* the wizard, and *after* the Task sequence has started. If you want CS.ini file to be processed just *after* you select your TS in the wizard, use Johan's trick above.
2. There are about 20 different wizard pages, and they don't appear in *all* scenarios. the wizard framework will attempt to do an intelligent job of filtering out pages that are not relevant to the scenario at hand. For example, in the graphic above, you
can see that the OS roles and Features page will appear/disappear. This can happen for example if the task sequence you selected earlier does or does *not* have a "OS Roles and Featrues" step in the Task sequence.
3. For me, the easiest way to process roles would be to create some new "Applications" and to put them in a folder.
Keith Garner - keithga.wordpress.com

MDT 2013 - Different settings per task sequence

Hi,
I'm trying to create different settings for different TaskSequenceIDs. For one TS I wanted to join the pc to a workgroup and do SkipApplications=YES and for the other TS I wanted to join a domain and do SkipApplications=NO. But I can't get it to work for
some strange reason.
I've tried and tested this solution https://gallery.technet.microsoft.com/scriptcenter/Different-settings-per-4faa55e9#content but it doesn't work.
I tried this too : http://www.the-d-spot.org/wordpress/2012/07/20/how-to-use-different-settings-per-task-sequence-with-mdt-2012/ but it doesn't work.
Perhaps MDT 2013 acts different then 2012 and 2010???? It would be nice if you could help me out on this one. :-)
Paul

@fapw, we use the database for a few years now and we're quite familiar with it. But we're going to install MDT for a client and they don't have SQL and they don't want to have it installed on one of their servers. So that's why I'm playing with the customsettings.ini.
The first I made was for a plain and simple capture, then I added Make&Model and I'm making it more and more complex. The idea is to have a final customsettings.ini that imitates - or gets as close as possible to - what we have already accomplished with
the database.
In the meantime I've read that the skip-panels-stuff is something that stands above everything and thus it's not possible to control that using properties, like f.ex. MACaddress. Well, that's alright then.
But I've got GOOD news for you all : selecting values for variables based on TaskSequenceID DOES WORK in MDT 2013 and ADK 8.1. This is what I did :
https://gallery.technet.microsoft.com/scriptcenter/Different-settings-per-4faa55e9#content
So I've downloaded the vbs, created an "external" tasksequenceid.ini which is read at the beginning of my Task Sequence and booted up the pc. When you select the tasksequence of your choice the parameters get filled in correctly ! OSDComputername
was the variable that I used to show me if the other tasksequenceid.ini file was read or not. If yes, the computername would have to be my value, if not it would be MININT-randomnumber.
Only downside of this fantastic wizard is that going back to change one of your options is not possible anymore. The moment a variable has a value, it doesn't change anymore! That particular behaviour was messing up my tests yesterday.

MDT 2013 Windows 8.1 Task sequence Stops After first Reboot. login

Hi There,
The issue I am having is that After the OS gets laid down, and the Windows 8.1 computer reboots, The task sequence does not continue. It fails everytime. There are not any obvious errors that happen in the process that I can see in the logs. But I have
customized this process quite a bit and I could use some help. We are deploying potentionally to over 30,000 computers.
The test machine I have been using is the Surface pro 2.
The interesting part is after a failure is if I start the process over again , boots into PE, then run diskpart manually from command prompt to Clean Disk 0, and then reboot and start the MDT task sequence, it will deploy fine.
I also have a custom step that copies the TS media from the stick to a Recovery partition I create. The user can launch a -re-image or MDT refresh from an Icon/script, which will unhide this "recovery partition", and kick off a lite touch refresh.
This works succesfully everytime. We have remote locations with very slow links, so MDT over the network or MDT integrated with SCCM is not an option at this time. So this is the solution.
I am attempting to use MDT 2013 to deploy Windows 8.1 Offline, and using GPT partitions.
I am using a custom Format and partiition Step, that call the CustomDiskpart.txt script from %deployroot%\Scripts.
I am also using a Split image, as multi partitioned EFI/NTFS USB sticks are not a possibility for us , also, the USB sticks capable of this are seen by MDT as a "fixed drive" anyways. Which can cause issues in itself. So the LTIAPPLY.wsf has
been edited to search and apply ther split .swm files. This works well.
After the Task sequence failure I have tried launching the Litetouch scripts from the C:\MINNINT folder manually to continue the sequence, but it doesnt do anything.
I don't want to always be running Diskpart manually before imaging a new OEM computer. I needa second pair of eyes on this.
Thank You in advance!

Hi,
Thanks Again for taking a look.
I checked the sysprep log in the image and they look fine. No errors.
As requested here are some logs. Let me know if I can provide anything else.
BDD.log
litetouch.log
SMSTS.log
Im not actually attempting to provide a recovery image. What I am doing is leveraging MDT to refresh the computer remotely. We can update the MDT media on the hidden data partition,when required and kick it off remotely. Some of the computers are very
remote, and without SCCM DP's, plus a combination of slow links and a lack of deskside techs made this a requirement. This works without incident.
The only issue I have is on a new computer if I run the sequence (offline USB media) it will fail the first time, unless I run a diskpart clean in PE first.. Then it will succeed. Refreshing the computer is fine.

Install Applications in task sequence - fails if there is no source

I found an odd issue in SCCM 2012 SP1. I have many applications that install perfectly when deployed. There is no source for the application because it is a network based install, and needs to be. If I try to add the application to the
"Install Application" method in a task sequence, it looks successful. But then re-edit the task sequence and it will tell you there is an issue with the "Install Application" method. The app will not install when you run the
task sequence either. If you then add a content folder to the application, it works like a charm.
In the meantime, I am providing a dummy content location for these apps so I can get things running. But has anyone run into this? Seems so odd that task sequences don't like apps without content.

These are Autodesk application installs. When the deployments are built, they are built to a network location and INI files are generated with paths in them. In the past, I manually edited these files to use local relative pathing, so they
could be used as content, downloaded to the system, and executed locally by SMS. I found issues with install Source locations though (yes, even with using SCCM's built in source control), that made me really want to change the INI's back to network locations,
so now there is no more need for content.
I will have to look into the DCR.

OSD: install software DURING task sequence based upon collection membership

Hi,
I'd like to refer to my
previous post as a starting point.
Below again the background of my question. But please advise on a powershell script that runs at the end of a task sequence that:
*enumerates the pc's collection memberships and based upon that lists the software available
*puts this software in a variable and does the installation DURING the task sequence
J.
Background:
At this time, software in our deployment (of Windows 7) is installed AFTER the task sequence is finished.
The software is deployed based upon the computer membership of collections (which get their info from AD groups).
Problem is that users see their pc as finished but don't have all their software. It even takes sometimes more then an hour even when we refresh computer policy after final reboot of the system. That's why we really need a bulletproof solution = installation
of software DURING task sequence.
Jan Hoedt

I found some time to adjust the script. Now I've created something similar for a device. Basically it finds the collections of which the device is a member, finds the targeted applications and creates task sequence variables for those applications.
See for more information:
http://www.petervanderwoude.nl/post/install-computer-targeted-application-during-os-deployment-via-powershell-and-configmgr-2012/
My Blog: http://www.petervanderwoude.nl/
Follow me on twitter: pvanderwoude

Superseding an application which is installed via OS task sequence

Hi I am using SCCM 2012 SP1 and want to update AppA_version_1 to the AppA_version_2. At the moment AppA_version_1 is a core application and is installed to all machines via OSD when the machines are built. For this reason we don't have any
collections for AppA_version_1.
I have now created a new application for AppA_version_2 and want to test the deployment to a group of machines. As part of the test deployment I want to supersede the AppA_version_1 which we currently have installed.
In the past I have tested supreseding business applications (which are not part of the task sequence and deployed to users not machines) by first creating a test collection, setting the supersedence options and then deploying the superseding (latest) application
to the test collection. When I am happy it works OK I deploy the superseding application to the main collection for that application.
I have not had to supersede an application which is part of the task sequence before but I presume I do it in just the same way ? At the moment I don't want to touch the task sequence. I want to test the deployment of AppA_version_2, then
release it to all production machines, then update the task sequence so it includes AppA_version_2. What I don't want is to deploy it to the test group but have it automatically update on all production machines.
The reason I ask is that I have read that if you update the Task Sequence with the latest version of your software and this supersedes a previous version, then all of your machines in production will receive the latest version even though it has not been
specifically deployed to them.
http://www.windows-noob.com/forums/index.php?/topic/8952-possible-bug-in-sp1-cu1-client-applications-that-supersede-others-may-rollout-unexpectedly/
Even though I am not going to update the task sequence with AppA_version_2 just yet, it has got me questioning the testing of the superseded application.
Am I OK to superseded AppA_version_1 with AppA_version_2 and deploy to a test collection (without it updating all machines in the organisation) even though AppA_version_1 is installed as part of the OSD Task Sequence.
Hope this makes sense
Thanks
G

Thanks Jorgen
What happens if I select the option : automatically upgrade any superseded versions of this application
? Would this ignore the fact that I was deploying to a test collection and automatically update all production machines where the software is installed ?
I haven't actually come across this option before, but I think that is because I usually create my deployments prior to setting the supersedence rules.
Thanks
G

SCCM 2012 R2 MDT 2013 Install Features after OS Install

I have a question in regards to installing Features on Windows Servers Post OS Install/OSD.
I have MDT 2013 integrated with SCCM 2012 R2. I have created a MDT TS doing the following:
Microsoft Deployment Custom Task Sequence (All other ones were for OSD)
I removed all the steps in the TS except for the "Use Toolkit Package"
Added Several MDT Sequence for Install Roles and Features, Selected SNMP for Server 2008, 2008 R2, 2008 R2 Core, 2012, 2012 R2.
Removed the boot image since it is not needed.
Deployed to my Test Collection.
I see the TS Running on the test servers but when I check Server Manager the SNMP is still not installed even though software center shows installed on the TS.
Am I missing something here? Any help would greatly be appreciated. Thanks!!

Disregard my previous post. I was tinkering with the Compliance Settings and corrected my ignorance.
Here were my steps:
Create Configuration Item
General: Put the name, Set Type to Window, filter set to "Server"
Supported Platforms: All servers 2008 and newer
Settings: Name,
Discovery Script -PowerShell
$FeatureName = "SNMP-Service"
If (Get-WindowsFeature | Where {$_.State -eq "Enabled" -and $_.FeatureName -eq $FeatureName})
$Compliance = "Compliant"
Else {
$Compliance = "NonCompliant"
Return $Compliance
Remediation Script - PowerShell
$FeatureName = "SNMP-Service"
Import-Module ServerManager
Install-WindowsFeature -Name $FeatureName -IncludeAllSubFeature
Compliance Rule: Name, Rule Type = Value, Must Comply Equals Compliant, Checked Run remediation script when not compliant, set Reports to Information
Created Config Baseline, Assigned Config Item for SNMP Service and then deployed to my Servers.

Deployment Workbench Adding Applications Using Task Sequence

I am trying to figure out how to add applications in Deployment Workbench. My biggest issue is what to put in the command line to get it to work. Someone else created folders with everything that would needed along with a batch file. Now I am trying to
figure out how to get that to work in Deployment Workbench. I am also trying to figure out how to then get it to work in Task Sequence since it is not currently working the way I have tried. Thanks.

Hi,
Here is a guidance for you:
Installing Applications with MDT.
http://lethewookiewin.wordpress.com/2011/04/21/84/
You referred that something didn’t work for you, can you kindly provide the error message? If you were using any scripts you can also attach them.
Thank you.

Deploying Applications Using Task Sequence

Hi, can someone please tell me what I am doing wrong. I am trying to deploy some App-V 5.0 prerequisites using a task sequence but for whatever reason the TS just will not execute the install application group I created (screenshot below).
The OSD part of the TS installs correctly without any errors but the applications just don't get installed.

Basically I have created four applications. The App-V Client has two dependencies which are the .NET framework and Windows Powershell. The Powershell application has one dependency which the .NET framework application. Those are the only conditions set.
The App-V client application is only deployed to the collection and not the DP (Do I need to deploy them to the DP as well?) Yes, I do have network connectivity and the ConfigMgr Client agent was successfully installed.
<![LOG[Entering ExecQueryAsync for query "select * from CCM_AppDeliveryType where (AppDeliveryTypeId = "ScopeId_CA0A280E-BB0E-4957-A215-D5E6D22810F0/DeploymentType_5379fd0b-70b1-46d6-835d-207eb71192d3" AND Revision = 2)"]LOG]!><time="21:35:05.085-60"
date="06-09-2014" component="AppDiscovery" context="" type="1" thread="2164" file="appprovider.cpp:406">
<![LOG[ Performing detection of app deployment type Microsoft Office Professional Plus 2013 - Windows Installer (*.msi file)(ScopeId_CA0A280E-BB0E-4957-A215-D5E6D22810F0/DeploymentType_5379fd0b-70b1-46d6-835d-207eb71192d3, revision 2) for system.]LOG]!><time="21:35:05.179-60"
date="06-09-2014" component="AppDiscovery" context="" type="1" thread="2164" file="appprovider.cpp:2148">
<![LOG[+++ MSI application not discovered [MSI Product Code: {90150000-0011-0000-1000-0000000FF1CE}, MSI Product version: ]]LOG]!><time="21:35:05.179-60" date="06-09-2014" component="AppDiscovery" context="" type="1" thread="2164" file="msihandler.cpp:131">
<![LOG[+++ Did not detect app deployment type Microsoft Office Professional Plus 2013 - Windows Installer (*.msi file)(ScopeId_CA0A280E-BB0E-4957-A215-D5E6D22810F0/DeploymentType_5379fd0b-70b1-46d6-835d-207eb71192d3, revision 2) for system.]LOG]!><time="21:35:05.179-60"
date="06-09-2014" component="AppDiscovery" context="" type="1" thread="2164" file="appprovider.cpp:540">
<![LOG[Entering ExecQueryAsync for query "select * from CCM_AppDeliveryType where (AppDeliveryTypeId = "ScopeId_CA0A280E-BB0E-4957-A215-D5E6D22810F0/DeploymentType_205c0280-ca05-4f70-8f62-88fd87d21a36" AND Revision = 1)"]LOG]!><time="21:35:06.224-60"
date="06-09-2014" component="AppDiscovery" context="" type="1" thread="2164" file="appprovider.cpp:406">
<![LOG[ Performing detection of app deployment type App-V Client Installer(ScopeId_CA0A280E-BB0E-4957-A215-D5E6D22810F0/DeploymentType_205c0280-ca05-4f70-8f62-88fd87d21a36, revision 1) for system.]LOG]!><time="21:35:06.536-60" date="06-09-2014"
component="AppDiscovery" context="" type="1" thread="2164" file="appprovider.cpp:2148">
<![LOG[+++ Application not discovered. [AppDT Id: ScopeId_CA0A280E-BB0E-4957-A215-D5E6D22810F0/DeploymentType_205c0280-ca05-4f70-8f62-88fd87d21a36, Revision: 1]]LOG]!><time="21:35:06.645-60" date="06-09-2014" component="AppDiscovery" context="" type="1"
thread="2164" file="localapphandler.cpp:291">
<![LOG[+++ Did not detect app deployment type App-V Client Installer(ScopeId_CA0A280E-BB0E-4957-A215-D5E6D22810F0/DeploymentType_205c0280-ca05-4f70-8f62-88fd87d21a36, revision 1) for system.]LOG]!><time="21:35:06.645-60" date="06-09-2014" component="AppDiscovery"
context="" type="1" thread="2164" file="appprovider.cpp:540">
<![LOG[Entering ExecQueryAsync for query "select * from CCM_AppDeliveryType where (AppDeliveryTypeId = "ScopeId_CA0A280E-BB0E-4957-A215-D5E6D22810F0/DeploymentType_63e07ea7-3574-4884-af7e-63f3706d51e5" AND Revision = 1)"]LOG]!><time="21:35:07.004-60"
date="06-09-2014" component="AppDiscovery" context="" type="1" thread="3300" file="appprovider.cpp:406">
<![LOG[ Performing detection of app deployment type .NET Framework Installer(ScopeId_CA0A280E-BB0E-4957-A215-D5E6D22810F0/DeploymentType_63e07ea7-3574-4884-af7e-63f3706d51e5, revision 1) for system.]LOG]!><time="21:35:07.160-60" date="06-09-2014"
component="AppDiscovery" context="" type="1" thread="3300" file="appprovider.cpp:2148">
<![LOG[+++ Application not discovered. [AppDT Id: ScopeId_CA0A280E-BB0E-4957-A215-D5E6D22810F0/DeploymentType_63e07ea7-3574-4884-af7e-63f3706d51e5, Revision: 1]]LOG]!><time="21:35:07.332-60" date="06-09-2014" component="AppDiscovery" context="" type="1"
thread="3300" file="localapphandler.cpp:291">
<![LOG[+++ Did not detect app deployment type .NET Framework Installer(ScopeId_CA0A280E-BB0E-4957-A215-D5E6D22810F0/DeploymentType_63e07ea7-3574-4884-af7e-63f3706d51e5, revision 1) for system.]LOG]!><time="21:35:07.332-60" date="06-09-2014" component="AppDiscovery"
context="" type="1" thread="3300" file="appprovider.cpp:540">
<![LOG[Entering ExecQueryAsync for query "select * from CCM_AppDeliveryType where (AppDeliveryTypeId = "ScopeId_CA0A280E-BB0E-4957-A215-D5E6D22810F0/DeploymentType_1780e074-b249-4f01-bd8a-1b03ebdbfba5" AND Revision = 2)"]LOG]!><time="21:35:07.457-60"
date="06-09-2014" component="AppDiscovery" context="" type="1" thread="3300" file="appprovider.cpp:406">
<![LOG[ Performing detection of app deployment type Powershell Installer(ScopeId_CA0A280E-BB0E-4957-A215-D5E6D22810F0/DeploymentType_1780e074-b249-4f01-bd8a-1b03ebdbfba5, revision 2) for system.]LOG]!><time="21:35:08.674-60" date="06-09-2014"
component="AppDiscovery" context="" type="1" thread="3300" file="appprovider.cpp:2148">
<![LOG[ In-line script returned error output: File D:\WINDOWS\CCM\SystemTemp\2544c273-aa77-4d14-b16b-143a812a9c19.ps1 cannot
be loaded. The file D:\WINDOWS\CCM\SystemTemp\2544c273-aa77-4d14-b16b-143a812a9
c19.ps1 is not digitally signed. The script will not execute on the system. Ple
ase see "get-help about_signing" for more details..
At line:1 char:2
+ & <<<< 'D:\WINDOWS\CCM\SystemTemp\2544c273-aa77-4d14-b16b-143a812a9c19.ps1'
+ CategoryInfo : NotSpecified: (:) [], PSSecurityException
+ FullyQualifiedErrorId : RuntimeException
]LOG]!><time="21:35:20.146-60" date="06-09-2014" component="AppDiscovery" context="" type="2" thread="3300" file="appexcnlib.cpp:1020">
<![LOG[Script Execution returned error message: File D:\WINDOWS\CCM\SystemTemp\2544c273-aa77-4d14-b16b-143a812a9c19.ps1 cannot
be loaded. The file D:\WINDOWS\CCM\SystemTemp\2544c273-aa77-4d14-b16b-143a812a9
c19.ps1 is not digitally signed. The script will not execute on the system. Ple
ase see "get-help about_signing" for more details..
At line:1 char:2
+ & <<<< 'D:\WINDOWS\CCM\SystemTemp\2544c273-aa77-4d14-b16b-143a812a9c19.ps1'
+ CategoryInfo : NotSpecified: (:) [], PSSecurityException
+ FullyQualifiedErrorId : RuntimeException
, ExitCode: 1]LOG]!><time="21:35:20.147-60" date="06-09-2014" component="AppDiscovery" context="" type="2" thread="3300" file="scripthandler.cpp:473">
<![LOG[ Script Execution Returned :1, Error Message: File D:\WINDOWS\CCM\SystemTemp\2544c273-aa77-4d14-b16b-143a812a9c19.ps1 cannot
be loaded. The file D:\WINDOWS\CCM\SystemTemp\2544c273-aa77-4d14-b16b-143a812a9
c19.ps1 is not digitally signed. The script will not execute on the system. Ple
ase see "get-help about_signing" for more details..
At line:1 char:2
+ & <<<< 'D:\WINDOWS\CCM\SystemTemp\2544c273-aa77-4d14-b16b-143a812a9c19.ps1'
+ CategoryInfo : NotSpecified: (:) [], PSSecurityException
+ FullyQualifiedErrorId : RuntimeException
. [AppDT Id: ScopeId_CA0A280E-BB0E-4957-A215-D5E6D22810F0/DeploymentType_1780e074-b249-4f01-bd8a-1b03ebdbfba5, Revision: 2]]LOG]!><time="21:35:20.147-60" date="06-09-2014" component="AppDiscovery" context="" type="3" thread="3300" file="scripthandler.cpp:506">
<![LOG[CScriptHandler::DiscoverApp failed (0x87d00327).]LOG]!><time="21:35:20.149-60" date="06-09-2014" component="AppDiscovery" context="" type="3" thread="3300" file="scripthandler.cpp:546">
<![LOG[Deployment type detection failed with error 0x87d00327.]LOG]!><time="21:35:20.149-60" date="06-09-2014" component="AppDiscovery" context="" type="3" thread="3300" file="appprovider.cpp:2203">
<![LOG[Failed to perform detection of app deployment type Powershell Installer(Powershell Installer, revision 2) for system. Error 0x87d00327]LOG]!><time="21:35:20.150-60" date="06-09-2014" component="AppDiscovery" context="" type="3" thread="3300"
file="appprovider.cpp:545">
<![LOG[Entering ExecQueryAsync for query "select * from CCM_AppDeliveryType where (AppDeliveryTypeId = "ScopeId_CA0A280E-BB0E-4957-A215-D5E6D22810F0/DeploymentType_5379fd0b-70b1-46d6-835d-207eb71192d3" AND Revision = 2)"]LOG]!><time="21:35:46.840-60"
date="06-09-2014" component="AppDiscovery" context="" type="1" thread="3300" file="appprovider.cpp:406">
<![LOG[ Performing detection of app deployment type Microsoft Office Professional Plus 2013 - Windows Installer (*.msi file)(ScopeId_CA0A280E-BB0E-4957-A215-D5E6D22810F0/DeploymentType_5379fd0b-70b1-46d6-835d-207eb71192d3, revision 2) for system.]LOG]!><time="21:35:46.855-60"
date="06-09-2014" component="AppDiscovery" context="" type="1" thread="3300" file="appprovider.cpp:2148">
<![LOG[+++ MSI application not discovered [MSI Product Code: {90150000-0011-0000-1000-0000000FF1CE}, MSI Product version: ]]LOG]!><time="21:35:46.855-60" date="06-09-2014" component="AppDiscovery" context="" type="1" thread="3300" file="msihandler.cpp:131">
<![LOG[+++ Did not detect app deployment type Microsoft Office Professional Plus 2013 - Windows Installer (*.msi file)(ScopeId_CA0A280E-BB0E-4957-A215-D5E6D22810F0/DeploymentType_5379fd0b-70b1-46d6-835d-207eb71192d3, revision 2) for system.]LOG]!><time="21:35:46.855-60"
date="06-09-2014" component="AppDiscovery" context="" type="1" thread="3300" file="appprovider.cpp:540">
<![LOG[Entering ExecQueryAsync for query "select * from CCM_AppDeliveryType where (AppDeliveryTypeId = "ScopeId_CA0A280E-BB0E-4957-A215-D5E6D22810F0/DeploymentType_205c0280-ca05-4f70-8f62-88fd87d21a36" AND Revision = 1)"]LOG]!><time="21:35:46.886-60"
date="06-09-2014" component="AppDiscovery" context="" type="1" thread="3300" file="appprovider.cpp:406">
<![LOG[ Performing detection of app deployment type App-V Client Installer(ScopeId_CA0A280E-BB0E-4957-A215-D5E6D22810F0/DeploymentType_205c0280-ca05-4f70-8f62-88fd87d21a36, revision 1) for system.]LOG]!><time="21:35:46.886-60" date="06-09-2014"
component="AppDiscovery" context="" type="1" thread="3300" file="appprovider.cpp:2148">
<![LOG[+++ Application not discovered. [AppDT Id: ScopeId_CA0A280E-BB0E-4957-A215-D5E6D22810F0/DeploymentType_205c0280-ca05-4f70-8f62-88fd87d21a36, Revision: 1]]LOG]!><time="21:35:46.902-60" date="06-09-2014" component="AppDiscovery" context="" type="1"
thread="3300" file="localapphandler.cpp:291">
<![LOG[+++ Did not detect app deployment type App-V Client Installer(ScopeId_CA0A280E-BB0E-4957-A215-D5E6D22810F0/DeploymentType_205c0280-ca05-4f70-8f62-88fd87d21a36, revision 1) for system.]LOG]!><time="21:35:46.902-60" date="06-09-2014" component="AppDiscovery"
context="" type="1" thread="3300" file="appprovider.cpp:540">
<![LOG[Entering ExecQueryAsync for query "select * from CCM_AppDeliveryType where (AppDeliveryTypeId = "ScopeId_CA0A280E-BB0E-4957-A215-D5E6D22810F0/DeploymentType_63e07ea7-3574-4884-af7e-63f3706d51e5" AND Revision = 1)"]LOG]!><time="21:35:46.902-60"
date="06-09-2014" component="AppDiscovery" context="" type="1" thread="3300" file="appprovider.cpp:406">
<![LOG[ Performing detection of app deployment type .NET Framework Installer(ScopeId_CA0A280E-BB0E-4957-A215-D5E6D22810F0/DeploymentType_63e07ea7-3574-4884-af7e-63f3706d51e5, revision 1) for system.]LOG]!><time="21:35:46.918-60" date="06-09-2014"
component="AppDiscovery" context="" type="1" thread="3300" file="appprovider.cpp:2148">
<![LOG[+++ Application not discovered. [AppDT Id: ScopeId_CA0A280E-BB0E-4957-A215-D5E6D22810F0/DeploymentType_63e07ea7-3574-4884-af7e-63f3706d51e5, Revision: 1]]LOG]!><time="21:35:46.918-60" date="06-09-2014" component="AppDiscovery" context="" type="1"
thread="3300" file="localapphandler.cpp:291">
<![LOG[+++ Did not detect app deployment type .NET Framework Installer(ScopeId_CA0A280E-BB0E-4957-A215-D5E6D22810F0/DeploymentType_63e07ea7-3574-4884-af7e-63f3706d51e5, revision 1) for system.]LOG]!><time="21:35:46.918-60" date="06-09-2014" component="AppDiscovery"
context="" type="1" thread="3300" file="appprovider.cpp:540">
<![LOG[Entering ExecQueryAsync for query "select * from CCM_AppDeliveryType where (AppDeliveryTypeId = "ScopeId_CA0A280E-BB0E-4957-A215-D5E6D22810F0/DeploymentType_1780e074-b249-4f01-bd8a-1b03ebdbfba5" AND Revision = 2)"]LOG]!><time="21:35:46.933-60"
date="06-09-2014" component="AppDiscovery" context="" type="1" thread="3300" file="appprovider.cpp:406">
<![LOG[ Performing detection of app deployment type Powershell Installer(ScopeId_CA0A280E-BB0E-4957-A215-D5E6D22810F0/DeploymentType_1780e074-b249-4f01-bd8a-1b03ebdbfba5, revision 2) for system.]LOG]!><time="21:35:46.933-60" date="06-09-2014"
component="AppDiscovery" context="" type="1" thread="3300" file="appprovider.cpp:2148">
<![LOG[ In-line script returned error output: File D:\WINDOWS\CCM\SystemTemp\014a97d8-4b1b-411f-99c9-559f6e45fcb1.ps1 cannot
be loaded. The file D:\WINDOWS\CCM\SystemTemp\014a97d8-4b1b-411f-99c9-559f6e45f
cb1.ps1 is not digitally signed. The script will not execute on the system. Ple
ase see "get-help about_signing" for more details..
At line:1 char:2
+ & <<<< 'D:\WINDOWS\CCM\SystemTemp\014a97d8-4b1b-411f-99c9-559f6e45fcb1.ps1'
+ CategoryInfo : NotSpecified: (:) [], PSSecurityException
+ FullyQualifiedErrorId : RuntimeException
]LOG]!><time="21:35:47.308-60" date="06-09-2014" component="AppDiscovery" context="" type="2" thread="3300" file="appexcnlib.cpp:1020">
<![LOG[Script Execution returned error message: File D:\WINDOWS\CCM\SystemTemp\014a97d8-4b1b-411f-99c9-559f6e45fcb1.ps1 cannot
be loaded. The file D:\WINDOWS\CCM\SystemTemp\014a97d8-4b1b-411f-99c9-559f6e45f
cb1.ps1 is not digitally signed. The script will not execute on the system. Ple
ase see "get-help about_signing" for more details..
At line:1 char:2
+ & <<<< 'D:\WINDOWS\CCM\SystemTemp\014a97d8-4b1b-411f-99c9-559f6e45fcb1.ps1'
+ CategoryInfo : NotSpecified: (:) [], PSSecurityException
+ FullyQualifiedErrorId : RuntimeException
, ExitCode: 1]LOG]!><time="21:35:47.308-60" date="06-09-2014" component="AppDiscovery" context="" type="2" thread="3300" file="scripthandler.cpp:473">
<![LOG[ Script Execution Returned :1, Error Message: File D:\WINDOWS\CCM\SystemTemp\014a97d8-4b1b-411f-99c9-559f6e45fcb1.ps1 cannot
be loaded. The file D:\WINDOWS\CCM\SystemTemp\014a97d8-4b1b-411f-99c9-559f6e45f
cb1.ps1 is not digitally signed. The script will not execute on the system. Ple
ase see "get-help about_signing" for more details..
At line:1 char:2
+ & <<<< 'D:\WINDOWS\CCM\SystemTemp\014a97d8-4b1b-411f-99c9-559f6e45fcb1.ps1'
+ CategoryInfo : NotSpecified: (:) [], PSSecurityException
+ FullyQualifiedErrorId : RuntimeException
. [AppDT Id: ScopeId_CA0A280E-BB0E-4957-A215-D5E6D22810F0/DeploymentType_1780e074-b249-4f01-bd8a-1b03ebdbfba5, Revision: 2]]LOG]!><time="21:35:47.308-60" date="06-09-2014" component="AppDiscovery" context="" type="3" thread="3300" file="scripthandler.cpp:506">
<![LOG[CScriptHandler::DiscoverApp failed (0x87d00327).]LOG]!><time="21:35:47.308-60" date="06-09-2014" component="AppDiscovery" context="" type="3" thread="3300" file="scripthandler.cpp:546">
<![LOG[Deployment type detection failed with error 0x87d00327.]LOG]!><time="21:35:47.308-60" date="06-09-2014" component="AppDiscovery" context="" type="3" thread="3300" file="appprovider.cpp:2203">
<![LOG[Failed to perform detection of app deployment type Powershell Installer(Powershell Installer, revision 2) for system. Error 0x87d00327]LOG]!><time="21:35:47.308-60" date="06-09-2014" component="AppDiscovery" context="" type="3" thread="3300"
file="appprovider.cpp:545">
I cannot find the location of AppEnforce.log (It is not in C:\Windows\CCM\Logs). Please bear with me, I am still learning ConfigMgr.

Deploy Application During Task Sequence

Hello I have created about 10 packages to be part of our Windows 7 deployment using installshield. The packages install ok manually and through SCCM Client Center. However when I add them to my Task Sequence I get 1603 errors??? Is it a permissions issue.
Some of my packages work some don't?
Here's the log error
Unmatched exit code 1603 is considered and execution failure.
SCCM Deployment Technician

Hi here is the log, any help appreciated. I think its permissions issue but not sure what I can do to remedy it?
=== Verbose logging started: 12/03/2015 10:11:15 Build type: SHIP UNICODE 5.00.7601.00 Calling process: C:\WINDOWS\system32\msiexec.exe ===
MSI (c) (54:B8) [10:11:15:124]: Resetting cached policy values
MSI (c) (54:B8) [10:11:15:124]: Machine policy value 'Debug' is 0
MSI (c) (54:B8) [10:11:15:124]: ******* RunEngine:
******* Product: Genetec_Omnicast_Client_4_8_2201_19_B2.msi
******* Action:
******* CommandLine: **********
MSI (c) (54:B8) [10:11:15:125]: Client-side and UI is none or basic: Running entire install on the server.
MSI (c) (54:B8) [10:11:15:125]: Grabbed execution mutex.
MSI (c) (54:B8) [10:11:15:140]: Cloaking enabled.
MSI (c) (54:B8) [10:11:15:140]: Attempting to enable all disabled privileges before calling Install on Server
MSI (c) (54:B8) [10:11:15:142]: Incrementing counter to disable shutdown. Counter after increment: 0
MSI (s) (C0:E0) [10:11:15:144]: Running installation inside multi-package transaction C:\Windows\ccmcache\9i\Genetec_Omnicast_Client_4_8_2201_19_B2.msi
MSI (s) (C0:E0) [10:11:15:144]: Grabbed execution mutex.
MSI (s) (C0:08) [10:11:15:145]: Resetting cached policy values
MSI (s) (C0:08) [10:11:15:145]: Machine policy value 'Debug' is 0
MSI (s) (C0:08) [10:11:15:145]: ******* RunEngine:
******* Product: C:\Windows\ccmcache\9i\Genetec_Omnicast_Client_4_8_2201_19_B2.msi
******* Action:
******* CommandLine: **********
MSI (s) (C0:08) [10:11:15:145]: Machine policy value 'DisableUserInstalls' is 0
MSI (s) (C0:08) [10:11:15:146]: User policy value 'SearchOrder' is 'nmu'
MSI (s) (C0:08) [10:11:15:146]: User policy value 'DisableMedia' is 0
MSI (s) (C0:08) [10:11:15:146]: Machine policy value 'AllowLockdownMedia' is 0
MSI (s) (C0:08) [10:11:15:146]: SOURCEMGMT: Media enabled only if package is safe.
MSI (s) (C0:08) [10:11:15:146]: SOURCEMGMT: Looking for sourcelist for product {410ED13C-DBAD-4228-9A77-D90AF1CB6B07}
MSI (s) (C0:08) [10:11:15:146]: SOURCEMGMT: Adding {410ED13C-DBAD-4228-9A77-D90AF1CB6B07}; to potential sourcelist list (pcode;disk;relpath).
MSI (s) (C0:08) [10:11:15:146]: SOURCEMGMT: Now checking product {410ED13C-DBAD-4228-9A77-D90AF1CB6B07}
MSI (s) (C0:08) [10:11:15:146]: SOURCEMGMT: Media is enabled for product.
MSI (s) (C0:08) [10:11:15:146]: SOURCEMGMT: Attempting to use LastUsedSource from source list.
MSI (s) (C0:08) [10:11:15:146]: SOURCEMGMT: Trying source C:\Windows\ccmcache\9a\.
MSI (s) (C0:08) [10:11:15:146]: Note: 1: 1402 2: HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Policies\Explorer 3: 2
MSI (s) (C0:08) [10:11:15:146]: Entering CMsiConfigurationManager::SetLastUsedSource.
MSI (s) (C0:08) [10:11:15:146]: Specifed source is already in a list.
MSI (s) (C0:08) [10:11:15:146]: User policy value 'SearchOrder' is 'nmu'
MSI (s) (C0:08) [10:11:15:146]: Machine policy value 'DisableBrowse' is 0
MSI (s) (C0:08) [10:11:15:146]: Machine policy value 'AllowLockdownBrowse' is 0
MSI (s) (C0:08) [10:11:15:146]: Adding new sources is allowed.
MSI (s) (C0:08) [10:11:15:147]: Set LastUsedSource to: C:\Windows\ccmcache\9a\.
MSI (s) (C0:08) [10:11:15:147]: Set LastUsedType to: n.
MSI (s) (C0:08) [10:11:15:147]: Set LastUsedIndex to: 1.
MSI (s) (C0:08) [10:11:15:147]: SOURCEMGMT: Resolved source to: 'C:\Windows\ccmcache\9a\'
MSI (s) (C0:08) [10:11:15:155]: SRSetRestorePoint skipped for this transaction.
MSI (s) (C0:08) [10:11:15:157]: File will have security applied from OpCode.
MSI (s) (C0:08) [10:11:15:171]: SOFTWARE RESTRICTION POLICY: Verifying package --> 'C:\Windows\ccmcache\9i\Genetec_Omnicast_Client_4_8_2201_19_B2.msi' against software restriction policy
MSI (s) (C0:08) [10:11:15:171]: SOFTWARE RESTRICTION POLICY: C:\Windows\ccmcache\9i\Genetec_Omnicast_Client_4_8_2201_19_B2.msi has a digital signature
MSI (s) (C0:08) [10:11:15:171]: SOFTWARE RESTRICTION POLICY: C:\Windows\ccmcache\9i\Genetec_Omnicast_Client_4_8_2201_19_B2.msi is permitted to run because the user token authorizes execution (system or service token).
MSI (s) (C0:08) [10:11:15:171]: End dialog not enabled
MSI (s) (C0:08) [10:11:15:171]: Original package ==> C:\Windows\ccmcache\9a\Genetec_Omnicast_Client_4_8_2201_19_B2.msi
MSI (s) (C0:08) [10:11:15:171]: Package we're running from ==> C:\WINDOWS\Installer\1e7f0.msi
MSI (s) (C0:08) [10:11:15:179]: APPCOMPAT: looking for appcompat database entry with ProductCode '{410ED13C-DBAD-4228-9A77-D90AF1CB6B07}'.
MSI (s) (C0:08) [10:11:15:180]: APPCOMPAT: no matching ProductCode found in database.
MSI (s) (C0:08) [10:11:15:181]: MSCOREE not loaded loading copy from system32
MSI (s) (C0:08) [10:11:15:183]: Machine policy value 'DisablePatch' is 0
MSI (s) (C0:08) [10:11:15:183]: Machine policy value 'AllowLockdownPatch' is 0
MSI (s) (C0:08) [10:11:15:183]: Machine policy value 'DisableLUAPatching' is 0
MSI (s) (C0:08) [10:11:15:183]: Machine policy value 'DisableFlyWeightPatching' is 0
MSI (s) (C0:08) [10:11:15:186]: SHELL32::SHGetFolderPath returned: C:\WINDOWS\system32\config\systemprofile\AppData\Roaming
MSI (s) (C0:08) [10:11:15:186]: Looking for file transform in shell folder: C:\WINDOWS\system32\config\systemprofile\AppData\Roaming\Microsoft\Installer\{410ED13C-DBAD-4228-9A77-D90AF1CB6B07}\Genetec_Omnicast_Client_4_8_2201_19_B2.mst
MSI (s) (C0:08) [10:11:15:186]: Note: 1: 2262 2: Patch 3: -2147287038
MSI (s) (C0:08) [10:11:15:186]: Note: 1: 2205 2: 3: PatchPackage
MSI (s) (C0:08) [10:11:15:187]: Note: 1: 2262 2: Media 3: -2147287038
MSI (s) (C0:08) [10:11:15:187]: Note: 1: 2262 2: File 3: -2147287038
MSI (s) (C0:08) [10:11:15:187]: TRANSFORM: 'PatchPackage' table is missing or empty. No pre-transform fixup necessary.
MSI (s) (C0:08) [10:11:15:187]: TRANSFORM: Applying regular transform to database.
MSI (s) (C0:08) [10:11:15:187]: Note: 1: 2262 2: ActionText 3: -2147287038
MSI (s) (C0:08) [10:11:15:187]: Note: 1: 2262 2: AdminExecuteSequence 3: -2147287038
MSI (s) (C0:08) [10:11:15:187]: Note: 1: 2262 2: Condition 3: -2147287038
MSI (s) (C0:08) [10:11:15:187]: Note: 1: 2262 2: AdminUISequence 3: -2147287038
MSI (s) (C0:08) [10:11:15:187]: Note: 1: 2262 2: AdvtExecuteSequence 3: -2147287038
MSI (s) (C0:08) [10:11:15:187]: Note: 1: 2262 2: AdvtUISequence 3: -2147287038
MSI (s) (C0:08) [10:11:15:187]: Note: 1: 2262 2: AppId 3: -2147287038
MSI (s) (C0:08) [10:11:15:187]: Note: 1: 2262 2: AppSearch 3: -2147287038
MSI (s) (C0:08) [10:11:15:188]: Note: 1: 2262 2: BindImage 3: -2147287038
MSI (s) (C0:08) [10:11:15:188]: Note: 1: 2262 2: File 3: -2147287038
MSI (s) (C0:08) [10:11:15:188]: Note: 1: 2262 2: CheckBox 3: -2147287038
MSI (s) (C0:08) [10:11:15:188]: Note: 1: 2262 2: Class 3: -2147287038
MSI (s) (C0:08) [10:11:15:188]: Note: 1: 2262 2: Icon 3: -2147287038
MSI (s) (C0:08) [10:11:15:188]: Note: 1: 2262 2: ProgId 3: -2147287038
MSI (s) (C0:08) [10:11:15:188]: Note: 1: 2262 2: ComboBox 3: -2147287038
MSI (s) (C0:08) [10:11:15:188]: Note: 1: 2262 2: Dialog 3: -2147287038
MSI (s) (C0:08) [10:11:15:188]: Note: 1: 2262 2: ControlCondition 3: -2147287038
MSI (s) (C0:08) [10:11:15:188]: Note: 1: 2262 2: ControlEvent 3: -2147287038
MSI (s) (C0:08) [10:11:15:188]: Note: 1: 2262 2: ModuleExclusion 3: -2147287038
MSI (s) (C0:08) [10:11:15:188]: Note: 1: 2262 2: ModuleSignature 3: -2147287038
MSI (s) (C0:08) [10:11:15:188]: Note: 1: 2262 2: Error 3: -2147287038
MSI (s) (C0:08) [10:11:15:188]: Note: 1: 2262 2: EventMapping 3: -2147287038
MSI (s) (C0:08) [10:11:15:188]: Note: 1: 2262 2: Extension 3: -2147287038
MSI (s) (C0:08) [10:11:15:188]: Note: 1: 2262 2: Font 3: -2147287038
MSI (s) (C0:08) [10:11:15:188]: Note: 1: 2262 2: IniFile 3: -2147287038
MSI (s) (C0:08) [10:11:15:188]: Note: 1: 2262 2: InstallUISequence 3: -2147287038
MSI (s) (C0:08) [10:11:15:188]: Note: 1: 2262 2: LaunchCondition 3: -2147287038
MSI (s) (C0:08) [10:11:15:188]: Note: 1: 2262 2: ListBox 3: -2147287038
MSI (s) (C0:08) [10:11:15:188]: Note: 1: 2262 2: ListView 3: -2147287038
MSI (s) (C0:08) [10:11:15:188]: Note: 1: 2262 2: LockPermissions 3: -2147287038
MSI (s) (C0:08) [10:11:15:188]: Note: 1: 2262 2: Media 3: -2147287038
MSI (s) (C0:08) [10:11:15:188]: Note: 1: 2262 2: ModuleComponents 3: -2147287038
MSI (s) (C0:08) [10:11:15:188]: Note: 1: 2262 2: MsiAssembly 3: -2147287038
MSI (s) (C0:08) [10:11:15:188]: Note: 1: 2262 2: MsiAssemblyName 3: -2147287038
MSI (s) (C0:08) [10:11:15:188]: Note: 1: 2262 2: ModuleDependency 3: -2147287038
MSI (s) (C0:08) [10:11:15:188]: Note: 1: 2262 2: MsiFileHash 3: -2147287038
MSI (s) (C0:08) [10:11:15:188]: Note: 1: 2262 2: ODBCDataSource 3: -2147287038
MSI (s) (C0:08) [10:11:15:188]: Note: 1: 2262 2: ODBCSourceAttribute 3: -2147287038
MSI (s) (C0:08) [10:11:15:188]: Note: 1: 2262 2: Patch 3: -2147287038
MSI (s) (C0:08) [10:11:15:188]: Note: 1: 2262 2: PublishComponent 3: -2147287038
MSI (s) (C0:08) [10:11:15:188]: Note: 1: 2262 2: RadioButton 3: -2147287038
MSI (s) (C0:08) [10:11:15:188]: Note: 1: 2262 2: RegLocator 3: -2147287038
MSI (s) (C0:08) [10:11:15:188]: Note: 1: 2262 2: RemoveFile 3: -2147287038
MSI (s) (C0:08) [10:11:15:188]: Note: 1: 2262 2: SelfReg 3: -2147287038
MSI (s) (C0:08) [10:11:15:188]: Note: 1: 2262 2: Shortcut 3: -2147287038
MSI (s) (C0:08) [10:11:15:188]: Note: 1: 2262 2: Signature 3: -2147287038
MSI (s) (C0:08) [10:11:15:188]: Note: 1: 2262 2: TextStyle 3: -2147287038
MSI (s) (C0:08) [10:11:15:188]: Note: 1: 2262 2: TypeLib 3: -2147287038
MSI (s) (C0:08) [10:11:15:188]: Note: 1: 2262 2: UIText 3: -2147287038
MSI (s) (C0:08) [10:11:15:188]: Note: 1: 2262 2: Upgrade 3: -2147287038
MSI (s) (C0:08) [10:11:15:188]: Note: 1: 2262 2: Verb 3: -2147287038
MSI (s) (C0:08) [10:11:15:188]: Note: 1: 2262 2: ISComponentExtended 3: -2147287038
MSI (s) (C0:08) [10:11:15:188]: Note: 1: 2262 2: ISCustomActionReference 3: -2147287038
MSI (s) (C0:08) [10:11:15:188]: Note: 1: 2262 2: ISSQLConnection 3: -2147287038
MSI (s) (C0:08) [10:11:15:188]: Note: 1: 2262 2: ISSQLConnectionDBServer 3: -2147287038
MSI (s) (C0:08) [10:11:15:188]: Note: 1: 2262 2: ISSQLDBMetaData 3: -2147287038
MSI (s) (C0:08) [10:11:15:188]: Note: 1: 2262 2: ISSQLConnectionScript 3: -2147287038
MSI (s) (C0:08) [10:11:15:188]: Note: 1: 2262 2: ISSQLScriptFile 3: -2147287038
MSI (s) (C0:08) [10:11:15:188]: Note: 1: 2262 2: LangDll 3: -2147287038
MSI (s) (C0:08) [10:11:15:188]: Note: 1: 2262 2: SeagateCondition 3: -2147287038
MSI (s) (C0:08) [10:11:15:188]: Note: 1: 2262 2: SeagateIPService 3: -2147287038
MSI (s) (C0:08) [10:11:15:188]: Note: 1: 2262 2: SeagateSourcePath 3: -2147287038
MSI (s) (C0:08) [10:11:15:188]: Note: 1: 2262 2: SeagateStreamFiles 3: -2147287038
MSI (s) (C0:08) [10:11:15:188]: Note: 1: 2262 2: SxsMsmGenComponents 3: -2147287038
MSI (s) (C0:08) [10:11:15:188]: Note: 1: 2262 2: MsiSFCBypass 3: -2147287038
MSI (s) (C0:08) [10:11:15:188]: Note: 1: 2262 2: HelpPlugin 3: -2147287038
MSI (s) (C0:08) [10:11:15:188]: Note: 1: 2262 2: HelpNamespace 3: -2147287038
MSI (s) (C0:08) [10:11:15:188]: Note: 1: 2262 2: HelpFileToNamespace 3: -2147287038
MSI (s) (C0:08) [10:11:15:188]: Note: 1: 2262 2: HelpFile 3: -2147287038
MSI (s) (C0:08) [10:11:15:188]: Note: 1: 2262 2: HelpFilter 3: -2147287038
MSI (s) (C0:08) [10:11:15:188]: Note: 1: 2262 2: HelpFilterToNamespace 3: -2147287038
MSI (s) (C0:08) [10:11:15:188]: Note: 1: 2262 2: _MsiPatchTransformView 3: -2147287038
MSI (s) (C0:08) [10:11:15:188]: Note: 1: 2262 2: #_BaselineCost 3: -2147287038
MSI (s) (C0:08) [10:11:15:188]: Note: 1: 2262 2: #_BaselineFile 3: -2147287038
MSI (s) (C0:08) [10:11:15:188]: Note: 1: 2262 2: #_BaselineData 3: -2147287038
MSI (s) (C0:08) [10:11:15:188]: Note: 1: 2262 2: #_PatchCache 3: -2147287038
MSI (s) (C0:08) [10:11:15:188]: APPCOMPAT: looking for appcompat database entry with ProductCode '{410ED13C-DBAD-4228-9A77-D90AF1CB6B07}'.
MSI (s) (C0:08) [10:11:15:188]: APPCOMPAT: no matching ProductCode found in database.
MSI (s) (C0:08) [10:11:15:188]: Transforms are not secure.
MSI (s) (C0:08) [10:11:15:189]: Transforming table Property.
MSI (s) (C0:08) [10:11:15:189]: PROPERTY CHANGE: Adding MsiLogFileLocation property. Its value is 'c:\temp\Genetec_Omnicast_Client_4_8_2201_19_B2.log'.
MSI (s) (C0:08) [10:11:15:189]: Command Line: TRANSFORMS=Genetec_Omnicast_Client_4_8_2201_19_B2.mst CURRENTDIRECTORY=C:\Windows\ccmcache\9i CLIENTUILEVEL=3 CLIENTPROCESSID=2900
MSI (s) (C0:08) [10:11:15:189]: PROPERTY CHANGE: Adding PackageCode property. Its value is '{AA766C40-990C-4B24-8E72-068FFF4D646D}'.
MSI (s) (C0:08) [10:11:15:189]: PROPERTY CHANGE: Adding TRANSFORMS property. Its value is '*26*Microsoft\Installer\{410ED13C-DBAD-4228-9A77-D90AF1CB6B07}\Genetec_Omnicast_Client_4_8_2201_19_B2.mst'.
MSI (s) (C0:08) [10:11:15:189]: Product Code passed to Engine.Initialize: '{410ED13C-DBAD-4228-9A77-D90AF1CB6B07}'
MSI (s) (C0:08) [10:11:15:189]: Product Code from property table before transforms: '{410ED13C-DBAD-4228-9A77-D90AF1CB6B07}'
MSI (s) (C0:08) [10:11:15:189]: Product Code from property table after transforms: '{410ED13C-DBAD-4228-9A77-D90AF1CB6B07}'
MSI (s) (C0:08) [10:11:15:189]: Product not registered: beginning first-time install
MSI (s) (C0:08) [10:11:15:189]: Determined that existing product (either this product or the product being upgraded with a patch) is installed per-user.
MSI (s) (C0:08) [10:11:15:189]: PROPERTY CHANGE: Deleting ALLUSERS property. Its current value is '1'.
MSI (s) (C0:08) [10:11:15:189]: Product {410ED13C-DBAD-4228-9A77-D90AF1CB6B07} is admin assigned: LocalSystem owns the publish key.
MSI (s) (C0:08) [10:11:15:189]: Product {410ED13C-DBAD-4228-9A77-D90AF1CB6B07} is managed.
MSI (s) (C0:08) [10:11:15:189]: MSI_LUA: Credential prompt not required, user is an admin
MSI (s) (C0:08) [10:11:15:189]: PROPERTY CHANGE: Adding ProductState property. Its value is '1'.
MSI (s) (C0:08) [10:11:15:189]: Entering CMsiConfigurationManager::SetLastUsedSource.
MSI (s) (C0:08) [10:11:15:189]: Specifed source is already in a list.
MSI (s) (C0:08) [10:11:15:189]: User policy value 'SearchOrder' is 'nmu'
MSI (s) (C0:08) [10:11:15:190]: Adding new sources is allowed.
MSI (s) (C0:08) [10:11:15:190]: Package name retrieved from configuration data: 'Genetec_Omnicast_Client_4_8_2201_19_B2.msi'
MSI (s) (C0:08) [10:11:15:190]: Note: 1: 2262 2: AdminProperties 3: -2147287038
MSI (s) (C0:08) [10:11:15:190]: Machine policy value 'DisableMsi' is 0
MSI (s) (C0:08) [10:11:15:190]: Machine policy value 'AlwaysInstallElevated' is 0
MSI (s) (C0:08) [10:11:15:190]: User policy value 'AlwaysInstallElevated' is 0
MSI (s) (C0:08) [10:11:15:190]: Product {410ED13C-DBAD-4228-9A77-D90AF1CB6B07} is admin assigned: LocalSystem owns the publish key.
MSI (s) (C0:08) [10:11:15:190]: Product {410ED13C-DBAD-4228-9A77-D90AF1CB6B07} is managed.
MSI (s) (C0:08) [10:11:15:190]: Running product '{410ED13C-DBAD-4228-9A77-D90AF1CB6B07}' with elevated privileges: Product is assigned.
MSI (s) (C0:08) [10:11:15:190]: PROPERTY CHANGE: Modifying TRANSFORMS property. Its current value is '*26*Microsoft\Installer\{410ED13C-DBAD-4228-9A77-D90AF1CB6B07}\Genetec_Omnicast_Client_4_8_2201_19_B2.mst'. Its new value: 'Genetec_Omnicast_Client_4_8_2201_19_B2.mst'.
MSI (s) (C0:08) [10:11:15:190]: PROPERTY CHANGE: Adding CURRENTDIRECTORY property. Its value is 'C:\Windows\ccmcache\9i'.
MSI (s) (C0:08) [10:11:15:190]: PROPERTY CHANGE: Adding CLIENTUILEVEL property. Its value is '3'.
MSI (s) (C0:08) [10:11:15:190]: PROPERTY CHANGE: Adding CLIENTPROCESSID property. Its value is '2900'.
MSI (s) (C0:08) [10:11:15:190]: Machine policy value 'DisableAutomaticApplicationShutdown' is 0
MSI (s) (C0:08) [10:11:15:191]: PROPERTY CHANGE: Adding MsiRestartManagerSessionKey property. Its value is '518597794e277e41aa15fee636fef8fd'.
MSI (s) (C0:08) [10:11:15:191]: RESTART MANAGER: Session opened.
MSI (s) (C0:08) [10:11:15:191]: PROPERTY CHANGE: Modifying TRANSFORMS property. Its current value is 'Genetec_Omnicast_Client_4_8_2201_19_B2.mst'. Its new value: '*26*Microsoft\Installer\{410ED13C-DBAD-4228-9A77-D90AF1CB6B07}\Genetec_Omnicast_Client_4_8_2201_19_B2.mst'.
MSI (s) (C0:08) [10:11:15:191]: TRANSFORMS property is now: *26*Microsoft\Installer\{410ED13C-DBAD-4228-9A77-D90AF1CB6B07}\Genetec_O
Property(S): DisplayNameCustom = Custom
Property(S): DisplayNameMinimal = Minimal
Property(S): DisplayNameTypical = Typical
Property(S): ErrorDialog = SetupError
Property(S): FIREWALLEXCEPTIONLIST = [INSTALLDIR]ConfigTool.exe;[INSTALLDIR]LiveViewer.exe;[INSTALLDIR]ArchivePlayer.exe
Property(S): FIXEDRIVEFOUND = no
Property(S): INSTALLLEVEL = 100
Property(S): ISSCRIPT_VERSION_MISSING = The InstallScript engine is missing from this machine. If available, please run ISScript.msi, or contact your support personnel for further assistance.
Property(S): ISVROOT_PORT_NO = 0
Property(S): IS_PROGMSG_XML_COSTING = Costing XML files...
Property(S): IS_PROGMSG_XML_CREATE_FILE = Creating XML file %s...
Property(S): IS_PROGMSG_XML_FILES = Performing XML file changes...
Property(S): IS_PROGMSG_XML_REMOVE_FILE = Removing XML file %s...
Property(S): IS_PROGMSG_XML_ROLLBACK_FILES = Rolling back XML file changes...
Property(S): IS_PROGMSG_XML_UPDATE_FILE = Updating XML file %s...
Property(S): IS_SQLSERVER_DIALOG = 0
Property(S): InstallChoice = AR
Property(S): Manufacturer = Genetec Inc.
Property(S): MsiLogging = voicewarmupx
Property(S): NET_FRAMEWORK_WIN7_MSG = Microsoft .Net Framework 3.5 SP1 must be turned on in order to continue with the installation. For information on how to do this, please see your Omnicast Installation and Upgrade Guide.
Property(S): NumOfLanguages = 0
Property(S): OMNICAST_REGISTRY_ROOT = SOFTWARE\Genetec\Genetec Omnicast4.8
Property(S): PIDTemplate = 12345<###-%%%%%%%>@@@@@
Property(S): PROGMSG_IIS_CREATEAPPPOOL = Creating application pool %s
Property(S): PROGMSG_IIS_CREATEAPPPOOLS = Creating application Pools...
Property(S): PROGMSG_IIS_CREATEVROOT = Creating IIS virtual directory %s
Property(S): PROGMSG_IIS_CREATEVROOTS = Creating IIS virtual directories...
Property(S): PROGMSG_IIS_CREATEWEBSERVICEEXTENSION = Creating web service extension
Property(S): PROGMSG_IIS_CREATEWEBSERVICEEXTENSIONS = Creating web service extensions...
Property(S): PROGMSG_IIS_EXTRACT = Extracting information for IIS virtual directories...
Property(S): PROGMSG_IIS_EXTRACTDONE = Extracted information for IIS virtual directories...
Property(S): PROGMSG_IIS_REMOVEAPPPOOL = Removing application pool
Property(S): PROGMSG_IIS_REMOVEAPPPOOLS = Removing application pools...
Property(S): PROGMSG_IIS_REMOVESITE = Removing web site at port %d
Property(S): PROGMSG_IIS_REMOVEVROOT = Removing IIS virtual directory %s
Property(S): PROGMSG_IIS_REMOVEVROOTS = Removing IIS virtual directories...
Property(S): PROGMSG_IIS_REMOVEWEBSERVICEEXTENSION = Removing web service extension
Property(S): PROGMSG_IIS_REMOVEWEBSERVICEEXTENSIONS = Removing web service extensions...
Property(S): PROGMSG_IIS_ROLLBACKAPPPOOLS = Rolling back application pools...
Property(S): PROGMSG_IIS_ROLLBACKVROOTS = Rolling back virtual directory and web site changes...
Property(S): PROGMSG_IIS_ROLLBACKWEBSERVICEEXTENSIONS = Rolling back web service extensions...
Property(S): ProductID = none
Property(S): ProductLanguage = 1033
Property(S): REBOOT = ReallySuppress
Property(S): ProductName = Genetec_Omnicast_Client_4_8_2201_19_B2
Property(S): ProgressType0 = install
Property(S): ProgressType1 = Installing
Property(S): ProgressType2 = installed
Property(S): ProgressType3 = installs
Property(S): RebootYesNo = No
Property(S): ReinstallModeText = omus
Property(S): SHOWLAUNCHPROGRAM = 0
Property(S): MSIFASTINSTALL = 2
Property(S): SecureCustomProperties = OLDVERDETECTED;SUPPORTDIR;OLDSAMEVERSIONDETECTED;CREATE_FIREWALL_RULES;INSTALLDIR
Property(S): ISReleaseFlags = GENETEC,NoFlag
Property(S): ARPINSTALLLOCATION = C:\Program Files (x86)\Genetec Omnicast Client 4.8\
Property(S): WindowsBuild = 7601
Property(S): VersionNT64 = 601
Property(S): VersionMsi = 5.00
Property(S): AdminUser = 1
Property(S): VersionDatabase = 110
Property(S): CLIENTPROCESSID = 2900
Property(S): CLIENTUILEVEL = 3
Property(S): PRODUCTLANGUAGE = 0
Property(S): LIMITUI = True
Property(S): COMPANYNAME = Yarra Trams
Property(S): ARPNOREMOVE = 1
Property(S): USERNAME = Yarra Trams
Property(S): ROOTDRIVE = C:\
Property(S): PackageCode = {AA766C40-990C-4B24-8E72-068FFF4D646D}
Property(S): TRANSFORMS = *26*Microsoft\Installer\{410ED13C-DBAD-4228-9A77-D90AF1CB6B07}\Genetec_Omnicast_Client_4_8_2201_19_B2.mst
Property(S): CURRENTDIRECTORY = C:\Windows\ccmcache\9i
Property(S): ProductState = 1
Property(S): MsiLogFileLocation = c:\temp\Genetec_Omnicast_Client_4_8_2201_19_B2.log
Property(S): ARPNOMODIFY = 1
MSI (s) (C0:08) [10:11:16:176]: Deferring clean up of packages/files, if any exist
MSI (s) (C0:08) [10:11:16:176]: MainEngineThread is returning 1603
MSI (s) (C0:E0) [10:11:16:178]: RESTART MANAGER: Session closed.
MSI (s) (C0:E0) [10:11:16:178]: No System Restore sequence number for this installation.
=== Logging stopped: 12/03/2015 10:11:16 ===
MSI (s) (C0:E0) [10:11:16:185]: User policy value 'DisableRollback' is 0
MSI (s) (C0:E0) [10:11:16:185]: Machine policy value 'DisableRollback' is 0
MSI (s) (C0:E0) [10:11:16:185]: Incrementing counter to disable shutdown. Counter after increment: 0
MSI (s) (C0:E0) [10:11:16:185]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2
MSI (s) (C0:E0) [10:11:16:186]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2
MSI (s) (C0:E0) [10:11:16:186]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1
MSI (s) (C0:E0) [10:11:16:187]: Restoring environment variables
MSI (s) (C0:E0) [10:11:16:187]: Destroying RemoteAPI object.
MSI (s) (C0:00) [10:11:16:187]: Custom Action Manager thread ending.
MSI (c) (54:B8) [10:11:16:188]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1
MSI (c) (54:B8) [10:11:16:188]: MainEngineThread is returning 1603
=== Verbose logging stopped: 12/03/2015 10:11:16 ===
MSI (s) (C0!24) [10:11:16:100]: Note: 1: 2715 2: notescfg.dll.DA2174F6_7851_4AC9_8758_F2A803F82287
MSI (s) (C0!24) [10:11:16:100]: Note: 1: 2711 2: wcsdsapi.dll.413A0FA5_373A_11D4_91AE_009027A76C22
SaveTableToIniFile: Table SeagateWebMimeType doesn't exist
Couldn't get component state for component "wcsdsapi.dll.413A0FA5_373A_11D4_91AE_009027A76C22".uReturn 1607
MSI (s) (C0:08) [10:11:16:101]: Doing action: ISSQLServerRollback
Action ended 10:11:16: GetWebInfo.A95D0BB4_0582_442D_B456_D295EAEB7628. Return value 1.
MSI (s) (C0:08) [10:11:16:102]: Transforming table CustomAction.
MSI (s) (C0:08) [10:11:16:102]: Note: 1: 2235 2: 3: ExtendedType 4: SELECT `Action`,`Type`,`Source`,`Target`, NULL, `ExtendedType` FROM `CustomAction` WHERE `Action` = 'ISSQLServerRollback'
MSI (s) (C0:08) [10:11:16:103]: Transforming table CustomAction.
MSI (s) (C0:08) [10:11:16:103]: Transforming table Binary.
Action start 10:11:16: ISSQLServerRollback.
MSI (s) (C0:08) [10:11:16:107]: Doing action: SxsInstallCA
Action ended 10:11:16: ISSQLServerRollback. Return value 1.
MSI (s) (C0:08) [10:11:16:108]: Transforming table CustomAction.
MSI (s) (C0:08) [10:11:16:108]: Note: 1: 2235 2: 3: ExtendedType 4: SELECT `Action`,`Type`,`Source`,`Target`, NULL, `ExtendedType` FROM `CustomAction` WHERE `Action` = 'SxsInstallCA'
MSI (s) (C0:08) [10:11:16:109]: Transforming table CustomAction.
MSI (s) (C0:08) [10:11:16:110]: Transforming table Binary.
MSI (s) (C0:3C) [10:11:16:119]: Invoking remote custom action. DLL: C:\WINDOWS\Installer\MSIBBCF.tmp, Entrypoint: CustomAction_SxsMsmInstall
Action start 10:11:16: SxsInstallCA.
1: sxsdelca 2: traceop 3: 1262 4: 0
1: sxsdelca 2: traceop 3: 1263 4: 0
1: sxsdelca 2: traceop 3: 1264 4: 0
1: sxsdelca 2: traceop 3: 1269 4: 0
MSI (s) (C0!60) [10:11:16:123]: Product: Genetec_Omnicast_Client_4_8_2201_19_B2 -- 1: ALLUSERS property is not 1 - this MSM cannot be used for a per-user or fallback-to-per-user install 2:
1: ALLUSERS property is not 1 - this MSM cannot be used for a per-user or fallback-to-per-user install
1: sxsdelca 2: SxsMsmInstall completed 3: 0 4: -2147467263
CustomAction SxsInstallCA returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox)
MSI (s) (C0:08) [10:11:16:133]: Machine policy value 'DisableRollback' is 0
MSI (s) (C0:08) [10:11:16:133]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2
Action ended 10:11:16: SxsInstallCA. Return value 3.
MSI (s) (C0:08) [10:11:16:134]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2
MSI (s) (C0:08) [10:11:16:134]: No System Restore sequence number for this installation.
MSI (s) (C0:08) [10:11:16:134]: Unlocking Server
MSI (s) (C0:08) [10:11:16:141]: Transforming table InstallExecuteSequence.
Action ended 10:11:16: INSTALL. Return value 3.
SCCM Deployment Technician

SCCM OSD Task sequence stuck at formatting C:

hi everyone,
Using SCCM 2012 R2 CU3 and trying to build Surface Pro 3.
I have successfully built 3 units but i have 2 units that are stuck at formatting C. Checked the logs and smsts log goes up to showing that diskpart command has been successful up until creating partitions but nothing to show after formatting drive C as
NTFS(Quick).
I have tried going into Winpe and running diskpart manually by launching F8 command prompt. Using diskpart manually, I have tried cleaning the disk altogether as well as manually creating the partition structure that SCCM TS is creating. Even if i try manually,
i get the same result. Formatting drive C never completes and gets stuck.Commandline i have tried is as below:
I have also tried creating a brand new task sequence with default UEFI partion/format options that had the same result.
If i try to view C drive through cmtrace tool ,the drive format shows up as "RAW".
Just to confirm that 3 surface pro 3's have already been built with exactly the same TS and firmware/driver pack being used is the latest from MS(JAn 2015).
Just wondering if anyone has come across something like this before??

Hi Tarun,
Any chance the drive is DOA (or on the way out)? Asking as you can't format even when trying manually.
You might have already seen these.
Johan has a post on the changes that are needed for a SCCM 2012 R2 TS and UEFI support.
http://www.deploymentresearch.com/Research/tabid/62/EntryId/139/Deploying-UEFI-machines-with-ConfigMgr-2012-R2.aspx
Also Niall Brady has a post on deploying the Surface Pro that may be of help to you.
http://www.niallbrady.com/2013/03/04/how-can-i-deploy-windows-8-x64-to-the-microsoft-surface-pro-using-configuration-manager-2012-sp1/
Sean

Install Application + Standalone task media

Hi
I am trying to image a Lenovo Tablet 2 using standalone media and it fails everytime it gets to the part of installing the applications. It says that the application must be installed in the full OS. Is this a pre-req for all SCCM 2012 applications deployed
as part of any method of task sequence. Do I always need a reboot to OS step before installing apps?
Thanks

Hi,
Yes you need a reboot to OS step before installing applications, even if you run scripts and so on, otherwise they will run in the WinPE context and not much an installer can do there. So the TS must have applied the image and rebooted to the full OS.
Regards,
Jörgen
-- My System Center blog ccmexec.com -- Twitter
@ccmexec

Reasons for not deploying applications using Task Sequence

Hi guys!
Could you provide me with some reasons why I shouldn't be using Task Sequences to deploy all of my applications? I like the idea that I can deploy multiple applications and packages at the same time, as well as being able to perform other tasks in the same
Task Sequence if needed. I also really like the progress bar window which shows end user the company and name of application being installed.
The SCCM Unleashed 2012 book mentions that while this is an available option it's not a good practice because "applications are meant to be state-based". Would someone be able to elaborate on that statement?
Is using Task Sequences for deploying applications generally a bad practice that I should try to avoid?

Hi,
here is a description for state based:
Depending on the deployment purpose you have specified in the deployment type of an application, System Center 2012 Configuration Manager periodically checks that the state of the application is the same as its purpose. For example, if an
application’s deployment type is specified as Required, Configuration Manager reinstalls the application if it has been removed. Only one deployment type can be created per application and collection pair.
If you deploy your applications by using task sequence you bypass this feature. You will install the application. but after this initial installation there will be no further check for the app to be still present on device.
You can use task sequences, but should be aware of the features you bypass in this scenario.
Regards
Eric
Eric Berg -- http://www.ericberg.de -- MCSE: Private Cloud MCSE: Server Infrastructure MCSE: Desktop Infrastructure

Need help with a simple Rename/Join Domain/Install SCCM Client Task Sequence

Good morning everyone,
I need to create a very simple task sequence that will run an .exe that we have created that renames the computer based on a prefix-serialnumber...then restarts, adds it to our domain, restarts, and then installs the SCCM client.
1) run rename program
2) join to domain
3) install sccm client
Can someone help me with the steps that will be required for this?
Thank you very much!
**note, these will not be formatted/have an OS installation ran on it with this task sequence. The situation is that we are receiving 400+ custom configured laptops, and we're going to have to rename/join/install sccm on each...trying to simplify
this
any recommendations are greatly appreciated!

Narcoticoo : Which boot image am i supposed to be using to insure that it boots into Standard Windows, NOT WinPE? I have a standard x86 package / boot image i've been using. If it boots up with this, it goes into WinPE (correct me if I'm wrong,
for this seems to be what happens each time it boots off the boot image...it does not go into windows standard/full)
When I go into properties of the one i'm using, and take the check off of "Use a boot image", where it will not boot to WinPE, it will not even show up in my list of available task sequences for
1) when I PXE boot to try the task sequence, or
2) when I try to make stand-alone media for this task sequence as you have suggested
When I run the standalone media, the only log files I find are the following with errors:
PackageID = 'MPS0014E' InstallSoftware
12/8/2014 12:28:36 PM 2344 (0x0928)
BaseVar = '', ContinueOnError='' InstallSoftware
12/8/2014 12:28:36 PM 2344 (0x0928)
ProgramName = 'MPHS - Rename Computer' InstallSoftware
12/8/2014 12:28:36 PM 2344 (0x0928)
SwdAction = '0002' InstallSoftware
12/8/2014 12:28:36 PM 2344 (0x0928)
IsSMSV4PlusClient() == true, HRESULT=80004005 (e:\nts_sccm_release\sms\client\osdeployment\installsoftware\main.cpp,332)
InstallSoftware 12/8/2014 12:28:36 PM
2344 (0x0928)
Configuration Manager client is not installed
InstallSoftware 12/8/2014 12:28:36 PM
2344 (0x0928)
Process completed with exit code 2147500037
TSManager 12/8/2014 12:28:36 PM
1544 (0x0608)
TSManager 12/8/2014 12:28:36 PM
1544 (0x0608)
Failed to run the action: Install Package.
Unspecified error (Error: 80004005; Source: Windows)
TSManager 12/8/2014 12:28:36 PM
1544 (0x0608)
Failed to run the action: Install Package. Execution has been aborted
TSManager 12/8/2014 12:28:36 PM
1544 (0x0608)
Do not send status message in full media case
TSManager 12/8/2014 12:28:36 PM
1544 (0x0608)
Failed to run the last action: Install Package. Execution of task sequence failed.
Unspecified error (Error: 80004005; Source: Windows)
TSManager 12/8/2014 12:28:36 PM
1544 (0x0608)
Do not send status message in full media case
TSManager 12/8/2014 12:28:36 PM
1544 (0x0608)
Execution::enExecutionFail != m_eExecutionResult, HRESULT=80004005 (e:\nts_sccm_release\sms\client\tasksequence\tsmanager\tsmanager.cpp,866)
TSManager 12/8/2014 12:43:48 PM
1544 (0x0608)
Task Sequence Engine failed! Code: enExecutionFail
TSManager 12/8/2014 12:43:48 PM
1544 (0x0608)
TSManager 12/8/2014 12:43:48 PM
1544 (0x0608)
Task sequence execution failed with error code 80004005
TSManager 12/8/2014 12:43:48 PM
1544 (0x0608)

MDT 2013 - Install Application in Task Sequence Stuck

Similar Messages

Maybe you are looking for