Jump to content


anyweb

using SCCM 2012 in a LAB - Part 7. Build and Capture Windows 7 X64

Recommended Posts

These are some awesome tutorials!!! Thank you! I have a question about PXE booting but it is not because I am receiving an error. I have my computer to set to boot to the network device first on every boot. What I am seeing is it will start the build and capture, as soon as the image is brought down and installed the pc will reboot. At this point it will pxe boot again which it shouldn't do. I can change the boot order to boot from the hard drive and that will resolve the issue but as I am working on eventually making this fully automated without the need to be at the computer. I have to wonder, Is there a way around this? Shouldn't it only PXE boot once after it starts the task sequence? I am probably missing something very simple here. I have done a lot of googling and have not found any answers but it could be I am just typing the wrong keywords. Thanks for everything!

Share this post


Link to post
Share on other sites


did you make your task sequence deployment available or required ??

Share this post


Link to post
Share on other sites

well unless you actually press F12 it should timeout and continue with the next boot device, the hard disc, so is it ? (after displaying the PXE boot menu....)

Share this post


Link to post
Share on other sites

Actually I am working on setting up a zero touch deploy. I would like to have it so i can add a computer or computers to a collection and it will kick off. I have replaced the pxe boot files with the *.n12 file so no F12 is required and also have it set so each computer would boot from the network as the first boot device. I have not seen anybody do a full zero touch deploy in sccm 2012 yet so was hoping to find a solution to the infinite boot loop. :)

Share this post


Link to post
Share on other sites

Problem PXE-boot.

 

I got the PXE-E53 no filenname....

 

When I follow the SMSPXE.log I see this "error"

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

 

Where the ItemKey is a key already used by another computer. If I delete all computers from my "Windows 7 Collection" the PXE booting works like a charm. So im pretty much stuck here.

It must be something with the resource id´s. Because it works as I said when I delete all the computers and all the recource id´s are deleted with the computers.

 

(I see no errors in my distmgr)

 

Anyone else seen this problem and can help me to solve it?

Share this post


Link to post
Share on other sites

Hi

I created new VM using Hyper V and I want to get to the BIOS of the new VM.

I need to change the boot order for PXE boot

 

How do I go to BIOS. The F2 or Del or F8 or F12 doesn't work?

 

 

Regards

Share this post


Link to post
Share on other sites

In the same boat as some others posted before though their fixes i already had in place.

 

Error relates to TSPxe after i select my task sequence in pxe i get an error " Cannot find package xxxx on your distribution point"

 

from the logs

 

Content location request for AKL00004:3 failed (Code 0x80040102)

 

From the previous replies

 

DNS is fine

I have created a boundary and a boundary group which points to the boundary that to linked to the dp.

I have "Updated the Distribution Points" on my x64 Boot image,(AKL00004), packages, ts etc.. and ran a verification which verified that it was on the dp.

I have created another Task sequence to no avail, same error.

post-17333-0-69933600-1346398885_thumb.png

Share this post


Link to post
Share on other sites

When i try and create the build and capture collection i do not know how to create the query. if i select all windows 7 then i get everything i did in the first collection i created. could you tell me how to create the build and capture collection?

 

thank you

 

Jeff

Share this post


Link to post
Share on other sites

Actually I am working on setting up a zero touch deploy. I would like to have it so i can add a computer or computers to a collection and it will kick off. I have replaced the pxe boot files with the *.n12 file so no F12 is required and also have it set so each computer would boot from the network as the first boot device. I have not seen anybody do a full zero touch deploy in sccm 2012 yet so was hoping to find a solution to the infinite boot loop. :)

 

if you want it to be zero touch then you should make your deployments Required (mandatory) but be very very careful doing so, only target these task sequences to Deploy OS collections and never to collections containing lots of computers (like All Systems)

Share this post


Link to post
Share on other sites

Hi,

 

i get also a problem deploying the captured image. I have no idea why it gets the pictured error while deploying the os to the system.

 

I also followed all steps. The only difference i am using SCCM 2012 SP1 with patched Config Manager Client. But the system doesn go so far...

 

Also there will no logs produced since the partition is not available. (No "C" Drive...)

 

Any hints and suggestion would be great!

post-18894-0-69479600-1359042331_thumb.jpg

Share this post


Link to post
Share on other sites

