Jump to content


anyweb

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

Recommended Posts

Finally managed to crack it. Posting here for others with the same issue. Basically, further down in your guide, you've got:

 

if you get any errors about packages not being found then enable the following setting in Data Access for all packages in your task sequence including the boot image:- copy the contents in this package to a package share on distribution points

 

post-1-0-94235500-1320659351.png

 

Note: once you have enabled the setting above your Deployment distribution settings gets a new drop down menu choice, access content directly from a distribution point when needed by the running task sequence

 

post-1-0-75319600-1320674392.png

 

and then try again.. our client is being built

 

I did this and hey presto, it worked, woo hoo!!

You may want to move this bit further up in your guide, as people like me who experience these errors, will not read further on and see the above until they've got the issue sorted.

 

Thanks

 

Alright, so I'm having the same issue that walsallf was having, but when I try to do this fix, SCCM will not allow me to choose "Access content directly from a distribution point when needed by the running task sequence". The option is there, but when I choose it and apply the change, it just reverts back to "Download content locally when needed by running task sequence". I was hoping that this would fix the \\boot\bcd issue I am having, but since I can't seem to change the option, I can't try it out. Anyone have any suggestions?

 

Edit: We solved this by removing the PXE service point option in Distribution point settings and then re-adding it. We had done this before, and it hadn't worked, but it worked this time. Building/capturing as we speak...

Share this post


Link to post
Share on other sites


Thanks for setting up the guides. They have been a big help. I'm having an issue trying to multicast an OS install with a deploy and capture task sequence. It keeps failing at the multicast. I have reset WDS and reset the distribute via win pe on the distribution point and the image but I still get a 0x8004005 error.

 

post-16184-0-77865000-1337801072_thumb.png

 

smsts1.log

Share this post


Link to post
Share on other sites

Hi garnik

I'have your identical problem.

Please anything can help us...

 

thanks

 

Hello! Click here

sorry, topic was created in Russian forum

Google Translator you some help

Share this post


Link to post
Share on other sites

The execution of the group (Build the Reference Machine) has failed and the execution has been aborted. An action failed.

Operation aborted (Error: 80004004; Source: Windows)

 

 

this is my new error.......

 

can you help me?

Share this post


Link to post
Share on other sites

THanks for help but using google traslator i don't understand nothing

can you explain me what do i do?

I hate this software.....

 

Ok, I will try help you

1. Go to Configuration Manager Console

2. Administration - Hierarchy Configuration - Boundary Groups and Create Boundary Group

3. Enter Boundary Group name and add all right boundary

4. Click Apply and OK

5. Must work :)

 

p.s. sorry my bad english, good luck!

Share this post


Link to post
Share on other sites

Finally managed to crack it. Posting here for others with the same issue. Basically, further down in your guide, you've got:

 

if you get any errors about packages not being found then enable the following setting in Data Access for all packages in your task sequence including the boot image:- copy the contents in this package to a package share on distribution points

 

post-1-0-94235500-1320659351.png

 

Note: once you have enabled the setting above your Deployment distribution settings gets a new drop down menu choice, access content directly from a distribution point when needed by the running task sequence

 

post-1-0-75319600-1320674392.png

 

and then try again.. our client is being built

 

I did this and hey presto, it worked, woo hoo!!

You may want to move this bit further up in your guide, as people like me who experience these errors, will not read further on and see the above until they've got the issue sorted.

 

Thanks

 

Did this solve the PXE boot problem for you? And you only had to tick this on your boot image?

Share this post


Link to post
Share on other sites

Hello!

 

First off, thanks for the guide. It's much appreciated.

I'm running SCCM 2012 the released version, but figured that this guide might apply anyway and so far it's working great.

 

I've got some issues with the PXE booting and it's bugging me out.

I've got my AD computers in the All Systems collection and i've made a seperate "test" collection that everything is deployed and hooked up to.

 

The issue now is that when i Add an existing computer from the All systems collection, to my 'IT test' collection i cannot boot with PXE. Although if i "Import computer information" and take the exact same machine, but enter the mac address etc. and tells it to join the 'IT test' collection, then i can PXE boot every time, even with different machines.

 

I can see the difference for the machines down in the informations tab when i've targeted it. In the 'Active Directory Site Name' field it says "Default First Site Name" for the ones from All systems and "Manual Machine Entry" for the ones i imported.

 

Any help out there?

 

Thanks!

Share this post


Link to post
Share on other sites

HI administrator,

 

thank you so much for your guides been a great help!! i'am just having issues with PXE please see attachment, just not sure what is causing this if you could point me in the right direction will be a great help.

 

thank you so much

 

Artik.post-11352-0-96795400-1340844481_thumb.jpg

Share this post


Link to post
Share on other sites

I am facing an error 80040102 during the task squence .

in smstslog it says content location for ses00001.8 failed than failed to resolve packageID=null than it also says failed to resolve selected task sequence dependencies. Can any 1 assist me with this please.

I updated my DP and all the package id exist there

than recreated all the packages but still the same error

Share this post


Link to post
Share on other sites

I am facing an error code 80040102 after choosing my task sequence.

It satys in smsts.log: The content location for ses00001.8 failed than failed to resolve packageID=null than it also says failed to resolve selected task sequence dependencies. Can any 1 assist me with this please.

I updated my DP and all the package id exist there

than recreated all the packages but still the same error

Share this post


Link to post
Share on other sites

