Windows 8.1 UDI Task Sequence black background on Install software part
Hi,
when deploying Windows 8.1 to our notebooks, first part of task sequence we got normal background like shown here:
but after applying OS and drivers and installing CM client, TS goes to installing software but with this black screen:
It all goes well at the end, TS finishes successfully but the question is why is this behavior happening?
Smsts.log and execmgr.log attached:
http://www.sendspace.com/filegroup/CK6%2FNXIafvRcZJUmUNg32g
Using:
SCCM 2012 R2 CU4
MDT 2013
Thank you,
Hi Yannara,
I would not agree because in Windows 7 deployment we got the above screen through the whole process, but as I said in Windows 8.1 deployment process during install software step screen is black.
With Windows 7, are you really saying, that the entire W7 deployment has a graphical background running all the time? My W7 and W8.1 looks alike, W7 most of the time saying on a black screen something like "prepare for the first time use" and Apps
and Updates are installing during that stage.
But, yes I might be wrong though :)
Similar Messages
-
I am trying to get Office 2010 to install using a UDI task sequence, and it IS installing, but it has a yellow exclamation point next to it at the summary screen after the task sequence completes, as does another app I am trying to install.
The apps that use an .MSI are fine, and get the green check, but the two apps that use .exe for their installers get the yellow warning sign. I assume this has to do with exit codes or detection rules, but I am very new to SCCM (using 2012 and MDT
2012 Update 1), so I need some help.
Thank you!
EDIT: This probably has to do with the fact that SuccessOrFailureCode being blank. I have been pouring over .vbs scripts and logs, but they all seem to indicate that my application installs just fine, with an exit code of 0. Where does this screen
get the SuccessOrFailureCode?
Like
This
Quote
MultiQuote
EditI have some updated info on this problem.
I am trying to install Symantec Endpoint Protection with a custom wrapped .EXE file, and I have created detection rules for the install.
According to AppEnforce.log, SEP is installing and returning an Exit code of '1', and that is being handled with my custom return code handling, which I've defined as a 'success'. However, the deployment summary is still showing a yellow exclamation point
next to the SEP install, and the SuccessOrFailureCode is blank.
Why isn't the SuccessOrFailureCode equal to '1'? Where is the disconnect between the AppEnforce.log and the deployment summary. -
N82 Black background after installing new maps
My N82 Maps show just a black background after installing latest maps for Middle east with new map loader. I am using Maps Version 2.0 Any help?
I just spent 1 1/2 hours on the phone with HP Tech Support but it was worth it. They are sending a replacement printer no charge to me (expect I chose to pay extra for next day shipping). Even though my printer is out of warranty!!! I normally buy HP products anyway but will definintely stay with this brand based on their excellent customer service and support. Thank you once again for your initial help online and for directing me on the right path!!!
-
Maintenance windows applies only to task sequences doesn't work
Problem:
SCCM 2012 R2 CU4
Task sequence deployment run outside maintenance windows when the maintenance windows is set to apply only to task sequences.
When the maintenance windows is set to apply to All deployments, the task sequence deployment run inside maintenance windows as expected.
The maintenance task defined was as:
Name: Maintenance Windows of Collection Coll_A
Time: 10:30am to 06:00am
Date: 20th March 2015
Apply this schedule to: Task Sequences
The task sequence defined was as:
Deployed to Collection Coll_A
Time: Run as soon as possible
The task sequence run at 9:48am on a workstation that is member of Coll_A.
There aren't other maintenances windows on others collections.
Below the workstation's serviceWindowsManager.log:
https://onedrive.live.com/redir?resid=BFBF530F33D996FD!123&authkey=!AI0dFPZ89XCL7xs&ithint=file%2clogWhen was the client added to the collection? Was it able to retrieve those MW policies before it received the TS?
Torsten Meringer | http://www.mssccmfaq.de
1_the client was added at the 9:30am.
2_Yes it is.
I have done another test and the result is the same:
_ first setting up the maintenance windows in Coll_A,
_ then insert the client in Coll_A and force a machine policy evaluation
_then deploy the task sequence in collection Coll_A -
Enabling Remote Desktop for Windows 7 as a task sequence
Hi there.
I have a task sequence to automate the creation of a base image of Windows 7 x64 Professional. In my base image I would like to have Remote Desktop enabled by default for all users. Is there a command or a script to do this that I can add into my task sequence to make this possible?
Thanks.I have to agree except I can't understand why anyone would use anything other than the unattend.xml. You can do all that plus so much more and it's the way Microsoft provides to do it. This is my complete x64 unattend.xml version but I also have
an x86 version. This should give you some idea of it's capabilities.
Drop the unattend.xml file into a package and reference it in the Task Sequence as shown below. I dropped both my x86 and x64 version of the unattend.xml into the package. I use an OSD HTA menu on the frontend to let helpdesk pick
between x86 and x64. I cropped the picture up a bit and took out company specific info but you should get the idea from the screen captures. This is how I deploy x86 and x64 in a single task sequence. I mark every line with a condition in the task
sequence with (C) which makes it easier to find lines with conditions. I use the condition to assign x86 and x64 software among other things. The selection in the HTA pretty much triggers everything.
<?xml version="1.0" encoding="utf-8"?>
<unattend xmlns="urn:schemas-microsoft-com:unattend" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<settings pass="auditSystem">
</settings>
<settings pass="auditUser">
</settings>
<settings pass="generalize">
</settings>
<settings pass="offlineServicing">
</settings>
<settings pass="oobeSystem">
<component name="Microsoft-Windows-Shell-Setup" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS">
<OOBE>
<HideEULAPage>true</HideEULAPage>
<NetworkLocation>Work</NetworkLocation>
<SkipMachineOOBE>false</SkipMachineOOBE>
<SkipUserOOBE>false</SkipUserOOBE>
<ProtectYourPC>3</ProtectYourPC>
</OOBE>
<UserAccounts>
<DomainAccounts>
<DomainAccountList wcm:action="add">
<DomainAccount wcm:action="add">
<Name>Workstation Admins</Name>
<Group>Administrators</Group>
</DomainAccount>
<Domain>DOMAIN</Domain>
</DomainAccountList>
</DomainAccounts>
</UserAccounts>
</component>
</settings>
<settings pass="specialize">
<component name="Microsoft-Windows-LUA-Settings" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<EnableLUA>false</EnableLUA>
</component>
<component name="Security-Malware-Windows-Defender" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="
http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance ">
<DisableAntiSpyware>true</DisableAntiSpyware>
</component>
<component name="Microsoft-Windows-SystemRestore-Main" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<DisableSR>1</DisableSR>
</component>
<component name="Networking-MPSSVC-Svc" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<DomainProfile_EnableFirewall>false</DomainProfile_EnableFirewall>
<PrivateProfile_EnableFirewall>true</PrivateProfile_EnableFirewall>
<PublicProfile_EnableFirewall>true</PublicProfile_EnableFirewall>
</component>
<component name="Microsoft-Windows-Deployment" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS">
<RunSynchronous>
<RunSynchronousCommand wcm:action="add">
<Path>reg add "HKLM\SOFTWARE\Policies\Microsoft\Windows NT\CurrentVersion\NetworkList\Signatures\FirstNetwork" /v Category /t REG_DWORD /d 00000000 /f</Path>
<Description>Setting Network Location</Description>
<Order>1</Order>
</RunSynchronousCommand>
</RunSynchronous>
</component>
<component name="Microsoft-Windows-TerminalServices-LocalSessionManager" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<fDenyTSConnections>false</fDenyTSConnections>
</component>
<component name="Microsoft-Windows-IE-InternetExplorer" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<DisableAccelerators>true</DisableAccelerators>
<DisableOOBAccelerators>true</DisableOOBAccelerators>
<SuggestedSitesEnabled>false</SuggestedSitesEnabled>
<DisableFirstRunWizard>true</DisableFirstRunWizard>
<DisableWelcomePage>true</DisableWelcomePage>
<Home_Page>http://www.google.com</Home_Page>
<SearchScopes>
<Scope wcm:action="add">
<ScopeDefault>true</ScopeDefault>
<ScopeDisplayName>Google</ScopeDisplayName>
<ScopeKey>SearchProvider1</ScopeKey>
<ScopeUrl>http://www.google.com/search?q={searchTerms}</ScopeUrl>
</Scope>
</SearchScopes>
</component>
<component name="Microsoft-Windows-Shell-Setup" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS">
<TimeZone>Central Standard Time</TimeZone>
</component>
</settings>
</unattend> -
How To: Deploying Windows & Office updates during task sequence
How do you guys apply windows and office updates during the task sequence?
Right now for Windows, I am offline servicing using my software deployment package.
For Office, I had the software deployment package, but can't figure out how to add it to my task sequence. All the options don't allow me to choose the package.
My end goal is to keep everything as up to date as possible, and if people image a computer and run Windows Update, they only have to download 10 or less updates, not 100+.Is Office part of your image or do you deploy Office as part of your task sequence?
If office is part of your image, i'd recommend that you create a fully automated build and capture process using the MDT lite touch, and use a separate WSUS server to update the image with Windows , Office and other updates.
It's pretty easy to setup.
Creating a Windows 8.1 reference image:
http://go.microsoft.com/?linkid=9845755
If Office is not part of the image, you need to deploy the updates using Software Updates In SCCM as part of your Task Sequence.
Ronni Pedersen | Microsoft MVP - ConfigMgr | Blogs:
www.ronnipedersen.com/ and www.SCUG.dk/ | Twitter
@ronnipedersen
It's a task sequence. I'm confused how Software Updates works with SCCM because I do not want to use it to update All Systems. I only want to update it to computers that get imaged which are Unknown Computers. We have WSUS to take care of updates.
If I deploy to Unknown Computers the updates in SCCM, once it joins the domain though to install all the other applications in the task sequence, will updates still go through now that it isn't a "Unknown ComputeR"? -
Operating System Package Section Window is blank for Task Sequence
Trying to create a capture and build sequence. I have added Win7 x64 to the 'Operating System Installers' section. But when going into 'Create Task Sequence' I dont have any operating systems to select. (see screenshot).
Only info I found on the web references to beta versions of SCCM 2012. I added server is SCCM 2012 R2 Update 1. (version 5.00.7958.1000).
Any Suggestions?During the Create Task Sequence Wizard, this step requires to use a
Operating System Image (a WIM file) and not a Operating System Installer.
An Operating System Installer can only be used by editing the task sequence after the wizard.
My Blog: http://www.petervanderwoude.nl/
Follow me on twitter: pvanderwoude -
Applications Installed through task sequence not showing up in Software Center
In the task sequence we use for our OSD Windows 7 machine build, we have Custom-Install Application steps which install a number of of our Applications. Each of these Applications has the "Allow this application to be installed from the Install
Application task sequence action without being deployed" checkbox checked. All of the Applications have the following properties set:
Installation behavior: Install for system
Logon requirement: Whether or not a user is logged in
Installation program visibility: Hidden
When a machine is built using this task sequence, all of the Applications install successfully - they show up in Control Panel\Programs and Features, and they run correctly. However, none of them show up in the Software Center. I'm not seeing anything in
any of the logs that indicates a problem, and the Software Center remains empty even after running all the client evaluation cycle actions
Interestingly, if I add a couple of the newly build machines to a collection, then target deployments for the already installed Applications to that collection, after running the Machine Policy Retrieval and Evaluation Cycle the Applications immediately
show up in Software Center as installed.
Does anyone know if Applications installed through a task sequence do not show up in the Software Center by default, or could you give me some troubleshooting tips if this is not normal?
Thanks for any suggestions!
SCCM 2012 SP1, Single site, W7 clientsWhy you deploy applications through task sequences? Task sequences are built and meant to be used with OSD, not application deployment.
To my knowledge, if you have application install step in a task sequence and you deploy that task sequence to a collection of machines, the software center on those machines only sees the task sequence itself, not the applications inside the task sequence.
If you want your applications to be shown in the software center, change the method of deploying stuff and deploy applications as they're are meant to. -
OSD Task Sequence Applications Fail to Install
Hello,
In my task sequence, any application that i add fails to install with Error Code 0x87d00215. Outside of the task sequence the
applications install with no problems.
A couple things that i have verified already
DP is set to allow clients to connect anonymously
Network Access Account is set and verified
Setting on the application for Allow
this application to be installed from the Install Application task sequence action instead of deploying it manually is set
Boundaries are set correctly as software installs correctly outside of the TS
Logs that do not show errors
IIS logs - Check out just fine
Location Services - Does not show any errors and finds the AD Forest/Site and MP successfully
CAS Log - Does not show any errors with the correct date
Data Transfer Log - Does not show any error with the correct date
Any ideas would be greatly appreciated.
ThanksThe AppEnforce log is empty and below are some bits from the AppDiscovery log and the AppIntentEval log which I did not see anything unusual.
AppDiscovery.log
Performing detection of app deployment type VMware Tools x32(ScopeId_20103BB4-95B0-4938-BBD1-B4F09F714BDF/DeploymentType_9fbcb77f-c553-45d8-9d5b-b4a6c2c0d4a1, revision 2) for system.
+++ Application not discovered. [AppDT Id: ScopeId_20103BB4-95B0-4938-BBD1-B4F09F714BDF/DeploymentType_9fbcb77f-c553-45d8-9d5b-b4a6c2c0d4a1, Revision: 2]
+++ Did not detect app deployment type VMware Tools x32(ScopeId_20103BB4-95B0-4938-BBD1-B4F09F714BDF/DeploymentType_9fbcb77f-c553-45d8-9d5b-b4a6c2c0d4a1, revision 2) for system.
Entering ExecQueryAsync for query "select * from CCM_AppDeliveryType where (AppDeliveryTypeId = "ScopeId_20103BB4-95B0-4938-BBD1-B4F09F714BDF/DeploymentType_955d0646-14a5-47d6-8146-be5811818c8f" AND Revision = 2)"
Performing detection of app deployment type Adobe AIR - Windows Installer (Native)(ScopeId_20103BB4-95B0-4938-BBD1-B4F09F714BDF/DeploymentType_955d0646-14a5-47d6-8146-be5811818c8f, revision 2) for system.
+++ Application not discovered. [AppDT Id: ScopeId_20103BB4-95B0-4938-BBD1-B4F09F714BDF/DeploymentType_955d0646-14a5-47d6-8146-be5811818c8f, Revision: 2]
+++ Did not detect app deployment type Adobe AIR - Windows Installer (Native)(ScopeId_20103BB4-95B0-4938-BBD1-B4F09F714BDF/DeploymentType_955d0646-14a5-47d6-8146-be5811818c8f, revision 2) for system.
Entering ExecQueryAsync for query "select * from CCM_AppDeliveryType where (AppDeliveryTypeId = "ScopeId_20103BB4-95B0-4938-BBD1-B4F09F714BDF/DeploymentType_fb1b4e3f-0600-4682-a865-37ec2bdf3255" AND Revision = 1)"
Performing detection of app deployment type Adobe Reader X MUI - Windows Installer (Native)(ScopeId_20103BB4-95B0-4938-BBD1-B4F09F714BDF/DeploymentType_fb1b4e3f-0600-4682-a865-37ec2bdf3255, revision 1) for system.
+++ MSI application not discovered [MSI Product Code: {AC76BA86-7AD7-FFFF-7B44-AA0000000001}, MSI Product version: ]
+++ Did not detect app deployment type Adobe Reader X MUI - Windows Installer (Native)(ScopeId_20103BB4-95B0-4938-BBD1-B4F09F714BDF/DeploymentType_fb1b4e3f-0600-4682-a865-37ec2bdf3255, revision 1) for system.
Entering ExecQueryAsync for query "select * from CCM_AppDeliveryType where (AppDeliveryTypeId = "ScopeId_20103BB4-95B0-4938-BBD1-B4F09F714BDF/DeploymentType_7b131081-c490-4a74-9595-c97a03b54bf2" AND Revision = 2)"
Performing detection of app deployment type Adobe Shockwave Player 11.6 - Windows Installer (Native)(ScopeId_20103BB4-95B0-4938-BBD1-B4F09F714BDF/DeploymentType_7b131081-c490-4a74-9595-c97a03b54bf2, revision 2) for system.
+++ Application not discovered. [AppDT Id: ScopeId_20103BB4-95B0-4938-BBD1-B4F09F714BDF/DeploymentType_7b131081-c490-4a74-9595-c97a03b54bf2, Revision: 2]
+++ Did not detect app deployment type Adobe Shockwave Player 11.6 - Windows Installer (Native)(ScopeId_20103BB4-95B0-4938-BBD1-B4F09F714BDF/DeploymentType_7b131081-c490-4a74-9595-c97a03b54bf2, revision 2) for system.
Entering ExecQueryAsync for query "select * from CCM_AppDeliveryType where (AppDeliveryTypeId = "ScopeId_20103BB4-95B0-4938-BBD1-B4F09F714BDF/DeploymentType_dc3e58ae-3e78-4ba5-8e13-8b4e565899c4" AND Revision = 6)"
Performing detection of app deployment type Flash(ScopeId_20103BB4-95B0-4938-BBD1-B4F09F714BDF/DeploymentType_dc3e58ae-3e78-4ba5-8e13-8b4e565899c4, revision 6) for system.
+++ Application not discovered. [AppDT Id: ScopeId_20103BB4-95B0-4938-BBD1-B4F09F714BDF/DeploymentType_dc3e58ae-3e78-4ba5-8e13-8b4e565899c4, Revision: 6]
+++ Did not detect app deployment type Flash(ScopeId_20103BB4-95B0-4938-BBD1-B4F09F714BDF/DeploymentType_dc3e58ae-3e78-4ba5-8e13-8b4e565899c4, revision 6) for system.
Entering ExecQueryAsync for query "select * from CCM_AppDeliveryType where (AppDeliveryTypeId = "ScopeId_20103BB4-95B0-4938-BBD1-B4F09F714BDF/DeploymentType_f5c8beed-13f7-4c10-82f6-640c7c314038" AND Revision = 2)" AppDiscovery 5/23/2012 3:10:56 PM 3520
(0x0DC0)
Performing detection of app deployment type VMware Tools x64(ScopeId_20103BB4-95B0-4938-BBD1-B4F09F714BDF/DeploymentType_f5c8beed-13f7-4c10-82f6-640c7c314038, revision 2) for system
+++ Application not discovered. [AppDT Id: ScopeId_20103BB4-95B0-4938-BBD1-B4F09F714BDF/DeploymentType_f5c8beed-13f7-4c10-82f6-640c7c314038, Revision: 2]
+++ Did not detect app deployment type VMware Tools x64(ScopeId_20103BB4-95B0-4938-BBD1-B4F09F714BDF/DeploymentType_f5c8beed-13f7-4c10-82f6-640c7c314038, revision 2) for system.
AppIntectEval.log
ScopeId_20103BB4-95B0-4938-BBD1-B4F09F714BDF/DeploymentType_01c75763-a985-4a58-99fc-35e5b5380106/2 :- Current State = NotInstalled, Applicability = Applicable, ResolvedState = Available, Title = Project 2010 Pro - Silent AppIntentEval 5/23/2012
3:10:56 PM 1912 (0x0778)
ScopeId_20103BB4-95B0-4938-BBD1-B4F09F714BDF/DeploymentType_4680375d-efcf-411b-8901-233d7a9694aa/1 :- Current State = NotInstalled, Applicability = NotApplicable, ResolvedState = None, Title = Autodesk 2012 64bit AppIntentEval 5/23/2012 3:10:56 PM 1912
(0x0778)
ScopeId_20103BB4-95B0-4938-BBD1-B4F09F714BDF/DeploymentType_5f72c7c1-b695-4f8d-b754-f8f6d1aa4046/9 :- Current State = NotInstalled, Applicability = Applicable, ResolvedState = Available, Title = Autodesk 2012 32bit AppIntentEval 5/23/2012 3:10:56
PM 1912 (0x0778)
ScopeId_20103BB4-95B0-4938-BBD1-B4F09F714BDF/DeploymentType_7b131081-c490-4a74-9595-c97a03b54bf2/2 :- Current State = NotInstalled, Applicability = Applicable, ResolvedState = Available, Title = Adobe Shockwave Player 11.6 - Windows Installer (Native) AppIntentEval 5/23/2012
3:10:56 PM 1912 (0x0778)
ScopeId_20103BB4-95B0-4938-BBD1-B4F09F714BDF/DeploymentType_9365b2e3-d0a3-4486-88bb-a7071d9b047b/4 :- Current State = NotInstalled, Applicability = Applicable, ResolvedState = Available, Title = LogMeIn - Windows Installer (Native) AppIntentEval 5/23/2012
3:10:56 PM 1912 (0x0778)
ScopeId_20103BB4-95B0-4938-BBD1-B4F09F714BDF/DeploymentType_955d0646-14a5-47d6-8146-be5811818c8f/2 :- Current State = NotInstalled, Applicability = Applicable, ResolvedState = Available, Title = Adobe AIR - Windows Installer (Native) AppIntentEval 5/23/2012
3:10:56 PM 1912 (0x0778)
ScopeId_20103BB4-95B0-4938-BBD1-B4F09F714BDF/DeploymentType_9fbcb77f-c553-45d8-9d5b-b4a6c2c0d4a1/2 :- Current State = NotInstalled, Applicability = Applicable, ResolvedState = Available, Title = VMware Tools x32 AppIntentEval 5/23/2012 3:10:56 PM 1912
(0x0778)
ScopeId_20103BB4-95B0-4938-BBD1-B4F09F714BDF/DeploymentType_dc3e58ae-3e78-4ba5-8e13-8b4e565899c4/6 :- Current State = NotInstalled, Applicability = Applicable, ResolvedState = Available, Title = Flash AppIntentEval 5/23/2012 3:10:56 PM 1912 (0x0778)
ScopeId_20103BB4-95B0-4938-BBD1-B4F09F714BDF/DeploymentType_f5c8beed-13f7-4c10-82f6-640c7c314038/2 :- Current State = NotInstalled, Applicability = NotApplicable, ResolvedState = None, Title = VMware Tools x64 AppIntentEval 5/23/2012 3:10:56 PM 1912
(0x0778)
ScopeId_20103BB4-95B0-4938-BBD1-B4F09F714BDF/DeploymentType_f8a1de4d-ffa9-4ba6-b51b-7e9a6810cfda/3 :- Current State = NotInstalled, Applicability = Applicable, ResolvedState = Available, Title = Silent Install AppIntentEval 5/23/2012 3:10:56 PM 1912
(0x0778)
ScopeId_20103BB4-95B0-4938-BBD1-B4F09F714BDF/DeploymentType_fb1b4e3f-0600-4682-a865-37ec2bdf3255/1 :- Current State = NotInstalled, Applicability = Applicable, ResolvedState = Available, Title = Adobe Reader X MUI - Windows Installer (Native) AppIntentEval 5/23/2012
3:10:56 PM 1912 (0x0778)
ScopeId_20103BB4-95B0-4938-BBD1-B4F09F714BDF/Application_07eed4d3-7acf-4717-93f9-74f717a191b4/5 :- Current State = NotInstalled, Applicability = Applicable, ResolvedState = Available, Title = LogMeIn Client AppIntentEval 5/23/2012 3:10:56 PM 1912
(0x0778)
ScopeId_20103BB4-95B0-4938-BBD1-B4F09F714BDF/Application_0bce5378-1b95-45ea-b210-e72cb65b2b37/3 :- Current State = NotInstalled, Applicability = Applicable, ResolvedState = Available, Title = Project 2010 Pro AppIntentEval 5/23/2012 3:10:56 PM 1912
(0x0778)
ScopeId_20103BB4-95B0-4938-BBD1-B4F09F714BDF/Application_808fe5d5-5b90-48aa-83cb-f5497d534691/6 :- Current State = NotInstalled, Applicability = Applicable, ResolvedState = Available, Title = VMware Tools AppIntentEval 5/23/2012 3:10:56 PM 1912
(0x0778)
ScopeId_20103BB4-95B0-4938-BBD1-B4F09F714BDF/Application_b1a04314-2a3a-47e2-98a0-ff09fc8e3948/3 :- Current State = NotInstalled, Applicability = Applicable, ResolvedState = Available, Title = Adobe AIR AppIntentEval 5/23/2012 3:10:56 PM 1912
(0x0778)
ScopeId_20103BB4-95B0-4938-BBD1-B4F09F714BDF/Application_b614de9b-5133-4788-a013-71c7de98a233/11 :- Current State = NotInstalled, Applicability = Applicable, ResolvedState = Available, Title = AutoCAD 2012 AppIntentEval 5/23/2012 3:10:56 PM 1912
(0x0778)
ScopeId_20103BB4-95B0-4938-BBD1-B4F09F714BDF/Application_c4ccbd68-7c0f-4b79-9437-eba3cb46e90c/5 :- Current State = NotInstalled, Applicability = Applicable, ResolvedState = Available, Title = Shockwave Player 11.6 AppIntentEval 5/23/2012 3:10:56 PM 1912
(0x0778)
ScopeId_20103BB4-95B0-4938-BBD1-B4F09F714BDF/Application_dec4acbc-b968-41d9-82e6-3f7767467c8e/2 :- Current State = NotInstalled, Applicability = Applicable, ResolvedState = Available, Title = Reader X AppIntentEval 5/23/2012 3:10:56 PM 1912 (0x0778)
ScopeId_20103BB4-95B0-4938-BBD1-B4F09F714BDF/Application_e4048d56-cfa1-43e0-b4df-f30b6a834828/3 :- Current State = NotInstalled, Applicability = Applicable, ResolvedState = Available, Title = Application Virtualization Client with SP1 and HF4 AppIntentEval 5/23/2012
3:10:56 PM 1912 (0x0778)
ScopeId_20103BB4-95B0-4938-BBD1-B4F09F714BDF/Application_ee3b1dcf-e401-44fe-8283-a6e5721dac11/10 :- Current State = NotInstalled, Applicability = Applicable, ResolvedState = Available, Title = Adobe Flash Player AppIntentEval 5/23/2012 3:10:56 PM 1912
(0x0778)
ScopeId_20103BB4-95B0-4938-BBD1-B4F09F714BDF/RequiredApplication_07eed4d3-7acf-4717-93f9-74f717a191b4/5 :- Current State = NonCompliant, Applicability = Applicable, ResolvedState = Compliant, Title = ApplicationIntentPolicy AppIntentEval 5/23/2012
3:10:56 PM 1912 (0x0778)
ScopeId_20103BB4-95B0-4938-BBD1-B4F09F714BDF/RequiredApplication_0bce5378-1b95-45ea-b210-e72cb65b2b37/3 :- Current State = NonCompliant, Applicability = Applicable, ResolvedState = Compliant, Title = ApplicationIntentPolicy AppIntentEval 5/23/2012
3:10:56 PM 1912 (0x0778)
ScopeId_20103BB4-95B0-4938-BBD1-B4F09F714BDF/RequiredApplication_808fe5d5-5b90-48aa-83cb-f5497d534691/6 :- Current State = NonCompliant, Applicability = Applicable, ResolvedState = Compliant, Title = ApplicationIntentPolicy AppIntentEval 5/23/2012
3:10:56 PM 1912 (0x0778)
ScopeId_20103BB4-95B0-4938-BBD1-B4F09F714BDF/RequiredApplication_b1a04314-2a3a-47e2-98a0-ff09fc8e3948/3 :- Current State = NonCompliant, Applicability = Applicable, ResolvedState = Compliant, Title = ApplicationIntentPolicy AppIntentEval 5/23/2012
3:10:56 PM 1912 (0x0778)
ScopeId_20103BB4-95B0-4938-BBD1-B4F09F714BDF/RequiredApplication_b614de9b-5133-4788-a013-71c7de98a233/11 :- Current State = NonCompliant, Applicability = Applicable, ResolvedState = Compliant, Title = ApplicationIntentPolicy AppIntentEval 5/23/2012
3:10:56 PM 1912 (0x0778)
ScopeId_20103BB4-95B0-4938-BBD1-B4F09F714BDF/RequiredApplication_c4ccbd68-7c0f-4b79-9437-eba3cb46e90c/5 :- Current State = NonCompliant, Applicability = Applicable, ResolvedState = Compliant, Title = ApplicationIntentPolicy AppIntentEval 5/23/2012
3:10:56 PM 1912 (0x0778)
ScopeId_20103BB4-95B0-4938-BBD1-B4F09F714BDF/RequiredApplication_dec4acbc-b968-41d9-82e6-3f7767467c8e/2 :- Current State = NonCompliant, Applicability = Applicable, ResolvedState = Compliant, Title = ApplicationIntentPolicy AppIntentEval 5/23/2012
3:10:56 PM 1912 (0x0778)
ScopeId_20103BB4-95B0-4938-BBD1-B4F09F714BDF/RequiredApplication_e4048d56-cfa1-43e0-b4df-f30b6a834828/3 :- Current State = NonCompliant, Applicability = Applicable, ResolvedState = Compliant, Title = ApplicationIntentPolicy AppIntentEval 5/23/2012
3:10:56 PM 1912 (0x0778)
ScopeId_20103BB4-95B0-4938-BBD1-B4F09F714BDF/RequiredApplication_ee3b1dcf-e401-44fe-8283-a6e5721dac11/10 :- Current State = NonCompliant, Applicability = Applicable, ResolvedState = Compliant, Title = ApplicationIntentPolicy AppIntentEval 5/23/2012
3:10:56 PM 1912 (0x0778) -
Windows vista 32 Bit Ultimate. Black screen after installing drivers B-Camp
I installed windows vista Ultimate 32 bit on my 2.26ghz mac mini 2gb ram. after installing vista and setting up my account, i installed the drivers from the apple CD that came with the mac. it installed all the drivers and requested me to reboot, so i did. once i rebooted, i got a black screen with a thin green line through the center of the screen. i hear the bootup sound but that is all i see. Any tips or anything on how to fix this?
How did you solve this? I am having the same problem.
-
Task sequence failing on Windows 8
I'm getting the following in the TSAgent.log on a Win8 Pro machine running ConfigMgr 2012 SP1 client:
<![LOG[Cannot find ClientConfig CCM_ClientAgentConfig]LOG]!><time="12:43:06.295+00" date="03-13-2013" component="TSAgent" context="" type="2" thread="3524"
file="tspolicy.cpp:1696">
<![LOG[Error initializing policy environment variables. Code 0x80040105]LOG]!><time="12:43:06.295+00" date="03-13-2013" component="TSAgent" context="" type="3" thread="3524" file="tslauncher.cpp:263">
<![LOG[Error initializing TS environment. Code 0x80040105]LOG]!><time="12:43:06.295+00" date="03-13-2013" component="TSAgent" context="" type="3" thread="3524" file="tslauncher.cpp:855">
<![LOG[Task sequence launcher advertisement failed!. Code 0x80040105]LOG]!><time="12:43:06.295+00" date="03-13-2013" component="TSAgent" context="" type="3" thread="3524" file="tslauncher.cpp:963">
<![LOG[CTSAgent::Execute - Failed to launch Task Sequence manager.]LOG]!><time="12:43:06.311+00" date="03-13-2013" component="TSAgent" context="" type="3" thread="3524" file="ctsagent.cpp:63">
The same task sequence works fine on Windows 7. The task sequence is configured to install a bunch of applications using the "Install Application" step.
Thanks
SteveI am seeing this with my customer with a WIndows Server 2008 R2 client. Its in a workgroup, install the client manually (CCMSETUP run locally). I approve the client and add it to a collection with a mandatory TS (non-OSD). It just hangs at "Installing..."
and I get the same errors above in TSAgent.log.
If I uninstall/reinstall the client some time fixes this. Any ideas what would cause its?
SCCM 2012 R2
TSAgentLog:
Successfully read 25 policy assignments
Unable to get NAACnfig in CCM_NetworkAccessAccount
Cannot find ClientCOnfig CCM_ClientAgentConfig
Error initializing policy environment variables. Code 0x80040105
Error initializing TS environment. Code 0x80040105
Task sequence launcher advertisement fail!, Code 0x800401015
CTSAgent::Execute - Failed to launch Task Sequence Manager
Levi Stevens | Technical Consultant Dell Services -
Occasional Task Sequence fail (1 out of 5) with Error 615 Your Password is too short
We have a task sequence that fails to install software and updates with an error liek this: Operation System Error 615: The password you provided was too short for the computers password policy. Please provide a longer password.
With all software installations I always tick the continue on failure. Consequently in a task sequence you see the entire list of installation requirements fail with this error. This includes Applications, Packages and Software Updates. Without any amendment,
the next time it is run, it runs successfully. Add to this the issue that the task sequence no longer displays the progress bar after rebooting into windows (x64) and it all points to the OSD process being a bit flaky.
By the way, we are installing Win7 x64 (No x86 anymore) over PXE.
So any pointers with this would be very gratefully received.
Anthony Sheehy - MCP, MCITPHere is the status message sent to Configuration Manager:
The task sequence execution engine failed executing the action (Freefall Sensor) in the group (Install) with the error code 2278559764
Action output: 7"'
Verified policy is compiled in 'root\ccm\policy\machine' namespace
content location count = 1
Invoking Execution Manager to install software
FALSE, HRESULT=87d01014 (e:\nts_sccm_release\sms\client\osdeployment\installsoftware\installsoftware.cpp,251)
0, HRESULT=87d01014 (e:\nts_sccm_release\sms\client\osdeployment\installsoftware\installsoftware.cpp,764)
Entering ReleaseSource() for C:\_SMSTaskSequence\Packages\WGS00137
reference count 1 for the source C:\_SMSTaskSequence\Packages\WGS00137 before releasing
Delete source directory C:\_SMSTaskSequence\Packages\WGS00137
Released the resolved source C:\_SMSTaskSequence\Packages\WGS00137
pInstall->Install(sPackageID, sProgramName), HRESULT=87d01014 (e:\nts_sccm_release\sms\client\osdeployment\installsoftware\main.cpp,361)
Failed to invoke Execution Manager to Install Software for PackageID='WGS00137' ProgramID='Silent Installation' AdvertID='WES20013' hr=0x87d01014
InstallSoftware failed, hr=0x87d01014
Install Software failed, hr=0x87d01014. The operating system reported error 615: The password provided is too short to meet the policy of your user account. Please choose a longer password.
And here's the group policy that is applied to that OU:
Enforce password history
0 passwords remembered
Maximum password age
0 days
Minimum password age
0 days
Minimum password length
0 characters
Password must meet complexity requirements
Disabled
Of course, the password complexity issue is a non-starter: How come SCCM 2007 task sequences did not have the same problem? Why does the Task Sequence work
sometimes and not others. All passwords I provide to Configuration Manager all conform to complexity rules anyway.
The relevant SMSTS.log portion is below:
<![LOG[Variable name: _SMSSWDProgramName]LOG]!><time="18:06:06.660-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:620">
<![LOG[Action command line: smsswd.exe /pkg:WGS00137 /install /basevar: /continueOnError:]LOG]!><time="18:06:06.660-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:522">
<![LOG[Adding instruction at 90]LOG]!><time="18:06:06.660-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:524">
<![LOG[
Parsing step node: Applications]LOG]!><time="18:06:06.660-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:458">
<![LOG[Description: ]LOG]!><time="18:06:06.660-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:462">
<![LOG[ContinueOnError: true]LOG]!><time="18:06:06.660-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:466">
<![LOG[SuccessCodeList: 0]LOG]!><time="18:06:06.660-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:474">
<![LOG[(__hrMethodRetVal == ((HRESULT)0L)) || (bFailIfMissing == false), HRESULT=80070002 (e:\NTS_SCCM_RELEASE\sms\common\inc\ccmxml.h,582)]LOG]!><time="18:06:06.660-60" date="05-28-2012" component="TSManager" context="" type="0" thread="1804" file="ccmxml.h:582">
<![LOG[No condition is associated with the step.]LOG]!><time="18:06:06.660-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:670">
<![LOG[Disable: ]LOG]!><time="18:06:06.660-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:483">
<![LOG[Run in attribute: FullOS]LOG]!><time="18:06:06.660-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:491">
<![LOG[Timeout: ]LOG]!><time="18:06:06.660-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:495">
<![LOG[DefaultVarlist found]LOG]!><time="18:06:06.660-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:579">
<![LOG[Variable name: OSDApp0Description]LOG]!><time="18:06:06.660-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:620">
<![LOG[Variable name: OSDApp0DisplayName]LOG]!><time="18:06:06.660-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:620">
<![LOG[Variable name: OSDApp0Name]LOG]!><time="18:06:06.660-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:620">
<![LOG[Variable name: OSDApp1Description]LOG]!><time="18:06:06.660-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:620">
<![LOG[Variable name: OSDApp1DisplayName]LOG]!><time="18:06:06.660-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:620">
<![LOG[Variable name: OSDApp1Name]LOG]!><time="18:06:06.660-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:620">
<![LOG[Variable name: OSDAppCount]LOG]!><time="18:06:06.660-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:620">
<![LOG[Action command line: smsappinstall.exe /app:ScopeId_69AC7FA1-9E68-49C4-8D43-9BA17630A64D/Application_28f01c04-7229-4152-85e2-f2f43daf92b2,ScopeId_69AC7FA1-9E68-49C4-8D43-9BA17630A64D/Application_382fdd99-2228-452d-a6f0-63e543ce628d /basevar: /continueOnError:True]LOG]!><time="18:06:06.660-60"
date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:522">
<![LOG[Adding instruction at 91]LOG]!><time="18:06:06.660-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:524">
<![LOG[
Parsing step node: Language Packs]LOG]!><time="18:06:06.660-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:458">
<![LOG[Description: ]LOG]!><time="18:06:06.660-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:462">
<![LOG[ContinueOnError: true]LOG]!><time="18:06:06.660-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:466">
<![LOG[SuccessCodeList: 0]LOG]!><time="18:06:06.660-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:474">
<![LOG[(__hrMethodRetVal == ((HRESULT)0L)) || (bFailIfMissing == false), HRESULT=80070002 (e:\NTS_SCCM_RELEASE\sms\common\inc\ccmxml.h,582)]LOG]!><time="18:06:06.660-60" date="05-28-2012" component="TSManager" context="" type="0" thread="1804" file="ccmxml.h:582">
<![LOG[No condition is associated with the step.]LOG]!><time="18:06:06.660-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:670">
<![LOG[Disable: ]LOG]!><time="18:06:06.660-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:483">
<![LOG[Run in attribute: FullOS]LOG]!><time="18:06:06.676-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:491">
<![LOG[Timeout: ]LOG]!><time="18:06:06.676-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:495">
<![LOG[DefaultVarlist found]LOG]!><time="18:06:06.676-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:579">
<![LOG[Variable name: OSDApp0Description]LOG]!><time="18:06:06.676-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:620">
<![LOG[Variable name: OSDApp0DisplayName]LOG]!><time="18:06:06.676-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:620">
<![LOG[Variable name: OSDApp0Name]LOG]!><time="18:06:06.676-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:620">
<![LOG[Variable name: OSDApp1Description]LOG]!><time="18:06:06.676-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:620">
<![LOG[Variable name: OSDApp1DisplayName]LOG]!><time="18:06:06.676-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:620">
<![LOG[Variable name: OSDApp1Name]LOG]!><time="18:06:06.676-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:620">
<![LOG[Variable name: OSDApp2Description]LOG]!><time="18:06:06.676-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:620">
<![LOG[Variable name: OSDApp2DisplayName]LOG]!><time="18:06:06.676-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:620">
<![LOG[Variable name: OSDApp2Name]LOG]!><time="18:06:06.676-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:620">
<![LOG[Variable name: OSDApp3Description]LOG]!><time="18:06:06.676-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:620">
<![LOG[Variable name: OSDApp3DisplayName]LOG]!><time="18:06:06.676-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:620">
<![LOG[Variable name: OSDApp3Name]LOG]!><time="18:06:06.676-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:620">
<![LOG[Variable name: OSDApp4Description]LOG]!><time="18:06:06.676-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:620">
<![LOG[Variable name: OSDApp4DisplayName]LOG]!><time="18:06:06.676-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:620">
<![LOG[Variable name: OSDApp4Name]LOG]!><time="18:06:06.676-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:620">
<![LOG[Variable name: OSDApp5Description]LOG]!><time="18:06:06.676-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:620">
<![LOG[Variable name: OSDApp5DisplayName]LOG]!><time="18:06:06.676-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:620">
<![LOG[Variable name: OSDApp5Name]LOG]!><time="18:06:06.676-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:620">
<![LOG[Variable name: OSDApp6Description]LOG]!><time="18:06:06.676-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:620">
<![LOG[Variable name: OSDApp6DisplayName]LOG]!><time="18:06:06.676-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:620">
<![LOG[Variable name: OSDApp6Name]LOG]!><time="18:06:06.676-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:620">
<![LOG[Variable name: OSDApp7Description]LOG]!><time="18:06:06.676-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:620">
<![LOG[Variable name: OSDApp7DisplayName]LOG]!><time="18:06:06.676-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:620">
<![LOG[Variable name: OSDApp7Name]LOG]!><time="18:06:06.676-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:620">
<![LOG[Variable name: OSDAppCount]LOG]!><time="18:06:06.676-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:620">
<![LOG[Action command line: smsappinstall.exe /app:ScopeId_69AC7FA1-9E68-49C4-8D43-9BA17630A64D/Application_9df3ec9a-e691-4106-b274-46c4c6c319b9,ScopeId_69AC7FA1-9E68-49C4-8D43-9BA17630A64D/Application_42e28566-b339-4773-92cf-05b8e748d996,ScopeId_69AC7FA1-9E68-49C4-8D43-9BA17630A64D/Application_305b4a34-0b5a-46fe-82dd-c57a5897e063,ScopeId_69AC7FA1-9E68-49C4-8D43-9BA17630A64D/Application_379afca3-f48e-486b-8848-296223481edd,ScopeId_69AC7FA1-9E68-49C4-8D43-9BA17630A64D/Application_502bf2db-e1c8-42ac-a499-61320d661cc3,ScopeId_69AC7FA1-9E68-49C4-8D43-9BA17630A64D/Application_455a6de9-fe98-47ed-8dab-e860dd4681ed,ScopeId_69AC7FA1-9E68-49C4-8D43-9BA17630A64D/Application_1707c97e-b4bb-4827-9117-02e79435213e,ScopeId_69AC7FA1-9E68-49C4-8D43-9BA17630A64D/Application_a17f2337-ad2e-42cb-9813-c9e167a85050
/basevar: /continueOnError:True]LOG]!><time="18:06:06.676-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:522">
<![LOG[Adding instruction at 92]LOG]!><time="18:06:06.676-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:524">
<![LOG[Processed all elements]LOG]!><time="18:06:06.676-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:333">
<![LOG[Adding end group instruction at 93]LOG]!><time="18:06:06.676-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:402">
<![LOG[The next instruction after group will be at 94]LOG]!><time="18:06:06.676-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:408">
<![LOG[
Parsing step node: Opt In to CEIP and WER]LOG]!><time="18:06:06.676-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:458">
Anthony Sheehy - MCP, MCITP -
Install Software Updates fails (timeouts) during OSD Task Sequence
Hi
As one of the lasts steps in our OSD Task Sequence we have an "Install Software Update" step where "Mandatory Software Updates" is choosen. It worked a week ago, but now the step fails with error code 0x800705B4
(This operation returned because the timeout period expired.)
When examining the WindowsUpdate.log I see an error followed by several minutes without log activity:
2014-02-18 10:39:13:874
416 b74
Report CWERReporter finishing event handling. (00000000)
2014-02-18 10:39:13:874
416 b74
Report CWERReporter finishing event handling. (00000000)
2014-02-18 10:39:13:874
416 b74
Report CWERReporter finishing event handling. (00000000)
2014-02-18 10:39:13:999
1632 4e4
COMAPI - Updates found = 260
2014-02-18 10:39:13:999
1632 4e4
COMAPI ---------
2014-02-18 10:39:13:999
1632 4e4
COMAPI -- END -- COMAPI: Search [ClientId = CcmExec]
2014-02-18 10:39:13:999
1632 4e4
COMAPI -------------
2014-02-18 10:39:18:835
416 b74
Report CWERReporter finishing event handling. (00000000)
2014-02-18 11:08:12:225
416 4dc
AU AU received policy change subscription event
2014-02-18 11:08:12:334
416 4dc
AU AU Options changed from policy.
2014-02-18 11:08:12:334
416 4dc
AU Successfully wrote event for AU health state:0
2014-02-18 11:08:12:334
416 4dc
AU ########### AU: Policy change processed ###########
When examining the WUAHadler.log - again there is no log activity during the Software Update step.
Its a WSUS Update Source type ({DCA8EDB2-927C-42AC-9D2E-3D98C3BC3759}), adding it.
WUAHandler 18-02-2014 10:39:05
2016 (0x07E0)
Existing WUA Managed server was already set (http://<servername>:8530), skipping Group Policy registration.
WUAHandler 18-02-2014 10:39:05
2016 (0x07E0)
Added Update Source ({DCA8EDB2-927C-42AC-9D2E-3D98C3BC3759}) of content type: 2
WUAHandler 18-02-2014 10:39:05
2016 (0x07E0)
Scan results will include all superseded updates.
WUAHandler 18-02-2014 10:39:05
2016 (0x07E0)
Search Criteria is (DeploymentAction=* AND Type='Software') OR (DeploymentAction=* AND Type='Driver')
WUAHandler 18-02-2014 10:39:05
2016 (0x07E0)
Async searching of updates using WUAgent started.
WUAHandler 18-02-2014 10:39:05
2016 (0x07E0)
Async searching completed. WUAHandler
18-02-2014 10:39:13 1108 (0x0454)
Successfully completed scan. WUAHandler
18-02-2014 10:39:15 2016 (0x07E0)
Removed Update Source ({DCA8EDB2-927C-42AC-9D2E-3D98C3BC3759}) of content type: 2
WUAHandler 18-02-2014 11:06:25
1160 (0x0488)
CWuaHandler::SetCategoriesForStateReportingExclusion called with E0789628-CE08-4437-BE74-2495B842F43B;E0789628-CE08-4437-BE74-2495B842F43B,A38C835C-2950-4E87-86CC-6911A52C34A3; for leaves and E0789628-CE08-4437-BE74-2495B842F43B,A38C835C-2950-4E87-86CC-6911A52C34A3;
for bundles WUAHandler
18-02-2014 11:09:25 2232 (0x08B8)
The Software Update Step started at 10:27 and the timeout came at 11:05.
Any ideas why the step times out? Or which logs I should look at?
Regards,
FCPolicyEvaluator.log:
No errors. The last event is:
Received notification that Local policy has changed.
PolicyAgent_PolicyEvaluator 19-02-2014 10:51:11
1692 (0x069C)
Raising event:
instance of CCM_PolicyAgent_SettingsEvaluationComplete
ClientID = "GUID:C2E937AA-CF24-420F-AD81-E8CEADBD7649";
DateTime = "20140219095123.565000+000";
PolicyNamespace = "\\\\.\\root\\ccm\\policy\\machine\\actualconfig";
ProcessID = 1748;
ThreadID = 1768;
PolicyAgent_PolicyEvaluator
19-02-2014 10:51:23 1768 (0x06E8)
Forcing settings update for local policy change.
PolicyAgent_PolicyEvaluator 19-02-2014 10:51:23
2900 (0x0B54)
Updating settings in \\.\root\ccm\policy\machine\actualconfig
PolicyAgent_PolicyEvaluator 19-02-2014 10:51:33
2900 (0x0B54)
Raising event:
instance of CCM_PolicyAgent_SettingsEvaluationComplete
ClientID = "GUID:C2E937AA-CF24-420F-AD81-E8CEADBD7649";
DateTime = "20140219095144.641000+000";
PolicyNamespace = "\\\\.\\root\\ccm\\policy\\machine\\actualconfig";
ProcessID = 1748;
ThreadID = 2900;
PolicyAgent_PolicyEvaluator
19-02-2014 10:51:44 2900 (0x0B54)
UpdatesHandler.log:
No errors. A couple of lines:
Successfully initiated scan. UpdatesHandler
19-02-2014 10:54:10 1768 (0x06E8)
Updates scan completion received, result = 0x0.
UpdatesHandler 19-02-2014 10:55:23
3572 (0x0DF4)
UpdatesStore.log
No errors. Just quering updates, and the last line:
Querying update status completed successfully.
UpdatesStore 19-02-2014 10:56:27
3300 (0x0CE4)
In the smsts.log I found an interesting thing:
Successfully initiated RefreshUpdates operation
InstallSWUpdate 19-02-2014 10:51:37
3424 (0x0D60)
Waiting for RefreshUpdates complete notification from Updates Deployment Agent
InstallSWUpdate 19-02-2014 10:51:37
3424 (0x0D60)
FALSE, HRESULT=800705b4 (e:\nts_sccm_release\sms\client\osdeployment\installswupdate\installswupdate.cpp,1273)
InstallSWUpdate 19-02-2014 11:21:37
3424 (0x0D60)
Timedout waiting for updates refresh complete notification
InstallSWUpdate 19-02-2014 11:21:37
3424 (0x0D60)
It times out after exactly 30 minutes. Does 2012 have the same "feature" as 2007? (http://support.microsoft.com/kb/2009754/da)
Still the last event in windowsupdate.log is:
2014-02-19 10:55:37:251
324 dd0
Report CWERReporter finishing event handling. (00000000)
Regards,
FC -
UDI OSD Task Sequences started failing with 0x80070002 error in SCCM 2012
This is kind of long, but here goes...
We built a UDI task sequence in SCCM 2012 (with MDT integration) that we were testing for deployment of a couple of different Win7 images. We customized the UDI experience thru the UDI wizard and XML file and OS deployment worked as expected
thru the task sequence (testing on Hyper-V VMs). Recently, this UDI TS started failing with error 0x80070002 during what appears to be the "Use Toolkit Package" step. This is after the OS image has already been laid down and after the ConfigMgr
client has been installed/configured. The SMSTS.log reports "Failed to open the task sequence key HKLM\Software\Microsoft\SMS\Task Sequence. Error code 0x8007002" Among other errors...I will post the entire log below...
After the error during deployment, Win7 will boot normally, however, you have no network connectivity and it appears the proper network driver didn't get loaded in the OS. Combine this with the fact that the TS should have joined the machine to our domain,
but you can't login because no network.. Im not sure if the network issue is a product of the TS failing early or the actual cause of the TS failure.
Anyway, I attempted to build another UDI task sequence using the same boot image and toolkit/settings packages, but am experiencing the same error during deployment. We have a few OSD task sequences built without UDI and those all still work just fine.
So, I am at a loss for where the root problem lies. Any suggestions or assistance would be greatly appreciated.
Here is the entire SMSTS.log and BDD.log...
https://skydrive.live.com/redir?resid=D65B1C4362892A26!110&authkey=!AKu5mOvDsXaEgvc
Thanks
Richie Tenhetyour failure does appear to be network (driver or otherwise) or dns related and it cannot contact the management point FQDN just around the time where it should download and execute the
Use Toolkit Package step...
"Starting Task Sequence Engine . . . "
"Non fatal error 0x80072ee7 in sending task sequence execution status message to MP"
"Start executing an instruciton. Instruction name: Use Toolkit Package. Instruction pointer: 83"
"unknown host (gethostbyname failed)"
"sending with winhttp failed; 80072ee7"
"Tried all the available http based locations. SMB based locations will be attempted now."
"Failed to resolve the source for SMS PKGID=P0100015, hr=0x80070002"
"Failed to run the action: Use Toolkit Package.
The system cannot find the file specified. (Error: 80070002; Source: Windows)"
that said, check that the package referenced above actually exists and is the correct source version on your distribution points, also verify (press F8 and check can you ping the FQDN of your management point) that you have network connectivity
around the time of the failure.
Step by Step Configuration Manager Guides >
2012 Guides |
2007 Guides | I'm on Twitter > ncbrady -
SCCM 2012 MDT 2012 UDI Require domain credentials to run task sequence
We are in the process of moving to SCCM 2012 integrated with MDT 2012 for OSD from using MDT 2012 by itself. We're trying out UDI task sequences and have noticed a pretty gaping hole in functionality vs MDT 2012 by itself: password protecting a task sequence.
In MDT 2012 there was a built-in feature that required domain credentials to run a task sequence. If one exists using SCCM/MDT 2012, I haven't been able to find it. I've only found stuff like this http://www.windows-noob.com/forums/index.php?/topic/2336-password-protect-a-task-sequence/ which
would allow you to set a password, but not authenticate against AD. So, I'm wondering if there are any options to protecting a task sequence with domain authentication?
My understanding is that the Refresh and Replace StageGroup only run when you kick off a UDI task sequence in Windows. That means I have to make a task sequence available to the Configuration Manager Client in order for a tech to run a Refresh/Replace. And,
that in turn means that the UDI task sequence will be visible to all users since it needs to be available to their computer. Or, am I completely missing how UDI OSD should flow? If so, then I hope someone can correct me.
I'd appreciate any help or advice you can give. Thanks.Hi,
I am sorry to say that you are correct in your conclusions. There is no builtin way in ConfigMgr/MDT/UDI to require a domain username/password to run a task sequence, your option from Windows-noob.com is one way of solving it.
Regards,
jörgen
-- My System Center blog ccmexec.com -- Twitter
@ccmexec
Thanks for the info. What about workflow? How do you usually handle UDI in Replace and Refresh scenarios? Do you deploy the task sequence to collections that users can access?
Maybe you are looking for
-
Why wont's Adobe Photoshop CC 2014 open?
My subscription for all CC products ended and I moved to a Photographer only plan. After recently downloading and installing Photoshop on my Mac (OS Mavericks), I get a message that "we are having trouble verifying your membership" and my Photoshop w
-
E61i internet browser doesn't display properly
Hello, I never had any problems browsing the internet on my E61i. My Nokia is always switched on, but today I had to switch it off for a while. After switching in on again, I wanted to use the internet on it. The strange thing was that it wouldn't di
-
Migration from sun/solaris to windows
While performing a migration of SAP from solaris to windows OS what are the implications, issues and things to keep in mind. Also which database would give the best performance (Oracle or MS SQL) and what are the specific requirements if latest relea
-
Populating a Pop List via WHEN-NEW-FORM-INSTANCE
Vendor provided a form that attempts to populate a pop list within a WHEN-NEW-FORM-INSTANCE trigger. Unfortunately when the user enters the form there are no values in the list. User has access to the table (verified by running SQL of cursor in SQL*P
-
Want to know abt report painter and need material
want to know abt report painter and need material . thanks.