How long does the Device Collection of Build and Capture Windows 7 x64 take to complete? Mines been running for quite some time and has no members and still has the hour glass. It's been there overnight. I have also noticed the same hourglass on 'All Systems' has been there for days! However 'All Systems' has members as this was run couple weeks back

Share this post


Link to post
Share on other sites

Hello;

Actually I didn't understand the logic completely ...

Can someone explain me please why we need to enter the path for wim file at Step.6 although sccm can access the wim file from operating system installer package path?

Share this post


Link to post
Share on other sites

Hi

 

I have this probleme when i try boot on lan, someone can help me please

 

booting from PXE menu

 

a local boot

b Managed Dos

c Managed WinPE

d Managed linux PE

 

i dont know what i do

Share this post


Link to post
Share on other sites

what hardware are you PXE booting, those menu choices don't look familiar... are you PXE booting to a configuration manager server ?

Share this post


Link to post
Share on other sites

Hello,

 

I have a question about including the configmanager client in my build and capture task sequence.

 

Right now, I have an SCCM 2012 Sp1/MDT 2012 Update 1 UDI deployment task sequence. When I use that task sequence to deploy the install.wim from the Windows 7 DVD, it works great. When I use that task sequence to deploy the .WIM that I created using this guide, the deployment fails at installing the configmanager client.

 

During my build and capture, I am installing the "Microsoft Configuration Manager Client Upgrade 5.0 ALL" package that I created following these instructions. I am also installing this same package during my deployments.

 

Is that right? It seems like I should either drop the client from either the Build and Capture or the deployment task sequence.

Share this post


Link to post
Share on other sites

Im having a pretty strange issue that I haven't found an answer to yet. Everything was working smoothly until I got to this portion of the guide. When I try to create the task sequence in SCCM I cannot see the distribution point. I can see and select the boot image, but when I try to select the operating system install package no distribution points are listed. The OS install package was distributed to the distribution point in a previous portion of this guide. When I look at the properties of the OS install package it shows the DP.

 

I tried uninstalling WDS and now I see a boatload of errors in my distmgr.log file

 

 

