XP Capture Error (0x0000007F)~~SCCM 2012

Hi All,
When I tried to capture XP image using SCCM 2012 media,
I am getting below error i have copied sysprep in C:\.
Error Code ~~0X0000007F

Hi,
Smsts.log location:
Windows PE before HDD format: x:\windows\temp\smstslog\smsts.log
Windows PE after HDD format: x:\smstslog\smsts.log and copied to c:\_SMSTaskSequence\Logs\Smstslog\smsts.log
Full version Windows before SCCM agent installed: c:\_SMSTaskSequence\Logs\Smstslog\smsts.log
Full version Windows after SCCM agent installed: c:\windows\system32\ccm\logs\Smstslog\smsts.log
Full version Windows (x64) after SCCM agent installed: c:\windows\sysWOW64\ccm\logs\Smstslog\smsts.log
After Task Sequence has finished running: c:\windows\system32\ccm\logs\smsts.log
After Task Sequence has finished running (x64): c:\windows\sysWOW64\ccm\logs\smsts.log
http://penetrateit.wordpress.com/2013/02/08/configuration-manager-2012-sp1-smsts-log-log-location/
(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.)
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.

Similar Messages

UDI OSD Task Sequences started failing with 0x80070002 error in SCCM 2012

This is kind of long, but here goes...
We built a UDI task sequence in SCCM 2012 (with MDT integration) that we were testing for deployment of a couple of different Win7 images. We customized the UDI experience thru the UDI wizard and XML file and OS deployment worked as expected
thru the task sequence (testing on Hyper-V VMs). Recently, this UDI TS started failing with error 0x80070002 during what appears to be the "Use Toolkit Package" step. This is after the OS image has already been laid down and after the ConfigMgr
client has been installed/configured. The SMSTS.log reports "Failed to open the task sequence key HKLM\Software\Microsoft\SMS\Task Sequence. Error code 0x8007002" Among other errors...I will post the entire log below...
After the error during deployment, Win7 will boot normally, however, you have no network connectivity and it appears the proper network driver didn't get loaded in the OS. Combine this with the fact that the TS should have joined the machine to our domain,
but you can't login because no network.. Im not sure if the network issue is a product of the TS failing early or the actual cause of the TS failure.
Anyway, I attempted to build another UDI task sequence using the same boot image and toolkit/settings packages, but am experiencing the same error during deployment. We have a few OSD task sequences built without UDI and those all still work just fine.
So, I am at a loss for where the root problem lies. Any suggestions or assistance would be greatly appreciated.
Here is the entire SMSTS.log and BDD.log...
https://skydrive.live.com/redir?resid=D65B1C4362892A26!110&authkey=!AKu5mOvDsXaEgvc
Thanks
Richie Tenhet

your failure does appear to be network (driver or otherwise) or dns related and it cannot contact the management point FQDN just around the time where it should download and execute the
Use Toolkit Package step...
"Starting Task Sequence Engine . . . "
"Non fatal error 0x80072ee7 in sending task sequence execution status message to MP"
"Start executing an instruciton. Instruction name: Use Toolkit Package. Instruction pointer: 83"
"unknown host (gethostbyname failed)"
"sending with winhttp failed; 80072ee7"
"Tried all the available http based locations. SMB based locations will be attempted now."
"Failed to resolve the source for SMS PKGID=P0100015, hr=0x80070002"
"Failed to run the action: Use Toolkit Package.
The system cannot find the file specified. (Error: 80070002; Source: Windows)"
that said, check that the package referenced above actually exists and is the correct source version on your distribution points, also verify (press F8 and check can you ping the FQDN of your management point) that you have network connectivity
around the time of the failure.
Step by Step Configuration Manager Guides >
2012 Guides |
2007 Guides | I'm on Twitter > ncbrady

SQL Service error on SCCM 2012 R2 Evaluation VHD

