Error while capturing Windows Xp image with MDT 2012.

Hi,
here is the log file. please go thriugh this log and resolve my issue.
------ Applying bootable Windows PE image ------ LTIApply
LTI applying Windows PE LTIApply
FAILURE ( 5610 ): False: Verify File:
\\WIN-0KLPXWQQGYL\DeploymentShare$\Boot\LiteTouchPE_x86.wim LTIApply
Command completed, return code = -2147467259 LiteTouch
Litetouch deployment failed, Return Code = -2147467259 0x80004005 LiteTouch
For more information, consult the task sequencer log ...\SMSTS.LOG. LiteTouch
Property RetVal is now = -2147467259 LiteTouch
CleanStartItems Complete LiteTouch 1
About to run command: MSHTA.exe "\\WIN-0KLPXWQQGYL\DeploymentShare$\Scripts\Wizard.hta" /definition:Summary_Definition_ENU.xml LiteTouch
Property definition is now = Summary_Definition_ENU.xml Wizard
Microsoft Deployment Toolkit version: 6.0.1763.0 Wizard
Not Wizard = False Wizard
Property WizardComplete is now = N Wizard
Property WizardComplete is now = Y Wizard
Command completed, return code = 0 LiteTouch
Unable to copy log to the network as no SLShare value was specified. LiteTouch
CleanStartItems Complete LiteTouch 10/31/2011 11:53:46 AM 0 (0x0000)
Unregistering TSCore.dll. LiteTouch 10/31/2011 11:53:46 AM 0 (0x0000)
About to run command: wscript.exe "\\WIN-0KLPXWQQGYL\DeploymentShare$\Scripts\LTICleanup.wsf"
ZTI ERROR - Non-zero return code by LiteTouch, rc = -2147467259 0x80004005