SetFileAttributesW failed for D:\RemoteInstall\SMSTempBootFiles\CMS00004\Windows\Boot\EFI\bootmgfw.efi SMS_DISTRIBUTION_MANAGER 5/29/2013 2:12:51 PM 6000 (0x1770)
RemoveFile failed; 0x80070005 SMS_DISTRIBUTION_MANAGER 5/29/2013 2:12:52 PM 6000 (0x1770)
RemoveDirectoryW failed (0x80070091) for D:\RemoteInstall\SMSTempBootFiles\CMS00004\Windows\Boot\EFI SMS_DISTRIBUTION_MANAGER 5/29/2013 2:12:52 PM 6000 (0x1770)
SetFileAttributesW failed for D:\RemoteInstall\SMSTempBootFiles\CMS00004\Windows\Boot\Fonts\segmono_boot.ttf SMS_DISTRIBUTION_MANAGER 5/29/2013 2:12:52 PM 6000 (0x1770)
RemoveFile failed; 0x80070005 SMS_DISTRIBUTION_MANAGER 5/29/2013 2:12:52 PM 6000 (0x1770)
SetFileAttributesW failed for D:\RemoteInstall\SMSTempBootFiles\CMS00004\Windows\Boot\Fonts\segoen_slboot.ttf SMS_DISTRIBUTION_MANAGER 5/29/2013 2:12:52 PM 6000 (0x1770)
RemoveFile failed; 0x80070005 SMS_DISTRIBUTION_MANAGER 5/29/2013 2:12:52 PM 6000 (0x1770)
SetFileAttributesW failed for D:\RemoteInstall\SMSTempBootFiles\CMS00004\Windows\Boot\Fonts\segoe_slboot.ttf SMS_DISTRIBUTION_MANAGER 5/29/2013 2:12:52 PM 6000 (0x1770)
RemoveFile failed; 0x80070005 SMS_DISTRIBUTION_MANAGER 5/29/2013 2:12:52 PM 6000 (0x1770)
SetFileAttributesW failed for D:\RemoteInstall\SMSTempBootFiles\CMS00004\Windows\Boot\Fonts\wgl4_boot.ttf SMS_DISTRIBUTION_MANAGER 5/29/2013 2:12:52 PM 6000 (0x1770)
RemoveFile failed; 0x80070005 SMS_DISTRIBUTION_MANAGER 5/29/2013 2:12:52 PM 6000 (0x1770)
RemoveDirectoryW failed (0x80070091) for D:\RemoteInstall\SMSTempBootFiles\CMS00004\Windows\Boot\Fonts SMS_DISTRIBUTION_MANAGER 5/29/2013 2:12:52 PM 6000 (0x1770)
SetFileAttributesW failed for D:\RemoteInstall\SMSTempBootFiles\CMS00004\Windows\Boot\PXE\abortpxe.com SMS_DISTRIBUTION_MANAGER 5/29/2013 2:12:52 PM 6000 (0x1770)
RemoveFile failed; 0x80070005 SMS_DISTRIBUTION_MANAGER 5/29/2013 2:12:52 PM 6000 (0x1770)
SetFileAttributesW failed for D:\RemoteInstall\SMSTempBootFiles\CMS00004\Windows\Boot\PXE\bootmgr.exe SMS_DISTRIBUTION_MANAGER 5/29/2013 2:12:52 PM 6000 (0x1770)
RemoveFile failed; 0x80070005 SMS_DISTRIBUTION_MANAGER 5/29/2013 2:12:52 PM 6000 (0x1770)
SetFileAttributesW failed for D:\RemoteInstall\SMSTempBootFiles\CMS00004\Windows\Boot\PXE\pxeboot.com SMS_DISTRIBUTION_MANAGER 5/29/2013 2:12:52 PM 6000 (0x1770)
RemoveFile failed; 0x80070005 SMS_DISTRIBUTION_MANAGER 5/29/2013 2:12:52 PM 6000 (0x1770)
SetFileAttributesW failed for D:\RemoteInstall\SMSTempBootFiles\CMS00004\Windows\Boot\PXE\pxeboot.n12 SMS_DISTRIBUTION_MANAGER 5/29/2013 2:12:52 PM 6000 (0x1770)
RemoveFile failed; 0x80070005 SMS_DISTRIBUTION_MANAGER 5/29/2013 2:12:52 PM 6000 (0x1770)
SetFileAttributesW failed for D:\RemoteInstall\SMSTempBootFiles\CMS00004\Windows\Boot\PXE\wdsmgfw.efi SMS_DISTRIBUTION_MANAGER 5/29/2013 2:12:52 PM 6000 (0x1770)
RemoveFile failed; 0x80070005 SMS_DISTRIBUTION_MANAGER 5/29/2013 2:12:52 PM 6000 (0x1770)
SetFileAttributesW failed for D:\RemoteInstall\SMSTempBootFiles\CMS00004\Windows\Boot\PXE\wdsnbp.com SMS_DISTRIBUTION_MANAGER 5/29/2013 2:12:52 PM 6000 (0x1770)
RemoveFile failed; 0x80070005 SMS_DISTRIBUTION_MANAGER 5/29/2013 2:12:52 PM 6000 (0x1770)
RemoveDirectoryW failed (0x80070091) for D:\RemoteInstall\SMSTempBootFiles\CMS00004\Windows\Boot\PXE SMS_DISTRIBUTION_MANAGER 5/29/2013 2:12:52 PM 6000 (0x1770)
RemoveDirectoryW failed (0x80070091) for D:\RemoteInstall\SMSTempBootFiles\CMS00004\Windows\Boot SMS_DISTRIBUTION_MANAGER 5/29/2013 2:12:52 PM 6000 (0x1770)
RemoveDirectoryW failed (0x80070091) for D:\RemoteInstall\SMSTempBootFiles\CMS00004\Windows SMS_DISTRIBUTION_MANAGER 5/29/2013 2:12:52 PM 6000 (0x1770)
RemoveDirectoryW failed (0x80070091) for D:\RemoteInstall\SMSTempBootFiles\CMS00004 SMS_DISTRIBUTION_MANAGER 5/29/2013 2:12:52 PM 6000 (0x1770)
Processing CMS00005 SMS_DISTRIBUTION_MANAGER 5/29/2013 2:12:52 PM 6000 (0x1770)
Library path mismatch: \\?\D:\SCCMContentLib, D:\SCCMContentLib SMS_DISTRIBUTION_MANAGER 5/29/2013 2:12:52 PM 6000 (0x1770)
Removing CMS00005 from D:\RemoteInstall\SMSImages SMS_DISTRIBUTION_MANAGER 5/29/2013 2:12:52 PM 6000 (0x1770)
Removing D:\RemoteInstall\SMSTempBootFiles\CMS00005 SMS_DISTRIBUTION_MANAGER 5/29/2013 2:12:52 PM 6000 (0x1770)
SetFileAttributesW failed for D:\RemoteInstall\SMSTempBootFiles\CMS00005\Windows\Boot\EFI\bootmgfw.efi SMS_DISTRIBUTION_MANAGER 5/29/2013 2:12:52 PM 6000 (0x1770)
RemoveFile failed; 0x80070005 SMS_DISTRIBUTION_MANAGER 5/29/2013 2:12:52 PM 6000 (0x1770)
RemoveDirectoryW failed (0x80070091) for D:\RemoteInstall\SMSTempBootFiles\CMS00005\Windows\Boot\EFI SMS_DISTRIBUTION_MANAGER 5/29/2013 2:12:52 PM 6000 (0x1770)
SetFileAttributesW failed for D:\RemoteInstall\SMSTempBootFiles\CMS00005\Windows\Boot\Fonts\segmono_boot.ttf SMS_DISTRIBUTION_MANAGER 5/29/2013 2:12:52 PM 6000 (0x1770)
RemoveFile failed; 0x80070005 SMS_DISTRIBUTION_MANAGER 5/29/2013 2:12:52 PM 6000 (0x1770)
SetFileAttributesW failed for D:\RemoteInstall\SMSTempBootFiles\CMS00005\Windows\Boot\Fonts\segoen_slboot.ttf SMS_DISTRIBUTION_MANAGER 5/29/2013 2:12:52 PM 6000 (0x1770)
RemoveFile failed; 0x80070005 SMS_DISTRIBUTION_MANAGER 5/29/2013 2:12:52 PM 6000 (0x1770)
SetFileAttributesW failed for D:\RemoteInstall\SMSTempBootFiles\CMS00005\Windows\Boot\Fonts\segoe_slboot.ttf SMS_DISTRIBUTION_MANAGER 5/29/2013 2:12:52 PM 6000 (0x1770)
RemoveFile failed; 0x80070005 SMS_DISTRIBUTION_MANAGER 5/29/2013 2:12:52 PM 6000 (0x1770)
SetFileAttributesW failed for D:\RemoteInstall\SMSTempBootFiles\CMS00005\Windows\Boot\Fonts\wgl4_boot.ttf SMS_DISTRIBUTION_MANAGER 5/29/2013 2:12:52 PM 6000 (0x1770)
RemoveFile failed; 0x80070005 SMS_DISTRIBUTION_MANAGER 5/29/2013 2:12:52 PM 6000 (0x1770)
RemoveDirectoryW failed (0x80070091) for D:\RemoteInstall\SMSTempBootFiles\CMS00005\Windows\Boot\Fonts SMS_DISTRIBUTION_MANAGER 5/29/2013 2:12:52 PM 6000 (0x1770)
SetFileAttributesW failed for D:\RemoteInstall\SMSTempBootFiles\CMS00005\Windows\Boot\PXE\abortpxe.com SMS_DISTRIBUTION_MANAGER 5/29/2013 2:12:52 PM 6000 (0x1770)
RemoveFile failed; 0x80070005 SMS_DISTRIBUTION_MANAGER 5/29/2013 2:12:52 PM 6000 (0x1770)
SetFileAttributesW failed for D:\RemoteInstall\SMSTempBootFiles\CMS00005\Windows\Boot\PXE\bootmgr.exe SMS_DISTRIBUTION_MANAGER 5/29/2013 2:12:53 PM 6000 (0x1770)
RemoveFile failed; 0x80070005 SMS_DISTRIBUTION_MANAGER 5/29/2013 2:12:53 PM 6000 (0x1770)
SetFileAttributesW failed for D:\RemoteInstall\SMSTempBootFiles\CMS00005\Windows\Boot\PXE\pxeboot.com SMS_DISTRIBUTION_MANAGER 5/29/2013 2:12:53 PM 6000 (0x1770)
RemoveFile failed; 0x80070005 SMS_DISTRIBUTION_MANAGER 5/29/2013 2:12:53 PM 6000 (0x1770)
SetFileAttributesW failed for D:\RemoteInstall\SMSTempBootFiles\CMS00005\Windows\Boot\PXE\pxeboot.n12 SMS_DISTRIBUTION_MANAGER 5/29/2013 2:12:53 PM 6000 (0x1770)
RemoveFile failed; 0x80070005 SMS_DISTRIBUTION_MANAGER 5/29/2013 2:12:53 PM 6000 (0x1770)
SetFileAttributesW failed for D:\RemoteInstall\SMSTempBootFiles\CMS00005\Windows\Boot\PXE\wdsmgfw.efi SMS_DISTRIBUTION_MANAGER 5/29/2013 2:12:53 PM 6000 (0x1770)
RemoveFile failed; 0x80070005 SMS_DISTRIBUTION_MANAGER 5/29/2013 2:12:53 PM 6000 (0x1770)
SetFileAttributesW failed for D:\RemoteInstall\SMSTempBootFiles\CMS00005\Windows\Boot\PXE\wdsnbp.com SMS_DISTRIBUTION_MANAGER 5/29/2013 2:12:53 PM 6000 (0x1770)
RemoveFile failed; 0x80070005 SMS_DISTRIBUTION_MANAGER 5/29/2013 2:12:53 PM 6000 (0x1770)
RemoveDirectoryW failed (0x80070091) for D:\RemoteInstall\SMSTempBootFiles\CMS00005\Windows\Boot\PXE SMS_DISTRIBUTION_MANAGER 5/29/2013 2:12:53 PM 6000 (0x1770)
RemoveDirectoryW failed (0x80070091) for D:\RemoteInstall\SMSTempBootFiles\CMS00005\Windows\Boot SMS_DISTRIBUTION_MANAGER 5/29/2013 2:12:53 PM 6000 (0x1770)
RemoveDirectoryW failed (0x80070091) for D:\RemoteInstall\SMSTempBootFiles\CMS00005\Windows SMS_DISTRIBUTION_MANAGER 5/29/2013 2:12:53 PM 6000 (0x1770)
RemoveDirectoryW failed (0x80070091) for D:\RemoteInstall\SMSTempBootFiles\CMS00005 SMS_DISTRIBUTION_MANAGER 5/29/2013 2:12:53 PM 6000 (0x1770)
RegQueryValueExW failed for Software\Microsoft\SMS\DP, INST_WDSAUTO SMS_DISTRIBUTION_MANAGER 5/29/2013 2:12:53 PM 6000 (0x1770)
RegReadDWord failed; 0x80070002 SMS_DISTRIBUTION_MANAGER 5/29/2013 2:12:53 PM 6000 (0x1770)
Machine is running Windows Server. (NTVersion=0X601, ServicePack=1) SMS_DISTRIBUTION_MANAGER 5/29/2013 2:12:53 PM 6000 (0x1770)
WDS is INSTALLED SMS_DISTRIBUTION_MANAGER 5/29/2013 2:12:53 PM 6000 (0x1770)
CcmUnregisterWDS SMS_DISTRIBUTION_MANAGER 5/29/2013 2:12:53 PM 6000 (0x1770)
Removing SMSPXE provider. Performing an uninstall SMS_DISTRIBUTION_MANAGER 5/29/2013 2:12:53 PM 6000 (0x1770)
PxeProviderUnRegister SMS_DISTRIBUTION_MANAGER 5/29/2013 2:12:53 PM 6000 (0x1770)
PxeLoadWdsPxe SMS_DISTRIBUTION_MANAGER 5/29/2013 2:12:53 PM 6000 (0x1770)
Loading wdspxe.dll from C:\Windows\system32\wdspxe.dll SMS_DISTRIBUTION_MANAGER 5/29/2013 2:12:53 PM 6000 (0x1770)
wdspxe.dll is loaded SMS_DISTRIBUTION_MANAGER 5/29/2013 2:12:53 PM 6000 (0x1770)
WDSServer status is 4 SMS_DISTRIBUTION_MANAGER 5/29/2013 2:12:56 PM 6000 (0x1770)
WDSServer is STARTED SMS_DISTRIBUTION_MANAGER 5/29/2013 2:12:56 PM 6000 (0x1770)
Removing existing PXE related directories SMS_DISTRIBUTION_MANAGER 5/29/2013 2:12:56 PM 6000 (0x1770)
Removing PXE Boot directory: D:\RemoteInstall\SMSBoot SMS_DISTRIBUTION_MANAGER 5/29/2013 2:12:56 PM 6000 (0x1770)
Removing PXE Temp directory: D:\RemoteInstall\SMSTemp SMS_DISTRIBUTION_MANAGER 5/29/2013 2:12:56 PM 6000 (0x1770)
Removing PXE Images directory: D:\RemoteInstall\SMSImages SMS_DISTRIBUTION_MANAGER 5/29/2013 2:12:56 PM 6000 (0x1770)
Removing PXE Images directory: D:\RemoteInstall\SMSTempBootFiles SMS_DISTRIBUTION_MANAGER 5/29/2013 2:12:56 PM 6000 (0x1770)
SetFileAttributesW failed for D:\RemoteInstall\SMSTempBootFiles\CMS00004\Windows\Boot\EFI\bootmgfw.efi SMS_DISTRIBUTION_MANAGER 5/29/2013 2:12:56 PM 6000 (0x1770)
RemoveFile failed; 0x80070005 SMS_DISTRIBUTION_MANAGER 5/29/2013 2:12:56 PM 6000 (0x1770)
RemoveDirectoryW failed (0x80070091) for D:\RemoteInstall\SMSTempBootFiles\CMS00004\Windows\Boot\EFI SMS_DISTRIBUTION_MANAGER 5/29/2013 2:12:56 PM 6000 (0x1770)
SetFileAttributesW failed for D:\RemoteInstall\SMSTempBootFiles\CMS00004\Windows\Boot\Fonts\segmono_boot.ttf SMS_DISTRIBUTION_MANAGER 5/29/2013 2:12:56 PM 6000 (0x1770)
RemoveFile failed; 0x80070005 SMS_DISTRIBUTION_MANAGER 5/29/2013 2:12:56 PM 6000 (0x1770)
SetFileAttributesW failed for D:\RemoteInstall\SMSTempBootFiles\CMS00004\Windows\Boot\Fonts\segoen_slboot.ttf SMS_DISTRIBUTION_MANAGER 5/29/2013 2:12:56 PM 6000 (0x1770)
RemoveFile failed; 0x80070005 SMS_DISTRIBUTION_MANAGER 5/29/2013 2:12:56 PM 6000 (0x1770)
SetFileAttributesW failed for D:\RemoteInstall\SMSTempBootFiles\CMS00004\Windows\Boot\Fonts\segoe_slboot.ttf SMS_DISTRIBUTION_MANAGER 5/29/2013 2:12:56 PM 6000 (0x1770)
RemoveFile failed; 0x80070005 SMS_DISTRIBUTION_MANAGER 5/29/2013 2:12:56 PM 6000 (0x1770)
SetFileAttributesW failed for D:\RemoteInstall\SMSTempBootFiles\CMS00004\Windows\Boot\Fonts\wgl4_boot.ttf SMS_DISTRIBUTION_MANAGER 5/29/2013 2:12:56 PM 6000 (0x1770)
RemoveFile failed; 0x80070005 SMS_DISTRIBUTION_MANAGER 5/29/2013 2:12:56 PM 6000 (0x1770)
RemoveDirectoryW failed (0x80070091) for D:\RemoteInstall\SMSTempBootFiles\CMS00004\Windows\Boot\Fonts SMS_DISTRIBUTION_MANAGER 5/29/2013 2:12:56 PM 6000 (0x1770)
SetFileAttributesW failed for D:\RemoteInstall\SMSTempBootFiles\CMS00004\Windows\Boot\PXE\abortpxe.com SMS_DISTRIBUTION_MANAGER 5/29/2013 2:12:56 PM 6000 (0x1770)
RemoveFile failed; 0x80070005 SMS_DISTRIBUTION_MANAGER 5/29/2013 2:12:56 PM 6000 (0x1770)
SetFileAttributesW failed for D:\RemoteInstall\SMSTempBootFiles\CMS00004\Windows\Boot\PXE\bootmgr.exe SMS_DISTRIBUTION_MANAGER 5/29/2013 2:12:56 PM 6000 (0x1770)
RemoveFile failed; 0x80070005 SMS_DISTRIBUTION_MANAGER 5/29/2013 2:12:56 PM 6000 (0x1770)
SetFileAttributesW failed for D:\RemoteInstall\SMSTempBootFiles\CMS00004\Windows\Boot\PXE\pxeboot.com SMS_DISTRIBUTION_MANAGER 5/29/2013 2:12:56 PM 6000 (0x1770)
RemoveFile failed; 0x80070005 SMS_DISTRIBUTION_MANAGER 5/29/2013 2:12:56 PM 6000 (0x1770)
SetFileAttributesW failed for D:\RemoteInstall\SMSTempBootFiles\CMS00004\Windows\Boot\PXE\pxeboot.n12 SMS_DISTRIBUTION_MANAGER 5/29/2013 2:12:56 PM 6000 (0x1770)
RemoveFile failed; 0x80070005 SMS_DISTRIBUTION_MANAGER 5/29/2013 2:12:56 PM 6000 (0x1770)
SetFileAttributesW failed for D:\RemoteInstall\SMSTempBootFiles\CMS00004\Windows\Boot\PXE\wdsmgfw.efi SMS_DISTRIBUTION_MANAGER 5/29/2013 2:12:56 PM 6000 (0x1770)
RemoveFile failed; 0x80070005 SMS_DISTRIBUTION_MANAGER 5/29/2013 2:12:57 PM 6000 (0x1770)
SetFileAttributesW failed for D:\RemoteInstall\SMSTempBootFiles\CMS00004\Windows\Boot\PXE\wdsnbp.com SMS_DISTRIBUTION_MANAGER 5/29/2013 2:12:57 PM 6000 (0x1770)
RemoveFile failed; 0x80070005 SMS_DISTRIBUTION_MANAGER 5/29/2013 2:12:57 PM 6000 (0x1770)
RemoveDirectoryW failed (0x80070091) for D:\RemoteInstall\SMSTempBootFiles\CMS00004\Windows\Boot\PXE SMS_DISTRIBUTION_MANAGER 5/29/2013 2:12:57 PM 6000 (0x1770)
RemoveDirectoryW failed (0x80070091) for D:\RemoteInstall\SMSTempBootFiles\CMS00004\Windows\Boot SMS_DISTRIBUTION_MANAGER 5/29/2013 2:12:57 PM 6000 (0x1770)
RemoveDirectoryW failed (0x80070091) for D:\RemoteInstall\SMSTempBootFiles\CMS00004\Windows SMS_DISTRIBUTION_MANAGER 5/29/2013 2:12:57 PM 6000 (0x1770)
RemoveDirectoryW failed (0x80070091) for D:\RemoteInstall\SMSTempBootFiles\CMS00004 SMS_DISTRIBUTION_MANAGER 5/29/2013 2:12:57 PM 6000 (0x1770)
SetFileAttributesW failed for D:\RemoteInstall\SMSTempBootFiles\CMS00005\Windows\Boot\EFI\bootmgfw.efi SMS_DISTRIBUTION_MANAGER 5/29/2013 2:12:57 PM 6000 (0x1770)
RemoveFile failed; 0x80070005 SMS_DISTRIBUTION_MANAGER 5/29/2013 2:12:57 PM 6000 (0x1770)
RemoveDirectoryW failed (0x80070091) for D:\RemoteInstall\SMSTempBootFiles\CMS00005\Windows\Boot\EFI SMS_DISTRIBUTION_MANAGER 5/29/2013 2:12:57 PM 6000 (0x1770)
SetFileAttributesW failed for D:\RemoteInstall\SMSTempBootFiles\CMS00005\Windows\Boot\Fonts\segmono_boot.ttf SMS_DISTRIBUTION_MANAGER 5/29/2013 2:12:57 PM 6000 (0x1770)
RemoveFile failed; 0x80070005 SMS_DISTRIBUTION_MANAGER 5/29/2013 2:12:57 PM 6000 (0x1770)
SetFileAttributesW failed for D:\RemoteInstall\SMSTempBootFiles\CMS00005\Windows\Boot\Fonts\segoen_slboot.ttf SMS_DISTRIBUTION_MANAGER 5/29/2013 2:12:57 PM 6000 (0x1770)
RemoveFile failed; 0x80070005 SMS_DISTRIBUTION_MANAGER 5/29/2013 2:12:57 PM 6000 (0x1770)
SetFileAttributesW failed for D:\RemoteInstall\SMSTempBootFiles\CMS00005\Windows\Boot\Fonts\segoe_slboot.ttf SMS_DISTRIBUTION_MANAGER 5/29/2013 2:12:57 PM 6000 (0x1770)
RemoveFile failed; 0x80070005 SMS_DISTRIBUTION_MANAGER 5/29/2013 2:12:57 PM 6000 (0x1770)
SetFileAttributesW failed for D:\RemoteInstall\SMSTempBootFiles\CMS00005\Windows\Boot\Fonts\wgl4_boot.ttf SMS_DISTRIBUTION_MANAGER 5/29/2013 2:12:57 PM 6000 (0x1770)
RemoveFile failed; 0x80070005 SMS_DISTRIBUTION_MANAGER 5/29/2013 2:12:57 PM 6000 (0x1770)
RemoveDirectoryW failed (0x80070091) for D:\RemoteInstall\SMSTempBootFiles\CMS00005\Windows\Boot\Fonts SMS_DISTRIBUTION_MANAGER 5/29/2013 2:12:57 PM 6000 (0x1770)
SetFileAttributesW failed for D:\RemoteInstall\SMSTempBootFiles\CMS00005\Windows\Boot\PXE\abortpxe.com SMS_DISTRIBUTION_MANAGER 5/29/2013 2:12:57 PM 6000 (0x1770)
RemoveFile failed; 0x80070005 SMS_DISTRIBUTION_MANAGER 5/29/2013 2:12:57 PM 6000 (0x1770)
SetFileAttributesW failed for D:\RemoteInstall\SMSTempBootFiles\CMS00005\Windows\Boot\PXE\bootmgr.exe SMS_DISTRIBUTION_MANAGER 5/29/2013 2:12:57 PM 6000 (0x1770)
RemoveFile failed; 0x80070005 SMS_DISTRIBUTION_MANAGER 5/29/2013 2:12:57 PM 6000 (0x1770)
SetFileAttributesW failed for D:\RemoteInstall\SMSTempBootFiles\CMS00005\Windows\Boot\PXE\pxeboot.com SMS_DISTRIBUTION_MANAGER 5/29/2013 2:12:57 PM 6000 (0x1770)
RemoveFile failed; 0x80070005 SMS_DISTRIBUTION_MANAGER 5/29/2013 2:12:57 PM 6000 (0x1770)
SetFileAttributesW failed for D:\RemoteInstall\SMSTempBootFiles\CMS00005\Windows\Boot\PXE\pxeboot.n12 SMS_DISTRIBUTION_MANAGER 5/29/2013 2:12:57 PM 6000 (0x1770)
RemoveFile failed; 0x80070005 SMS_DISTRIBUTION_MANAGER 5/29/2013 2:12:57 PM 6000 (0x1770)
SetFileAttributesW failed for D:\RemoteInstall\SMSTempBootFiles\CMS00005\Windows\Boot\PXE\wdsmgfw.efi SMS_DISTRIBUTION_MANAGER 5/29/2013 2:12:57 PM 6000 (0x1770)
RemoveFile failed; 0x80070005 SMS_DISTRIBUTION_MANAGER 5/29/2013 2:12:57 PM 6000 (0x1770)
SetFileAttributesW failed for D:\RemoteInstall\
Here are some jpg's.