Hi
I've downloaded the VHD SCCM 2012 R2, but, SQL Server evaluation is out of date
http://www.microsoft.com/en-us/download/details.aspx?id=40840
I've one error "SLQ Server 2012 has expired...."
How I do now ?
Thanks at all
Scorpio92

Or you could fix this Microsoft?
This issue is at least 2 years old going back to the previous product (SCCM 2012 SP1):
https://social.technet.microsoft.com/Forums/en-US/151f6aa0-5391-4396-998f-d5d5782ed08f/system-center-2012-service-pack-1-configuration-manager-evaluation-vhd
How was this not fixed when you created the 2012 R2 VHD?
This is literally unfathomable how you could do this even once - you create a VHD for evaluation with a date specific eval of SQL? But then you imbeciles manage to do it at least a second time?
None of you at the team behind this deserve your jobs.

Error OOB SCCM 2012 R2 - AMT vPro

I am running SCCM 2012 R2 to make the provisioning of vPRO, but I'm encountering some difficulties.
At first when efetued the configuration of Intel SCS 9, unable to login normally efetued some tests shutdown and power on and functioned normally. The next day when I got to the office, was no longer running the web interface, I'm not getting login. No changes
were made in the environment during this period. When I try to make the AMT discovery in SCCM, it generates me the error "Failed to establish tcp session" and gives me the IP and the host port 16993. If I place the PSK or PKI configuration within
the MEBx, it generates a user and password error saying it can not authenticate with the Admin user.
Already redid the procedure following the Intel and Microsoft manual, but the error persists. SCCM can identify the version of vPRO, but the status it says "Can not Stand", regardless of the version ... 4.x, 5.x and 6.x, it displays the same message
every time.
This is the log of the error when I'm not using PSK setting in the MEBx that is generated in the AMT discovery of SCCM
================================================================
AMT Discovery Worker: Wait 9 seconds... SMS_AMT_OPERATION_MANAGER 05/12/2014 14:49:47 2984 (0x0BA8)
Discover INFRANOTE using IP address 10.234.9.13 SMS_AMT_OPERATION_MANAGER 05/12/2014 14:49:46 4492 (0x118C)
CAMTDiscoveryWSMan::DoConnectToAMTDevice: Failed to establish tcp session to 10.234.9.13:16993. SMS_AMT_OPERATION_MANAGER 05/12/2014 14:49:48 4492 (0x118C)
DoPingDiscoveryForAMTDevice succeeded. SMS_AMT_OPERATION_MANAGER 05/12/2014 14:49:48 4492 (0x118C)
Discovery to IP address 10.234.9.13 succeed. AMT status is 0. SMS_AMT_OPERATION_MANAGER 05/12/2014 14:49:48 4492 (0x118C)
CSMSAMTDiscoveryTask::Execute, discovery to INFRANOTE succeed. AMT status is 0. SMS_AMT_OPERATION_MANAGER 05/12/2014 14:49:48 4492 (0x118C)
================================================================
And this is the log generated when using PSK / PKI configuration in MEBx:
================================================================
DoPingDiscoveryForAMTDevice succeeded.
SMS_AMT_OPERATION_MANAGER
08/12/2014 17:01:25
5336 (0x14D8)
Error 0x80090304 returned by InitializeSecurityContext during follow up TLS handshaking with server.
SMS_AMT_OPERATION_MANAGER
08/12/2014 17:01:25
5336 (0x14D8)
**** Error 0x1d38b100 returned by ApplyControlToken
SMS_AMT_OPERATION_MANAGER
08/12/2014 17:01:25
5336 (0x14D8)
DoSoapDiscovery failed with user name: admin.
SMS_AMT_OPERATION_MANAGER
08/12/2014 17:01:26
5336 (0x14D8)
Error 0x80090304 returned by InitializeSecurityContext during follow up TLS handshaking with server.
SMS_AMT_OPERATION_MANAGER
08/12/2014 17:01:26
5336 (0x14D8)
**** Error 0x1d38b100 returned by ApplyControlToken
SMS_AMT_OPERATION_MANAGER
08/12/2014 17:01:26
5336 (0x14D8)
DoSoapDiscovery failed with user name: admin.
SMS_AMT_OPERATION_MANAGER
08/12/2014 17:01:26
5336 (0x14D8)
Flag iWSManFlagSkipRevocationCheck is not set.
SMS_AMT_OPERATION_MANAGER
08/12/2014 17:01:26
5336 (0x14D8)
session params : https://FQDN COMPUTER:16993
, 11001
SMS_AMT_OPERATION_MANAGER
08/12/2014 17:01:26
5336 (0x14D8)
ERROR: Invoke(get) failed: 80020009argNum = 0
SMS_AMT_OPERATION_MANAGER
08/12/2014 17:01:26
5336 (0x14D8)
Description: A security error occurred
SMS_AMT_OPERATION_MANAGER
08/12/2014 17:01:26
5336 (0x14D8)
Error: Failed to get AMT_SetupAndConfigurationService instance.
SMS_AMT_OPERATION_MANAGER
08/12/2014 17:01:26
5336 (0x14D8)
DoWSManDiscovery failed with user name: admin.
SMS_AMT_OPERATION_MANAGER
08/12/2014 17:01:26
5336 (0x14D8)
Flag iWSManFlagSkipRevocationCheck is not set.
SMS_AMT_OPERATION_MANAGER
08/12/2014 17:01:26
5336 (0x14D8)
session params : https://FQDN COMPUTER:16993
, 11001
SMS_AMT_OPERATION_MANAGER
08/12/2014 17:01:26
5336 (0x14D8)
ERROR: Invoke(get) failed: 80020009argNum = 0
SMS_AMT_OPERATION_MANAGER
08/12/2014 17:01:26
5336 (0x14D8)
Description: A security error occurred
SMS_AMT_OPERATION_MANAGER
08/12/2014 17:01:26
5336 (0x14D8)
Error: Failed to get AMT_SetupAndConfigurationService instance.
SMS_AMT_OPERATION_MANAGER
08/12/2014 17:01:26
5336 (0x14D8)
DoWSManDiscovery failed with user name: admin.
SMS_AMT_OPERATION_MANAGER
08/12/2014 17:01:26
5336 (0x14D8)
Start Kerberos Discovery
SMS_AMT_OPERATION_MANAGER
08/12/2014 17:01:26
5336 (0x14D8)
Flag iWSManFlagSkipRevocationCheck is not set.
SMS_AMT_OPERATION_MANAGER
08/12/2014 17:01:26
5336 (0x14D8)
session params : https://FQDN COMPUTER:16993
, 484001
SMS_AMT_OPERATION_MANAGER
08/12/2014 17:01:26
5336 (0x14D8)
ERROR: Invoke(get) failed: 80020009argNum = 0
SMS_AMT_OPERATION_MANAGER
08/12/2014 17:01:26
5336 (0x14D8)
Description: A security error occurred
SMS_AMT_OPERATION_MANAGER
08/12/2014 17:01:26
5336 (0x14D8)
Error: Failed to get AMT_SetupAndConfigurationService instance.
SMS_AMT_OPERATION_MANAGER
08/12/2014 17:01:26
5336 (0x14D8)
DoKerberosWSManDiscovery failed.
SMS_AMT_OPERATION_MANAGER
08/12/2014 17:01:26
5336 (0x14D8)
Flag iWSManFlagSkipRevocationCheck is not set.
SMS_AMT_OPERATION_MANAGER
08/12/2014 17:01:26
5336 (0x14D8)
session params : https://IP + Port (16993)
, 15001
SMS_AMT_OPERATION_MANAGER
08/12/2014 17:01:26
5336 (0x14D8)
ERROR: Invoke(get) failed: 80020009argNum = 0
SMS_AMT_OPERATION_MANAGER
08/12/2014 17:01:26
5336 (0x14D8)
Description: A security error occurred
SMS_AMT_OPERATION_MANAGER
08/12/2014 17:01:26
5336 (0x14D8)
Error: Failed to get AMT_SetupAndConfigurationService instance.
SMS_AMT_OPERATION_MANAGER
08/12/2014 17:01:26
5336 (0x14D8)
DoWSManDiscovery failed with user name: admin.
SMS_AMT_OPERATION_MANAGER
08/12/2014 17:01:26
5336 (0x14D8)
Flag iWSManFlagSkipRevocationCheck is not set.
SMS_AMT_OPERATION_MANAGER
08/12/2014 17:01:26
5336 (0x14D8)
session params : https://IP + port (16993)
, 15001
SMS_AMT_OPERATION_MANAGER
08/12/2014 17:01:26
5336 (0x14D8)
ERROR: Invoke(get) failed: 80020009argNum = 0
SMS_AMT_OPERATION_MANAGER
08/12/2014 17:01:26
5336 (0x14D8)
Description: A security error occurred
SMS_AMT_OPERATION_MANAGER
08/12/2014 17:01:26
5336 (0x14D8)
Error: Failed to get AMT_SetupAndConfigurationService instance.
SMS_AMT_OPERATION_MANAGER
08/12/2014 17:01:26
5336 (0x14D8)
DoWSManDiscovery failed with user name: admin.
SMS_AMT_OPERATION_MANAGER
08/12/2014 17:01:26
5336 (0x14D8)
Discovery to IP address 10.234.10.84 succeed. AMT status is 1.
SMS_AMT_OPERATION_MANAGER
08/12/2014 17:01:26
5336 (0x14D8)
CSMSAMTDiscoveryTask::Execute, discovery to "COMPUTER NAME succeed. AMT status is 1.
SMS_AMT_OPERATION_MANAGER
08/12/2014 17:01:26
5336 (0x14D8)
CSMSAMTDiscoveryTask::Execute - DDR written to C:\Program Files\Microsoft Configuration Manager\inboxes\auth\ddm.box
SMS_AMT_OPERATION_MANAGER
08/12/2014 17:01:26
5336 (0x14D8)
CStateMsgReporter::DeliverMessages - Queued message: TT=1201 TIDT=0 TID='Unspecified' SID=10 MUF=0 PCNT=1, P1='FQDN' P2='' P3='' P4='' P5=''
SMS_AMT_OPERATION_MANAGER
08/12/2014 17:01:27
5336 (0x14D8)
CStateMsgReporter::DeliverMessages - Created state message file: C:\Program Files\Microsoft Configuration Manager\inboxes\auth\statesys.box\incoming\w73tgg1d.SMX
SMS_AMT_OPERATION_MANAGER
08/12/2014 17:01:27
5336 (0x14D8)
General Worker Thread Pool: Succeed to run the task "FQDN". Remove it from task list.
SMS_AMT_OPERATION_MANAGER
08/12/2014 17:01:27
5336 (0x14D8)
General Worker Thread Pool: Work thread 5336 has been requested to shut down.
SMS_AMT_OPERATION_MANAGER
08/12/2014 17:01:27
5336 (0x14D8)
General Worker Thread Pool: Work thread 5336 exiting.
SMS_AMT_OPERATION_MANAGER
08/12/2014 17:01:27
5336 (0x14D8)
General Worker Thread Pool: Current size of the thread pool is 0
SMS_AMT_OPERATION_MANAGER
08/12/2014 17:01:27
3696 (0x0E70)
AMT Discovery Worker: Wakes up to process instruction files
SMS_AMT_OPERATION_MANAGER
08/12/2014 17:01:45
3728 (0x0E90)
AMT Discovery Worker: Wait 3600 seconds...
SMS_AMT_OPERATION_MANAGER
08/12/2014 17:01:45
3728 (0x0E90)
Could anyone help?
Thank you.

