Jump to content


anyweb

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

Recommended Posts

Hello Everyone,

 

I've enabled the PXE on the DP and on my VMs the PXE booting works pefectly,

But on physical computers i'm getting to following error:

 

30blhjc.jpg

What can i do to fix it?

 

This is what i get from the smspxe.log when trying to load the physical machine from the PXE:

 

Set media certificate in transport SMSPXE 3/15/2012 9:31:45 AM 3220 (0x0C94)

Set authenticator in transport SMSPXE 3/15/2012 9:31:45 AM 3220 (0x0C94)

Set authenticator in transport SMSPXE 3/15/2012 9:31:45 AM 3220 (0x0C94)

Client lookup reply: <ClientIDReply><Identification Unknown="0" ItemKey="0" ServerName="" ServerRemoteName=""><Machine><ClientID/><NetbiosName/></Machine></Identification></ClientIDReply>

SMSPXE 3/15/2012 9:31:45 AM 3220 (0x0C94)

PXE::CBootImageManager::FindMatchingArchitectureBootImage SMSPXE 3/15/2012 9:31:45 AM 3220 (0x0C94)

Getting boot action for unknown machine: item key: 2046820352 SMSPXE 3/15/2012 9:31:45 AM 3220 (0x0C94)

Set media certificate in transport SMSPXE 3/15/2012 9:31:45 AM 3220 (0x0C94)

Set authenticator in transport SMSPXE 3/15/2012 9:31:45 AM 3220 (0x0C94)

Set authenticator in transport SMSPXE 3/15/2012 9:31:45 AM 3220 (0x0C94)

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

SMSPXE 3/15/2012 9:31:45 AM 3220 (0x0C94)

Client Identity: {FEB30AE8-30CD-4144-A8D8-FC0628C1DDCE} SMSPXE 3/15/2012 9:31:45 AM 3220 (0x0C94)

Set media certificate in transport SMSPXE 3/15/2012 9:31:45 AM 3220 (0x0C94)

Set authenticator in transport SMSPXE 3/15/2012 9:31:45 AM 3220 (0x0C94)

Set authenticator in transport SMSPXE 3/15/2012 9:31:45 AM 3220 (0x0C94)

 

 

My SCCM server is a VM that's running on ESX 4.0 host and he's network card is E1000.

 

BTW, how to i edit my account that i'll recived emails notifcation when someone answer's my questions?

Thanks!

Share this post


Link to post
Share on other sites


Hi All, i've been trying to fix this problem by reading all the comments, unfortunately unsuccesfuld,

my clients appear in the all systems list but not in the Build and Capture windows 7 X64 collection, i only see them in the Membership rules (i tried creating a vm just in case)

 

I'm stuck on the PXE boot, i've read different comments, and tried most of the solutions, without any luck.

 

my clients don't really catch anything, i can just see the DHCP searching after a while i get PXE-E53: No boot filename received.

 

i've also noticed that my WDS in not configured

 

i'be been stuck here for a few days, would really appreciate som help :)

Share this post


Link to post
Share on other sites

Where can i find the smsts.log file? I do not see it with the Configuration Manager log files.

 

I turned on the pxe password, and it will give me the task sequence wizard.

 

But I'm getting this error:

post-13301-0-96668500-1328565574_thumb.png

 

For anyone else having the Failed to Run Task Sequence with 0x80004005 where you are using the NAT Virtual Network in VMware Workstation - make sure in the Virtual Network Editor you configure the DNS server to that of your Active Directory DC / DNS server so it can resolve you internal domain name (i.e. testlab.local) when trying to find your SCCM server distribution point by FQDN (i.e. sccm.testlab.local).

 

This was driving me nuts for ages since I followed the guide correctly. It was only when investigating smsts.log I noticed the DNS issue also like others have mentioned.

post-15282-0-16386400-1332003065_thumb.jpg

  • Like 1

Share this post


Link to post
Share on other sites

Hi All, i've been trying to fix this problem by reading all the comments, unfortunately unsuccesfuld,

my clients appear in the all systems list but not in the Build and Capture windows 7 X64 collection, i only see them in the Membership rules (i tried creating a vm just in case)

 

I'm stuck on the PXE boot, i've read different comments, and tried most of the solutions, without any luck.

 

my clients don't really catch anything, i can just see the DHCP searching after a while i get PXE-E53: No boot filename received.

 

i've also noticed that my WDS in not configured

 

i'be been stuck here for a few days, would really appreciate som help :)

 

I had the PXE-E53 error when using VMware Workstation where the machines were configured to use the NAT network in VMware Virtual Network Editor. Problem for me is that I had turned DHCP off in the NAT network. Turning this back on fixed the problem and clients could PXE boot.

post-15282-0-67122100-1332003033_thumb.jpg

Share this post


Link to post
Share on other sites

 

