Hi All

I have a working TS but I got a new model that we need to build and it is giving me issues

it is a Dell 7010 and the issue comes in that it fails with the following error 0x80070070 - which has to do with available disk space - I am waiting for the techs on site to mail me the log file when they press F8 when the error occurs. :-(

the 7010 are shipped with the following disk config from Dell

If support at the remote site take the disk out and remove all partitions my TS works on this model as well but we cannot take out the disk out of each system to delete all the partitions every time

on the other models it is working just not in this he same one - They will also receive XE2 and 5810 models later on and I suspect that they will have the same issue

in my TS I have the following configuration

the Partitions within this step are configured as follow

Partition name: Windows

Type: Recovery

use specific size: 300MB

File System NTFS -> Quick format enabled

---------------------------------------------------

Partition Type:EFI

Use specific size: 500MB

Files system: fat32 -> quick format

-------------------------------------------------

Partition Type : MSR

Use specific size: 128Mb----------------------------------------------

Partition name: Windows

Type: Primary

Use a percentage of free remaining space: 100%

File System: NTFS -> Quick format enabled

under "Apply Operating system" the following is configured:

apply operating system from a Captured image: -> Image Package "WIN7EntSP1 X64 en-US"

Image: 2-2

Destination:"Next available formatted partition"

thx

kind regards

hi everyone,

Using SCCM 2012 R2 CU3 and trying to build Surface Pro 3.

I have successfully built 3 units but i have 2 units that are stuck at formatting C. Checked the logs and smsts log goes up to showing that diskpart command has been successful up until creating partitions but nothing to show after formatting drive C as NTFS(Quick).

I have tried going into Winpe and running diskpart manually by launching F8 command prompt. Using diskpart manually, I have tried cleaning the disk altogether as well as manually creating the partition structure that SCCM TS is creating. Even if i try manually, i get the same result. Formatting drive C never completes and gets stuck.Commandline i have tried is as below:

I have also tried creating a brand new task sequence with default UEFI partion/format options that had the same result. 

If i try to view C drive through cmtrace tool ,the drive format shows up as "RAW".

Just to confirm that 3 surface pro 3's have already been built with exactly the same TS and firmware/driver pack being used is the latest from MS(JAn 2015).

Just wondering if anyone has come across something like this before??

Here's my environment:

SCCM 2012 SP1 installed on Server 2008 R2 in a Hyper-V environment

Brand new boot images created after SP1 upgrade using Windows ADK

The virtual is using 1 network adapter (the legacy network adapter has been disabled, as a trobleshooting step)

PXE and WDS have been removed and recreated numerous times

This has never worked since implementation of SCCM 2012 (7/2012)

Attempted on multiple physical clients and a virtual client

The boot images work fine when setup as USB boot media

The network boot always finds the SCCM server as this screen shows:

Then it proceeds to loading the \SMSboot\boot.sdi. Some times it fails right here other times it proceeds to \SMSImages\MFC0008D\BootImagex86.MFC0008D.wim. Either way it gets a bit into the progress bar but always fails to this screen:

The smspxe.log shows the following:

Client lookup reply: <ClientIDReply><Identification Unknown="0" ItemKey="16777391" ServerName="" ServerRemoteName=""><Machine><ClientID/><NetbiosName/></Machine></Identification></ClientIDReply>
 SMSPXE 4/10/2013 8:21:12 AM 844 (0x034C)
00:15:5D:0A:6C:0D, BB01BB09-CF61-4611-8820-73941512B432: device is in the database. SMSPXE 4/10/2013 8:21:12 AM 844 (0x034C)
Client boot action reply: <ClientIDReply><Identification Unknown="0" ItemKey="16777391" ServerName="" ServerRemoteName=""><Machine><ClientID>GUID:0ba9fb20-f317-475e-8a24-bead025b5e31</ClientID><NetbiosName/></Machine></Identification><PXEBootAction LastPXEAdvertisementID="" LastPXEAdvertisementTime="" OfferID="MFC200EE" OfferIDTime="4/2/2013 11:21:00 AM" PkgID="MFC00007" PackageVersion="" PackagePath="http://(siteserver)/SMS_DP_SMSPKG$/MFC0008D" BootImageID="MFC0008D" Mandatory="0"/></ClientIDReply>
 SMSPXE 4/10/2013 8:21:12 AM 844 (0x034C)
00:15:5D:0A:6C:0D, BB01BB09-CF61-4611-8820-73941512B432: found optional advertisement MFC200EE SMSPXE 4/10/2013 8:21:12 AM 844 (0x034C)
Client boot action reply: <ClientIDReply><Identification Unknown="0" ItemKey="16777391" ServerName="" ServerRemoteName=""><Machine><ClientID>GUID:0ba9fb20-f317-475e-8a24-bead025b5e31</ClientID><NetbiosName/></Machine></Identification><PXEBootAction LastPXEAdvertisementID="" LastPXEAdvertisementTime="" OfferID="MFC200EE" OfferIDTime="4/2/2013 11:21:00 AM" PkgID="MFC00007" PackageVersion="" PackagePath="http://(siteserver)/SMS_DP_SMSPKG$/MFC0008D" BootImageID="MFC0008D" Mandatory="0"/></ClientIDReply>
 SMSPXE 4/10/2013 8:21:16 AM 844 (0x034C)
00:15:5D:0A:6C:0D, BB01BB09-CF61-4611-8820-73941512B432: found optional advertisement MFC200EE SMSPXE 4/10/2013 8:21:16 AM 844 (0x034C)
Looking for bootImage MFC0008D SMSPXE 4/10/2013 8:21:16 AM 844 (0x034C)

________________________________________________________________________________________________________________________

It also shows this occasionally after "Looking for bootImage"

BootImage MFC0008D needs to be updated (new packageID=MFC0008D) VersionUpdate=true SMSPXE 4/2/2013 11:25:41 AM 4020 (0x0FB4)

________________________________________________________________________________________________________________________

The only errors I've found have been in the distmgr.log when I've updated the boot images: (notice errors related to wimgapi.dll and errors related to set attribute, remove file, and remove directory failures)

STATMSG: ID=2300 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=(siteserver) SITE=MFC PID=2676 TID=6104 GMTDATE=Tue Apr 02 20:18:43.917 2013 ISTR0="BootImagex86" ISTR1="MFC0008D" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=400 AVAL0="MFC0008D" SMS_DISTRIBUTION_MANAGER 4/2/2013 1:18:43 PM 6104 (0x17D8)
Start updating the package MFC0008D... SMS_DISTRIBUTION_MANAGER 4/2/2013 1:18:43 PM 6104 (0x17D8)
Package storage format has changed for MFC0008D. Updating the distribution points SMS_DISTRIBUTION_MANAGER 4/2/2013 1:18:43 PM 6104 (0x17D8)
Enabling package MFC0008D for SMB access on MSWNET:["SMS_SITE=MFC"]\\(siteserver)\SMSPKGC$\MFC0008D\ SMS_DISTRIBUTION_MANAGER 4/2/2013 1:18:44 PM 6104 (0x17D8)
Attempting to add or update a package on a distribution point. SMS_DISTRIBUTION_MANAGER 4/2/2013 1:18:44 PM 6104 (0x17D8)
The distribution point is on the siteserver and the package is a content type package. There is nothing to be copied over. SMS_DISTRIBUTION_MANAGER 4/2/2013 1:18:44 PM 6104 (0x17D8)
STATMSG: ID=2342 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=(siteserver) SITE=MFC PID=2676 TID=6104 GMTDATE=Tue Apr 02 20:18:44.683 2013 ISTR0="BootImagex86" ISTR1="["Display=\\(siteserver)\"]MSWNET:["SMS_SITE=MFC"]\\(siteserver)\" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=2 AID0=400 AVAL0="MFC0008D" AID1=404 AVAL1="["Display=\\(siteserver)\"]MSWNET:["SMS_SITE=MFC"]\\(siteserver)\" SMS_DISTRIBUTION_MANAGER 4/2/2013 1:18:44 PM 6104 (0x17D8)
The current user context will be used for connecting to ["Display=\\(siteserver)\"]MSWNET:["SMS_SITE=MFC"]\\(siteserver)\. SMS_DISTRIBUTION_MANAGER 4/2/2013 1:18:45 PM 6104 (0x17D8)
No network connection is needed to ["Display=\\(siteserver)\"]MSWNET:["SMS_SITE=MFC"]\\(siteserver)\ as this is the local machine. SMS_DISTRIBUTION_MANAGER 4/2/2013 1:18:45 PM 6104 (0x17D8)
CreateSignatureShare, connecting to DP SMS_DISTRIBUTION_MANAGER 4/2/2013 1:18:45 PM 6104 (0x17D8)
Signature share exists on distribution point path \\(siteserver)\SMSSIG$ SMS_DISTRIBUTION_MANAGER 4/2/2013 1:18:45 PM 6104 (0x17D8)
Set share security on share \\(siteserver)\SMSSIG$ SMS_DISTRIBUTION_MANAGER 4/2/2013 1:18:45 PM 6104 (0x17D8)
Share SMSPKGC$ exists on distribution point \\(siteserver)\SMSPKGC$ SMS_DISTRIBUTION_MANAGER 4/2/2013 1:18:45 PM 6104 (0x17D8)
Set share security on share \\(siteserver)\SMSPKGC$ SMS_DISTRIBUTION_MANAGER 4/2/2013 1:18:45 PM 6104 (0x17D8)
Set share security on share \\(siteserver)\SCCMContentLib$ SMS_DISTRIBUTION_MANAGER 4/2/2013 1:18:45 PM 6104 (0x17D8)
Successfully created directory \\(siteserver)\SMSPKGC$\MFC0008D for package MFC0008D SMS_DISTRIBUTION_MANAGER 4/2/2013 1:18:46 PM 6104 (0x17D8)
Copying package MFC0008D to the package share location \\(siteserver)\SMSPKGC$\MFC0008D on the server ["Display=\\(siteserver)\"]MSWNET:["SMS_SITE=MFC"]\\(siteserver)\ SMS_DISTRIBUTION_MANAGER 4/2/2013 1:18:46 PM 6104 (0x17D8)
SMSDP_ExpandPXEImage: MFC0008D, 1174406304 SMS_DISTRIBUTION_MANAGER 4/2/2013 1:18:47 PM 6104 (0x17D8)
Library path mismatch: \\?\C:\SCCMContentLib, C:\SCCMContentLib SMS_DISTRIBUTION_MANAGER 4/2/2013 1:18:47 PM 6104 (0x17D8)
Expanding C:\SCCMContentLib\FileLib\DE79\DE7975B36C7DCA08953E8404A1FC115DC9A250828456A8E34C5C158C1907EE14 from package MFC0008D SMS_DISTRIBUTION_MANAGER 4/2/2013 1:18:47 PM 6104 (0x17D8)
Finding Wimgapi.Dll SMS_DISTRIBUTION_MANAGER 4/2/2013 1:18:47 PM 6104 (0x17D8)
MsiEnumRelatedProducts failed SMS_DISTRIBUTION_MANAGER 4/2/2013 1:18:47 PM 6104 (0x17D8)
FindProduct failed; 0x80070103 SMS_DISTRIBUTION_MANAGER 4/2/2013 1:18:47 PM 6104 (0x17D8)
MsiEnumRelatedProducts failed SMS_DISTRIBUTION_MANAGER 4/2/2013 1:18:47 PM 6104 (0x17D8)
FindProduct failed; 0x80070103 SMS_DISTRIBUTION_MANAGER 4/2/2013 1:18:47 PM 6104 (0x17D8)
Found C:\Windows\system32\wimgapi.dll SMS_DISTRIBUTION_MANAGER 4/2/2013 1:18:47 PM 6104 (0x17D8)
Sleep 30 minutes... SMS_DISTRIBUTION_MANAGER 4/2/2013 1:18:48 PM 4216 (0x1078)
SetFileAttributesW failed for C:\RemoteInstall\SMSTempBootFiles\MFC0008D\Windows\Boot\EFI\bootmgfw.efi SMS_DISTRIBUTION_MANAGER 4/2/2013 1:18:48 PM 6104 (0x17D8)
RemoveFile failed; 0x80070005 SMS_DISTRIBUTION_MANAGER 4/2/2013 1:18:48 PM 6104 (0x17D8)
RemoveDirectoryW failed (0x80070091) for C:\RemoteInstall\SMSTempBootFiles\MFC0008D\Windows\Boot\EFI SMS_DISTRIBUTION_MANAGER 4/2/2013 1:18:48 PM 6104 (0x17D8)
SetFileAttributesW failed for C:\RemoteInstall\SMSTempBootFiles\MFC0008D\Windows\Boot\Fonts\segmono_boot.ttf SMS_DISTRIBUTION_MANAGER 4/2/2013 1:18:48 PM 6104 (0x17D8)
RemoveFile failed; 0x80070005 SMS_DISTRIBUTION_MANAGER 4/2/2013 1:18:48 PM 6104 (0x17D8)
SetFileAttributesW failed for C:\RemoteInstall\SMSTempBootFiles\MFC0008D\Windows\Boot\Fonts\segoen_slboot.ttf SMS_DISTRIBUTION_MANAGER 4/2/2013 1:18:48 PM 6104 (0x17D8)
RemoveFile failed; 0x80070005 SMS_DISTRIBUTION_MANAGER 4/2/2013 1:18:48 PM 6104 (0x17D8)
SetFileAttributesW failed for C:\RemoteInstall\SMSTempBootFiles\MFC0008D\Windows\Boot\Fonts\segoe_slboot.ttf SMS_DISTRIBUTION_MANAGER 4/2/2013 1:18:48 PM 6104 (0x17D8)
RemoveFile failed; 0x80070005 SMS_DISTRIBUTION_MANAGER 4/2/2013 1:18:48 PM 6104 (0x17D8)
SetFileAttributesW failed for C:\RemoteInstall\SMSTempBootFiles\MFC0008D\Windows\Boot\Fonts\wgl4_boot.ttf SMS_DISTRIBUTION_MANAGER 4/2/2013 1:18:48 PM 6104 (0x17D8)
RemoveFile failed; 0x80070005 SMS_DISTRIBUTION_MANAGER 4/2/2013 1:18:48 PM 6104 (0x17D8)
RemoveDirectoryW failed (0x80070091) for C:\RemoteInstall\SMSTempBootFiles\MFC0008D\Windows\Boot\Fonts SMS_DISTRIBUTION_MANAGER 4/2/2013 1:18:48 PM 6104 (0x17D8)
SetFileAttributesW failed for C:\RemoteInstall\SMSTempBootFiles\MFC0008D\Windows\Boot\PXE\abortpxe.com SMS_DISTRIBUTION_MANAGER 4/2/2013 1:18:48 PM 6104 (0x17D8)
RemoveFile failed; 0x80070005 SMS_DISTRIBUTION_MANAGER 4/2/2013 1:18:48 PM 6104 (0x17D8)
SetFileAttributesW failed for C:\RemoteInstall\SMSTempBootFiles\MFC0008D\Windows\Boot\PXE\bootmgr.exe SMS_DISTRIBUTION_MANAGER 4/2/2013 1:18:48 PM 6104 (0x17D8)
RemoveFile failed; 0x80070005 SMS_DISTRIBUTION_MANAGER 4/2/2013 1:18:48 PM 6104 (0x17D8)
SetFileAttributesW failed for C:\RemoteInstall\SMSTempBootFiles\MFC0008D\Windows\Boot\PXE\pxeboot.com SMS_DISTRIBUTION_MANAGER 4/2/2013 1:18:48 PM 6104 (0x17D8)
RemoveFile failed; 0x80070005 SMS_DISTRIBUTION_MANAGER 4/2/2013 1:18:48 PM 6104 (0x17D8)
SetFileAttributesW failed for C:\RemoteInstall\SMSTempBootFiles\MFC0008D\Windows\Boot\PXE\pxeboot.n12 SMS_DISTRIBUTION_MANAGER 4/2/2013 1:18:48 PM 6104 (0x17D8)
RemoveFile failed; 0x80070005 SMS_DISTRIBUTION_MANAGER 4/2/2013 1:18:48 PM 6104 (0x17D8)
SetFileAttributesW failed for C:\RemoteInstall\SMSTempBootFiles\MFC0008D\Windows\Boot\PXE\wdsmgfw.efi SMS_DISTRIBUTION_MANAGER 4/2/2013 1:18:48 PM 6104 (0x17D8)
RemoveFile failed; 0x80070005 SMS_DISTRIBUTION_MANAGER 4/2/2013 1:18:48 PM 6104 (0x17D8)
SetFileAttributesW failed for C:\RemoteInstall\SMSTempBootFiles\MFC0008D\Windows\Boot\PXE\wdsnbp.com SMS_DISTRIBUTION_MANAGER 4/2/2013 1:18:48 PM 6104 (0x17D8)
RemoveFile failed; 0x80070005 SMS_DISTRIBUTION_MANAGER 4/2/2013 1:18:48 PM 6104 (0x17D8)
RemoveDirectoryW failed (0x80070091) for C:\RemoteInstall\SMSTempBootFiles\MFC0008D\Windows\Boot\PXE SMS_DISTRIBUTION_MANAGER 4/2/2013 1:18:48 PM 6104 (0x17D8)
RemoveDirectoryW failed (0x80070091) for C:\RemoteInstall\SMSTempBootFiles\MFC0008D\Windows\Boot SMS_DISTRIBUTION_MANAGER 4/2/2013 1:18:48 PM 6104 (0x17D8)
RemoveDirectoryW failed (0x80070091) for C:\RemoteInstall\SMSTempBootFiles\MFC0008D\Windows SMS_DISTRIBUTION_MANAGER 4/2/2013 1:18:48 PM 6104 (0x17D8)
RemoveDirectoryW failed (0x80070091) for C:\RemoteInstall\SMSTempBootFiles\MFC0008D SMS_DISTRIBUTION_MANAGER 4/2/2013 1:18:48 PM 6104 (0x17D8)
Expanding MFC0008D to C:\RemoteInstall\SMSImages SMS_DISTRIBUTION_MANAGER 4/2/2013 1:18:48 PM 6104 (0x17D8)
Used 1 out of 3 allowed processing threads. SMS_DISTRIBUTION_MANAGER 4/2/2013 1:18:48 PM 1872 (0x0750)
Sleep 3600 seconds... SMS_DISTRIBUTION_MANAGER 4/2/2013 1:18:48 PM 1872 (0x0750)
STATMSG: ID=2330 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=(siteserver) SITE=MFC PID=2676 TID=6104 GMTDATE=Tue Apr 02 20:18:49.796 2013 ISTR0="MFC0008D" ISTR1="["Display=\\(siteserver)\"]MSWNET:["SMS_SITE=MFC"]\\(siteserver)\" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=2 AID0=400 AVAL0="MFC0008D" AID1=404 AVAL1="["Display=\\(siteserver)\"]MSWNET:["SMS_SITE=MFC"]\\(siteserver)\" SMS_DISTRIBUTION_MANAGER 4/2/2013 1:18:49 PM 6104 (0x17D8)
Successfully created/updated the package server in the data source SMS_DISTRIBUTION_MANAGER 4/2/2013 1:18:49 PM 6104 (0x17D8)
Performing cleanup prior to returning. SMS_DISTRIBUTION_MANAGER 4/2/2013 1:18:49 PM 6104 (0x17D8)
The Package Action is 1, the Update Mask is 266240 and UpdateMaskEx is 1064960. SMS_DISTRIBUTION_MANAGER 4/2/2013 1:18:49 PM 6104 (0x17D8)
Successfully created/updated the package MFC0008D SMS_DISTRIBUTION_MANAGER 4/2/2013 1:18:49 PM 6104 (0x17D8)
STATMSG: ID=2311 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=(siteserver) SITE=MFC PID=2676 TID=6104 GMTDATE=Tue Apr 02 20:18:49.943 2013 ISTR0="MFC0008D" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=400 AVAL0="MFC0008D" SMS_DISTRIBUTION_MANAGER 4/2/2013 1:18:49 PM 6104 (0x17D8)
Set share security on share \\(siteserver)\SCCMContentLib$ SMS_DISTRIBUTION_MANAGER 4/2/2013 1:18:49 PM 6104 (0x17D8)
Set share security on share \\(siteserver)\SCCMContentLib$ SMS_DISTRIBUTION_MANAGER 4/2/2013 1:18:49 PM 6104 (0x17D8)
Created policy provider trigger for ID MFC0008D SMS_DISTRIBUTION_MANAGER 4/2/2013 1:18:51 PM 6104 (0x17D8)
Package MFC0008D does not have a preferred sender. SMS_DISTRIBUTION_MANAGER 4/2/2013 1:18:51 PM 6104 (0x17D8)
Package MFC0008D is new or has changed, replicating to all applicable sites. SMS_DISTRIBUTION_MANAGER 4/2/2013 1:18:51 PM 6104 (0x17D8)
CDistributionSrcSQL::UpdateAvailableVersion PackageID=MFC0008D, Version=2, Status=2301 SMS_DISTRIBUTION_MANAGER 4/2/2013 1:18:51 PM 6104 (0x17D8)
StoredPkgVersion (2) of package MFC0008D. StoredPkgVersion in database is 2. SMS_DISTRIBUTION_MANAGER 4/2/2013 1:18:51 PM 6104 (0x17D8)
SourceVersion (2) of package MFC0008D. SourceVersion in database is 2. SMS_DISTRIBUTION_MANAGER 4/2/2013 1:18:51 PM 6104 (0x17D8)
STATMSG: ID=2301 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=(siteserver) SITE=MFC PID=2676 TID=6104 GMTDATE=Tue Apr 02 20:18:51.876 2013 ISTR0="BootImagex86" ISTR1="MFC0008D" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=400 AVAL0="MFC0008D" SMS_DISTRIBUTION_MANAGER 4/2/2013 1:18:51 PM 6104 (0x17D8)
Exiting package processing thread. SMS_DISTRIBUTION_MANAGER 4/2/2013 1:18:51 PM 6104 (0x17D8)
Used 0 out of 3 allowed processing threads. SMS_DISTRIBUTION_MANAGER 4/2/2013 1:18:57 PM 1872 (0x0750)
The last source update time for pkg MFC0008D is 4/2/2013 10:56:53 AM Pacific Daylight Time SMS_DISTRIBUTION_MANAGER 4/2/2013 1:18:57 PM 1872 (0x0750)
The next start time for pkg MFC0008D is 4/2/2013 1:18:57 PM Pacific Daylight Time SMS_DISTRIBUTION_MANAGER 4/2/2013 1:18:57 PM 1872 (0x0750)

___________________________________________________________________________________________________________________________

At this point I'm out of ideas. I've searched all the forums tried just about everything I can think of except for settings DHCP options or IP Helpers. I've declined to do that because it appears to find the server just fine. Also the client, DHCP, and the SCCMPXE Point are all on the same subnet.

Help me Obi-(technet)-wan you're my only hope!

Hi all,

Here's a quick rundown of my setup. Got SCCM 2012 R2 installed. Configured DHCP scope options 66 and 67 as the target machine and SCCM server are on different VLANs. Can build Generation 1 VMs without issue. Generation 2 VMs, however, are not building. Here's the scenarios I've encountered so far:

with "067 Bootfile Name: Boot\x64\wdsmgfw.efi" set in dhcp I get the below result(sidenote: tried disabling "Secure Boot" just in case but this made no difference):

With "067 Bootfile Name: Boot\x64\wdsnbp.com" and "Secure Boot" enabled I get this:

With "067 Bootfile Name: Boot\x64\wdsnbp.com" and "Secure Boot" disabled I simply get:Boot Failed. EFI Network. No Operating System was Loaded. Press a key to retry the boot sequence...

As you may have guessed, nothing pops up in the smspxe.log for any of the above scenarios. The network folks say there's nothing blocking the communication between the target machine and the sccm server.

Has anyone got any suggestions as to what I might be doing wrong? Done a fair bit of hunting around online but haven't managed to get very far.

Gen 2 VMs clearly have some great potential but they're not much use if I can't get them built! Any help/info would be much appreciated

SCCM 2012 R2 CU4
We have a task sequence that migrates users from XP to Windows 7.

SMSTS.log
Executing command line: "bcdedit.exe"
CreateProcess failed. Code(0x80070002)
Command line execution failed (80070002)
Backing up existing boot system before trying to set up new boot system
Failed to install boot image.
Unspecified error (Error: 80004005; Source: Windows) TSManager 3/3/2015 10:39:54 AM 18212 (0x4724)
Failed to install boot image HOP000DA.
Unspecified error (Error: 80004005; Source: Windows) TSManager 3/3/2015 10:39:54 AM 18212 (0x4724)
Failed to reboot the system. Error 0x(80004005) TSManager 3/3/2015 10:39:54 AM 18212 (0x4724)
Failed to initialize a system reboot.
Unspecified error (Error: 80004005; Source: Windows) TSManager 3/3/2015 10:39:54 AM 18212 (0x4724)
Fatal error is returned in check for reboot request of the action (Restart in Windows PE).
Unspecified error (Error: 80004005; Source: Windows) TSManager 3/3/2015 10:39:54 AM 18212 (0x4724)
An error (0x80004005) is encountered in execution of the task sequence TSManager 3/3/2015 10:39:54 AM 18212 (0x4724)
Set authenticator in transport TSManager 3/3/2015 10:39:54 AM 18212 (0x4724)
Task Sequence Engine failed! Code: 80004005 TSManager 3/3/2015 10:54:56 AM 18212 (0x4724)
**************************************************************************** TSManager 3/3/2015 10:54:56 AM 18212 (0x4724)
Task sequence execution failed with error code 80004005 TSManager 3/3/2015 10:54:56 AM 18212 (0x4724)
Cleaning Up. TSManager 3/3/2015 10:54:56 AM 18212 (0x4724)
Removing Authenticator TSManager 3/3/2015 10:54:56 AM 18212 (0x4724)
Failed to delete directory 'C:\_SMSTaskSequence\WinPE' TSManager 3/3/2015 10:54:57 AM 18212 (0x4724)
SetNamedSecurityInfo() failed. TSManager 3/3/2015 10:54:57 AM 18212 (0x4724)
SetObjectOwner() failed. 0x80070005. TSManager 3/3/2015 10:54:57 AM 18212 (0x4724)
RemoveFile() failed for C:\_SMSTaskSequence\WinPE\WinPeSettings.dat. 0x80070005. TSManager 3/3/2015 10:54:57 AM 18212 (0x4724)
RemoveDirectoryW failed (0x80070091) for C:\_SMSTaskSequence\WinPE TSManager 3/3/2015 10:54:57 AM 18212 (0x4724)
Cleaning up task sequence folder TSManager 3/3/2015 10:54:57 AM 18212 (0x4724)
Unable to delete file C:\_SMSTaskSequence\TSEnv.dat (0x80070005). Continuing. TSManager 3/3/2015 10:54:59 AM 18212 (0x4724)
Unable to delete file C:\_SMSTaskSequence\WinPE\WinPeSettings.dat (0x80070005). Continuing. TSManager 3/3/2015 10:54:59 AM 18212 (0x4724)
Unable to delete directory C:\_SMSTaskSequence\WinPE (0x80070091).  Continuing. TSManager 3/3/2015 10:54:59 AM 18212 (0x4724)
Failed to delete directory 'C:\_SMSTaskSequence' TSManager 3/3/2015 10:54:59 AM 18212 (0x4724)
Deleting volume ID file C:\_SMSTSVolumeID.7159644d-f741-45d5-ab29-0ad8aa4771ca ... TSManager 3/3/2015 10:54:59 AM 18212 (0x4724)
Successfully unregistered Task Sequencing Environment COM Interface. TSManager 3/3/2015 10:54:59 AM 18212 (0x4724)
Executing command line: "C:\WINDOWS\CCM\TsProgressUI.exe" /Unregister TSManager 3/3/2015 10:54:59 AM 18212 (0x4724)
==========[ TsProgressUI started in process 17308 ]========== TsProgressUI 3/3/2015 10:54:59 AM 7248 (0x1C50)
Unregistering COM classes TsProgressUI 3/3/2015 10:54:59 AM 7248 (0x1C50)
Shutdown complete. TsProgressUI 3/3/2015 10:54:59 AM 7248 (0x1C50)
Process completed with exit code 0 TSManager 3/3/2015 10:54:59 AM 18212 (0x4724)
Successfully unregistered TS Progress UI. TSManager 3/3/2015 10:54:59 AM 18212 (0x4724)
Start to cleanup TS policy TSManager 3/3/2015 10:54:59 AM 18212 (0x4724)
End TS policy cleanup TSManager 3/3/2015 10:54:59 AM 18212 (0x4724)
RegQueryValueExW is unsuccessful for Software\Microsoft\SMS\Task Sequence, SMSTSEndProgram TSManager 3/3/2015 10:54:59 AM 18212 (0x4724)
GetTsRegValue() is unsuccessful. 0x80070002. TSManager 3/3/2015 10:54:59 AM 18212 (0x4724)
End program:  TSManager 3/3/2015 10:54:59 AM 18212 (0x4724)
Error executing Task Sequence Manager service. Code 0x80004005 TSManager 3/3/2015 10:54:59 AM 18212 (0x4724)
Sending error status message TSManager 3/3/2015 10:54:59 AM 18212 (0x4724)
Set authenticator in transport TSManager 3/3/2015 10:54:59 AM 18212 (0x4724)

Hi

I have a new Lenovo model which I need to be able to build with SCCM

I have pxe booted using our current boot wim and the laptop reboots shortly after configuring networks.  I have opend a command prompt and can see that the laptop doesn't get an ip address.  I have downloaded network drivers for the laptop and have used drvload to test the installation of drivers and have found one which works.

I want to take a copy of my current boot wim, create a new wim based on that, add the new driver and then use this new wim to boot the laptop.  I also want to take a copy of a Task Sequence, add the new laptop drivers and associate this with the new boot wim.  Essentially I want to create a new boot wim and task Sequence.

It is my understanding that machines will boot with the boot wim which is associated with the last Task Sequence that was deployed.  My question is, how can I test booting the laptop with the new boot wim and apply the new Task Sequence without this affecting any other machines ?  While testing I don't want any production / unknown machines booting using the new wim.  Unfortunately I don't have a test environment set up at the moment.  I know I can create a boot media which uses the new boot wim but then how can I advertise /deploy the new TS without other machines using the boot wim associated with it.

Thanks

Here is the problem in general the device will sysprep using the capture media and reboot into the PE environment and begin the capture sequence. 

It will scans and captures volume 1 of 2, scans volume 2, then begins to capture volume 2 and about a third of the way through the TS fails with the error code 0x80070002. 

I have performed this task too many times to count with successful results.  I have also tested this in a VM environment without any errors.  Drive space isn't an issue on any of the servers or file shares within SCCM

After looking through the logs you can see that:

WIM has entered capture phase for 95235 items CaptureSystemImage 1136 (0x0470)
WIM error:D:\Windows\System32\autochk.exe:BAK.
The system cannot find the file specified. (Error: 80070002; Source: Windows) CaptureSystemImage 1576 (0x0628)
Failure detected.  Aborting WIM operation CaptureSystemImage 1136 (0x0470)
hVolumeImage = WIMCaptureImage( m_hImageFile, const_cast<LPWSTR>(pathTargetVolume.c_str()), WIM_FLAG_VERIFY ), HRESULT=80070002 (e:\nts_sccm_release\sms\framework\tscore\wimfile.cpp,475) CaptureSystemImage 1136 (0x0470)
Unable to capture the volume image (0x80070002) CaptureSystemImage 1136 (0x0470)
ImageFile.CaptureVolumeImage( (*itr), &saFilesToNotCapture), HRESULT=80070002 (e:\nts_sccm_release\sms\client\osdeployment\capturesystemimage\capturesystemimage.cpp,747) CaptureSystemImage 1136 (0x0470)
CaptureSystemImage( progressUi, slVolumesToCapture, sOfflineSystemRoot, ImageFile), HRESULT=80070002 (e:\nts_sccm_release\sms\client\osdeployment\capturesystemimage\capturesystemimage.cpp,908) CaptureSystemImage 1136 (0x0470)
Failed to capture system image.
The system cannot find the file specified. (Error: 80070002; Source: Windows) CaptureSystemImage 1136 (0x0470)

___________________________________________________________________________________________________

After which the system reboots to "preparing your computer for use" "set up windows" screen.

Below you find the complete log.

Thanks for your help!

___________________________________________________________________________________________________

I´m having serious problem after R2 upgrade and I´m in a hurry to fix this, because OSD in production is interrupted.

So, before R2 upgrade, OSD with W7 x64 was working fine. Image had 2 indexes and it was captured with MDT based task, with 2 partitions (which is wrong, I know).

After I performed R2 upgrade, we noticed that Windows started go to D: drive. PreserveDrive letter variable has no effect, since image was captured previously in the wrong way. After I forced the image to go to C: By modifying Apply Image step (I changed from  OSDisk to Logical C:), I got W7 go to C: but now I can see BDEDrive letter in Windows Explorer. Enabling or disabling"do not assign drive letter to this partition" at BDEDrive partition has also no effect.

In WinPE and OSPhase, I can see drive letters with diskpart and BDEDrive has always come up with letter.

Capturing new image will take longer time to test everything else, so that´s why I´m trying to make this work with old image. CM 2012 R2 non-CU is with MDT 2013 and we´re using UDI based MDT tasks.

Any help or sightview is good, share you thoughts please :)

Hello,

I have the problem that when I install a Application through SCCM MDT UDI Wizard that application installation stop with the error

"error 615: The password provided is too short to meet the policy of your user account. Please choose a longer password. "

I'm using the SP1 for SCCM with UC1.

Is there any chance to solve this issue?

BR,

bad3m3ist3r

Hi together

I cannot stage any more clients in some of our sites I get the following Error in Component Status view:

Critical SMS_DESPOOLER

Despooler.log on Site Servers says:

- CFileLibrary::OpenFile failed; 0x80070003

- CContentBundle::ExtractContentBundle failed; 0x80070003

- Failed to extract contents to the content library. 0x80070003

- Failed to extract package contents from C:\PROGRAM FILES\MICROSOFT CONFIGURATION MANAGER\INBOXES\DESPOOLR.BOX\RECEIVE\PKG71E8Z.TRY. Error = 3

- We've retried enough times on job 00001F5B, give it up.

- Despooler failed to execute the instruction, error code = 8

- but there is enough space !

- from then on nothing more but: Waiting for ready instruction file....

ooGDoo

SCCM R2 not able to PXE boot from Surface pro. I am new to environment. How can I tell if PXE broadcasts are making it to device and to sccm ? I recieve the following output in CMTRACE in SMSPXE.log   ..  Am I doing something completely wrong ? 

Client boot action reply: <ClientIDReply><Identification Unknown="0" ItemKey="16781189" ServerName=""><Machine><ClientID/><NetbiosName/></Machine></Identification><PXEBootAction LastPXEAdvertisementID="" LastPXEAdvertisementTime="" OfferID="" OfferIDTime="" PkgID="" PackageVersion="" PackagePath="" BootImageID="" Mandatory=""/></ClientIDReply>

Mj

I'm trying to make a tool my technicians can use to create a backup image for an existing machine.

What I thought of was using a BAT that I could inject into my Boot images and run some really simple DISM command:

Dism /Capture-Image /ImageFile:D:\%computername%.wim /CaptureDir:C:\ /Name:"Captured Image"

Problem is the %computername% to name the WIM keeps comming up as MINWINPC.wim. It's not even the MININT-xxxxxx computer name that WinPE generates. 

Maybe I'm not using the command correctly, but is there a way I can make the computer name something identifiable, like the computer's serial #?

We deploy Windows servers in 4 different datacenters.  Each datacenter has it's own DP, and they are all a member of the same OSD DP group I created.

Long story short, there are some times when a firewall will be blocking access to the local DP but not access to the SCCM server which is also a MP and a DP, or access to other DPs in other datacenters.

However when I build, the build fails because it can't retrieve content from the local DP because of firewall.  80072ee2 errors and such. 

Why is the build not trying to grab content from a DP that it can talk to over port 80?  I even tried checking the "When no local DP is available, use remote DP" but that hasn't resolved it.  The logs show it ONLY trying to connect to the local DP, and when it can't do that the build fails.

HI together,

I have a big problem. The clients (unknown) we try to stage are started than start the PXE and then abort. After that they have an PXE advertisement that needs to be cleared. So we delete the unknown devices. But they wont even start the PXE. After that we are registering the clients and advise them to the OSD Release Collection. There I can see the "old" advertisement and I try to clear it. But after every start of the client the PXE aborts.

Can anyone help out? A check of the Log is quite difficult because it wont even start the PXE.

Regards ooGDoo

ooGDoo

Screenshots of errors:

http://sdrv.ms/17epiNz

Here's my setup:

Windows Server 2012 on Hyper V

SCCM 2012 SP1 installed as primary site

Server is set up as PXE distribution point

WDS was set up by enabling PXE distribution point, not by manually adding the role and configuring

2 Boot images created (one for x86 and one for x64) and updated on distribution points

Both boot images are set to be deployed from the PXE-enabled point

I have a build and capture task sequence distributed to a collection with my test computer that I'm trying to PXE boot

Options 66 and 67 are set up on the DHCP scope, this should be working fine (it can reach the server, it just seems to not be getting a boot image)

Looking for any advice, let me know what more information I need to give, if any. Thank you. 

So we just got some new dell laptop for my company(Latitude E5450). I can't seem to image these systems. However I am able to image all other systems I have. Please help. here is my log.

Hi,

We have SCCM 2012 R2 in place and have previously had it working fine to PXE deploy images to machines.

Recently we have bought a bunch of Surface Pro 3 tablets and have setup a task sequence and imported drivers to our environment. We downloaded the drivers from microsofts website. We have the surface pro 3 docks and i have inserted both NIC drivers from microsofts website into the boot image its using. The content is showing as being successfully distributed to the local DP after adding the drivers.

The problem seems to be that when the client pxe boots it gets to the SCCM splash screen and then reboots. It looks like there is no network connectivity as i've looked at command prompt and tried to ping the sccm server and its unreachable. 

In the smsts log file on the client there are errors stating:

"Failed to download pxe variable file. Code(0x00000001)
PxeGetPxeData failed with 0x80004005:

and

"RegOpenKeyExW failed for Software\Microsoft\SMS\Task Sequence
GetTsRegValue() failed. 0x80070002"

Any suggestions?

Any tips?

We are looking for some script which will allow us to capture a computer-name from manual input during an OSD task Sequence deployment.

We have previously used the following VBS code successfully with SCCM 2007:
"set env = CreateObject("Microsoft.SMS.TSEnvironment")
Name = inputbox("Enter the name for the new computer" ,"Prompt for Computer Name:",env("_SMSTSMachineName"),400,0)
env("OSDComputerName") = Name"

However, this does not seem to work successfully after our recent migration to SCCM 2012

We have tried unsuccessfully to find a solution online, including the following links & forum posts:
http://www.windows-noob.com/forums/index.php?/topic/5542-how-can-i-easily-prompt-for-a-computer-name-in-configuration-manager-2012/
https://t3chn1ck.wordpress.com/2009/04/24/script-to-prompt-for-system-name-in-sccm-osd/
http://blogs.technet.com/b/breben/archive/2009/01/25/prompt-for-computer-name-in-osd-task-sequence.aspx

Note that this is an issue when we are building PCs using Task Sequence Media (i.e., building from usb sticks) only. When building from deployments advertised via PXE boot, etc, the computer name is retained from the AD computer account. However, when using TS media, the PCs always build using the self-generated "minintxxx..." format computer name, which can be a pain to rectify after the event.

Nothing we have tried thus far seems to capture the required input; most of the suggestions from the linked posts fail, either ignoring the computer-name we input at the prompt (e.g., resulting in the "minint..." format name)

I would appreciate any help as this causes a fair bit of hassle, having to rename the computer each time it is rebuilt from usb stick. Note that we will require a working solution for usb rebuilds so we can build PCs in site at location where the network connection is low or unreliable bandwidth.

Thanks

Stan

Hi

I migrate a "driver package" the SCCM 2007 to SCCM 2012 (No problem)

My problem: When i try to create a "drivers packages", i enter UNC but when i clic to "Next", i have always a same message: "Specify a UNC path to an empty folder".

It's necessary to "import drivers" before ? what is a problem because when i go to UNC i view all files (inf,exe, etc..)

Thanks