I wouldn't even try using CM with AMT. CM only supports some of the older Vpro chipsets. I had a case open with CSS and they literally suggested that I use the Intel software instead of CM.
John Marcum | Microsoft MVP - Enterprise Client Management
My blog: System Center Admin | Twitter:
@SCCM_Marcum | Linkedin:
John Marcum

Error installing SCCM 2012 client on server

Hi Guys,
I am trying to install the SCCM 2012 client on a machine in my domain. The account specified in client settings is indeed a local admin on this server, but I get the error below:
Any assistance much appreciated!

Hi GSS1,
You can check on the C:\Windows\ccmsetup\logs , files: ccmsetup.log and client.msi.log for errors of clues about the real failure.
On the other hand I would recommend you the manual installation from the UNC path, like:
\\SCCMServerName\SMS_sitecode\Client\ccmsetup.exe
and using the parameters listed here to define the settings: https://technet.microsoft.com/en-us/library/bb693546.aspx?f=255&MSPPError=-2147217396
Optionally you can copy the files from the \\...\Client\ folder to local and try a local installation.
Any of this steps will give you more clues about the failure if they fail or success.
Please share any update for more suggestions!

Error installing SCCM 2012 SP1 client

Hi All,
I am getting the following error, detailed in the client.msi.log, when trying to install the SCCM 2012 SP1 client on a couple of windows 2008 R2 servers.
Error 1904. Module C:\Windows\CCM\StatusAgentProxy.dll failed to register. HRESULT -2147010895
The ccmsetup.log details the same message without Error 1904 indicated.
I am installing the client using the SUP method, which has worked without any problems on all 180 other windows servers I have done. ccmsetup starts and downloads all pre reqs required for the client rollout, but it then hits this error and does not
finish the installation.
Any help would be much appreciated?
Regards PowerShell90

