matt_nz

I'm in the process of setting up SCCM 2012 with MDT 2012 intergration in our corporation and everyting is going pretty smoothly - except for my XP deployments to our old HP 6910p laptops Here's a few things I've tried: Built a new XP image in a Hyper-V machine, created a task sequence and gone to deploy it. On the first boot of XP it bluescreens (and reboots instalntly) but I'm fairly certain it's due to storage driver issues however either turning on native SATA mode or AHCI has no effect of the bluescreens. Figured this was a HAL issue as a Hyper-V VM and 6910p use different types. So, next step was to install XP onto a 6910p, make my configuration changes without installing any drivers (outside of XP's built in stuff) and then capture. XP now boots without bluescreening on the first boot but gets stuck at the Windows Setup screen with a "Please wait" dialogue. It never moves past this point. As a test, I disabled the steps in the task sequence that install my imported 6910p drivers but this made no difference. As a final test, I copied the working XP image WIM from our older MDT 2010 enviroment which I know works fine on a 6910p but the same issue as in my second attempt occurs, again with either the driver step enabled or disabled. So clearly its something that SCCM is doing which is different to MDT 2010 that is causing this to fail. I'm not really sure where to go from here...no matter what I do I can't get a successful XP deployment. It makes me appreciate the setup process of Windows 7 and 8...

When it comes to using it in production I don't think we'll be able to avoid SSL as we'll be wanting to use SCCM to provision Intel AMT machines as well.

Alright, well, it seems I was just rushing things a bit. I left it overnight, came back in the morning and things were semi-working! Before I went to bed, PXE booting wasn't really doing anything on the client, just that DHCP line with the spinning cursor. When I tried again in the morning it was now contacting the WDS server but halting before continuing on. Looking in the logs I now had this: WARNING: _SMSTSCertStoreName Not Set. This might cause client failures in native mode. SMSPXE 19/08/2012 12:46:10 p.m. 1740 (0x06CC) WARNING: _SMSTSCertSelection Not Set. This might cause client failures in native mode. SMSPXE 19/08/2012 12:46:10 p.m. 1740 (0x06CC) Which indicated it was still a certificate error. In the SCCM console, I went to Administration, Security and then Certificates. In there I had a bunch of blocked certficates and the issued to fields were showing as GUIDs rather than actual FQDNs. To resolve the problem, I opened the properties of each Certificate, noticed that they were showing as not installed so installed them manually to the Local Computer's (the Primary server) trusted store. Once that was done, I unblocked each certificate and then attempted PXE again - and now it's working perfectly! So the moral of the story I've learn is, if something appears to not be working with SCCM, give it a few hours and see if it clears itself up...

Hi there! Over the last few weeks I've been playing around with SCCM 2012 to get the hang of it and for the most part, with the help of many of the guides I've found on here I've got it humming along quite nicely. Now I'm starting to play with some of the individual parts of SCCM and I've run into a problem getting PXE booting to work and I believe it has something to do with Certs. I'm running in HTTPS with PKIs but I think I'm missing something when it comes to PXE as I'm getting the following messages spammed in my SMSPXE.log file whenever a machine tries to PXE boot: PXE::CBootImageManager::FindMatchingArchitectureBootImage SMSPXE 19/08/2012 2:53:41 a.m. 5596 (0x15DC) Set enterpirse certificate in transport SMSPXE 19/08/2012 2:53:41 a.m. 5596 (0x15DC) Set media certificate in transport SMSPXE 19/08/2012 2:53:41 a.m. 5596 (0x15DC) Set authenticator in transport SMSPXE 19/08/2012 2:53:41 a.m. 5596 (0x15DC) In SSL, but with no client cert SMSPXE 19/08/2012 2:53:41 a.m. 5596 (0x15DC) Set authenticator in transport SMSPXE 19/08/2012 2:53:41 a.m. 5596 (0x15DC) In SSL, but with no client cert SMSPXE 19/08/2012 2:53:41 a.m. 5596 (0x15DC) Client boot action reply: <ClientIDReply><Identification Unknown="0" ItemKey="16777220" ServerName="" ServerRemoteName=""><Machine><ClientID/><NetbiosName/></Machine></Identification><PXEBootAction LastPXEAdvertisementID="" LastPXEAdvertisementTime="" OfferID="" OfferIDTime="" PkgID="" PackageVersion="" PackagePath="" BootImageID="" Mandatory=""/></ClientIDReply> SMSPXE 19/08/2012 2:53:41 a.m. 5596 (0x15DC) Client Identity: cf9295de-a9b7-44dc-b29a-0500ab51db6b SMSPXE 19/08/2012 2:53:41 a.m. 5596 (0x15DC) Set enterpirse certificate in transport SMSPXE 19/08/2012 2:53:41 a.m. 5596 (0x15DC) Set media certificate in transport SMSPXE 19/08/2012 2:53:41 a.m. 5596 (0x15DC) Set authenticator in transport SMSPXE 19/08/2012 2:53:41 a.m. 5596 (0x15DC) In SSL, but with no client cert SMSPXE 19/08/2012 2:53:41 a.m. 5596 (0x15DC) Set authenticator in transport SMSPXE 19/08/2012 2:53:41 a.m. 5596 (0x15DC) In SSL, but with no client cert SMSPXE 19/08/2012 2:53:41 a.m. 5596 (0x15DC) I've followed the Step-By-Step guide found here, http://technet.microsoft.com/en-us/library/gg682023.aspx#BKMK_webserver2008_cm2012 under "Deploying the Client Certificate for Distribution Points" and I've imported the PFX certificate into the settings of "Distribution Point" from a location that everyone has read access to.