Error 0x7b is something different. IT means that you don't have the correct storage driver installed. Are you running an IHCA? To get around this most IT professionals will create their images on *virtual machines* like Hyper-V. YOu won't need to load any
special drivers, and even better the image you create will be pretty clean (as long as it's a generic image). Don, It's not clear from *where* you received the 7b, Was it within Windows XP? Within WinPE, or somewhere else? Be specific.
Additionaly, the "Sysprep and Capture" Task Sequence Template is great if you *already* have the image created just the way you want. However, if you are starting from scratch, I would recommend looking into using the *full* "CLient" deployment Task Sequence
Template. That will allow you to deploy the OS, install applications, sysprep *AND* capture all in one automated process.
Keith Garner - keithga.wordpress.com

Similar Messages

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.

MDT : creating windows 7x64 images with required applications and deploying it

Hi,
We have to create windows 7 x64 and windows 8 images with all the custom applications and which can also be used on all the hardwares. I heard MDT can be used. How can I do this and what are the pre-requisites for installion and steps for configuring MDT
tool ?
do we need ADK for installing MDT ? I tried installing ADK ,but it says you need have ADK documentation_x86_en_us.msi.
Thanks.

For drivers, I have always used the .inf files.
For applications, it depends upon how you want to deploy them. Lots of people build their 'gold' image to contain all the applications they want installed, and then use that as a basis for deployment. Others build special scripts in to select
specific applications based on security groups.
The thing about MDT is that it is very flexible and can be adapted to a lot of different situations. You first need to define exactly how you plan to use it and then build your image(s) accordingly.
The guides you can find online will assist you in the specific steps for the solution option you chose. There is not a single, simple answer to cover all cases.
.:|:.:|:. tim

Error while creating the HTTP client with destination GB_DPSRetrieve

Hi All,
It is an interface R/3 -->XI --> HTTP ( proxy to HTTP ).
Please find the error log below and throw some light why the HTTP adapter is getting error -
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" xmlns:SAP="http://sap.com/xi/XI/Message/30">
- <SOAP:Header>
- <SAP:Main xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" xmlns:wsu="http://www.docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" versionMajor="003" versionMinor="000" SOAP:mustUnderstand="1" wsu:Id="wsuid-main-92ABE13F5C59AB7FE10000000A1551F7">
<SAP:MessageClass>SystemError</SAP:MessageClass>
<SAP:ProcessingMode>synchronous</SAP:ProcessingMode>
<SAP:MessageId>DC98499F-7E42-74F1-A41F-0017A4107EE6</SAP:MessageId>
<SAP:RefToMessageId>DC98499C-A1EA-BEF1-B4DD-00110A63BF06</SAP:RefToMessageId>
<SAP:TimeSent>2007-11-21T15:51:30Z</SAP:TimeSent>
- <SAP:Sender>
<SAP:Party agency="http://sap.com/xi/XI" scheme="XIParty">GovernmentGateway</SAP:Party>
<SAP:Service>GGMailbox</SAP:Service>
<SAP:Interface namespace="http://sap.com/xi/E-FILING_GB/2005">DPSretrieve</SAP:Interface>
</SAP:Sender>
- <SAP:Receiver>
<SAP:Party agency="" scheme="" />
<SAP:Service>SAP_DEV_ERP2005</SAP:Service>
<SAP:Interface namespace="http://sap.com/xi/HR">HR_GB_EFI_DPSretrieve</SAP:Interface>
</SAP:Receiver>
<SAP:Interface namespace="http://sap.com/xi/E-FILING_GB/2005">DPSretrieve</SAP:Interface>
</SAP:Main>
- <SAP:ReliableMessaging xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:QualityOfService>BestEffort</SAP:QualityOfService>
</SAP:ReliableMessaging>
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="PLAINHTTP_ADAPTER">ATTRIBUTE_CLIENT_DEST</SAP:Code>
<SAP:P1>GB_DPSRetrieve</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Error while creating the HTTP client with destination GB_DPSRetrieve</SAP:Stack>
<SAP:Retry>N</SAP:Retry>
</SAP:Error>
- <SAP:HopList xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
- <SAP:Hop timeStamp="2007-11-21T15:51:30Z" wasRead="false">
<SAP:Engine type="BS">SAP_DEV_ERP2005</SAP:Engine>
<SAP:Adapter namespace="http://sap.com/xi/XI/System">XI</SAP:Adapter>
<SAP:MessageId>DC98499C-A1EA-BEF1-B4DD-00110A63BF06</SAP:MessageId>
<SAP:Info>3.0</SAP:Info>
</SAP:Hop>
- <SAP:Hop timeStamp="2007-11-21T15:51:30Z" wasRead="false">
<SAP:Engine type="IS">is.00.lbsth-tb1ci</SAP:Engine>
<SAP:Adapter namespace="http://sap.com/xi/XI/System">XI</SAP:Adapter>
<SAP:MessageId>DC98499C-A1EA-BEF1-B4DD-00110A63BF06</SAP:MessageId>
<SAP:Info>3.0</SAP:Info>
</SAP:Hop>
- <SAP:Hop timeStamp="2007-11-21T15:51:30Z" wasRead="false">
<SAP:Engine type="IS" />
<SAP:Adapter namespace="http://sap.com/xi/XI/System">HTTP</SAP:Adapter>
<SAP:MessageId>DC98499C-A1EA-BEF1-B4DD-00110A63BF06</SAP:MessageId>
<SAP:Info />
</SAP:Hop>
</SAP:HopList>
- <SAP:RunTime xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
<SAP:Date>20071121</SAP:Date>
<SAP:Time>155130</SAP:Time>
<SAP:Host>lbsth-tb1ci</SAP:Host>
<SAP:SystemId>XIS</SAP:SystemId>
<SAP:SystemNr>00</SAP:SystemNr>
<SAP:OS>Windows NT</SAP:OS>
<SAP:DB>ORACLE</SAP:DB>
<SAP:Language />
<SAP:ProcStatus>023</SAP:ProcStatus>
<SAP:AdapterStatus>000</SAP:AdapterStatus>
<SAP:User>PISUPER</SAP:User>
<SAP:TraceLevel>1</SAP:TraceLevel>
<SAP:LogSeqNbr>000</SAP:LogSeqNbr>
<SAP:RetryLogSeqNbr>000</SAP:RetryLogSeqNbr>
<SAP:PipelineIdInternal>SAP_CENTRAL</SAP:PipelineIdInternal>
<SAP:PipelineIdExternal>CENTRAL</SAP:PipelineIdExternal>
<SAP:PipelineElementId>60C3C53B4BB7B62DE10000000A1148F5</SAP:PipelineElementId>
<SAP:PipelineService>PLSRV_CALL_ADAPTER</SAP:PipelineService>
<SAP:QIdInternal />
<SAP:CommitActor>X</SAP:CommitActor>
<SAP:SplitNumber>0</SAP:SplitNumber>
<SAP:NumberOfRetries>0</SAP:NumberOfRetries>
<SAP:NumberOfManualRetries>0</SAP:NumberOfManualRetries>
<SAP:TypeOfEngine client="200">CENTRAL</SAP:TypeOfEngine>
<SAP:PlsrvExceptionCode />
<SAP:EOReferenceRuntime type="TID" />
<SAP:EOReferenceInbound type="TID" />
<SAP:EOReferenceOutbound type="TID" />
<SAP:MessageSizePayload>0</SAP:MessageSizePayload>
<SAP:MessageSizeTotal>2918</SAP:MessageSizeTotal>
<SAP:PayloadSizeRequest>0</SAP:PayloadSizeRequest>
<SAP:PayloadSizeRequestMap>0</SAP:PayloadSizeRequestMap>
<SAP:PayloadSizeResponse>0</SAP:PayloadSizeResponse>
<SAP:PayloadSizeResponseMap>0</SAP:PayloadSizeResponseMap>
<SAP:Reorganization>INI</SAP:Reorganization>
<SAP:AdapterInbound>PLAINHTTP</SAP:AdapterInbound>
<SAP:AdapterOutbound>IENGINE</SAP:AdapterOutbound>
<SAP:InterfaceAction>INIT</SAP:InterfaceAction>
<SAP:RandomNumber>15</SAP:RandomNumber>
<SAP:AckStatus>000</SAP:AckStatus>
<SAP:SkipReceiverDetermination />
<SAP:Receiver_Agreement_GUID>24422A5646443F8E9D975D57A3EE8162</SAP:Receiver_Agreement_GUID>
</SAP:RunTime>
- <SAP:PerformanceHeader xmlns:SAP="http://sap.com/xi/XI/Message/30">
- <SAP:RunTimeItem>
<SAP:Name type="ADAPTER_IN">INTEGRATION_ENGINE_HTTP_ENTRY</SAP:Name>
<SAP:Timestamp type="begin" host="lbsth-tb1ci">20071121155130.5</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="ADAPTER_IN">INTEGRATION_ENGINE_HTTP_ENTRY</SAP:Name>
<SAP:Timestamp type="end" host="lbsth-tb1ci">20071121155130.515</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="CORE">INTEGRATION_ENGINE</SAP:Name>
<SAP:Timestamp type="begin" host="lbsth-tb1ci">20071121155130.515</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="CORE">INTEGRATION_ENGINE</SAP:Name>
<SAP:Timestamp type="end" host="lbsth-tb1ci">20071121155130.515</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="PLSRV">PLSRV_RECEIVER_DETERMINATION</SAP:Name>
<SAP:Timestamp type="begin" host="lbsth-tb1ci">20071121155130.515</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="PLSRV">PLSRV_RECEIVER_DETERMINATION</SAP:Name>
<SAP:Timestamp type="end" host="lbsth-tb1ci">20071121155130.515</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="PLSRV">PLSRV_INTERFACE_DETERMINATION</SAP:Name>
<SAP:Timestamp type="begin" host="lbsth-tb1ci">20071121155130.515</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="PLSRV">PLSRV_INTERFACE_DETERMINATION</SAP:Name>
<SAP:Timestamp type="end" host="lbsth-tb1ci">20071121155130.515</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="PLSRV">PLSRV_RECEIVER_MESSAGE_SPLIT</SAP:Name>
<SAP:Timestamp type="begin" host="lbsth-tb1ci">20071121155130.515</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="PLSRV">PLSRV_RECEIVER_MESSAGE_SPLIT</SAP:Name>
<SAP:Timestamp type="end" host="lbsth-tb1ci">20071121155130.515</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="PLSRV">PLSRV_MAPPING_REQUEST</SAP:Name>
<SAP:Timestamp type="begin" host="lbsth-tb1ci">20071121155130.515</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="PLSRV">PLSRV_MAPPING_REQUEST</SAP:Name>
<SAP:Timestamp type="end" host="lbsth-tb1ci">20071121155130.531</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="PLSRV">PLSRV_OUTBOUND_BINDING</SAP:Name>
<SAP:Timestamp type="begin" host="lbsth-tb1ci">20071121155130.531</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="PLSRV">PLSRV_OUTBOUND_BINDING</SAP:Name>
<SAP:Timestamp type="end" host="lbsth-tb1ci">20071121155130.531</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="PLSRV">PLSRV_CALL_ADAPTER</SAP:Name>
<SAP:Timestamp type="begin" host="lbsth-tb1ci">20071121155130.531</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="CORE">INTEGRATION_ENGINE</SAP:Name>
<SAP:Timestamp type="end" host="lbsth-tb1ci">20071121155130.656</SAP:Timestamp>
</SAP:RunTimeItem>
</SAP:PerformanceHeader>
- <SAP:Diagnostic xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:TraceLevel>Information</SAP:TraceLevel>
<SAP:Logging>Off</SAP:Logging>
</SAP:Diagnostic>
- <SAP:Trace xmlns:SAP="http://sap.com/xi/XI/Message/30">
<Trace level="1" type="T">SystemError message generated. Guid: DC98499F7E4274F1A41F0017A4107EE6</Trace>
<Trace level="1" type="T">Error during execution of message : DC98499CA1EABEF1B4DD00110A63BF06</Trace>
<Trace level="1" type="T">ApplicationMessage was (=RefToMsgId): DC98499CA1EABEF1B4DD00110A63BF06</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
- 
</SAP:Trace>
</SOAP:Header>
- <SOAP:Body>
<SAP:Manifest xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:wsu="http://www.docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" wsu:Id="wsuid-manifest-5CABE13F5C59AB7FE10000000A1551F7" />
</SOAP:Body>
</SOAP:Envelope>
Regards,
Kishore

Hi,
In the HTTP Receiver what is the Addressing Type used ? (URL Address or HTTP Destination).
If its URL Addressing Type, check if right Authentication Type is used with valid values and for HTTP Addressing Type check this HTTP Client Create Error, it could be helpful.
Also check if the Target system can be reached from the XI server to validate the configuration parameters.
Regards,
S.Santhosh Kumar

Error while adding a custom field with Input help via AET

Hi All,
I need to add two custom field under Service orders at Item level in component BT140I_SRVP.
One field is required to have the input search help f4 and autopopulates the second field
I am able to add one field(not requiring help) successfully through AET .
I have created one Zsearch_help in se11 and its successfully running and Autopopulating seocnd field while I am testing it
While adding second field through AET,I need to enter following details as -
field label,search relevant ,serach help etc.
When I type the name of my 'Zsearch_help' against field search help it gives me following error
'Search help is not compatible'.
Secondly,not getting getter and setter methods for the attrributes in BTAdminI.
Last,please tell me if i create zhelp and activate it,would it automatically appear in the list on AETwhile assiging it to input field?
Please help me out.Kindly be detailed as I am new to SAP CRM.
Thanks,
Shivani

The question is answered in CRM 7.0 forum:
Getting error while adding a custom field (with input help) through AET

Error while creating the sales order with billing reference

hi alll
i am getting error while creating the sales order with billing reference.The line items are coming in grey.I am not able to change the items as well as the quantity field.Can u guide me
cheers
shalsa007........

Dear SAP SD 007
I can confidently tell that an enhancement or an user exit has been applied in your scenario
You have to check that
Normally when creating a sales order with respect or referring billing documents the qty will be in editable mode and it is standard problem
Your people has solved the standard problem by enhancement
Usually OR--LF-PGI----F2 (SAY THE QTY IS 25 UNITS)
Now you are creating returns order with reference to F2 in the return order type Re there is a standard issue that user can edit the qty to 30 from the original 25
To solve this only your people have used userexit
Line items and qty greyed out means definately there is some enhancement or user exit applied
You have to check that
Regards
Raja

Error while executing SDM process phase with action DEPLOY_SLOT

Hi,
I am upgrading CRM 2007 to CRM 7.0 and got an error in Java side.
Following is DEPLOY_SLOT_1_DON_01.LOG
<!LOGHEADER[START]/>
<!HELP[Manual modification of the header may cause parsing problem!]/>
<!LOGGINGVERSION[1.5.3.7185 - 630]/>
<!NAME[C:\usr\sap\jupgrade\log\DEPLOY_SLOT_1__DON_01.LOG]/>
<!PATTERN[DEPLOY_SLOT_1__DON_01.LOG]/>
<!FORMATTER[com.sap.tc.logging.TraceFormatter(%24d %s: %m)]/>
<!ENCODING[UTF8]/>
<!LOGHEADER[END]/>
May 20, 2009 4:15:48 AM Info:
May 20, 2009 4:15:48 AM Info: ============================================
May 20, 2009 4:15:48 AM Info: = Starting to execute command 'deploy' =
May 20, 2009 4:15:48 AM Info: ============================================
May 20, 2009 4:15:48 AM Info: Starting SDM - Software Deployment Manager...
May 20, 2009 4:15:49 AM Info: tc/SL/SDM/SDM/sap.com/SAP AG/7.0103.20081105085605.0000
May 20, 2009 4:15:51 AM Info: SDM operation mode successfully set to: Standalone
May 20, 2009 4:15:52 AM Info: Initializing Network Manager (50017)
May 20, 2009 4:15:52 AM Info: Checking if another SDM is running on port 50018
May 20, 2009 4:15:53 AM Info: -
Starting deployment -
May 20, 2009 4:15:53 AM Info: Error handling strategy: OnErrorSkipDepending
May 20, 2009 4:15:53 AM Info: Prerequisite error handling strategy: OnPrerequisiteErrorStop
May 20, 2009 4:15:53 AM Info: Update strategy: UpdateLowerVersions
May 20, 2009 4:15:53 AM Info: Starting deployment prerequisites:
May 20, 2009 4:15:55 AM Info: Loading selected archives...
May 20, 2009 4:15:55 AM Info: Loading archive 'C:\usr\sap\jupgrade\data\archives\ADSSAP03_0.SCA'
May 20, 2009 4:16:43 AM Info: Loading archive '
nbg-dev-cd1\sapmnt\trans\EPS\in\BIBASES16_0-10003477.SCA'
May 20, 2009 4:16:48 AM Info: Loading archive '
nbg-dev-cd1\sapmnt\trans\EPS\in\BIIBC16_0-10003495.SCA'
May 20, 2009 4:16:50 AM Info: Loading archive '
nbg-dev-cd1\sapmnt\trans\EPS\in\BIREPPLAN16_0-10002878.SCA'
May 20, 2009 4:17:00 AM Info: Loading archive '
nbg-dev-cd1\sapmnt\trans\EPS\in\BIWDALV16_0-10003475.SCA'
May 20, 2009 4:17:02 AM Info: Loading archive '
nbg-dev-cd1\sapmnt\trans\EPS\in\BIWEBAPP16_0-10003476.SCA'
May 20, 2009 4:17:13 AM Info: Loading archive 'C:\usr\sap\jupgrade\data\archives\BIMMR03_0.SCA'
May 20, 2009 4:17:24 AM Info: Loading archive 'C:\usr\sap\jupgrade\data\archives\BIUDI03_0.SCA'
May 20, 2009 4:17:31 AM Info: Loading archive 'C:\usr\sap\jupgrade\data\archives\BPCRMAPP02_0.SCA'
May 20, 2009 4:17:35 AM Info: Loading archive 'C:\usr\sap\jupgrade\data\archives\BPCRMFND02_0.SCA'
May 20, 2009 4:17:37 AM Info: Loading archive 'C:\usr\sap\jupgrade\data\archives\CAF03_0.SCA'
May 20, 2009 4:18:02 AM Info: Loading archive 'C:\usr\sap\jupgrade\data\archives\CAFKM03_0.SCA'
May 20, 2009 4:18:04 AM Info: Loading archive 'C:\usr\sap\jupgrade\data\archives\CAFUM03_0.SCA'
May 20, 2009 4:18:08 AM Info: Loading archive 'C:\usr\sap\jupgrade\data\archives\CRMAPP02_0.SCA'
May 20, 2009 4:18:09 AM Info: Loading archive 'C:\usr\sap\jupgrade\data\archives\CRMFND02_1.SCA'
May 20, 2009 4:18:10 AM Info: Loading archive '
nbg-dev-cd1\sapmnt\trans\EPS\in\DICBS16_0-10003500.SCA'
May 20, 2009 4:18:13 AM Info: Loading archive '
nbg-dev-cd1\sapmnt\trans\EPS\in\DICMS16_0-10003499.SCA'
May 20, 2009 4:18:20 AM Info: Loading archive '
nbg-dev-cd1\sapmnt\trans\EPS\in\DIDTR16_0-10003501.SCA'
May 20, 2009 4:18:26 AM Info: Loading archive 'C:\usr\sap\jupgrade\data\archives\EPPSERV03_0.SCA'
May 20, 2009 4:18:43 AM Info: Loading archive 'C:\usr\sap\jupgrade\data\archives\EPWDC03_0.SCA'
May 20, 2009 4:18:45 AM Info: Loading archive 'C:\usr\sap\jupgrade\data\archives\EPBC203_0.SCA'
May 20, 2009 4:18:50 AM Info: Loading archive 'C:\usr\sap\jupgrade\data\archives\KMKWJIKS03_0.SCA'
May 20, 2009 4:18:51 AM Info: Loading archive 'C:\usr\sap\jupgrade\data\archives\KMCBC03_0.SCA'
May 20, 2009 4:18:56 AM Info: Loading archive 'C:\usr\sap\jupgrade\data\archives\KMCCM03_0.SCA'
May 20, 2009 4:19:03 AM Info: Loading archive 'C:\usr\sap\jupgrade\data\archives\KMCCOLL03_0.SCA'
May 20, 2009 4:19:10 AM Info: Loading archive 'C:\usr\sap\jupgrade\data\archives\LMPORTAL03_0.SCA'
May 20, 2009 4:19:12 AM Info: Loading archive 'C:\usr\sap\jupgrade\data\archives\LMTOOLS03_01.SCA'
May 20, 2009 4:19:43 AM Error: There is already a component of the same type with identical name 'tc/cts/appl' and vendor 'sap.com' selected.
May 20, 2009 4:19:43 AM Info: Loading archive 'C:\usr\sap\jupgrade\data\archives\NETPDK03_0.SCA'
May 20, 2009 4:19:45 AM Info: Loading archive 'C:\usr\sap\jupgrade\data\archives\RTC03_0.SCA'
May 20, 2009 4:19:48 AM Info: Loading archive 'C:\usr\sap\jupgrade\data\archives\RTCSTREAM03_0.SCA'
May 20, 2009 4:19:49 AM Info: Loading archive 'C:\usr\sap\jupgrade\data\archives\SAPCRMAPP02_1.SCA'
May 20, 2009 4:20:55 AM Info: Loading archive 'C:\usr\sap\jupgrade\data\archives\SAPCRMDIC02_0.SCA'
May 20, 2009 4:21:00 AM Info: Loading archive 'C:\usr\sap\jupgrade\data\archives\SAPEU03_0.SCA'
May 20, 2009 4:21:39 AM Info: Loading archive 'C:\usr\sap\jupgrade\data\archives\SAPSHRAPP02_0.SCA'
May 20, 2009 4:23:18 AM Info: Loading archive 'C:\usr\sap\jupgrade\data\archives\SWLIFECYCL03_0.SCA'
May 20, 2009 4:23:24 AM Info: Loading archive 'C:\usr\sap\jupgrade\data\archives\UMEADMIN03_0.SCA'
May 20, 2009 4:23:27 AM Info: Loading archive 'C:\usr\sap\jupgrade\data\archives\UWLJWF03_0.SCA'
May 20, 2009 4:23:33 AM Info: Loading archive 'C:\usr\sap\jupgrade\data\archives\VCBASE03_0.SCA'
May 20, 2009 4:23:37 AM Info: Loading archive 'C:\usr\sap\jupgrade\data\archives\VCFLEX03_0.SCA'
May 20, 2009 4:23:54 AM Info: Loading archive 'C:\usr\sap\jupgrade\data\archives\VCFRAMEWORK03_0.SCA'
May 20, 2009 4:23:58 AM Info: Loading archive '
nbg-dev-cd1\sapmnt\trans\EPS\in\VCKITBI16_0-10003603.SCA'
May 20, 2009 4:23:59 AM Info: Loading archive 'C:\usr\sap\jupgrade\data\archives\VCKITGP03_0.SCA'
May 20, 2009 4:24:00 AM Info: Loading archive 'C:\usr\sap\jupgrade\data\archives\VCKITXX03_0.SCA'
May 20, 2009 4:24:02 AM Info: Loading archive 'C:\usr\sap\jupgrade\data\archives\WDEXTENSIONS03_0.SCA'
May 20, 2009 4:24:05 AM Error: Error while loading selected archives.
May 20, 2009 4:24:05 AM Error: Prerequisites were aborted.
May 20, 2009 4:24:13 AM Error: Error while loading selected archives.
May 20, 2009 4:24:13 AM Info: Summarizing the deployment results:
May 20, 2009 4:24:13 AM Error: Initial: C:\usr\sap\jupgrade\data\archives\ADSSAP03_0.SCA
May 20, 2009 4:24:13 AM Error: Initial:
nbg-dev-cd1\sapmnt\trans\EPS\in\BIBASES16_0-10003477.SCA
May 20, 2009 4:24:13 AM Error: Initial:
nbg-dev-cd1\sapmnt\trans\EPS\in\BIIBC16_0-10003495.SCA
May 20, 2009 4:24:13 AM Error: Initial:
nbg-dev-cd1\sapmnt\trans\EPS\in\BIREPPLAN16_0-10002878.SCA
May 20, 2009 4:24:13 AM Error: Initial:
nbg-dev-cd1\sapmnt\trans\EPS\in\BIWDALV16_0-10003475.SCA
May 20, 2009 4:24:13 AM Error: Initial:
nbg-dev-cd1\sapmnt\trans\EPS\in\BIWEBAPP16_0-10003476.SCA
May 20, 2009 4:24:13 AM Error: Initial: C:\usr\sap\jupgrade\data\archives\BIMMR03_0.SCA
May 20, 2009 4:24:13 AM Error: Initial: C:\usr\sap\jupgrade\data\archives\BIUDI03_0.SCA
May 20, 2009 4:24:13 AM Error: Initial: C:\usr\sap\jupgrade\data\archives\BPCRMAPP02_0.SCA
May 20, 2009 4:24:13 AM Error: Initial: C:\usr\sap\jupgrade\data\archives\BPCRMFND02_0.SCA
May 20, 2009 4:24:13 AM Error: Initial: C:\usr\sap\jupgrade\data\archives\CAF03_0.SCA
May 20, 2009 4:24:13 AM Error: Initial: C:\usr\sap\jupgrade\data\archives\CAFKM03_0.SCA
May 20, 2009 4:24:13 AM Error: Initial: C:\usr\sap\jupgrade\data\archives\CAFUM03_0.SCA
May 20, 2009 4:24:13 AM Error: Initial: C:\usr\sap\jupgrade\data\archives\CRMAPP02_0.SCA
May 20, 2009 4:24:13 AM Error: Initial: C:\usr\sap\jupgrade\data\archives\CRMFND02_1.SCA
May 20, 2009 4:24:13 AM Error: Initial:
nbg-dev-cd1\sapmnt\trans\EPS\in\DICBS16_0-10003500.SCA
May 20, 2009 4:24:13 AM Error: Initial:
nbg-dev-cd1\sapmnt\trans\EPS\in\DICMS16_0-10003499.SCA
May 20, 2009 4:24:13 AM Error: Initial:
nbg-dev-cd1\sapmnt\trans\EPS\in\DIDTR16_0-10003501.SCA
May 20, 2009 4:24:13 AM Error: Initial: C:\usr\sap\jupgrade\data\archives\EPPSERV03_0.SCA
May 20, 2009 4:24:13 AM Error: Initial: C:\usr\sap\jupgrade\data\archives\EPWDC03_0.SCA
May 20, 2009 4:24:13 AM Error: Initial: C:\usr\sap\jupgrade\data\archives\EPBC203_0.SCA
May 20, 2009 4:24:13 AM Error: Initial: C:\usr\sap\jupgrade\data\archives\KMKWJIKS03_0.SCA
May 20, 2009 4:24:13 AM Error: Initial: C:\usr\sap\jupgrade\data\archives\KMCBC03_0.SCA
May 20, 2009 4:24:13 AM Error: Initial: C:\usr\sap\jupgrade\data\archives\KMCCM03_0.SCA
May 20, 2009 4:24:13 AM Error: Initial: C:\usr\sap\jupgrade\data\archives\KMCCOLL03_0.SCA
May 20, 2009 4:24:13 AM Error: Initial: C:\usr\sap\jupgrade\data\archives\LMPORTAL03_0.SCA
May 20, 2009 4:24:13 AM Error: Precondition violated: C:\usr\sap\jupgrade\data\archives\LMTOOLS03_01.SCA
May 20, 2009 4:24:13 AM Error: Initial: C:\usr\sap\jupgrade\data\archives\NETPDK03_0.SCA
May 20, 2009 4:24:13 AM Error: Initial: C:\usr\sap\jupgrade\data\archives\RTC03_0.SCA
May 20, 2009 4:24:13 AM Error: Initial: C:\usr\sap\jupgrade\data\archives\RTCSTREAM03_0.SCA
May 20, 2009 4:24:13 AM Error: Initial: C:\usr\sap\jupgrade\data\archives\SAPCRMAPP02_1.SCA
May 20, 2009 4:24:13 AM Error: Initial: C:\usr\sap\jupgrade\data\archives\SAPCRMDIC02_0.SCA
May 20, 2009 4:24:13 AM Error: Initial: C:\usr\sap\jupgrade\data\archives\SAPEU03_0.SCA
May 20, 2009 4:24:13 AM Error: Initial: C:\usr\sap\jupgrade\data\archives\SAPSHRAPP02_0.SCA
May 20, 2009 4:24:13 AM Error: Initial: C:\usr\sap\jupgrade\data\archives\SWLIFECYCL03_0.SCA
May 20, 2009 4:24:13 AM Error: Initial: C:\usr\sap\jupgrade\data\archives\UMEADMIN03_0.SCA
May 20, 2009 4:24:13 AM Error: Initial: C:\usr\sap\jupgrade\data\archives\UWLJWF03_0.SCA
May 20, 2009 4:24:13 AM Error: Initial: C:\usr\sap\jupgrade\data\archives\VCBASE03_0.SCA
May 20, 2009 4:24:13 AM Error: Initial: C:\usr\sap\jupgrade\data\archives\VCFLEX03_0.SCA
May 20, 2009 4:24:13 AM Error: Initial: C:\usr\sap\jupgrade\data\archives\VCFRAMEWORK03_0.SCA
May 20, 2009 4:24:13 AM Error: Initial:
nbg-dev-cd1\sapmnt\trans\EPS\in\VCKITBI16_0-10003603.SCA
May 20, 2009 4:24:13 AM Error: Initial: C:\usr\sap\jupgrade\data\archives\VCKITGP03_0.SCA
May 20, 2009 4:24:13 AM Error: Initial: C:\usr\sap\jupgrade\data\archives\VCKITXX03_0.SCA
May 20, 2009 4:24:13 AM Error: Initial: C:\usr\sap\jupgrade\data\archives\WDEXTENSIONS03_0.SCA
May 20, 2009 4:24:13 AM Error: Processing error. Return code: 4
It appears to me that somehow there is a component conflict:
May 20, 2009 4:19:12 AM Info: Loading archive 'C:\usr\sap\jupgrade\data\archives\LMTOOLS03_01.SCA'
May 20, 2009 4:19:43 AM Error: There is already a component of the same type with identical name 'tc/cts/appl' and vendor 'sap.com' selected.
May 20, 2009 4:19:43 AM Info: Loading archive 'C:\usr\sap\jupgrade\data\archives\NETPDK03_0.SCA'
Is it advisable at all to manually delete the above LMTOOLS03_01.SCA from the location and try again or this will lead to more errors?
Please help ASAP, thanks a lot,
Shival

Following is the trouble ticket information:
Trouble Ticket Report
Upgrade to Enhancement Package 1 SR1 for SAP NetWeaver/ SAP Business Suite 7 SR1
SID................: CD1
Hostname...........: nbg-dev-cd1
Install directory..: c:/usr/sap/CD1
Upgrade directory..: C:\usr\sap\jupgrade
Database...........: SAP DB
Operating System...: NT
JDK version........: 1.4.2_15 Sun Microsystems Inc.
SAPJup version.....: 1.5.6
Source release.....: 700
Target release.....: 700
Current usages.....: AS;EP;EPC;BP-CRM;JCRM;AAS
ABAP stack present.: true
The execution of UPGRADE/UPGRADE/DEPLOY_ONLINE ended in error.
Error while executing SDM process phase with action DEPLOY_SLOT. See C:\usr\sap\jupgrade\log\DEPLOY_SLOT_1__DON_01.LOG for details.
Cannot execute Java process for deployList with parameters C:/usr/sap/jupgrade/tmp/SLOT.DEPLOY.LST.
Return code condition success evaluated to false for process java.exe for action ACTION_DEPLOY_LIST.
More information can be found in the log file C:\usr\sap\jupgrade\log\DEPLOY_ONLINE_DON_01.LOG.
Use the information provided to trouble-shoot the problem. There might be an OSS note providing a solution to this problem. Search for OSS notes with the following search terms:
com.sap.sdt.j2ee.phases.PhaseTypeSDMProcess
com.sap.sdt.ucp.phases.PhaseException
Error while executing SDM process phase with action DEPLOY_SLOT. See C:\usr\sap\jupgrade\log\DEPLOY_SLOT_1__DON_01.LOG for details.
DEPLOY_ONLINE
UPGRADE
NetWeaver Upgrade
SAPJup
Java Upgrade

Error while using window.open() in JSP page

I am getting error while using window.open() in my JSP page.
This is code in my JSP page,
<h:commandLink onclick="loadContextSensitiveHelp(#{setNewDayStatusBean. cycleStatusViewObject.helpUrl});" value="Help">
function loadContextSensitiveHelp(helpPageName) {
top.consoleRef=window.open('#{facesContext.externalContext.requestContextPath}/main/patient/helpPageName','myconsole',
'width=350,height=250'
+',menubar=0'
+',toolbar=0'
+',status=0'
+',scrollbars=1'
+',resizable=0')
top.consoleRef.document.close()
I am getting the following error in my browser,
type Exception report
message
description The server encountered an internal error () that prevented it from fulfilling this request.
exception
org.apache.jasper.JasperException: /SetNewDayStatus.jsp(69,34) #{..} is not allowed in template text
     org.apache.jasper.compiler.DefaultErrorHandler.jspError(DefaultErrorHandler.java:40)
     org.apache.jasper.compiler.ErrorDispatcher.dispatch(ErrorDispatcher.java:407)
     org.apache.jasper.compiler.ErrorDispatcher.jspError(ErrorDispatcher.java:102)
     org.apache.jasper.compiler.Validator$ValidateVisitor.visit(Validator.java:711)
     org.apache.jasper.compiler.Node$ELExpression.accept(Node.java:935)
     org.apache.jasper.compiler.Node$Nodes.visit(Node.java:2336)
     org.apache.jasper.compiler.Node$Visitor.visitBody(Node.java:2386)
     org.apache.jasper.compiler.Validator$ValidateVisitor.visit(Validator.java:838)
     org.apache.jasper.compiler.Node$CustomTag.accept(Node.java:1507)
     org.apache.jasper.compiler.Node$Nodes.visit(Node.java:2336)
     org.apache.jasper.compiler.Node$Visitor.visitBody(Node.java:2386)
     org.apache.jasper.compiler.Node$Visitor.visit(Node.java:2392)
     org.apache.jasper.compiler.Node$Root.accept(Node.java:489)
     org.apache.jasper.compiler.Node$Nodes.visit(Node.java:2336)
     org.apache.jasper.compiler.Validator.validate(Validator.java:1737)
     org.apache.jasper.compiler.Compiler.generateJava(Compiler.java:178)
     org.apache.jasper.compiler.Compiler.compile(Compiler.java:306)
     org.apache.jasper.compiler.Compiler.compile(Compiler.java:286)
     org.apache.jasper.compiler.Compiler.compile(Compiler.java:273)
     org.apache.jasper.JspCompilationContext.compile(JspCompilationContext.java:566)
     org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:317)
     org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:320)
     org.apache.jasper.servlet.JspServlet.service(JspServlet.java:266)
     javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
     com.sun.faces.context.ExternalContextImpl.dispatch(ExternalContextImpl.java:428)
     com.sun.faces.application.ViewHandlerImpl.executePageToBuildView(ViewHandlerImpl.java:444)
     com.sun.faces.application.ViewHandlerImpl.renderView(ViewHandlerImpl.java:116)
     com.sun.faces.lifecycle.RenderResponsePhase.execute(RenderResponsePhase.java:106)
     com.sun.faces.lifecycle.LifecycleImpl.phase(LifecycleImpl.java:251)
     com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:144)
     javax.faces.webapp.FacesServlet.service(FacesServlet.java:245)