Hi,
I've seen this issue a couple of times and usually it's related to incorrect Versions of C++ Library installed on the system you try to install the Client. Try and remove any existing installations, reboot and install this version;
http://www.microsoft.com/en-us/download/details.aspx?id=26368
Let me know how it goes.

Steps to create MDT based Build and capture TS in SCCM 2012 R2

Hi ,
I have MDT2012 update 1 with Config manager 2012 R2 integrated. If I try to create MDT task sequence in config manager console, I don't see and template for build and capture. Anyone using the build and capture, pls. share steps with me . Any help will be
appreciated. Preferably UDI based if possible. Thanks in advance.
Regards,

MDT 2012 Update 1 is for SCCM 2012 SP1
MDT 2013 is for SCCM 2012 R2
So you need to upgrade your MDT installation. After that, make sure to install the ConfigMgr integration from the start screen (menu)
http://technet.microsoft.com/en-US/windows/dn475741.aspx
Tim Nilimaa | Blog: http://infoworks.tv | Twitter: @timnilimaa

Error Message SCCM 2012 ERROR: Unable to access target machine for request

Should I be concerned with this message, or will it resolve on its own?
---> ERROR: Unable to access target machine for request: "2097153953", machine name: "MININT-NAEAFL", access denied or invalid network path. SMS_CLIENT_CONFIG_MANAGER 4/21/2015 11:34:59 AM 8100 (0x1FA4)
Execute query exec [sp_CP_SetLastErrorCode] 2097153953, 53 SMS_CLIENT_CONFIG_MANAGER 4/21/2015 11:34:59 AM 8100 (0x1FA4)
This machine is nowhere in my AD or SCCM...It was at one time, But I have deleted it. It still appears in the Logs. The CCM.LOG to be Precise
Bryan

