Jump to content


anyweb

using System Center 2012 Configuration Manager - Part 7. Build and Capture Windows 7 X64 SP1

Recommended Posts

the computers that you are pxe booting need to be on the same VLAN as the Configuration Manager server hosting the PXE dp

Share this post


Link to post
Share on other sites

Hello,

 

I am having an issue getting a device to connect to the boot image I am running SP1.

 

Bellow is from my SMSPXE.log

 

Machine is running Windows Longhorn. (NTVersion=0X602, ServicePack=0) SMSPXE 5/23/2013 10:51:37 AM 5176 (0x1438)
Cannot read the registry value of MACIgnoreListFile (00000000) SMSPXE 5/23/2013 10:51:37 AM 5176 (0x1438)
MAC Ignore List Filename in registry is empty SMSPXE 5/23/2013 10:51:37 AM 5176 (0x1438)
Begin validation of Certificate [Thumbprint D9A8EF451F57975D0B27ADAD55ECF75132EEB866] issued to '{63563751-1AB4-47AD-8540-7119491D8F03}' SMSPXE 5/23/2013 10:51:37 AM 5176 (0x1438)
Completed validation of Certificate [Thumbprint D9A8EF451F57975D0B27ADAD55ECF75132EEB866] issued to '{63563751-1AB4-47AD-8540-7119491D8F03}' SMSPXE 5/23/2013 10:51:37 AM 5176 (0x1438)
Initializing PXEPerfObject. SMSPXE 5/23/2013 10:51:37 AM 5176 (0x1438)
Could not load logging configuration for component ccmperf. Using default values. SMSPXE 5/23/2013 10:51:37 AM 5176 (0x1438)
HTTP is selected for Client. The current state is 0. SMSPXE 5/23/2013 10:51:37 AM 5176 (0x1438)
Client lookup reply: <ClientIDReply><Identification Unknown="0" ItemKey="0" ServerName="" ServerRemoteName=""><Machine><ClientID/><NetbiosName/></Machine></Identification></ClientIDReply>
SMSPXE 5/23/2013 10:51:37 AM 5176 (0x1438)
PXE::CBootImageInfo::CBootImageInfo: key= SMSPXE 5/23/2013 10:51:37 AM 5176 (0x1438)
PXE::CBootImageInfo::CBootImageInfo: key= SMSPXE 5/23/2013 10:51:37 AM 5176 (0x1438)
Adding WB000002.3 SMSPXE 5/23/2013 10:51:37 AM 5176 (0x1438)
Adding WB000005.3 SMSPXE 5/23/2013 10:51:39 AM 5176 (0x1438)
Found new image WB000002 SMSPXE 5/23/2013 10:51:43 AM 5176 (0x1438)
Opening image file E:\Images\SMSImages\WB000002\boot.WB000002.wim SMSPXE 5/23/2013 10:51:43 AM 5176 (0x1438)
Found Image file: E:\Images\SMSImages\WB000002\boot.WB000002.wim
PackageID: WB000002
ProductName: Microsoft® Windows® Operating System
Architecture: 0
Description: Microsoft Windows PE (x86)
Version:
Creator:
SystemDir: WINDOWS
SMSPXE 5/23/2013 10:51:43 AM 5176 (0x1438)
Closing image file E:\Images\SMSImages\WB000002\boot.WB000002.wim SMSPXE 5/23/2013 10:51:43 AM 5176 (0x1438)
Found new image WB000005 SMSPXE 5/23/2013 10:51:44 AM 5176 (0x1438)
Opening image file E:\Images\SMSImages\WB000005\boot.WB000005.wim SMSPXE 5/23/2013 10:51:44 AM 5176 (0x1438)
Found Image file: E:\Images\SMSImages\WB000005\boot.WB000005.wim
PackageID: WB000005
ProductName: Microsoft® Windows® Operating System
Architecture: 9
Description: Microsoft Windows PE (x64)
Version:
Creator:
SystemDir: WINDOWS
SMSPXE 5/23/2013 10:51:44 AM 5176 (0x1438)
Closing image file E:\Images\SMSImages\WB000005\boot.WB000005.wim SMSPXE 5/23/2013 10:51:44 AM 5176 (0x1438)
Begin validation of Certificate [Thumbprint D9A8EF451F57975D0B27ADAD55ECF75132EEB866] issued to '{63563751-1AB4-47AD-8540-7119491D8F03}' SMSPXE 5/23/2013 10:51:45 AM 5176 (0x1438)
Completed validation of Certificate [Thumbprint D9A8EF451F57975D0B27ADAD55ECF75132EEB866] issued to '{63563751-1AB4-47AD-8540-7119491D8F03}' SMSPXE 5/23/2013 10:51:45 AM 5176 (0x1438)
PXE Provider finished loading. SMSPXE 5/23/2013 10:51:45 AM 5176 (0x1438)
Cannot read the registry value of MACIgnoreListFile (800703e5) SMSPXE 5/23/2013 10:51:49 AM 5448 (0x1548)
MAC Ignore List Filename in registry is empty SMSPXE 5/23/2013 10:51:49 AM 5448 (0x1548)
Cannot read the registry value of MACIgnoreListFile (00000000) SMSPXE 5/23/2013 10:52:06 AM 804 (0x0324)
MAC Ignore List Filename in registry is empty SMSPXE 5/23/2013 10:52:06 AM 804 (0x0324)

 

 