note The full stack trace of the root cause is available in the Apache Tomcat/6.0.13 logs.
Anyone help me to solve this issue. Thanks............................

I am getting error while using window.open() in my JSP page.
This is code in my JSP page,
<h:commandLink onclick="loadContextSensitiveHelp(#{setNewDayStatusBean. cycleStatusViewObject.helpUrl});" value="Help">
function loadContextSensitiveHelp(helpPageName) {
top.consoleRef=window.open('#{facesContext.externalContext.requestContextPath}/main/patient/helpPageName','myconsole',
'width=350,height=250'
+',menubar=0'
+',toolbar=0'
+',status=0'
+',scrollbars=1'
+',resizable=0')
top.consoleRef.document.close()
I am getting the following error in my browser,
type Exception report
message
description The server encountered an internal error () that prevented it from fulfilling this request.
exception
org.apache.jasper.JasperException: /SetNewDayStatus.jsp(69,34) #{..} is not allowed in template text
     org.apache.jasper.compiler.DefaultErrorHandler.jspError(DefaultErrorHandler.java:40)
     org.apache.jasper.compiler.ErrorDispatcher.dispatch(ErrorDispatcher.java:407)
     org.apache.jasper.compiler.ErrorDispatcher.jspError(ErrorDispatcher.java:102)
     org.apache.jasper.compiler.Validator$ValidateVisitor.visit(Validator.java:711)
     org.apache.jasper.compiler.Node$ELExpression.accept(Node.java:935)
     org.apache.jasper.compiler.Node$Nodes.visit(Node.java:2336)
     org.apache.jasper.compiler.Node$Visitor.visitBody(Node.java:2386)
     org.apache.jasper.compiler.Validator$ValidateVisitor.visit(Validator.java:838)
     org.apache.jasper.compiler.Node$CustomTag.accept(Node.java:1507)
     org.apache.jasper.compiler.Node$Nodes.visit(Node.java:2336)
     org.apache.jasper.compiler.Node$Visitor.visitBody(Node.java:2386)
     org.apache.jasper.compiler.Node$Visitor.visit(Node.java:2392)
     org.apache.jasper.compiler.Node$Root.accept(Node.java:489)
     org.apache.jasper.compiler.Node$Nodes.visit(Node.java:2336)
     org.apache.jasper.compiler.Validator.validate(Validator.java:1737)
     org.apache.jasper.compiler.Compiler.generateJava(Compiler.java:178)
     org.apache.jasper.compiler.Compiler.compile(Compiler.java:306)
     org.apache.jasper.compiler.Compiler.compile(Compiler.java:286)
     org.apache.jasper.compiler.Compiler.compile(Compiler.java:273)
     org.apache.jasper.JspCompilationContext.compile(JspCompilationContext.java:566)
     org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:317)
     org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:320)
     org.apache.jasper.servlet.JspServlet.service(JspServlet.java:266)
     javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
     com.sun.faces.context.ExternalContextImpl.dispatch(ExternalContextImpl.java:428)
     com.sun.faces.application.ViewHandlerImpl.executePageToBuildView(ViewHandlerImpl.java:444)
     com.sun.faces.application.ViewHandlerImpl.renderView(ViewHandlerImpl.java:116)
     com.sun.faces.lifecycle.RenderResponsePhase.execute(RenderResponsePhase.java:106)
     com.sun.faces.lifecycle.LifecycleImpl.phase(LifecycleImpl.java:251)
     com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:144)
     javax.faces.webapp.FacesServlet.service(FacesServlet.java:245)
