Smsts.log in SCCM 2012
Hi,
Where I can find smsts.log file in SCCM12 server? I am not able to find the same. Is the log name changed to some different name?
Regards, Shishir Kushawaha "If this thread answered your question, please click on "Mark as Answer"
The log file will be found on the client - not the server (unless you specifically run a task sequence on the server and it is now the client).
The log is in a different location depending on the situation
During OS Deployment
Before your hard drive is formatted and partitioned
X:\windows\temp\smstslog\
After your hard drive is partitioned formatted
X:\smstslog\ and then is in C:\_SMSTaskSequence\logs\smstslog\
Within Windows
Within Windows before the SCCM agent is installed:
C:\_SMSTaskSequence\logs\smstslog\
Within Windows after the SCCM agent installed:
C:\windows\system32\ccm\logs\smstslog\
When the Task Sequence completes on a x86
C:\windows\system32\ccm\logs\
For x64 Systems
C:\windows\SysWOW64\ccm\logs\
Gerry Hampson | Blog:
www.gerryhampsoncm.blogspot.ie | LinkedIn:
Gerry Hampson | Twitter:
@gerryhampson
I am pretty sure this is incorrect. The location after TS completion is %systemroot%\ccm\logs (usually c:\windows\ccm\logs) on both x86 and x64 platforms.
Similar Messages
-
SCCM 2012 R2 Remote DP (w PXE): cannot find SCCM installation path nor logs
Hello All,
I'm deploying a new SCCM 2012 R2 environment.
I've got 1 primary site with a remote DP with PXE enabled.
The PXE point is working: clients can pxe boot.
However, I can't find the SMSPXE log on the server..
I can't find any SCCM related log for that matter on the server..
Can anyone tell me what I'm missing? How can it be that I can't find the logs?
The C:\Program Files doesn't contain a Configuration Manager folder neither.
Thanks!
FilipHi,
Kent has a blog post on it here:
http://blog.coretech.dk/kea/smspxe-log-in-sccm-2012/
" the log is placed on the distribution point in <X>\SMS_DP$\SMS\Logs where X is the location of the contentlibrary"
Regards,
Jörgen
-- My System Center blog ccmexec.com -- Twitter
@ccmexec -
Hi,
I have this SCCM 2012 standard CM task sequence which writes its logs at the end of the task sequence to a folder. When succesfull to\\server\share\success\computername, when failed to \\server\share\failed\computername
It then also sends a mail with location of logfiles.
Please advise on dynamic logging within sccm 2012 R2: how do I configure this? In ini-file, I set the SLShareDynamicLogging to a servershare?
J.
Jan HoedtIt would be customsettings.ini in MDT and this is not available in native CM12 task sequences. Integrating MDT in CM12 would add that. You can set task sequence variables in CM12 though using computer variables, collection variables, task sequence steps
or scripts during the task sequence.
Torsten Meringer | http://www.mssccmfaq.de -
SCCM 2012 OSD: central logging, smsts.log
Hi,
Is there a way to follow an SCCM MDT integrated task sequence in real time?
We configured central logging and this is working fine, though it is only BDD.log that is copied. When task sequence fails or is succesfull the other files are copied too.
We want to have the possibilty to monitor in real time, without needing to go on the machine itself and open smsts.log.
Please advise.
J.
Jan HoedtI first created threads about configuring central logging in SCCM, numerous indeed.
That worked fine but then we decided to go to MDT logging, again some threads.
No logging is satisfactory to us, neither is the status message. I don't get the concept of the satus message, why is it there whereas smsts.log is containing all logdata.
We deploy a lot of machines to debug. These are on the central logging share. Loggings like smsts.log also can easily be sent for comment when issues. To be able to debug correctly, we need the smsts.log, it's a struggle each time to go on the machine and
get the smsts.log (when machine is in winpe-phase or has network issues. I don't understand why a simple concept = central logging of smsts.log (not the status messages) is that hard to configure/would not exist at all.
Jan Hoedt -
SCCM 2012 R2 - WindowsUpdate.log showing error 0x80240037
Hi,
Setup details:
1) OS: Windows 2012 R2
2) SCCM version: SCCM 2012 R2 with SUP role (WSUS v6.3.9600.16384)
3) SQL: SQL 2012
All the above resides on a single machine.
Error description:
Windows 2012 R2 Server clients are not reporting back to the server. "Required" column is showing "0" for all security updates. Investigation in the WindowsUpdate.log shows "WARNING: Failed to get WU Exemption info from NLM,
assuming not exempt error = 0x80240037".
Latest updates are downloaded, synchronized and deployed via SUP but the clients are not receiving the updates. Please advise. Thanks.
Regards,
KLHi,
You may check the following blog.
http://blogs.technet.com/b/sus/archive/2012/09/05/additional-note-on-kb-2734608-regarding-wsu-windows-8-and-windows-server-2012.aspx
Best Regards,
Joyce
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place. -
Any idea what this message is trying to tell me? ISV Proxy Client Registrations ad worked fine in SCCM 2012 prior to R2. This message in the title is present in MP_RegistrationManager.log. The ISV Proxy Certificate lists as "unblocked".
If this is true, then that was a pretty sleathy move to remove this support.
BAEHi BEnsinger,
You should set your proxy agent type = 8. Everything should work correctly if you do. The change wasn't intended to be a "stealthy" move.
This was originally documented in in ConfigMgr 2007 and remains the same in ConfigMgr 2012:
http://msdn.microsoft.com/en-us/library/cc146744.aspx
The error text may be a little odd - but I'm assuming you're actually registering a client, and according to the SDK docs, you should be using type = 8.
Dave Randall [MSFT]
- Dave -
OSD SCCM 2012 R2: MDT integrated task sequence central logging not working
Hi,
Please advise on making dynamic logging work for SCCM 2012 R2 MDT integrated tasks sequence.
This is what I specified in customsettings.ini
[Settings]
Priority=Default
Properties=MyCustomProperty
[Default]
OSInstall=Y
SkipCapture=YES
SkipAdminPassword=NO
SkipProductKey=YES
; Copy Logs if en error occurs or when deployment is successfully completed
SLSHARE=\\sccmserver\OSD\Logs\MDT
; Enable Dynamig Logging
SLSHAREDynamicLogging=\\\sccmserver\OSD\Logs\MDTDynLogs\%OSDComputername%
UserID=administrator
UserDomain=ourdomain
UserPassword=ourpassword
Jan HoedtI keep on getting access denied though when I connect in a dosprompt with the credentials I can make a connection.
Mapping server share: \\ourdomain.com\share ZTIValidate 4/03/2014 0:08:14 0 (0x0000)
<Message containing password has been suppressed> ZTIValidate 4/03/2014 0:08:14 0 (0x0000)
Access is denied.
ZTIValidate 4/03/2014 0:08:14 0 (0x0000)
Unable to connect to \\ourdomain.com\share. Sleeping for 5 seconds. ZTIValidate 4/03/2014 0:08:14 0 (0x0000)
<Message containing password has been suppressed> ZTIValidate 4/03/2014 0:08:19 0 (0x0000)
Access is denied.
ZTIValidate 4/03/2014 0:08:19 0 (0x0000)
Unable to connect to \\ourdomain.com\share. Sleeping for 10 seconds. ZTIValidate 4/03/2014 0:08:19 0 (0x0000)
<Message containing password has been suppressed> ZTIValidate 4/03/2014 0:08:29 0 (0x0000)
Access is denied.
ZTIValidate 4/03/2014 0:08:29 0 (0x0000)
Unable to connect to \\ourdomain.com\share. Sleeping for 15 seconds. ZTIValidate 4/03/2014 0:08:29 0 (0x0000)
<Message containing password has been suppressed> ZTIValidate 4/03/2014 0:08:44 0 (0x0000)
Access is denied.
ZTIValidate 4/03/2014 0:08:44 0 (0x0000)
Unable to connect to \\ourdomain.com\share. Sleeping for 20 seconds. ZTIValidate 4/03/2014 0:08:44 0 (0x0000)
<Message containing password has been suppressed> ZTIValidate 4/03/2014 0:09:04 0 (0x0000)
Access is denied.
ZTIValidate 4/03/2014 0:09:05 0 (0x0000)
Unable to connect to \\ourdomain.com\share. Sleeping for 25 seconds. ZTIValidate 4/03/2014 0:09:05 0 (0x0000)
ERROR - Unable to map a network drive to \\ourdomain.com\share. ZTIValidate 4/03/2014 0:09:30 0 (0x0000)
An invalid SLShareDynamicLogging value of \\ourdomain.com\share\PackageSources\OSD\Logs\MDT-DynLogs\computername was specified. ZTIValidate 4/03/2014 0:09:30 0 (0x0000)
Jan Hoedt -
SCCM 2012 creates 4732 event logs for 3 of Servers
Hi,
My problem is SCCM 2012 R2 which I have installed recently is creating 4732 security logs in 3 of our servers for every 5hrs interval which is an audit exposure. When I investigated which gives me local administrator ID is getting added to the NT Authority
Group, which I'm not able to explain. Can some one help me in understanding it or Is there anyway I can stop that?
Regards,
Vighnesh
Vighnesh Kumar. SHi,
Please provide more information as Torsten said.
Are there Event ID: 4733 messages existed in event log if it creates 4732 logs every 5 hours? Is it the same account being added to the same Group?
Best Regards,
Joyce
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place. -
SCCM 2012 R2 C2 OSD deployments no logs when Applications fail
Hello,
Have Task Sequences with the Install Application step {as well as other steps for packages, etc.} that installs Applications when one of the Applications fail I usually see exactly what Application fails through the Console Status Message Query "All
Status Messages for a Specific Package at a Specific Site".
Troubleshooting: When I look in C:\Windows\CCM\logs. I see none of the logs: AppDiscovery.log(s), AppEnforce.log(s), AppIntentEval.log (s)?
Note: This only happens if there is an error in the Install Application step...normally the logs are there. Any ideas on how to fix this?
Thanks!Here is a snippet of smsts.log There are 2 Install Applications steps the first one has 9 applications the 2nd has 1 application.
<![LOG[
Parsing step node: CCL Shipboard Applications]LOG]!><time="09:30:41.501+240" date="04-10-2015" component="TSManager" context="" type="1" thread="2112" file="tsxml.cpp:459">
<![LOG[Description: ]LOG]!><time="09:30:41.501+240" date="04-10-2015" component="TSManager" context="" type="1" thread="2112" file="tsxml.cpp:463">
<![LOG[ContinueOnError: true]LOG]!><time="09:30:41.501+240" date="04-10-2015" component="TSManager" context="" type="1" thread="2112" file="tsxml.cpp:467">
<![LOG[SuccessCodeList: 0]LOG]!><time="09:30:41.501+240" date="04-10-2015" component="TSManager" context="" type="1" thread="2112" file="tsxml.cpp:475">
<![LOG[No condition is associated with the step.]LOG]!><time="09:30:41.501+240" date="04-10-2015" component="TSManager" context="" type="1" thread="2112" file="tsxml.cpp:670">
<![LOG[Disable: ]LOG]!><time="09:30:41.501+240" date="04-10-2015" component="TSManager" context="" type="1" thread="2112" file="tsxml.cpp:484">
<![LOG[Run in attribute: FullOS]LOG]!><time="09:30:41.501+240" date="04-10-2015" component="TSManager" context="" type="1" thread="2112" file="tsxml.cpp:492">
<![LOG[Timeout: ]LOG]!><time="09:30:41.501+240" date="04-10-2015" component="TSManager" context="" type="1" thread="2112" file="tsxml.cpp:496">
<![LOG[DefaultVarlist found]LOG]!><time="09:30:41.501+240" date="04-10-2015" component="TSManager" context="" type="1" thread="2112" file="tsxml.cpp:579">
<![LOG[Variable name: OSDApp0Description]LOG]!><time="09:30:41.501+240" date="04-10-2015" component="TSManager" context="" type="1" thread="2112" file="tsxml.cpp:620">
<![LOG[Variable name: OSDApp0DisplayName]LOG]!><time="09:30:41.501+240" date="04-10-2015" component="TSManager" context="" type="1" thread="2112" file="tsxml.cpp:620">
<![LOG[Variable name: OSDApp0Name]LOG]!><time="09:30:41.501+240" date="04-10-2015" component="TSManager" context="" type="1" thread="2112" file="tsxml.cpp:620">
<![LOG[Variable name: OSDApp1Description]LOG]!><time="09:30:41.501+240" date="04-10-2015" component="TSManager" context="" type="1" thread="2112" file="tsxml.cpp:620">
<![LOG[Variable name: OSDApp1DisplayName]LOG]!><time="09:30:41.501+240" date="04-10-2015" component="TSManager" context="" type="1" thread="2112" file="tsxml.cpp:620">
<![LOG[Variable name: OSDApp1Name]LOG]!><time="09:30:41.501+240" date="04-10-2015" component="TSManager" context="" type="1" thread="2112" file="tsxml.cpp:620">
<![LOG[Variable name: OSDApp2Description]LOG]!><time="09:30:41.501+240" date="04-10-2015" component="TSManager" context="" type="1" thread="2112" file="tsxml.cpp:620">
<![LOG[Variable name: OSDApp2DisplayName]LOG]!><time="09:30:41.501+240" date="04-10-2015" component="TSManager" context="" type="1" thread="2112" file="tsxml.cpp:620">
<![LOG[Variable name: OSDApp2Name]LOG]!><time="09:30:41.501+240" date="04-10-2015" component="TSManager" context="" type="1" thread="2112" file="tsxml.cpp:620">
<![LOG[Variable name: OSDApp3Description]LOG]!><time="09:30:41.501+240" date="04-10-2015" component="TSManager" context="" type="1" thread="2112" file="tsxml.cpp:620">
<![LOG[Variable name: OSDApp3DisplayName]LOG]!><time="09:30:41.501+240" date="04-10-2015" component="TSManager" context="" type="1" thread="2112" file="tsxml.cpp:620">
<![LOG[Variable name: OSDApp3Name]LOG]!><time="09:30:41.501+240" date="04-10-2015" component="TSManager" context="" type="1" thread="2112" file="tsxml.cpp:620">
<![LOG[Variable name: OSDApp4Description]LOG]!><time="09:30:41.501+240" date="04-10-2015" component="TSManager" context="" type="1" thread="2112" file="tsxml.cpp:620">
<![LOG[Variable name: OSDApp4DisplayName]LOG]!><time="09:30:41.501+240" date="04-10-2015" component="TSManager" context="" type="1" thread="2112" file="tsxml.cpp:620">
<![LOG[Variable name: OSDApp4Name]LOG]!><time="09:30:41.501+240" date="04-10-2015" component="TSManager" context="" type="1" thread="2112" file="tsxml.cpp:620">
<![LOG[Variable name: OSDApp5Description]LOG]!><time="09:30:41.501+240" date="04-10-2015" component="TSManager" context="" type="1" thread="2112" file="tsxml.cpp:620">
<![LOG[Variable name: OSDApp5DisplayName]LOG]!><time="09:30:41.501+240" date="04-10-2015" component="TSManager" context="" type="1" thread="2112" file="tsxml.cpp:620">
<![LOG[Variable name: OSDApp5Name]LOG]!><time="09:30:41.501+240" date="04-10-2015" component="TSManager" context="" type="1" thread="2112" file="tsxml.cpp:620">
<![LOG[Variable name: OSDApp6Description]LOG]!><time="09:30:41.501+240" date="04-10-2015" component="TSManager" context="" type="1" thread="2112" file="tsxml.cpp:620">
<![LOG[Variable name: OSDApp6DisplayName]LOG]!><time="09:30:41.501+240" date="04-10-2015" component="TSManager" context="" type="1" thread="2112" file="tsxml.cpp:620">
<![LOG[Variable name: OSDApp6Name]LOG]!><time="09:30:41.501+240" date="04-10-2015" component="TSManager" context="" type="1" thread="2112" file="tsxml.cpp:620">
<![LOG[Variable name: OSDApp7Description]LOG]!><time="09:30:41.501+240" date="04-10-2015" component="TSManager" context="" type="1" thread="2112" file="tsxml.cpp:620">
<![LOG[Variable name: OSDApp7DisplayName]LOG]!><time="09:30:41.501+240" date="04-10-2015" component="TSManager" context="" type="1" thread="2112" file="tsxml.cpp:620">
<![LOG[Variable name: OSDApp7Name]LOG]!><time="09:30:41.501+240" date="04-10-2015" component="TSManager" context="" type="1" thread="2112" file="tsxml.cpp:620">
<![LOG[Variable name: OSDApp8Description]LOG]!><time="09:30:41.517+240" date="04-10-2015" component="TSManager" context="" type="1" thread="2112" file="tsxml.cpp:620">
<![LOG[Variable name: OSDApp8DisplayName]LOG]!><time="09:30:41.517+240" date="04-10-2015" component="TSManager" context="" type="1" thread="2112" file="tsxml.cpp:620">
<![LOG[Variable name: OSDApp8Name]LOG]!><time="09:30:41.517+240" date="04-10-2015" component="TSManager" context="" type="1" thread="2112" file="tsxml.cpp:620">
<![LOG[Variable name: OSDAppCount]LOG]!><time="09:30:41.517+240" date="04-10-2015" component="TSManager" context="" type="1" thread="2112" file="tsxml.cpp:620">
<![LOG[Action command line: smsappinstall.exe /app:ScopeId_7646039D-6256-43FA-A12E-9A7A6A4F5A84/Application_75fb5490-a490-4e64-9545-fcd0429bc135,ScopeId_7646039D-6256-43FA-A12E-9A7A6A4F5A84/Application_848807ff-6527-4984-b789-315489b5d8fb,ScopeId_7646039D-6256-43FA-A12E-9A7A6A4F5A84/Application_275df3b1-48df-49dd-8f4d-e739352e9da5,ScopeId_7646039D-6256-43FA-A12E-9A7A6A4F5A84/Application_a5e881ca-e355-4119-ae4c-ecb0b809da1d,ScopeId_7646039D-6256-43FA-A12E-9A7A6A4F5A84/Application_b4ade0f0-0801-4772-a1b1-2f07b9e774d9,ScopeId_7646039D-6256-43FA-A12E-9A7A6A4F5A84/Application_c57aedb5-5a8a-49a7-98ed-89b48fe78d12,ScopeId_7646039D-6256-43FA-A12E-9A7A6A4F5A84/Application_01266b3d-f6cb-4dc4-b255-36c3244b998f,ScopeId_7646039D-6256-43FA-A12E-9A7A6A4F5A84/Application_b5d3c8f3-cb78-4e1a-8796-f8285128e315,ScopeId_7646039D-6256-43FA-A12E-9A7A6A4F5A84/Application_83d05a3c-a613-40d7-88da-ceb0a07ef60e
/basevar: /continueOnError:True]LOG]!><time="09:30:41.517+240" date="04-10-2015" component="TSManager" context="" type="1" thread="2112" file="tsxml.cpp:522">
<![LOG[Adding instruction at 56]LOG]!><time="09:30:41.517+240" date="04-10-2015" component="TSManager" context="" type="1" thread="2112" file="tsxml.cpp:524">
<![LOG[
Parsing step node: CCL Shipboard Application Part 2]LOG]!><time="09:30:41.517+240" date="04-10-2015" component="TSManager" context="" type="1" thread="2112" file="tsxml.cpp:459">
<![LOG[Description: ]LOG]!><time="09:30:41.517+240" date="04-10-2015" component="TSManager" context="" type="1" thread="2112" file="tsxml.cpp:463">
<![LOG[ContinueOnError: true]LOG]!><time="09:30:41.517+240" date="04-10-2015" component="TSManager" context="" type="1" thread="2112" file="tsxml.cpp:467">
<![LOG[SuccessCodeList: 0]LOG]!><time="09:30:41.517+240" date="04-10-2015" component="TSManager" context="" type="1" thread="2112" file="tsxml.cpp:475">
<![LOG[No condition is associated with the step.]LOG]!><time="09:30:41.517+240" date="04-10-2015" component="TSManager" context="" type="1" thread="2112" file="tsxml.cpp:670">
<![LOG[Disable: ]LOG]!><time="09:30:41.517+240" date="04-10-2015" component="TSManager" context="" type="1" thread="2112" file="tsxml.cpp:484">
<![LOG[Run in attribute: FullOS]LOG]!><time="09:30:41.517+240" date="04-10-2015" component="TSManager" context="" type="1" thread="2112" file="tsxml.cpp:492">
<![LOG[Timeout: ]LOG]!><time="09:30:41.517+240" date="04-10-2015" component="TSManager" context="" type="1" thread="2112" file="tsxml.cpp:496">
<![LOG[DefaultVarlist found]LOG]!><time="09:30:41.517+240" date="04-10-2015" component="TSManager" context="" type="1" thread="2112" file="tsxml.cpp:579">
<![LOG[Variable name: OSDApp0Description]LOG]!><time="09:30:41.517+240" date="04-10-2015" component="TSManager" context="" type="1" thread="2112" file="tsxml.cpp:620">
<![LOG[Variable name: OSDApp0DisplayName]LOG]!><time="09:30:41.517+240" date="04-10-2015" component="TSManager" context="" type="1" thread="2112" file="tsxml.cpp:620">
<![LOG[Variable name: OSDApp0Name]LOG]!><time="09:30:41.517+240" date="04-10-2015" component="TSManager" context="" type="1" thread="2112" file="tsxml.cpp:620">
<![LOG[Variable name: OSDAppCount]LOG]!><time="09:30:41.517+240" date="04-10-2015" component="TSManager" context="" type="1" thread="2112" file="tsxml.cpp:620">
<![LOG[Action command line: smsappinstall.exe /app:ScopeId_7646039D-6256-43FA-A12E-9A7A6A4F5A84/Application_cdad2a4f-c0cc-4fd5-9833-0b273c8dca01 /basevar: /continueOnError:False]LOG]!><time="09:30:41.517+240" date="04-10-2015"
component="TSManager" context="" type="1" thread="2112" file="tsxml.cpp:522">
<![LOG[Adding instruction at 57]LOG]!><time="09:30:41.517+240" date="04-10-2015" component="TSManager" context="" type="1" thread="2112" file="tsxml.cpp:524"> -
SCCM 2012 R2 OS: central logging?
Hi,
We would like to have OSD logfiles in a central shared location instead on the pc itself.
This way we can find out issues without having to dig into the machine (when machine is down, blue screen ...).
J.
Jan HoedtThis is what I was looking for, great article: http://schadda.blogspot.be/2012/01/sccm-2012-how-to-catch-errors-in-task.html
Jan Hoedt
This is basically the same as the MDT (CM integrated) task sequences already provide out of the box.
Torsten Meringer | http://www.mssccmfaq.de -
NO SMSTS.LOG file after OSD
Single Primary Site SCCM 2012 R2 CU4.
Deploying BareMetal machines using basic task sequence.
The machine joins the domain however the sccm client install failed and I cannot locate the SMSTS.log anywhere.
In C:\windows we have ccmsetup with ccmsetup.log, client.msi.log and MicrosoftPolicyPlatformSetup.msi.
There is no c:\_SMSTaskSequence or C:\WIndows\CCM folder.
CCMSETUP.log
<![LOG[Deleted file C:\Windows\ccmsetup\ccmsetup.cab.download]LOG]!><time="13:41:10.611+300" date="02-20-2015" component="ccmsetup" context="" type="1" thread="984" file="ccmsetup.cpp:9497">
<![LOG[Deleted file C:\Windows\ccmsetup\ccmsetup.xml]LOG]!><time="13:41:10.611+300" date="02-20-2015" component="ccmsetup" context="" type="1" thread="984" file="ccmsetup.cpp:9497">
<![LOG[Deleted file C:\Windows\ccmsetup\vcredist_x86.exe.download]LOG]!><time="13:41:10.611+300" date="02-20-2015" component="ccmsetup" context="" type="1" thread="984" file="ccmsetup.cpp:9497">
<![LOG[Deleted file C:\Windows\ccmsetup\vc50727_x64.exe.download]LOG]!><time="13:41:10.611+300" date="02-20-2015" component="ccmsetup" context="" type="1" thread="984" file="ccmsetup.cpp:9497">
<![LOG[Deleted file C:\Windows\ccmsetup\MicrosoftPolicyPlatformSetup.msi.download]LOG]!><time="13:41:10.611+300" date="02-20-2015" component="ccmsetup" context="" type="1" thread="984"
file="ccmsetup.cpp:9497">
<![LOG[Deleted file C:\Windows\ccmsetup\WindowsFirewallConfigurationProvider.msi.download]LOG]!><time="13:41:10.611+300" date="02-20-2015" component="ccmsetup" context="" type="1" thread="984"
file="ccmsetup.cpp:9497">
<![LOG[Deleted file C:\Windows\ccmsetup\SCEPInstall.exe.download]LOG]!><time="13:41:10.611+300" date="02-20-2015" component="ccmsetup" context="" type="1" thread="984" file="ccmsetup.cpp:9497">
<![LOG[Deleted file C:\Windows\ccmsetup\client.msi.download]LOG]!><time="13:41:10.627+300" date="02-20-2015" component="ccmsetup" context="" type="1" thread="984" file="ccmsetup.cpp:9497">
<![LOG[CcmSetup failed with error code 0x80070663]LOG]!><time="13:41:10.627+300" date="02-20-2015" component="ccmsetup" context="" type="1" thread="984" file="ccmsetup.cpp:10883">
CLIENT.MSI
MSI (s) (A4:64) [13:41:10:003]: Note: 1: 1402 2: HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Policies\Explorer 3: 2
MSI (s) (A4:64) [13:41:10:003]: File will have security applied from OpCode.
MSI (s) (A4:64) [13:41:10:050]: SOFTWARE RESTRICTION POLICY: Verifying package --> 'C:\Windows\ccmsetup\{181D79D7-1115-4D96-8E9B-5833DF92FBB4}\client.msi' against software restriction policy
MSI (s) (A4:64) [13:41:10:050]: SOFTWARE RESTRICTION POLICY: C:\Windows\ccmsetup\{181D79D7-1115-4D96-8E9B-5833DF92FBB4}\client.msi has a digital signature
MSI (s) (A4:64) [13:41:10:050]: SOFTWARE RESTRICTION POLICY: C:\Windows\ccmsetup\{181D79D7-1115-4D96-8E9B-5833DF92FBB4}\client.msi is permitted to run because the user token authorizes execution (system or service token).
MSI (s) (A4:64) [13:41:10:050]: End dialog not enabled
MSI (s) (A4:64) [13:41:10:050]: Original package ==> C:\Windows\ccmsetup\{181D79D7-1115-4D96-8E9B-5833DF92FBB4}\client.msi
MSI (s) (A4:64) [13:41:10:050]: Package we're running from ==> C:\Windows\Installer\5159e.msi
MSI (s) (A4:64) [13:41:10:050]: APPCOMPAT: Compatibility mode property overrides found.
MSI (s) (A4:64) [13:41:10:050]: APPCOMPAT: looking for appcompat database entry with ProductCode '{8864FB91-94EE-4F16-A144-0D82A232049D}'.
MSI (s) (A4:64) [13:41:10:050]: APPCOMPAT: no matching ProductCode found in database.
MSI (s) (A4:64) [13:41:10:050]: Machine policy value 'TransformsSecure' is 0
MSI (s) (A4:64) [13:41:10:050]: User policy value 'TransformsAtSource' is 0
MSI (s) (A4:64) [13:41:10:050]: Note: 1: 2262 2: MsiFileHash 3: -2147287038
MSI (s) (A4:64) [13:41:10:050]: Unable to create a temp copy of patch 'C:\WINDOWS\TEMP\KB2994331_X64.MSP'.
MSI (s) (A4:64) [13:41:10:050]: Note: 1: 1708
MSI (s) (A4:64) [13:41:10:050]: Product: Configuration Manager Client -- Installation failed.
MSI (s) (A4:64) [13:41:10:050]: Windows Installer installed the product. Product Name: Configuration Manager Client. Product Version: 5.00.7958.1000. Product Language: 1033. Manufacturer: Microsoft Corporation. Installation success or error status: 1635.
MSI (s) (A4:64) [13:41:10:112]: MainEngineThread is returning 1635
MSI (s) (A4:74) [13:41:10:112]: No System Restore sequence number for this installation.
This update package could not be opened. Verify that the update package exists and that you can access it, or contact the application vendor to verify that this is a valid Windows Installer update package.
C:\Windows\ccmsetup\{181D79D7-1115-4D96-8E9B-5833DF92FBB4}\client.msi
MSI (s) (A4:74) [13:41:10:112]: User policy value 'DisableRollback' is 0
MSI (s) (A4:74) [13:41:10:112]: Machine policy value 'DisableRollback' is 0
MSI (s) (A4:74) [13:41:10:112]: Incrementing counter to disable shutdown. Counter after increment: 0
MSI (s) (A4:74) [13:41:10:112]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2
MSI (s) (A4:74) [13:41:10:112]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2
MSI (s) (A4:74) [13:41:10:112]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\InProgress 3: 2
MSI (s) (A4:74) [13:41:10:112]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\InProgress 3: 2
MSI (s) (A4:74) [13:41:10:112]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1
MSI (s) (A4:74) [13:41:10:112]: Restoring environment variables
MSI (c) (54:70) [13:41:10:112]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1
MSI (c) (54:70) [13:41:10:112]: MainEngineThread is returning 1635
=== Verbose logging stopped: 2/20/2015 13:41:10 ===Until the client agent is installed, smsts.log will be in C:\Windows\Temp.
That won't help you troubleshoot the client agent installation failure though. For Windows Installer installations, 1603 is a generic error code that means you needs to examine the verbose msi log file (client.msi.log in this case) in depth. Searching
for the string "return code 3" and then scanning the lines above this will lead you to exact item that failed.
Jason | http://blog.configmgrftw.com | @jasonsandys -
SCCM 2012 SP1 MDT task sequence fails on reboot does not retain ip
we are having a sccm 2012 sp1 server that used for installation of win 8.1 Enterprise , the task sequence works perfectly fine but when we run the same task on HP Elite 8300 system having Intel 82579LM Adapter from Windows XP , after the reboot the
task fails as no ip address is assigned the NIC , We did download the WInPE Adapter drivers from HP site and injecting to the x86 Boot Image (6.2.9200) however the task still fails ,
Our environment uses all static ip address , the same task as mentioned earlier has worked fine with Different brands of HP elite 8200/8100 , infact the elite 8200 also uses the same NIC card
Find below the smsts.log file
Main error in the log file is
No physical network adapters found OSDNetSettings 2/12/2014 1:02:38 AM 2064 (0x0810)
Found network adapter "Intel(R) 82579LM Gigabit Network Connection" with IP Address 169.254.181.151. TSMBootstrap 2/12/2014 1:05:41 PM 1984 (0x07C0)
Xtract from LOG
SMSTSRebootDelay=60 Reboot 2/12/2014 1:01:56 AM 3496 (0x0DA8)
SMSTSRebootMessage=A new Microsoft Windows operating system is being installed. The computer must restart to continue. Reboot 2/12/2014 1:01:56 AM 3496 (0x0DA8)
SMSTSRebootRequested=WinPE Reboot 2/12/2014 1:01:56 AM 3496 (0x0DA8)
Process completed with exit code 0 TSManager 2/12/2014 1:01:56 AM 1876 (0x0754)
!--------------------------------------------------------------------------------------------! TSManager 2/12/2014 1:01:56 AM 1876 (0x0754)
Successfully completed the action (Restart to Windows PE) with the exit win32 code 0 TSManager 2/12/2014 1:01:56 AM 1876 (0x0754)
Set authenticator in transport TSManager 2/12/2014 1:01:56 AM 1876 (0x0754)
Set a global environment variable _SMSTSLastActionRetCode=0 TSManager 2/12/2014 1:01:57 AM 1876 (0x0754)
Set a global environment variable _SMSTSLastActionSucceeded=true TSManager 2/12/2014 1:01:57 AM 1876 (0x0754)
Clear local default environment TSManager 2/12/2014 1:01:57 AM 1876 (0x0754)
Updated security on object E:\_SMSTaskSequence. TSManager 2/12/2014 1:01:57 AM 1876 (0x0754)
Set a global environment variable _SMSTSNextInstructionPointer=59 TSManager 2/12/2014 1:01:57 AM 1876 (0x0754)
Set a TS execution environment variable _SMSTSNextInstructionPointer=59 TSManager 2/12/2014 1:01:57 AM 1876 (0x0754)
Set a global environment variable _SMSTSInstructionStackString=0 41 57 TSManager 2/12/2014 1:01:57 AM 1876 (0x0754)
Set a TS execution environment variable _SMSTSInstructionStackString=0 41 57 TSManager 2/12/2014 1:01:57 AM 1876 (0x0754)
Save the current environment block TSManager 2/12/2014 1:01:57 AM 1876 (0x0754)
Executing command line: "bcdedit.exe" TSManager 2/12/2014 1:01:57 AM 1876 (0x0754)
CreateProcess failed. Code(0x80070002) TSManager 2/12/2014 1:01:57 AM 1876 (0x0754)
Command line execution failed (80070002) TSManager 2/12/2014 1:01:57 AM 1876 (0x0754)
Staging boot image UNB0003A TSManager 2/12/2014 1:01:57 AM 1876 (0x0754)
ResolveSource flags: 0x00000000 TSManager 2/12/2014 1:01:59 AM 1876 (0x0754)
SMSTSPersistContent: . The content for package UNB0003A will be persisted TSManager 2/12/2014 1:01:59 AM 1876 (0x0754)
Set authenticator in transport TSManager 2/12/2014 1:01:59 AM 1876 (0x0754)
WinHttp credentials set TSManager 2/12/2014 1:01:59 AM 1876 (0x0754)
List of files to be downloaded TSManager 2/12/2014 1:01:59 AM 1876 (0x0754)
Downloaded file from http://unb-ho-sccmdb.exch1.mas.unb.com:80/SMS_DP_SMSPKG$/UNB0003A/sccm?/WinPE.UNB0003A.wim to E:\_SMSTaskSequence\Packages\UNB0003A\WinPE.UNB0003A.wim TSManager 2/12/2014 1:02:22 AM 1876
(0x0754)
VerifyContentHash: Hash algorithm is 32780 TSManager 2/12/2014 1:02:22 AM 1876 (0x0754)
Found boot image E:\_SMSTaskSequence\Packages\UNB0003A\WinPE.UNB0003A.wim TSManager 2/12/2014 1:02:25 AM 1876 (0x0754)
Copying boot image locally... TSManager 2/12/2014 1:02:25 AM 1876 (0x0754)
Failed to find ADK installation root registry key TSManager 2/12/2014 1:02:32 AM 1876 (0x0754)
Opening image file E:\_SMSTaskSequence\WinPE\sources\boot.wim TSManager 2/12/2014 1:02:32 AM 1876 (0x0754)
Applying image 1 to volume E:\_SMSTaskSequence\WinPE TSManager 2/12/2014 1:02:32 AM 1876 (0x0754)
Closing image file E:\_SMSTaskSequence\WinPE\sources\boot.wim TSManager 2/12/2014 1:02:35 AM 1876 (0x0754)
Capturing WinPE bootstrap settings TSManager 2/12/2014 1:02:35 AM 1876 (0x0754)
Environment scope successfully created: Global\{E7E5BB69-6198-4555-B5CA-6C46A2B5EB78} TSManager 2/12/2014 1:02:35 AM 1876 (0x0754)
Executing command line: "osdnetsettings.exe" capture adapters:true scope:Global\{E7E5BB69-6198-4555-B5CA-6C46A2B5EB78} TSManager 2/12/2014 1:02:35 AM 1876 (0x0754)
==============================[ OSDNetSettings.exe ]=========================== OSDNetSettings 2/12/2014 1:02:36 AM 2064 (0x0810)
Command line: "osdnetsettings.exe" capture adapters:true scope:Global\{E7E5BB69-6198-4555-B5CA-6C46A2B5EB78} OSDNetSettings 2/12/2014 1:02:36 AM 2064 (0x0810)
No adapters found with non-empty DNSDomainSuffixSearchOrder OSDNetSettings 2/12/2014 1:02:36 AM 2064 (0x0810)
Adapter "ROOT\SYMC_TEEFER2MP\0000" not found OSDNetSettings 2/12/2014 1:02:38 AM 2064 (0x0810)
No physical network adapters found OSDNetSettings 2/12/2014 1:02:38 AM 2064 (0x0810)
OSDNetSettings finished: 0x00000000 OSDNetSettings 2/12/2014 1:02:38 AM 2064 (0x0810)
Process completed with exit code 0 TSManager 2/12/2014 1:02:38 AM 1876 (0x0754)
Installing boot image to hard drive TSManager 2/12/2014 1:02:38 AM 1876 (0x0754)
Backing up existing boot system before trying to set up new boot system TSManager 2/12/2014 1:02:38 AM 1876 (0x0754)
BootLoader::backup: C:\, E:\_SMSTaskSequence\backup TSManager 2/12/2014 1:02:39 AM 1876 (0x0754)
BootLoader::restore: E:\_SMSTaskSequence\WinPE, C:\ TSManager 2/12/2014 1:02:43 AM 1876 (0x0754)
Saving bcd store to E:\_SMSTaskSequence\WinPE\boot\BCD TSManager 2/12/2014 1:02:43 AM 1876 (0x0754)
Executing command line: "E:\_SMSTaskSequence\WinPE\SMS\bin\i386\bootsect.exe" /NT60 SYS /MBR TSManager 2/12/2014 1:02:45 AM 1876 (0x0754)
Process completed with exit code 0 TSManager 2/12/2014 1:02:46 AM 1876 (0x0754)
Updated security on object E:\_SMSTaskSequence. TSManager 2/12/2014 1:02:47 AM 1876 (0x0754)
Set a global environment variable _SMSTSNextInstructionPointer=59 TSManager 2/12/2014 1:02:47 AM 1876 (0x0754)
Set a TS execution environment variable _SMSTSNextInstructionPointer=59 TSManager 2/12/2014 1:02:47 AM 1876 (0x0754)
Set a global environment variable _SMSTSInstructionStackString=0 41 57 TSManager 2/12/2014 1:02:47 AM 1876 (0x0754)
Set a TS execution environment variable _SMSTSInstructionStackString=0 41 57 TSManager 2/12/2014 1:02:47 AM 1876 (0x0754)
Save the current environment block TSManager 2/12/2014 1:02:47 AM 1876 (0x0754)
Updated security on object C:\_SMSTSVolumeID.7159644d-f741-45d5-ab29-0ad8aa4771ca. TSManager 2/12/2014 1:02:47 AM 1876 (0x0754)
Updated security on object D:\_SMSTSVolumeID.7159644d-f741-45d5-ab29-0ad8aa4771ca. TSManager 2/12/2014 1:02:47 AM 1876 (0x0754)
Updated security on object E:\_SMSTSVolumeID.7159644d-f741-45d5-ab29-0ad8aa4771ca. TSManager 2/12/2014 1:02:47 AM 1876 (0x0754)
Updated security on object E:\_SMSTaskSequence. TSManager 2/12/2014 1:02:47 AM 1876 (0x0754)
Set a global environment variable _SMSTSNextInstructionPointer=59 TSManager 2/12/2014 1:02:47 AM 1876 (0x0754)
Set a TS execution environment variable _SMSTSNextInstructionPointer=59 TSManager 2/12/2014 1:02:47 AM 1876 (0x0754)
Set a global environment variable _SMSTSInstructionStackString=0 41 57 TSManager 2/12/2014 1:02:47 AM 1876 (0x0754)
Set a TS execution environment variable _SMSTSInstructionStackString=0 41 57 TSManager 2/12/2014 1:02:47 AM 1876 (0x0754)
Save the current environment block TSManager 2/12/2014 1:02:47 AM 1876 (0x0754)
Expand a string: %_SMSTSMDataPath%\Logs TSManager 2/12/2014 1:02:47 AM 1876 (0x0754)
<![LOG[LOGGING: Finalize process ID set to 780]LOG]!><time="01:04:01.537+480" date="02-12-2014" component="TSBootShell" context="" type="1" thread="784" file="tslogging.cpp:1495">
1/1/1601 12:00:00 AM 1995266923 (0x76ED5B6B)
==============================[ TSBootShell.exe ]============================== TSBootShell 2/12/2014 1:04:01 AM 784 (0x0310)
Succeeded loading resource DLL 'X:\sms\bin\i386\1033\TSRES.DLL' TSBootShell 2/12/2014 1:04:01 AM 784 (0x0310)
Debug shell is enabled TSBootShell 2/12/2014 1:04:01 AM 784 (0x0310)
Waiting for PNP initialization... TSBootShell 2/12/2014 1:04:01 AM 796 (0x031C)
RAM Disk Boot Path: MULTI(0)DISK(0)RDISK(0)PARTITION(3)\_SMSTASKSEQUENCE\WINPE\SOURCES\BOOT.WIM TSBootShell 2/12/2014 1:04:01 AM 796 (0x031C)
WinPE boot path: E:\_SMSTASKSEQUENCE\WINPE\SOURCES\BOOT.WIM TSBootShell 2/12/2014 1:04:01 AM 796 (0x031C)
Booted from fixed disk TSBootShell 2/12/2014 1:04:01 AM 796 (0x031C)
Found config path E:\_SMSTaskSequence TSBootShell 2/12/2014 1:04:01 AM 796 (0x031C)
hMap != 0, HRESULT=80070002 (e:\nts_sccm_release\sms\framework\tscore\environmentscope.cpp,515) TSBootShell 2/12/2014 1:04:01 AM 796 (0x031C)
m_pGlobalScope->open(), HRESULT=80070002 (e:\nts_sccm_release\sms\framework\tscore\environmentlib.cpp,337) TSBootShell 2/12/2014 1:04:01 AM 796 (0x031C)
this->open(), HRESULT=80070002 (e:\nts_sccm_release\sms\framework\tscore\environmentlib.cpp,549) TSBootShell 2/12/2014 1:04:01 AM 796 (0x031C)
hMap != 0, HRESULT=80070002 (e:\nts_sccm_release\sms\framework\tscore\environmentscope.cpp,515) TSBootShell 2/12/2014 1:04:01 AM 796 (0x031C)
m_pGlobalScope->open(), HRESULT=80070002 (e:\nts_sccm_release\sms\framework\tscore\environmentlib.cpp,337) TSBootShell 2/12/2014 1:04:01 AM 796 (0x031C)
this->open(), HRESULT=80070002 (e:\nts_sccm_release\sms\framework\tscore\environmentlib.cpp,549) TSBootShell 2/12/2014 1:04:01 AM 796 (0x031C)
hMap != 0, HRESULT=80070002 (e:\nts_sccm_release\sms\framework\tscore\environmentscope.cpp,515) TSBootShell 2/12/2014 1:04:01 AM 796 (0x031C)
m_pGlobalScope->open(), HRESULT=80070002 (e:\nts_sccm_release\sms\framework\tscore\environmentlib.cpp,337) TSBootShell 2/12/2014 1:04:01 AM 796 (0x031C)
open(), HRESULT=80070002 (e:\nts_sccm_release\sms\framework\tscore\environmentlib.cpp,430) TSBootShell 2/12/2014 1:04:01 AM 796 (0x031C)
Can not find DeploymentType in file TsmBootstrap.ini or the file doesn't exist. This is not running on Windows To Go. TSBootShell 2/12/2014 1:04:01 AM 796 (0x031C)
hMap != 0, HRESULT=80070002 (e:\nts_sccm_release\sms\framework\tscore\environmentscope.cpp,515) TSBootShell 2/12/2014 1:04:01 AM 796 (0x031C)
m_pGlobalScope->open(), HRESULT=80070002 (e:\nts_sccm_release\sms\framework\tscore\environmentlib.cpp,337) TSBootShell 2/12/2014 1:04:01 AM 796 (0x031C)
open(), HRESULT=80070002 (e:\nts_sccm_release\sms\framework\tscore\environmentlib.cpp,430) TSBootShell 2/12/2014 1:04:01 AM 796 (0x031C)
Restoring boot system from E:\_SMSTaskSequence\backup TSBootShell 2/12/2014 1:04:01 AM 796 (0x031C)
Successfully loaded the BCD boot system TSBootShell 2/12/2014 1:04:05 AM 796 (0x031C)
Successfully loaded an exported NTLDR boot system TSBootShell 2/12/2014 1:04:05 AM 796 (0x031C)
BootLoader::restore: E:\_SMSTaskSequence\backup, C:\ TSBootShell 2/12/2014 1:04:05 AM 796 (0x031C)
Successfully merged logs from cache. TSBootShell 2/12/2014 1:04:06 AM 796 (0x031C)
hMap != 0, HRESULT=80070002 (e:\nts_sccm_release\sms\framework\tscore\environmentscope.cpp,515) TSBootShell 2/12/2014 1:04:06 AM 796 (0x031C)
m_pGlobalScope->open(), HRESULT=80070002 (e:\nts_sccm_release\sms\framework\tscore\environmentlib.cpp,337) TSBootShell 2/12/2014 1:04:06 AM 796 (0x031C)
open(), HRESULT=80070002 (e:\nts_sccm_release\sms\framework\tscore\environmentlib.cpp,430) TSBootShell 2/12/2014 1:04:06 AM 796 (0x031C)
Loading bootstrap settings from E:\_SMSTaskSequence\WinPE TSBootShell 2/12/2014 1:04:06 AM 796 (0x031C)
Loading saved WinPE settings TSBootShell 2/12/2014 1:04:06 AM 796 (0x031C)
Creating key 'Software\Microsoft\SMS\47006C006F00620061006C005C007B00450037004500350042004200360039002D0036003100390038002D0034003500350035002D0042003500430041002D003600430034003600410032004200350045004200370038007D00' TSBootShell
2/12/2014 1:04:06 AM 796 (0x031C)
Environment scope successfully created: Global\{E7E5BB69-6198-4555-B5CA-6C46A2B5EB78} TSBootShell 2/12/2014 1:04:06 AM 796 (0x031C)
Configuring WinPE bootstrap settings TSBootShell 2/12/2014 1:04:06 AM 796 (0x031C)
Creating WinPE answer file TSBootShell 2/12/2014 1:04:06 AM 796 (0x031C)
Setting hive location to "X:\windows\system32" TSBootShell 2/12/2014 1:04:06 AM 796 (0x031C)
Getting namespace "Microsoft-Windows-Setup" for architecture "x86" TSBootShell 2/12/2014 1:04:06 AM 796 (0x031C)
Configuring global network settings TSBootShell 2/12/2014 1:04:06 AM 796 (0x031C)
Join type: TSBootShell 2/12/2014 1:04:06 AM 796 (0x031C)
DNS domain: exch1.mas.unb.com TSBootShell 2/12/2014 1:04:06 AM 796 (0x031C)
DNS domain search order: TSBootShell 2/12/2014 1:04:06 AM 796 (0x031C)
IP filter sec enabled: false TSBootShell 2/12/2014 1:04:06 AM 796 (0x031C)
No adapters found in environment. Performing global configuration only. TSBootShell 2/12/2014 1:04:06 AM 796 (0x031C)
Writing configuration information to E:\_SMSTaskSequence\WinPE\WinPeUnattend.xml TSBootShell 2/12/2014 1:04:06 AM 796 (0x031C)
Successfully saved configuration information to E:\_SMSTaskSequence\WinPE\WinPeUnattend.xml TSBootShell 2/12/2014 1:04:06 AM 796 (0x031C)
Executing command line: wpeinit.exe -winpe TSBootShell 2/12/2014 1:04:06 AM 796 (0x031C)
The command completed successfully. TSBootShell 2/12/2014 1:05:40 AM 796 (0x031C)
Starting DNS client service. TSBootShell 2/12/2014 1:05:40 AM 796 (0x031C)
Finalizing network settings TSBootShell 2/12/2014 1:05:40 AM 796 (0x031C)
No adapters found in environment. Performing global finalization only. TSBootShell 2/12/2014 1:05:40 AM 796 (0x031C)
Finalizing global network settings TSBootShell 2/12/2014 1:05:40 AM 796 (0x031C)
DNS domain: exch1.mas.unb.com TSBootShell 2/12/2014 1:05:40 AM 796 (0x031C)
DNS domain search order: TSBootShell 2/12/2014 1:05:40 AM 796 (0x031C)
DNS for WINS enabled: false TSBootShell 2/12/2014 1:05:40 AM 796 (0x031C)
LMHosts file enabled: true TSBootShell 2/12/2014 1:05:40 AM 796 (0x031C)
Host lookup file: TSBootShell 2/12/2014 1:05:40 AM 796 (0x031C)
WINS scope ID: TSBootShell 2/12/2014 1:05:40 AM 796 (0x031C)
Executing command line: X:\sms\bin\i386\TsmBootstrap.exe /env:WinPE /configpath:E:\_SMSTaskSequence TSBootShell 2/12/2014 1:05:40 AM 796 (0x031C)
The command completed successfully. TSBootShell 2/12/2014 1:05:40 AM 796 (0x031C)
==============================[ TSMBootStrap.exe ]============================== TSMBootstrap 2/12/2014 1:05:40 AM 1984 (0x07C0)
Command line: X:\sms\bin\i386\TsmBootstrap.exe /env:WinPE /configpath:E:\_SMSTaskSequence TSMBootstrap 2/12/2014 1:05:40 AM 1984 (0x07C0)
Succeeded loading resource DLL 'X:\sms\bin\i386\1033\TSRES.DLL' TSMBootstrap 2/12/2014 1:05:40 AM 1984 (0x07C0)
Succeeded loading resource DLL 'X:\sms\bin\i386\TSRESNLC.DLL' TSMBootstrap 2/12/2014 1:05:40 AM 1984 (0x07C0)
Adding SMS bin folder "X:\sms\bin\i386" to the system environment PATH TSMBootstrap 2/12/2014 1:05:40 AM 1984 (0x07C0)
Failed to open PXE registry key. Not a PXE boot. TSMBootstrap 2/12/2014 1:05:40 AM 1984 (0x07C0)
Resuming Task Sequence in WinPE TSMBootstrap 2/12/2014 1:05:40 AM 1984 (0x07C0)
Creating key 'Software\Microsoft\SMS\47006C006F00620061006C005C007B00350031004100300031003600420036002D0046003000440045002D0034003700350032002D0042003900370043002D003500340045003600460033003800360041003900310032007D00' TSMBootstrap
2/12/2014 1:05:40 AM 1984 (0x07C0)
Environment scope successfully created: Global\{51A016B6-F0DE-4752-B97C-54E6F386A912} TSMBootstrap 2/12/2014 1:05:40 AM 1984 (0x07C0)
Creating key 'Software\Microsoft\SMS\47006C006F00620061006C005C007B00420041003300410033003900300030002D0043004100360044002D0034006100630031002D0038004300320038002D003500300037003300410046004300320032004200300033007D00' TSMBootstrap
2/12/2014 1:05:40 AM 1984 (0x07C0)
Environment scope successfully created: Global\{BA3A3900-CA6D-4ac1-8C28-5073AFC22B03} TSMBootstrap 2/12/2014 1:05:40 AM 1984 (0x07C0)
Loading the Task Sequencing Environment from "E:\_SMSTaskSequence\TSEnv.dat". TSMBootstrap 2/12/2014 1:05:41 AM 1984 (0x07C0)
Updating the local data path in the Task Sequencing Environment. TSMBootstrap 2/12/2014 1:05:41 AM 1984 (0x07C0)
Setting LogMaxSize to 1000000 TSMBootstrap 2/12/2014 1:05:41 AM 1984 (0x07C0)
Setting LogMaxHistory to 1 TSMBootstrap 2/12/2014 1:05:41 AM 1984 (0x07C0)
Setting LogLevel to 0 TSMBootstrap 2/12/2014 1:05:41 AM 1984 (0x07C0)
Setting LogEnabled to 1 TSMBootstrap 2/12/2014 1:05:41 AM 1984 (0x07C0)
Setting LogDebug to 1 TSMBootstrap 2/12/2014 1:05:41 AM 1984 (0x07C0)
Command line for extension .exe is "%1" %* TSMBootstrap 2/12/2014 1:05:41 AM 1984 (0x07C0)
Set command line: "X:\sms\bin\i386\TsProgressUI.exe" /Register:WinPE TSMBootstrap 2/12/2014 1:05:41 AM 1984 (0x07C0)
Executing command line: "X:\sms\bin\i386\TsProgressUI.exe" /Register:WinPE TSMBootstrap 2/12/2014 1:05:41 AM 1984 (0x07C0)
==========[ TsProgressUI started in process 2004 ]========== TsProgressUI 2/12/2014 1:05:41 AM 2008 (0x07D8)
Command line: "X:\sms\bin\i386\TsProgressUI.exe" /Register:W
In dire need of help,
I have already gone through the below articles on the NET
http://social.technet.microsoft.com/Forums/systemcenter/en-US/0fe5cded-51cf-487a-97e3-837fb3426a3e/install-software-updates-in-osd-reboots-leaves-clients-in-provisioning-mode?forum=configmgrosd
http://social.technet.microsoft.com/Forums/systemcenter/en-US/c590e486-d3ca-423f-8953-e596160f3567/updates-hang-during-osd-kb2509007-not-working-for-me?forum=configmgrosd
Awating response,
Hasan RezaWell Finally I sorted my issue ,
Just want to share the solution, may be it would be helpful to some one else and save some times
The problem was that the Xp images has lot of hidden NIC installed , this would not allow the system to work with the correct NIC card and Ip address (System -> View Hidden Devices) , what I did 2 things
1) Copied the OSD Script folder from the SCCM Server to the Client pc and ran that ztigather.wsf and captured the output , it was evident that it showed capturing multiple adapters , (There are some blogs that pointed out that OSD can capture only one nic
due to the only one Adapter0 section being defined in the ZTIgather.xml file,)
2) I open the registry at the xp pc navigated to HKLM-> System ->Current Control Set-> Services-> TCPIP -> Parameters-> Interfaces ->
Expect for the NIC card that had the Ip address assigned I deleted all other nic card's guid,
As then post running deleting the old scanstate (USMTUTIL /rd c:\statestore) , reran the task and VOILA..
All worked fine , below are the two post I followed , though notvery relevant but they were helpful and help me reached the conclusion.
Thanks,
Hasan Reza.
http://systemscenter.ru/mdt2012.en/ztigatherwsf.htm
http://social.technet.microsoft.com/Forums/windowsserver/en-US/8acb7cd1-7028-4ffe-86c9-eb43041cf8b3/how-do-i-get-rid-of-second-169254xx-ipv4-address-on-windows-server-2008-sp2-x86?forum=winservergen -
Error while deploying Windows 2008 R2 using SCCM 2012 R2
I am trying to deploy Window 2008 R2 image (captured from a reference machine) using SCCM 2012 R2. I have integrated MDT 2013 with SCCM 2012 R2 and created an MDT task sequence. During deployment, towards the end of Applying image.wim, it gives me
an error that task sequence failed with the error code 0x80070002. And then the system reboots. After reboot, I am able to login to the Windows Server. It seems to work fine, but there are no applications etc installed. Also the _SMSTS log folder is still
present in the C drive. And in the smsts.log file, i can see errors like failed to copy unattend.xml file. Please help me.Hi,
Error code 0x80070002, it means the system cannot find file specified.
For more information, please review the link below:
Task Sequence Failed with the Error Code 0x80070002
http://prajwaldesai.com/task-sequence-failed-error-code-0x80070002/
Note: Microsoft provides third-party contact information to help you find technical support. This contact information may change without notice. Microsoft does not guarantee the accuracy of this third-party contact information.
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place. -
SCCM 2012 SP1 - OS Deployment - hash could not be matched for the downloded content
I've got a newly deployed SCCM 2012 SP1 running on Windows Server 2012. The W2K12 runs as vm on ESX 5.1. I'm having very odd issues with OS deployment. The TS keeps failing when processing SCCM client installation - it downloads the package but then it fails
straight away with the 80091007 - hash values couldn't be matched error - some extract from smsts.log attached below. It's very consistent, it happens every time - it downloads and applies the image fine straight after that it bombs out.
What is very interesting is that it works perfectly fine when I deploy vms (on the same or different host) - the issue seems to be be only affecting physical machines (laptops desktops). This might suggest some network issues (vSwitch with Cisco switches) but
the config on the switch is very simple and this shouldn't be the case.
I had a few virtualised SCCM 2007 installations (ESX 5 and 4) and it always worked with no problems.
I tried to recreate the package (changing source directory), turn binary differential replication on and off, copy the content of the package to the dist point or not copy. Push client installation (or other package deployments) work fine
When I tried to deploy with no download - sometimes it works but most of the time I'd get the files/folder corrupt error (can't remember the No)
This is starting to drive me crazy - There are some significant changes in the way SCCM 2012 is validating package integrity (like Content Lib folder) but the consistency of this problem is just very odd.
Anyone has any clues?
thanks
- Downloaded file from http://GTKVMGMT05.GTK.LOC...m?/x64/wic_x64_enu.exe to C:\_SMSTaskSequence\Packages\GTK0000C\x64/wic_x64_enu.exe
- Download done setting progress bar to 100
VerifyContentHash: Hash algorithm is 32780
c:\_smstasksequence\packages\GTK0000c\i386 is a directory. Setting directory security
c:\_smstasksequence\packages\GTK0000c\x64 is a directory. Setting directory security
- Hash could not be matched for the downloded content. Original ContentHash = 5EF3A189C48F3469440A83026EC8ECD36EAD6EAF3B5D35663F8201BDE175413C, Downloaded ContentHash = FA4516EDD2D7907F8FA472A3E1B717DF2DD4A0976CD4CEAE11045EE62EC8C661
0L == TS::Utility::VerifyPackageHash(pszContentID, sDestination), HRESULT=80091007 (e:\nts_sccm_release\sms\framework\tscore\resolvesource.cpp,2999)
- DownloadContentAndVerifyHash(pszPackageID, L"SMSPackage", saHttpContentSources, saSMBContentSources, saMulticastContentSources, sDestination, dwFlags, L"", 0, dwPackageFlags, pszUserName, pszUserPassword ), HRESULT=80091007 (e:\nts_sccm_release\sms\framework\tscore\resolvesource.cpp,3106)
- DownloadContentLocally(pszSource, sSourceDirectory, dwFlags, hUserToken, pszUserName, pszUserPassword), HRESULT=80091007 (e:\nts_sccm_release\sms\framework\tscore\resolvesource.cpp,3331)
ResolveSource(pszSource, sSourceDirectory, dwFlags, 0, 0, 0), HRESULT=80091007 (e:\nts_sccm_release\sms\framework\tscore\resolvesource.cpp,3221)
TS::Utility::ResolveSource(sClientPackageID, sClientPackagePath), HRESULT=80091007 (e:\nts_sccm_release\sms\client\osdeployment\osdgina\basesetuphook.cpp,1655)
- Failed to resolve package source "GTK0000C"
- Exiting ConfigureEx: 0x80091007
- BaseSetupHook::configure(sWindowsDir), HRESULT=80091007 (e:\nts_sccm_release\sms\client\osdeployment\osdgina\osdsetuphook.cpp,292)
- Failed to configure OSD setup hook (0x80091007)
- Failed to configure OSD setup hook (0x80091007)is this the only indication of a problem in your smsts.log file ? did you apply the
authenticode hotfix or have you
downloaded the SP1 media after that hotfix was applied ?
Step by Step Configuration Manager Guides >
2012 Guides |
2007 Guides | I'm on Twitter > ncbrady -
SCCM 2012 CU2 OSD forest trust: ReleaseRequest failed with error code 0x87d00317
Hello,
Actually i have a difficult Problem with my SCCM 2012 R2 CU2 Windows 7 x64 SP1 Tasksequence:
I get the folowing error in smsts.log:
::RegQueryValueExW(hSubKey, szReg, NULL, NULL, NULL, &dwSize), HRESULT=80070002 (e:\qfe\nts\sms\framework\tscore\utils.cpp,811) TSManager 9/5/2014 1:20:35 PM 1740 (0x06CC)
RegQueryValueExW is unsuccessful for Software\Microsoft\SMS\Task Sequence, SMSTSEndProgram TSManager 9/5/2014 1:20:35 PM 1740 (0x06CC)
GetTsRegValue() is unsuccessful. 0x80070002. TSManager 9/5/2014 1:20:35 PM 1740 (0x06CC)
End program: TSManager 9/5/2014 1:20:35 PM 1740 (0x06CC)
Finalize logging request ignored from process 1736 TSManager 9/5/2014 1:20:35 PM 1740 (0x06CC)
Waiting for CcmExec service to be fully operational TSManager 9/5/2014 1:20:35 PM 1740 (0x06CC)
CcmExec service is up and fully operational TSManager 9/5/2014 1:20:35 PM 1740 (0x06CC)
Access handle will be read from _SMSTSActiveRequestHandle TSManager 9/5/2014 1:20:35 PM 1740 (0x06CC)
Access handle: {B699D570-B2BF-4874-8CB7-3B208B380969} TSManager 9/5/2014 1:20:35 PM 1740 (0x06CC)
Attempting to release request using {B699D570-B2BF-4874-8CB7-3B208B380969} TSManager 9/5/2014 1:20:35 PM 1740 (0x06CC)
CoCreateInstance succeeded TSManager 9/5/2014 1:20:35 PM 1740 (0x06CC)
pISoftwareExecutionRequestMgr->ReleaseRequest(ActiveRequestGUID), HRESULT=87d00317 (e:\nts_sccm_release\sms\client\tasksequence\tsmanager\tsmanagerutils.cpp,136) TSManager 9/5/2014 1:20:35 PM 1740 (0x06CC)
ReleaseRequest failed with error code 0x87d00317 TSManager 9/5/2014 1:20:35 PM 1740 (0x06CC)
Task Sequence Manager could not release active TS request. code 87D00317 TSManager 9/5/2014 1:20:35 PM 1740 (0x06CC)
Here is the complete smsts.log: http://1drv.ms/1pwTEBf
To explain the Problem in Detail:
The SCCM Primary Site Server and the Clients are in different trusted (bidirectional) forests!
Everythings working fine in this Scenario, I can install SCCM Agent on the Clients with Manual ccmsetup and with Client Push Installation. Additionally i can deploy Software Updates and so on... only OSD is crashing in the releaserequest step.
During my Tasksequence new Clients are joined to Domain A while SCCM Primary Site Server is installed in Domain B
If I change my TS and let the Clients also join Domain B everything works without any Problems and the Tasksequence finish without any Errors.
My Problem must be related to the different Domains and the forest trust.
My Setup:
MP published to DNS in both domains
Schema Extended in both domains
System Management Container published and verified in both domains
ccmsetup Parameters in TS: ccmsetup SMSMP=sccm.domain.b FSP=sccm.domain.b DNSSUFFIX=Domain.b
Network Access account configured with Domain B account
Domain Join account has create Computer rights on the OU in Domain A (Domain join is successful)
DNs conditional forwarders configured in both Domains and DNS resolutin is working in both directions
Any suggestions?
Many thanks.
regards,
ChristianHi Christian,
So do you actual get an error message in your TS or is it just failing to join Domain B? (Could be both if the machines fails to join the domain).
Can you review netsetup.log on the machines after the issue and see what error message you might be getting during the domain join process?
Also, if it a domain join issue, can you try manually joining to domain B using the same service account?
Maybe you are looking for
-
Will the macbook be able to run...
Counter-strike 1.6 The macbook I am getting is the better white one, and I am getting the router and a total of 1 gig ram.
-
The bookmark box does not appear, bookmarks straight to the bottom of the list
When I use the Bookmarks menu at the top of the page, hit Bookmark this page, the little box that USED to popup to assign what catagory folder the bookmark is to go into, does not appear. the page is bookmarked, but goes on the bottom of the list, in
-
I am, indeed, yet another confused iPod touch user, this time however, rightly so. Before the issue occurred, the iPod was working, but certain things were not, I was unsure if it was my iPod, or simply a problem with the AIM servers. I had been usin
-
Can anybody help?? I was using the application locally for the last 7 months.
-
I have my Blackberry Curve 8330 to sync with my Windows XP computer at work. I just got an Imac for Christmas and would love to ALSO sync it with that at home. Can you sync with both the Imac and XP or do I have to make a choice? Thanks so much.