Share this post


Link to post
Share on other sites

Looks like I was confusiong two different problems as one. I had to add the windows 7 install.wim to the operating system images I was then able to select it in the task sequence. Im still not sure about the errors in my log file though...

Share this post


Link to post
Share on other sites

Hi, I'm trying to creat the task sequence for capturing the image and that, (step 6). However when I go to add the Operating system image I get nothing to choose from. So in the Select an Operating System Image step I just get There are no items to show in this view. Any ideas what could be causing this?

Share this post


Link to post
Share on other sites

that's because this guide was created before SP1 was released, SP1 changed the way that build and capture works, if you want to see the new process look at the guides below

 

Share this post


Link to post
Share on other sites

hi all

Ran into this, only reason I found out was because I couldn't press F8 in my deploy task,. I have tried searching the error string, but have not found anything useful ... Has anyone encountered the same error?

Error setting property (TransformAnalysisDate) 0x80041002!

Error setting property (TransformReadiness) 0x80041002!

I know this is over a year old but I'm getting this exact same error during the creation of my MDT Task Sequence. What does this even mean?

Share this post


Link to post
Share on other sites

I appreciate your recommendations on using sccm 2012 sp1.

the question i have is: we have been using Acronis to capture our master image for our school system. It has all the drivers onboard for all of our machine models

plus all the software we use in our system.

 

what i am trying to do is to use either a capture media or a capture task sequence to capture our master image after we run sysprep and shut machine down.

Our sysprep has a good unattend.xml file which lets us name machine at restart and auto joins our domain with local admin active with p/w

 

So far I have been able to do this sucessfully with imageX on a bootable cd by capturing volume d: to either external hdd or to a network share.

 

How can I do this with sccm2012 so I don't have to use the command prompt to do the imageX.

All I want to do is capture the OS volume after I run sysprep.

 

Thanks for all your great suggestions and instructions.

 

dac

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...

×
×
  • Create New...