No, this is nothing to be concerned with. Assuming you have auto-client push enabled, it will try to push the client agent to a resource without the agent every hour for 7 days. Thus, after the 7 day period expires from the last time it was discovered,
it won't try to push to this system anymore.
Jason | http://blog.configmgrftw.com | @jasonsandys

Collection evaluator error in SCCM 2012 SP1

I m getting below errors continuously in colleval.log,
CCEPSource::GetCollectionInfo:- Collection Not Found with CollectionID=2924
CEP-ErrorCode=-2016280319
CEP-Failed to process Collection Extended Properties changes, Status = COLLECTION NOT FOUND FOREIGN KEY CONSTRAINTS, changes will be retried on next processing cycle.
But, there is no such collection id '2924' in SCCM database. Due to these continuous errors, SMS_Collection_Evaluator component is in Critical.

Colleval.box had some CEP files (240+ files) and I deleted all of them.
Now, Colleval.box is empty and Colleval.box\Retry folder is also empty.

SCCM 2012 SP1 fails to install OSD of Captured Image

I installed Windows Server 2012, Visual Studio Pro 2008, 2010, 2012 and SQL Server 2012 onto a machine. Configured the settings on Windows Server 2012 and SQL 2012 to how the Developers requested to be configured. Ran the Capture Media from SCCM 2012 SP1,
saved to the designated network share. Capture was successful.
I create a TS to deploy the image to the other Dev Servers but it reboots to say no valid operating system found. I checked Monitoring for the Deployment I see the Task sequence but has the following error: Device - Unknown, MessageID - 11170, Description
- The task sequence manager could not successfully complete execution of the task sequence.
I see in the Apply Operation System from a captured image shows 1-1, 2-2, or 3-3. Does it matter which one I select and if so what does the numbers mean?
Any help is greatly appreciated, thanks!!