Thanks!

Share this post


Link to post
Share on other sites

so i've followed this guide exactly, and i can't get my vm to pxe boot.

I'm using the rtm of sccm 2012 (not sp1)

i'm using a legacy card (although not really applicable for vmware workstation) i've got dhcp and network boot enabled on a smoothwall to keep this lab seperate from my production.

looking through the settings for WDS it says that pxe is set to ignore all clients is this correct... i've enabled it to see what happens and it doesn't do anything, is there another setting somewhere that needs to be switched on for network boot to work? should WDS be enabled or does sccm use its own deployment system ?

been scratching my head all week over this hope someone can help !

 

thanks

Share this post


Link to post
Share on other sites

locate the smspxe.log on your server hosting the pxe role on the dp, and search for the MAC address of the computer that you are pxe booting, does it reveal anything for yo

Share this post


Link to post
Share on other sites

Hi,

 

These guides are a huge lifesaver so thanks for this, although I have a question.

 

I was wondering whether there's any information on deploying a build and capture TS that also installs applications and drivers? I tried to do this by adding apps and drivers in the TS but although the base image of Windows 7 installed fine, none of the drivers or apps I applied to the TS were installed, and I know these definitely work as I've test deployed them. Do you need to deploy the apps and drivers individually to the collection containing your test B+C machine too?

Perhaps someone could point me in the direction of the best log to view regarding B+C please?

 

Thanks a million

Share this post


Link to post
Share on other sites

you shouldn't be installing drivers in a build and capture task sequence as you should be using virtual hardware (driver agnostic) for the build and capture process,

save the driver installation for the Deploy task sequence, and that is covered here many times. The log to look at when troubleshooting anything OSD related is smsts.log or smsts*.log

 

cheers

niall

Share this post


Link to post
Share on other sites

I have set this up step by step and everything is working now... except Capturing the image.

 

It boots back up and waits at the login screen but no capture takes place. I have seen you keep re-posting about the smsts.log and I have troubleshot all other issues from there, but now I don't see the _SMSTaskSequence directory anymore.

 

Here is the only thing I think I have different, from this image below do I need to enter:

SMSMP=SiteCode.ServerName.FQDN

or

SMSMP=ServerName.FQDN

 

post-8369-0-68478200-1375128450_thumb.jpg

 

 

Thank you in advance.

Share this post


Link to post
Share on other sites

Ok, scratch my last. I would created a new client package and looks like everything works. Was able to capture my image as well.

 

Still would like to know more about the SMSMP if you get a chance, I will still try to google and find more as well.

 

Also I am still getting these errors in SMSTS.log - 401 - Authentication failure on request with anonymous access, retrying with context credentials. ApplyOperatingSystem

-----------------------------------------------------------------------------------------------------
From the SMSTS.log
Downloaded file from http://Server.FQDN.local:443/NOCERT_SMS_DP_SMSPKG$/MVH0004D/sccm?/autorun.inf to C:\_SMSTaskSequence\Packages\MVH0004D\autorun.inf  ApplyOperatingSystem 7/30/2013 7:10:23 AM 1504 (0x05E0)
401 - Authentication failure on request with anonymous access, retrying with context credentials. ApplyOperatingSystem 7/30/2013 7:10:23 AM 1504 (0x05E0)
401 - Authentication failure on request with context credentials, retrying with supplied credentials. ApplyOperatingSystem 7/30/2013 7:10:23 AM 1504 (0x05E0)
-----------------------------------------------------------------------------------------------------
MVH0004D is my Apply Operating System Task

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

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.