I have an interesting issue. After I import the computer to do the Build and Capture, it does not show up in Build and Capture device group. It does show up under All System. I try to add it to the Build and Capture but never shows up. I have a laptop I also want to test with and it does not show up there either after trying to add it.. I figured I allow the system to run overnight to see if it changes but doesn't. I created three device groups to separate out Win7 machines, 2008 r2 servers and 2008 servers using a query. They took an overnight something to occur before they showed up in the device group even after countless Update Memberships and Refreshes.

Any ideas why this is happening?

Share this post


Link to post
Share on other sites

Hi Need help please. I got almost everything working and was able to capture but when I try to add an application on the task sequence, It always fails. It give me (0x80004005) error. Logs shows " Failed to run the action: install application. When I remove the install applications step, task sequence successfully finishes and captures the image. I need to install applications and capture. All apps are showing in the DP content as ok. Help please. thanks a bunch.

Share this post


Link to post
Share on other sites

I can get to the PXE image options but it fails to install because it says the following:

 

This task sequence cannot be run because the program files for CLA00008 cannot be lcoated on a distribution point. For more information, contact your sys admin or helpdesk operator.

 

Not sure why I am getting this error sicne I did distribute to the DP. Any suggestions?

Share this post


Link to post
Share on other sites

I have a couple questions. You say to start the WDS service in troubleshooting but I can't do so. I am running SCCM 2012 CTP2 and Server 2012 RC. I have confirmed that WDS works and can download boot images so PXE can work stand alone with WDS, naturally it hijacks the image so the task sequence never kicks off. Am I missing something to get SCCM to work? DO I configure WDS from the yellow bang or ignore it? If so AD DS or stand alone? I feel like I am close thanks to your write-up. I am missing something no doubt. PXE never connects to DHCP in my current state which is removing the Role and readding it via the PXE distribution Point. I am using a legacy adapter and setup the bios to boot into PXE automatically via the legacy adapter in the boot order. Is that part of the issues? Seems OK with WDS alone.

Share this post


Link to post
Share on other sites

I have been loosely following your guide and my boot images "Image ID" is referenced CAS0000x and CAS000x (where x is the incremental number) where yours was referencing P01000x. Is this OK?

 

When I PXE boot I get "failed to run task sequence" because the boot image could not be found on the DP. I have made all the recommended settings per your guide as shown in the images. I did notice that "Update Distribution Points" was grayed out for the boot images as shown in the first image. I realized I had to do that from the CAS (difference from your pictures). I went ahead and updated the boot images from the CAS successfully but still failed to run task sequence because the boot image was not found on the DP. I actually added all four packages (two boot images, client and OS files) from the build and capture to the DP on P01 and they are in D:\SMSPKGD$. I somehow think this is related to the fact that your boot images are on P01 and mine are on the CAS. Either I did something wrong or the screen captures in your post are wrong.

 

post-4029-0-07161700-1342552171_thumb.png

post-4029-0-10924200-1342552172_thumb.png

post-4029-0-22261800-1342552173_thumb.png

post-4029-0-77312000-1342552773_thumb.png

post-4029-0-69857500-1342552775_thumb.jpg

post-4029-0-22524900-1342553284_thumb.png

 

Thanks,

 

Mike

Share this post


Link to post
Share on other sites

I found the issue. I had given a few test machines static ip addresses to initially test installing the client. I added those IP addresses to a boundary and assigned the boundry to a boundary group. I have 2007 running along side so I have to be careful. I moved on to OSD and when I PXE booted the machine obviously got a new DHCP address (not the one I had assigned in the OS) which made it fall outside the boundary group. To resolve the issue I created a reservation in DHCP for the machines and added the addresses to a new boundary and added the boundary to a boundary group. The next time I PXE booted the task sequence worked like a charm.

 

The static IPs were a bad idea...use reservations while testing ConfigMgr 2012 along side 2007!

 

Mike

Share this post


Link to post
Share on other sites

I would still like to know why some people have to choose "copy the content in this package..." and some do not. What is the reasoning?

 

Thanks,

 

Mike

Share this post


Link to post
Share on other sites

So I finally got the PXE to boot and install the image with updates. However it failed to Capture the image.

 

I created a VM PC for this which the install for the OS and updates took 2 days for some reason, think its my VM because when it loads to windows it takes it sweet time to respond to my commands.

 

However now I am wondering how do I find out why or how the capture process failed?

 

How can I get a capture of this image instead of doing the whole build and capture process over again?

 

FYI: This is my first time using SCCM and I greatly appreciate this website because it has helped me greatly from a NOOB perspective. Thanks!!

Share this post


Link to post
Share on other sites

 

 

However now I am wondering how do I find out why or how the capture process failed?

 

 

the smsts.log file will reveal why it failed to capture your image, look in c:\windows\ccm\logs\

 

you can post it here if you wish

Share this post


Link to post
Share on other sites

Just so anyone getting the \boot\bcd error knows, this error can happen if you're working with real physical devices which at some point in their lifespan were Ghosted (or imaged using some similar imaging method) and as a result have the same GUID as other devices in the SCCM All Systems collection.

A way around the issue is to power off a machine(s) having the problem(i.e. the machines with identical GUIDs), (make note of its GUID & MAC address before you do), delete the machine(s) from SCCM's All Systems collection, then manually re-add each device (which is why I suggest knowing its MAC address).

And specifically if you're getting this error following anyweb's tutorial here on Build and Capture, you'll want to assign the device back to the build and capture collection once you done the aforementioned delete/manual re-add.

Credit goes to http://adventuresinosd.blogspot.com/2011_03_01_archive.html (scroll down on that page)

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...