Hi Blacksuit,
Those numbers of the captured image stand for the indexes that are part of your WIM. And yes, it does matter which one you select. In the ConfigMgr console, go to your Software Library > Operating Systems > Operating System Images and select
the image you imported into ConfigMgr. Then at the bottom, click the Details tab to display your indexes. The index that contains your OS will have an OS Version and a description. The other indexes will be data images and not contain any
information in the Details tab. You'll need to choose the index (number) that contains the OS for the Apply OS step. To apply the data image indexes, use the Apply Data Image task sequence step and specify the partitions to apply the images
too before the Apply OS step.
Good luck!
-Matt

Sccm 2012 r2 error setup cannot compile mof file tasksequenceprovider.mof

Am getting this error during SCCM 2012 R2 installation on the same server which has SQL 2012 with SP1. "setup cannot compile mof file tasksequenceprovider.mof". Any help?

Hi,
The following blog introduced a tool scans winodws module which may help find out the missing file.
http://blogs.technet.com/b/configurationmgr/archive/2010/01/05/the-configuration-manager-service-pack-install-guide.aspx

SCCM 2012 R2 SQL Errors

I am getting following errors in SCCM 2012 R2 console since today!!!
Any ideas:
Microsoft SQL Server reported SQL message 266, severity 16: [25000][266][Microsoft][SQL Server Native Client 11.0][SQL Server]Transaction count after EXECUTE indicates a mismatching number of BEGIN and COMMIT statements. Previous count = 1, current count
= 0. : sp_addrolemember
Please refer to your Configuration Manager documentation, SQL Server documentation, or the Microsoft Knowledge Base for further troubleshooting information.

Parvinder,
Check the link in that thread. The resolution being the following:
'Hi guys,
I have just fixed this issue in our environment a few minutes ago. I had exactly the same issue. The problem relates
to the computer record as you described. The line:
<10-27-2009 12:20:45> ***SqlError: [42000][15410][Microsoft][ODBC SQL Server Driver][SQL Server]User or role 'DOMAIN\SERVER1$'
does not exist in this database. : sp_addrolemember
is the give away.
I went in to the SQL Management Studio, opend the SCCM database and removed the 'DOMAIN\SERVER1$' record. In my case
the problem was becasue a Branch DP server had been renamed but the DB login still hadt he old server name. Removing the OLD server login record from the databse and the main SQL security database and readding it using the NEW name resolved the problem.
When you re-add the server name make sure that you give the login the correct database rights, e.g. if it is a PXE Service
Point it will need that database right again. It is best to check the user rights for the computer and note the rights down before you remove and re-add it.
After this I re-ran the SETUP.EXe for SP2 and it went through perfectly.
Hope this helps.
Nathan
NSutton'
Cheers
Paul | sccmentor.wordpress.com

