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

[arema]

Yep that was before I reinstalled SCCM when used to type notepad SMSTSLog from the temp directory it was giving me access denied error. How ever after reinstalling SCCM it's failing with same error and when I press F8 nothing happened even though cmd prompt is enaled in the boot image.

[anyweb]

did you re-distribute your boot images to your dp's after enabling the command prompt support?

[arema]

Geat I had a DNS issue fom the cmd pompt it was not resolving the fqdn of the sccm server all good now, thanks for your help.

 

Regards

[techguyben]

I believe I fixed my issue.

 

It was a DNS issues, also I believe I had updated the distribution point with the boot image before they were actually distributed.

 

I now have everything working.

 

This guides are amazing. Great work!

[mca91601]

I'm trying to get this guide working. PXE is not booting, nor have I ever had it booting successfully. I always get the abortpxe.com error.

[Davidsod]

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:

 

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!

[Surya]

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

[nstylin]

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:

 

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.

[nstylin]

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.

[Surya]

 

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?