I had the PXE-E53 error when using VMware Workstation where the machines were configured to use the NAT network in VMware Virtual Network Editor. Problem for me is that I had turned DHCP off in the NAT network. Turning this back on fixed the problem and clients could PXE boot.

 

i'm using Hyper-V and my DHCP is enabled, i'm kinda more concerned about the machine not showing up in the collection or the WDS not being configured, no ideas for those 2?

Share this post


Link to post
Share on other sites

Ok, I built a new VM of SCCM from scratch and followed everything listed here. I cannot get PXE to boot. Still getting the abortpxe.com error. What e;se should I check, I'm pulling my hair here... 2 servers later and PXE still gives me abortpxe.com. HELP! >_<

Share this post


Link to post
Share on other sites

what does the smspxe.log file reveal ? search for the MAC address of the client you are PXE booting

Share this post


Link to post
Share on other sites

what does the smspxe.log file reveal ? search for the MAC address of the client you are PXE booting

 

my smspxe.log files do not even show a MAC address :\ something is up...

post-14853-0-29470400-1332280459_thumb.png

Share this post


Link to post
Share on other sites

Hi. Im having problems with the capture itself. The task sequence runs fine, and deploys windows with updates and everything, but after the restart it doesn't continue the process. Just leaves me with a windows finished installing.

Share this post


Link to post
Share on other sites

 

my smspxe.log files do not even show a MAC address :\ something is up...

 

This is also happening to a VM machine I am trying to PXE boot as well, any help investigating this is appreciated. Thanks!

Share this post


Link to post
Share on other sites

did you guys remember to enable pxe support on the boot image itself ?

Share this post


Link to post
Share on other sites

did you guys remember to enable pxe support on the boot image itself ?

 

Do you mean the "Deploy this boot image from the PXE service point"? If so, then yes, they are checked/enabled.

Share this post


Link to post
Share on other sites

 

Do you mean the "Deploy this boot image from the PXE service point"? If so, then yes, they are checked/enabled.

 

Just to experiment, I made another VM Server and configured just plain WDS, no SCCM install attempt. I updated DHCP options 66 and 67 to use this new WDS server as the PXE and boot image point. Both the VMware machine and Dell Optiplex 755 I deployed to PXE booted fine, prompted for the F12 and booted into Windows7 Setup correctly.

 

So, I don't know what's going wrong with the SCCM server, it's just not cooperating - as I don't even touch the WDS console to modify anything and let SCCM do the configurations when the roles are added.

Share this post


Link to post
Share on other sites

Has anyone ever had the issue where the image capture process fails just at the stage when it connects to the \\***\sources\os\windows7x64 share and complains about the share already being in use? This appears to be the last hurdle in getting this working and I'm unsure why it is failing here, seems a bit strange!

Share this post


Link to post
Share on other sites

It's taken me a few days but finally, it is now capturing the image :)

 

Turns out I had an issue with the server firewall that was blocking any connections so the final stage of capture could not connect to the server share. Now that is resolved the captured image is being stored as I type! Fingers crossed this is one of the last hurdles to this superb bit of software, further kudos for writing these guides, they've been invaluable!

Share this post


Link to post
Share on other sites

Hi,

 

Thank you for the great install guide ;-)

 

I followed all your instructions and almost everything worked fine.

The VM found the SCCM, asked for the PW and started to install after, but i had to choose the time zone manually.

Any idea’s how I could fix that?

Greetings

Share this post


Link to post
Share on other sites

what does the smspxe.log file reveal ? search for the MAC address of the client you are PXE booting

 

3 servers later, still abortpxe.com error. NO MAC address is visible in the SMSPXE.log file. Any help please? This issue is turning my hair gray.

Share this post


Link to post
Share on other sites

thanks for posting your troubleshooting and resolution, keep it up !

Share this post


Link to post
Share on other sites
I seem to be having almost the same issue. I also double checked the steps shown above. The message I'm getting is: PXE-E53: No boot filename received PXE-M0F: Exiting Intel PXE ROM Operating System not found This message definitely seems to point something in CM, maybe I did miss something, but I just can't pin point it.

 

In my case this happens on 2 reasons:

1) u havent put the computer to the correct advertisment collection

2) there are no pxe boot files in the pxe server (several ways to correct this, but i found it is just simpler to copy from another pxe server the files and it works :) kinda silly way to fix but i like it.)

Share this post


Link to post
Share on other sites

Figured out why is wasn't running the Task Sequences: 1) needed to open WDS and make sure PXE was set to respond to all computers (all plus unknown). 2) Boot Images>Update Distribution Points, after I did this, it started working.

 

Also, adding/importing machines manually doesn't work all the time and when it does, takes a minute or two to take effect and get added to the group you're advertising too - that's pretty annoying.

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!

Share this post


Link to post
Share on other sites

diablo: From the last sentence on this guide: "In the next part of this series, we will Deploy our captured WIM and continue learning about this fantastic product "

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