Huge wim files with sccm 2012 capture media.

So I'm making new image of two new HP models. 850/840 G2.
Win 7 and Win8.1
Image will have only newest win updates
Newest device drivers
Problem is that when I use capture media from SCCM 2012 R2, the WIM files are around 40-50Gb. And I'm a bit lost with this and don't know what to do.
I did all the things in same way like it was with G1 models. And then the WIM size was 9-11Gb.
I checked the inside of the wim file and there was hiberfil.sys files etc that are 16Gb as the RAM on the machine is the same ammount. Ram ammount was same in the G1 models also and this didn't happen. Also winsxs folder was under windows and that was
way over 10Gb.
Also one thing that is strange is that during capture, it captures 3 volumes. Disk should only have that 350MB and the windows installation.
Anyone have had this kind of experience?

Hi
I don't know exactly how I should go with the virtual machine thing .
This is just a small part in my work that I do, so I have done it the most "fastest" way for my self.
Basically I just need 2-3 images with machine drivers and windows update installed.
If making image trough virtual machine would require me to create driver package for each model and then notice that x amount of devices still don't get installed and I would need to create installation package of those missing drivers. That is something I
don't have time for...
Also when using driver package and installation for some special drivers from their won packages it feels that it takes long. And if i have my stuff already in the WIM file, things go smoothly much faster.
But if the virtualmachine trick is somehow superior, hit me with url. Thank you!
Strange thing is that some time ago all worked fine. And I was thinking that if someone has seen this kind of problem before.
It somewhow feels that it's capturing all the drives I have attached to machine. Volyme 3 of 3. And volyme is a disk? Not a partition?
I had usb stick (sccm capture media), machine harddriver with 350mb partition and the windows partition. Also external USB disk that it should save the WIM into.
Probaply next I will test the same machine with different harddrive...

WinPE Error Capture and Deploy Win7 - SCCM 2012 R2 w/ CU1

Hi Forum
Deploy and Capture: Windows 7 x64
SCCM Primary single site server: Server 2012 R2
Version: SCCM 2012 R2 w/ CU1
Environment is Hyper-V on Windows 8.1, deploying to a Gen1 VM with a legacy adapter.
I am running into an issue whilst building a lab environment. I have built a Capture and Deploy TS (using the standard TS, ie not MDT although this is integrated) and deployed to an imported machine using the MAC address via PXE. Custom Client package has
been created and put against the TS.
The machine picks up the PXE response and boots into the SCCM WinPE environment and I choose the TS. The only currently available TS is the Build and Capture.
It runs through the TS restarting at various points as expected and then after the Client Manager package is installed it restarts and runs the TS... at this point it starts saying. "Initiating Hardware Devices.." (or something to that effect).
It does this for about 15 seconds before I get this error:
Windows PE initialization failed with error code 0x8022001B
Seen here:
I am unable to get the cmd prompt up at this point and it will restart and carry on a normal build, no TS running, meaning no capture.
If any can advise, please do.
Thanks in advance
NN

Hyper-V should work fine without any drivers injected, and you did your VM correctly.
During this error, what you see in a back ground, ConfMgr wallpaper or Windows 7 black first-run screen "preparing/first run"? I´m just thinking, is there any chance, that you have additional restart step set to boot to WinPE, instead of booting
to default OS?
Otherwise, you will need to be able to Access CMD with F8 for more troubleshooting. Make sure you have F8 command Support enabled on boot image and re-distrubute it. Or create new boot image as Peter suggested.

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.

XP Capture Error (0x0000007F)~~SCCM 2012

Similar Messages

Maybe you are looking for