note The full stack trace of the root cause is available in the Apache Tomcat/6.0.13 logs.
Anyone help me to solve this issue. Thanks............................

Error while creating the HTTP client with destination

Hi ,
I am getting this error while connecting to https location on receiver channel . The below error i am getting in SXMB_moni
Error while creating the HTTP client with destination
The receiver party is doing some security setting on there end and for that purpose we have provided the external IP address to them , after that we are getting the above error.
We have already installed the client certificate on our staging server , and have done the correct setting in SM59 and channel.

Check few things..
1) I believe you use specify destination for the addressing type field in the comm channel. If so make sure you entered valid target URL address in the SM59 of type http destination.
2) Check the validitity of the certificate. You can import the certificate both in java and abap stack.
3) Make sure certificate is installed as expected.
4) Send the request and talk to the target system and check what error information they get in their log related to ssl.

Windows 7 Imaging with ZCM Agent installed

Has anyone successfully made a Windows 7 image with the ZCM agent already installed on the base image?
I am trying to get the unattended setup to login once to but the workstation prompts for the ZCM login information?
Any suggestions?

Yes
You have to disable the zcm logon prompt, then run a reghack to enable zcm logon as your last step after the first auto logon.

HT1846 gtp error while installing windows from usb! how to solve it.

gtp error while installing windows from usb! how to solve it.

Hello mmarti,
Thanks for using Apple Support Communities.
Please ensure you are following the Boot Camp installation guide, as you should be selecting the partition named "BOOTCAMP" when you are at the Windows installer screen. See page 6 of the following PDF:
http://manuals.info.apple.com/MANUALS/1000/MA1636/en_US/boot_camp_install-setup_ 10.8.pdf
Take care,
Alex H.

SCCM 2012 R2 With MDT 2012 AND MDT 2013 Side by Side

Currently we're running 2012 R2 CU3 with MDT 2012 integrated into it. We're looking at upgrading to MDT 2013 (whatever the latest update is). What I'm wondering, and can't seem to find any information on, is if we can continue to use our MDT 2012 boot
.wims/OSD Task Sequences/etc until such time as we create and test new ones or are we going to have to update everything right away?

Are you sure you are using MDT *2013* with ConfigMgr 2012 *R2*? That's not a supported configuration and I think there are multiple technical problems with this combination.
The task sequences themselves don't change -- because they are ConfigMgr task sequences -- but the MDT tasks must be updated to use the MDT 2013 tasks. Boot image use is partially dependent upon the OS you are deploying however only WinPE 3.1 and WinPE 5.0
based boot images are supported in R2.
Jason | http://blog.configmgrftw.com | @jasonsandys
Did you mean to ask if we were running MDT 2012 with ConfigMgr 2012 R2? Then yes we are. We did the upgrade from SP1 CU2 to R2 CU3 a couple of weeks ago but haven't upgraded MDT to 2013 yet. That's our next step but we also don't want to take down/break imaging
capability if we can help it (major college, staff/students constantly breaking stuff, etc).

Creating Windows 8.1 master image with MDT 2013,cannot capture .WIM

I am having an issue with creating a master image with Windows 8.1 and MDT 2013.
I have followed extensive tutorials on how to create a master image using Microsoft Deployment Toolkit. my goal is to have a fully configured windows 8.1 image which I can deploy through Windows Deployment Services. I have been relatively successful thus far,
except for one issue I have run into, which is successfully capturing this image as a .WIM.
I have successfully created a task sequence and the task sequence is able to run all the way through until the final step. Essentially the task sequence is supposed to install Windows and Office, then suspend the task sequence to allow me to make customisations
to the start screen and desktop background, and I simply click resume task sequence, and the task sequence should sysprep reboot and capture the machine image as a .WIM file.
the task sequence is able to sysprep the machine, but upon rebooting it boots into out of box experience, and does not create a wim file. I receive an error saying: "cannot find script file C:\ltibootstrap.Vbs" after the machine completes OOBE
I am using Windows Server 2012 r2, creating my Master machine image using hyper-v, and my master image is running Windows 8.1.
Any help would be greatly appreciated.

I'm not sure about the sequence of steps here. Try taking your captured.wim file and deploying it using MDT again, or at least to another machine. MDT sometimes leaves extra files around on the captured machine, so simply rebooting it may not get a accurate
test results.
IF you are getting the ltibootstrap.vbs it is most likely because there is a stray unattend.xml file somewhere in your image that is looking for this file. Crack open your Wim file and search for any unattend.xml files.
Keith Garner - Principal Consultant [owner] -
http://DeploymentLive.com

Since upgrade to MDT 2013, can't capture Windows 7 image.

Hi fellas,
I use Virtual Box to create a 32- and 64-bit reference Windows 7 VM, which I then capture using an MDT Sysprep & Capture TS. This worked without a hitch using MDT 2012.
I recently upgraded to MDT 2013. Since then, after the VM syspreps and reboots, I get a boot manager error saying Windows failed to start. Status: 0xc0000260.
Not sure where to look for any logs. What I've done so far:
- Upgraded to latest version of Virtual Box (4.3.18)
- Rebuilt both VMs from scratch.
- Deleted and recreated the deployment share and Sysprep & Capture task sequences.
Stumped for the time being, although I could always just boot to my Win PE disc and manually capture with imagex. But c'mon.

Thanks for your input, but this is indeed a configuration issue, and it makes sense.
Vbox VMs are configured according to the guest OS installed on them. For my Windows 7 x64 VM, it's configured of course to run as Windows 7 x64. In the MDT 2012 environment, the Windows PE version
was 3.0, which is based on Windows 7, and hence the VM could boot to it since it was configured for it.
But MDT 2013 uses PE 5.0, based on 8.1. The VM crashes or throws an error when trying to boot the PE 5.0 boot image. I went into the VM's settings and changed the Guest OS to 8.1 x64, and it booted successfully to Windows PE and captured the
image according to the Sysprep & Capture sequence.
Sorry for the wild goose chase fellas. This should've been the first thing I checked.

Capture system image with MDT

Hello everyone,
I want to create a Windows 7 installation disc that will allow me to have, immediately after installation, a system updated with the latest hotfixes, installed programs and all the settings I want already selected in the system.
Now, I used MDT 2013 on x64 Windows 8.1 Pro to create a DeploymentShare Windows 7 Pro x86, including drivers, applications and various hotfixes, once I create the image of Windows PE, through which I install the above system from DeploymentShare, all row smoothly,
but I have any dubious:
1) Once the system is installed, they log me in as Administrator, why?
2) If I log in as Administrator, then I have to run the sysprep.exe / generalize / oobe before delivering the computer to an imaginary customer?
3) If I want to make changes to the settings of the user (for example to make sure that hidden folders see by default after installation or arrange the icons on the desktop as I will ensure that the end user see it exactly so) I have to use the CopyProfile?
4) If yes, at what stage should I use the CopyProfile? Specifying an unattend.xml during sysprep.exe on point 2? Or maybe I recapture system image after install it and use the file *.wim with a different unattend.xml, that is, in practice doing two laps of
installation?
5) Once I captured the system image, when I try to install it, the system logs me in again with Administrator account instead of OOBE, why?
I want to do this final procedure on the end user PC:
1) Put the DVD (or USB) of this modified Windows
2) Install Windows automatically with all applications, hotfixes and settings
3) Once Windows is installed, I install in audit mode all drivers for that PC and sysprep /oobe it
4) Give the PC to the client
Thank you in advance!
P.S: sorry for my bad english

1. By design, a hold out from the days when MDT also supported XP.
2. By design, images need to be syspreped if they are to be applied to other machines.
3. Typically I do *NOT* recommend making changes to HKCU during imaging, instead settings should be applied using GPO or other method. CopyProfile can work as a last resort.
4. CopyProfile is applied during "Specialize" as per documentation, not during sysprep.
5. MDT enables the local administrator account for use in MDT deployments later. Check out the unattend64.xml template in the MDT install directory:
<RunSynchronous>
<RunSynchronousCommand wcm:action="add">
<Description>EnableAdmin</Description>
<Order>1</Order>
<Path>cmd /c net user Administrator /active:yes</Path>
</RunSynchronousCommand>
<RunSynchronousCommand wcm:action="add">
<Description>UnfilterAdministratorToken</Description>
<Order>2</Order>
<Path>cmd /c reg add HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System /v FilterAdministratorToken /t REG_DWORD /d 0 /f</Path>
</RunSynchronousCommand>
<RunSynchronousCommand wcm:action="add">
<Description>disable user account page</Description>
<Order>3</Order>
<Path>reg add HKLM\Software\Microsoft\Windows\CurrentVersion\Setup\OOBE /v UnattendCreatedUser /t REG_DWORD /d 1 /f</Path>
</RunSynchronousCommand>
</RunSynchronous>
This works for MDT deployment later, but if you have a custom process, you may need to adjust the system.
Keith Garner - Principal Consultant [owner] -
http://DeploymentLive.com

Error while capturing Windows Xp image with MDT 2012.

Similar Messages

Maybe you are looking for