boyjaew2

I have a pretty basic question, I think. I have a collection that ended up with three antimaleware policies on it. The Default Policy an Admin-type policy and the custom policy (laptops policy) that applied to the clients before I created the admin collection. I probably should have created the collection first, but that's in the past. The way I'm thinking about the priority level of each dictates that the policy i created for the collection is the one actually applying custom settings and then other settings are applied as the policies with the other priorities are "filtered" in. So- admin policy priority 1 - applies custom settings for admin collection Laptop policy priortiy 3 - applies custom settings that aren't accounted for in the admin policy Default policy priority 10,000 - applies everything else that hasn't been accounted for in the other two Is that the correct way to think about that and secondly can I remove the laptops policy and is it even necessary?

Thanks for the feedback. I'll give it a try.

I just set up a new standalone primary site in our environment and I am playing hell getting PXE going. Through the various steps I have taken to validate everything is working I noticed that if I look at the WDS configuration VIA server manager they do no match up with the [proper] settings that I have set on the DP role. For example, I have obviously enabled PXE on the role, but in the WDS console under PXE response tab it is clearly checked "Do not respond to any client computers". I find this a bit odd. I do not run sccm and dhcp on the same server. So, I expected all this to be "set up for me" when I enabled PXE on the DP role. Is this usual behaviour or should I back track on WDS and try again? Thanks.

Thanks for confirming.

Okay, here we go, turns out the freakin' time and date on this particular laptop was WAY off. It had nothing to do with SCCM at all. Once I went into the BIOS and changed the date and time it PXE'd and ran the task TS as expected.So, check you BIOS time I guess.

log: DNS is working and certificates are not expired. PXE boots fine fails after entering password for task sequence - Help please.... LOGGING: Finalize process ID set to 824 TSBootShell 1/1/1980 1:27:12 AM 828 (0x033C) ==============================[ TSBootShell.exe ]============================== TSBootShell 1/1/1980 1:27:12 AM 828 (0x033C) Succeeded loading resource DLL 'X:\sms\bin\x64\1033\TSRES.DLL' TSBootShell 1/1/1980 1:27:12 AM 828 (0x033C) Debug shell is enabled TSBootShell 1/1/1980 1:27:12 AM 828 (0x033C) Waiting for PNP initialization... TSBootShell 1/1/1980 1:27:12 AM 860 (0x035C) Booted from network (PXE) TSBootShell 1/1/1980 1:27:12 AM 860 (0x035C) Found config path X:\sms\data\ TSBootShell 1/1/1980 1:27:12 AM 860 (0x035C) Booting from removable media, not restoring bootloaders on hard drive TSBootShell 1/1/1980 1:27:12 AM 860 (0x035C) Executing command line: wpeinit.exe -winpe TSBootShell 1/1/1980 1:27:12 AM 860 (0x035C) The command completed successfully. TSBootShell 1/1/1980 1:27:33 AM 860 (0x035C) Starting DNS client service. TSBootShell 1/1/1980 1:27:33 AM 860 (0x035C) Executing command line: X:\sms\bin\x64\TsmBootstrap.exe /env:WinPE /configpath:X:\sms\data\ TSBootShell 1/1/1980 1:27:34 AM 860 (0x035C) The command completed successfully. TSBootShell 1/1/1980 1:27:34 AM 860 (0x035C) ==============================[ TSMBootStrap.exe ]============================== TSMBootstrap 1/1/1980 1:27:34 AM 908 (0x038C) Command line: X:\sms\bin\x64\TsmBootstrap.exe /env:WinPE /configpath:X:\sms\data\ TSMBootstrap 1/1/1980 1:27:34 AM 908 (0x038C) Succeeded loading resource DLL 'X:\sms\bin\x64\1033\TSRES.DLL' TSMBootstrap 1/1/1980 1:27:34 AM 908 (0x038C) Succeeded loading resource DLL 'X:\sms\bin\x64\TSRESNLC.DLL' TSMBootstrap 1/1/1980 1:27:34 AM 908 (0x038C) PXE Boot with Root = X:\ TSMBootstrap 1/1/1980 1:27:34 AM 908 (0x038C) Executing from PXE in WinPE TSMBootstrap 1/1/1980 1:27:34 AM 908 (0x038C) Loading TsPxe.dll from X:\sms\bin\x64\TsPxe.dll TSMBootstrap 1/1/1980 1:27:34 AM 908 (0x038C) TsPxe.dll loaded TSPxe 1/1/1980 1:27:34 AM 908 (0x038C) Device has PXE booted TSPxe 1/1/1980 1:27:34 AM 908 (0x038C) Variable Path: \SMSTemp\2012.10.25.12.55.57.0003.{0F6519A1-2BAE-43A8-A600-ACEA47D69C8D}.boot.var TSPxe 1/1/1980 1:27:34 AM 908 (0x038C) Succesfully added firewall rule for Tftp TSPxe 1/1/1980 1:27:34 AM 908 (0x038C) Executing: X:\sms\bin\x64\smstftp.exe -i 10.10.10.51 get \SMSTemp\2012.10.25.12.55.57.0003.{0F6519A1-2BAE-43A8-A600-ACEA47D69C8D}.boot.var X:\sms\data\variables.dat TSPxe 1/1/1980 1:27:34 AM 908 (0x038C) Command line for extension .exe is "%1" %* TSPxe 1/1/1980 1:27:34 AM 908 (0x038C) Set command line: "X:\sms\bin\x64\smstftp.exe" -i 10.10.10.51 get \SMSTemp\2012.10.25.12.55.57.0003.{0F6519A1-2BAE-43A8-A600-ACEA47D69C8D}.boot.var X:\sms\data\variables.dat TSPxe 1/1/1980 1:27:34 AM 908 (0x038C) Executing command line: "X:\sms\bin\x64\smstftp.exe" -i 10.10.10.51 get \SMSTemp\2012.10.25.12.55.57.0003.{0F6519A1-2BAE-43A8-A600-ACEA47D69C8D}.boot.var X:\sms\data\variables.dat TSPxe 1/1/1980 1:27:34 AM 908 (0x038C) Process completed with exit code 0 TSPxe 1/1/1980 1:27:34 AM 908 (0x038C) Succesfully removed firewall rule for Tftp TSPxe 1/1/1980 1:27:34 AM 908 (0x038C) Successfully downloaded pxe variable file. TSPxe 1/1/1980 1:27:34 AM 908 (0x038C) we are booted using PXE TSPxe 1/1/1980 1:27:34 AM 908 (0x038C) we are booted using PXE and we don't use a password or the password is provided by the user TSPxe 1/1/1980 1:27:34 AM 908 (0x038C) Found network adapter "Intel® 82579LM Gigabit Network Connection" with IP Address 10.10.10.152. TSPxe 1/1/1980 1:27:34 AM 908 (0x038C) Run PXE Interactive TSPxe 1/1/1980 1:27:34 AM 908 (0x038C) Running Wizard in Interactive mode TSPxe 1/1/1980 1:27:34 AM 908 (0x038C) Loading Media Variables from "X:\sms\data\variables.dat" TSPxe 1/1/1980 1:27:34 AM 908 (0x038C) CryptDecrypt (hKey, 0, 1, 0, pData, &dwDecryptedLen), HRESULT=80090005 (e:\nts_sccm_release\sms\framework\smscrypt\windes.cpp,150) TSPxe 1/1/1980 1:27:34 AM 908 (0x038C) SMS::Crypto::DES::DecryptBuffer( (BYTE*)pszPassword, (DWORD)(wcslen(pszPassword)*sizeof(WCHAR)), encryptedBuffer.getBuffer(), (DWORD)encryptedBuffer.size(), pbDecryptedBuffer, dwDecryptedBufferSize ), HRESULT=80090005 (e:\nts_sccm_release\sms\framework\tscore\tsremovablemedia.cpp,387) TSPxe 1/1/1980 1:27:34 AM 908 (0x038C) Activating Welcome Page. TSPxe 1/1/1980 1:27:34 AM 908 (0x038C) Loading bitmap TSPxe 1/1/1980 1:27:34 AM 908 (0x038C) WelcomePage::OnWizardNext() TSPxe 1/1/1980 1:29:40 AM 908 (0x038C) Loading Media Variables from "X:\sms\data\variables.dat" TSPxe 1/1/1980 1:29:40 AM 908 (0x038C) CryptDecrypt (hKey, 0, 1, 0, pData, &dwDecryptedLen), HRESULT=80090005 (e:\nts_sccm_release\sms\framework\smscrypt\windes.cpp,150) TSPxe 1/1/1980 1:29:40 AM 908 (0x038C) SMS::Crypto::DES::DecryptBuffer( (BYTE*)pszPassword, (DWORD)(wcslen(pszPassword)*sizeof(WCHAR)), encryptedBuffer.getBuffer(), (DWORD)encryptedBuffer.size(), pbDecryptedBuffer, dwDecryptedBufferSize ), HRESULT=80090005 (e:\nts_sccm_release\sms\framework\tscore\tsremovablemedia.cpp,387) TSPxe 1/1/1980 1:29:40 AM 908 (0x038C) Loading Media Variables from "X:\sms\data\variables.dat" TSPxe 1/1/1980 1:29:40 AM 908 (0x038C) CryptDecrypt (hKey, 0, 1, 0, pData, &dwDecryptedLen), HRESULT=80090005 (e:\nts_sccm_release\sms\framework\smscrypt\windes.cpp,150) TSPxe 1/1/1980 1:29:40 AM 908 (0x038C) SMS::Crypto::DES::DecryptBuffer( (BYTE*)pszPassword, (DWORD)(wcslen(pszPassword)*sizeof(WCHAR)), encryptedBuffer.getBuffer(), (DWORD)encryptedBuffer.size(), pbDecryptedBuffer, dwDecryptedBufferSize ), HRESULT=80090005 (e:\nts_sccm_release\sms\framework\tscore\tsremovablemedia.cpp,387) TSPxe 1/1/1980 1:29:40 AM 908 (0x038C) Verifying media password. TSPxe 1/1/1980 1:29:40 AM 908 (0x038C) Loading Media Variables from "X:\sms\data\variables.dat" TSPxe 1/1/1980 1:29:40 AM 908 (0x038C) Spawned thread 1004 to download policy. TSPxe 1/1/1980 1:29:40 AM 908 (0x038C) Entering TSMediaWizardControl::GetPolicy. TSPxe 1/1/1980 1:29:40 AM 1004 (0x03EC) Environment scope "Global\{51A016B6-F0DE-4752-B97C-54E6F386A912}" successfully created TSPxe 1/1/1980 1:29:40 AM 1004 (0x03EC) Environment scope "Global\{BA3A3900-CA6D-4ac1-8C28-5073AFC22B03}" successfully created TSPxe 1/1/1980 1:29:40 AM 1004 (0x03EC) Setting LogMaxSize to 1000000 TSPxe 1/1/1980 1:29:40 AM 1004 (0x03EC) Setting LogMaxHistory to 1 TSPxe 1/1/1980 1:29:40 AM 1004 (0x03EC) Setting LogLevel to 0 TSPxe 1/1/1980 1:29:40 AM 1004 (0x03EC) Setting LogEnabled to 1 TSPxe 1/1/1980 1:29:40 AM 1004 (0x03EC) Setting LogDebug to 1 TSPxe 1/1/1980 1:29:40 AM 1004 (0x03EC) Loading variables from the Task Sequencing Removable Media. TSPxe 1/1/1980 1:29:41 AM 1004 (0x03EC) Loading Media Variables from "X:\sms\data\variables.dat" TSPxe 1/1/1980 1:29:41 AM 1004 (0x03EC) Setting SMSTSMP TS environment variable TSPxe 1/1/1980 1:29:41 AM 1004 (0x03EC) Setting _SMSMediaGuid TS environment variable TSPxe 1/1/1980 1:29:41 AM 1004 (0x03EC) Setting _SMSTSBootMediaPackageID TS environment variable TSPxe 1/1/1980 1:29:41 AM 1004 (0x03EC) Setting _SMSTSHTTPPort TS environment variable TSPxe 1/1/1980 1:29:41 AM 1004 (0x03EC) Setting _SMSTSHTTPSPort TS environment variable TSPxe 1/1/1980 1:29:41 AM 1004 (0x03EC) Setting _SMSTSIISSSLState TS environment variable TSPxe 1/1/1980 1:29:41 AM 1004 (0x03EC) Setting _SMSTSLaunchMode TS environment variable TSPxe 1/1/1980 1:29:41 AM 1004 (0x03EC) Setting _SMSTSMediaPFX TS environment variable TSPxe 1/1/1980 1:29:41 AM 1004 (0x03EC) Setting _SMSTSPublicRootKey TS environment variable TSPxe 1/1/1980 1:29:41 AM 1004 (0x03EC) Setting _SMSTSSiteCode TS environment variable TSPxe 1/1/1980 1:29:41 AM 1004 (0x03EC) Setting _SMSTSSiteSigningCertificate TS environment variable TSPxe 1/1/1980 1:29:41 AM 1004 (0x03EC) Setting _SMSTSUseFirstCert TS environment variable TSPxe 1/1/1980 1:29:41 AM 1004 (0x03EC) Setting _SMSTSx64UnknownMachineGUID TS environment variable TSPxe 1/1/1980 1:29:41 AM 1004 (0x03EC) Setting _SMSTSx86UnknownMachineGUID TS environment variable TSPxe 1/1/1980 1:29:41 AM 1004 (0x03EC) Root CA Public Certs= TSPxe 1/1/1980 1:29:41 AM 1004 (0x03EC) Missing root CA environment variable from variables file TSPxe 1/1/1980 1:29:41 AM 1004 (0x03EC) Custom hook from X:\\TSConfig.INI is TSPxe 1/1/1980 1:29:41 AM 1004 (0x03EC) No hook is found to be executed before downloading policy TSPxe 1/1/1980 1:29:41 AM 1004 (0x03EC) Authenticator from the environment is empty. TSPxe 1/1/1980 1:29:41 AM 1004 (0x03EC) Need to create Authenticator Info using PFX TSPxe 1/1/1980 1:29:41 AM 1004 (0x03EC) Set media certificate in transport TSPxe 1/1/1980 1:29:41 AM 1004 (0x03EC) Set authenticator in transport TSPxe 1/1/1980 1:29:41 AM 1004 (0x03EC) CLibSMSMessageWinHttpTransport::Send: URL: sccm12.trihydro.com:80 GET /SMS_MP/.sms_aut?MPKEYINFORMATION TSPxe 1/1/1980 1:29:41 AM 1004 (0x03EC) Request was succesful. TSPxe 1/1/1980 1:29:41 AM 1004 (0x03EC) Default CSP is Microsoft Enhanced RSA and AES Cryptographic Provider TSPxe 1/1/1980 1:29:41 AM 1004 (0x03EC) Default CSP Type is 24 TSPxe 1/1/1980 1:29:41 AM 1004 (0x03EC) New settings: TSPxe 1/1/1980 1:29:41 AM 1004 (0x03EC) site=CCM,CCM, MP=http://sccm12.trihydro.com, ports: http=80,https=443 TSPxe 1/1/1980 1:29:41 AM 1004 (0x03EC) certificates are received from MP. TSPxe 1/1/1980 1:29:41 AM 1004 (0x03EC) Getting MP time information TSPxe 1/1/1980 1:29:41 AM 1004 (0x03EC) Set authenticator in transport TSPxe 1/1/1980 1:29:41 AM 1004 (0x03EC) Requesting client identity TSPxe 1/1/1980 1:29:41 AM 1004 (0x03EC) Setting message signatures. TSPxe 1/1/1980 1:29:41 AM 1004 (0x03EC) Setting the authenticator. TSPxe 1/1/1980 1:29:41 AM 1004 (0x03EC) CLibSMSMessageWinHttpTransport::Send: URL: sccm12.trihydro.com:80 CCM_POST /ccm_system/request TSPxe 1/1/1980 1:29:41 AM 1004 (0x03EC) Request was succesful. TSPxe 1/1/1980 1:29:41 AM 1004 (0x03EC) pNext != NULL, HRESULT=80004005 (e:\nts_sccm_release\sms\framework\osdmessaging\libsmsmessaging.cpp,1967) TSPxe 1/1/1980 1:29:41 AM 1004 (0x03EC) reply has no message header marker TSPxe 1/1/1980 1:29:41 AM 1004 (0x03EC) DoRequest (sReply, true), HRESULT=80004005 (e:\nts_sccm_release\sms\framework\osdmessaging\libsmsmessaging.cpp,5709) TSPxe 1/1/1980 1:29:41 AM 1004 (0x03EC) Failed to get client identity (80004005) TSPxe 1/1/1980 1:29:41 AM 1004 (0x03EC) ClientIdentity.RequestClientIdentity (), HRESULT=80004005 (e:\nts_sccm_release\sms\client\tasksequence\tsmbootstrap\tsmediawizardcontrol.cpp,1036) TSPxe 1/1/1980 1:29:41 AM 1004 (0x03EC) failed to request for client TSPxe 1/1/1980 1:29:41 AM 1004 (0x03EC) Exiting TSMediaWizardControl::GetPolicy. TSPxe 1/1/1980 1:29:41 AM 1004 (0x03EC) pWelcomePage->m_pTSMediaWizardControl->GetPolicy(), HRESULT=80004005 (e:\nts_sccm_release\sms\client\tasksequence\tsmbootstrap\tsmediawelcomepage.cpp,303) TSPxe 1/1/1980 1:29:41 AM 1004 (0x03EC) Setting wizard error: An error occurred while retrieving policy for this computer (0x80004005). For more information, contact your system administrator or helpdesk operator. TSPxe 1/1/1980 1:29:41 AM 908 (0x038C) WelcomePage::OnWizardNext() TSPxe 1/1/1980 1:29:41 AM 908 (0x038C) Skipping Confirmation Page. TSPxe 1/1/1980 1:29:41 AM 908 (0x038C) Skipping Task Sequence Selection Page. TSPxe 1/1/1980 1:29:41 AM 908 (0x038C) Skipping Variables Selection Page. TSPxe 1/1/1980 1:29:41 AM 908 (0x038C) Skipping Resolve Progress Page. TSPxe 1/1/1980 1:29:41 AM 908 (0x038C) Activating Finish Page. TSPxe 1/1/1980 1:29:41 AM 908 (0x038C) Initializing the countdown timer. TSPxe 1/1/1980 1:29:41 AM 908 (0x038C) Loading bitmap TSPxe 1/1/1980 1:29:41 AM 908 (0x038C) Executing command line: X:\WINDOWS\system32\cmd.exe /k TSBootShell 1/1/1980 1:29:47 AM 828 (0x033C) The command completed successfully. TSBootShell 1/1/1980 1:29:47 AM 828 (0x033C) Successfully launched command shell. TSBootShell 1/1/1980 1:29:47 AM 828 (0x033C)

Thanks, man Yeah, that all makes perfect sense. I have enabled this since and it HAS made things much easier (obviously). Thanks again for the feedback on both counts.

So, check this out. After I: - disabled PXE and Multicast on the DP - Stopped WDS - Rebooted the SCCM server - Enabled PXE (before I did this the WDS was not showing up - I was in a state of WTF) - Eventually after I enabled PXE again WDS started - I updated the boot images to the DP PXE is now working properly again. In the smspxe.log it looks to my untrained eyes as if it had to re-find all the boot images. I can post the log if anyone wants to see. . Anyway, I was receiving the exact same error message as the OP and this is what fixed it for me. The thing that is so frustrating, like I said, is that NOTHING had been changed since the last time I imaged a batch of PCs. At least I didn't change it and I am the only one with access to this server. So, I'm stumped and await the next time it bugs out for no apparent reason. RocketMan, thanks for the advice. I had been avoiding unknown pc support for some reason. Thanks for reminding me. I'm going to enable it, seems like it would save me some time.....if it doesn't break something. Thanks again! I hope this helps somebody. This forum is pretty much the only place on the net that I have ever found pertinent information and I hope I can contribute if even in a very small way. If this site wasn't here I don't know where I could look.

I think in the beginning I was having some issues with PXE and not enabling support for unknown computers was part of what I did to fix. I would certainly enable it if it will work. I don't enjoy importing them all one by one or with a file, but it is what fixed it in the beginning. So, it just kind of got left that way. When you say re-seat RAM in the system are you talking about the client I'm trying to image or the SCCM server? Sccm is running in a VM. So, I can't really re-seat that. I'll try both of the above suggestions and see how it goes. Thanks for the suggestions!

Geez, man! I don't get it. Nobody has been on the SCCM server for two weeks. I know this because I'm the only admin. But here it is ONCE AGAIN pxe boot FAIL. It was working absolutely flawlessly for weeks and now ...nothing. This is a bit from my last attempt. From smspxe.log PXE::CNotifyTimer::TimerSignalFunc SMSPXE 10/4/2012 1:03:47 PM 5492 (0x1574) PXE::CNotifyTimer::ProcessTimer SMSPXE 10/4/2012 1:03:47 PM 5492 (0x1574) PXE::CBootImageManager::PerformMaintenenceTasks SMSPXE 10/4/2012 1:03:47 PM 5492 (0x1574) PXE::CBootImageManager::PurgeOldImages SMSPXE 10/4/2012 1:03:47 PM 5492 (0x1574) PXE::CNotifyTimer::Init SMSPXE 10/4/2012 1:03:47 PM 5492 (0x1574) PXE::CNotifyTimer::CancelTimer SMSPXE 10/4/2012 1:03:47 PM 5492 (0x1574) PXE::CNotifyTimer::RegisterTimeout SMSPXE 10/4/2012 1:03:47 PM 5492 (0x1574) PXE::CNotifyTimer::TimerSignalFunc SMSPXE 10/4/2012 1:13:47 PM 6036 (0x1794) PXE::CNotifyTimer::ProcessTimer SMSPXE 10/4/2012 1:13:47 PM 6036 (0x1794) PXE::CBootImageManager::PerformMaintenenceTasks SMSPXE 10/4/2012 1:13:47 PM 6036 (0x1794) PXE::CBootImageManager::PurgeOldImages SMSPXE 10/4/2012 1:13:47 PM 6036 (0x1794) PXE::CNotifyTimer::Init SMSPXE 10/4/2012 1:13:47 PM 6036 (0x1794) PXE::CNotifyTimer::CancelTimer SMSPXE 10/4/2012 1:13:47 PM 6036 (0x1794) PXE::CNotifyTimer::RegisterTimeout SMSPXE 10/4/2012 1:13:47 PM 6036 (0x1794) PXE::CNotifyTimer::TimerSignalFunc SMSPXE 10/4/2012 1:23:47 PM 5796 (0x16A4) PXE::CNotifyTimer::ProcessTimer SMSPXE 10/4/2012 1:23:47 PM 5796 (0x16A4) PXE::CBootImageManager::PerformMaintenenceTasks SMSPXE 10/4/2012 1:23:47 PM 5796 (0x16A4) PXE::CBootImageManager::PurgeOldImages SMSPXE 10/4/2012 1:23:47 PM 5796 (0x16A4) PXE::CNotifyTimer::Init SMSPXE 10/4/2012 1:23:47 PM 5796 (0x16A4) PXE::CNotifyTimer::CancelTimer SMSPXE 10/4/2012 1:23:47 PM 5796 (0x16A4) PXE::CNotifyTimer::RegisterTimeout SMSPXE 10/4/2012 1:23:47 PM 5796 (0x16A4) PXE::CNotifyTimer::TimerSignalFunc SMSPXE 10/4/2012 1:23:47 PM 5796 (0x16A4) PXE::CNotifyTimer::ProcessTimer SMSPXE 10/4/2012 1:23:47 PM 5796 (0x16A4) Begin validation of Certificate [Thumbprint 76A1F747FFA33163E7DB0DEC217D11D17DDE96C6] issued to '{A36E2639-05CC-4D5E-A4B4-4CEECA42C58A}' SMSPXE 10/4/2012 1:23:47 PM 5796 (0x16A4) Completed validation of Certificate [Thumbprint 76A1F747FFA33163E7DB0DEC217D11D17DDE96C6] issued to '{A36E2639-05CC-4D5E-A4B4-4CEECA42C58A}' SMSPXE 10/4/2012 1:23:47 PM 5796 (0x16A4) PXE::CNotifyTimer::Init SMSPXE 10/4/2012 1:23:47 PM 5796 (0x16A4) PXE::CNotifyTimer::CancelTimer SMSPXE 10/4/2012 1:23:47 PM 5796 (0x16A4) PXE::CNotifyTimer::RegisterTimeout SMSPXE 10/4/2012 1:23:47 PM 5796 (0x16A4) Set media certificate in transport SMSPXE 10/4/2012 1:27:36 PM 3608 (0x0E18) Set authenticator in transport SMSPXE 10/4/2012 1:27:36 PM 3608 (0x0E18) Set authenticator in transport SMSPXE 10/4/2012 1:27:36 PM 3608 (0x0E18) Client lookup reply: <ClientIDReply><Identification Unknown="0" ItemKey="0" ServerName="" ServerRemoteName=""><Machine><ClientID/><NetbiosName/></Machine></Identification></ClientIDReply> SMSPXE 10/4/2012 1:27:36 PM 3608 (0x0E18) Set media certificate in transport SMSPXE 10/4/2012 1:27:36 PM 3608 (0x0E18) Set authenticator in transport SMSPXE 10/4/2012 1:27:36 PM 3608 (0x0E18) Set authenticator in transport SMSPXE 10/4/2012 1:27:36 PM 3608 (0x0E18) Set media certificate in transport SMSPXE 10/4/2012 1:33:19 PM 3608 (0x0E18) Set authenticator in transport SMSPXE 10/4/2012 1:33:19 PM 3608 (0x0E18) Set authenticator in transport SMSPXE 10/4/2012 1:33:19 PM 3608 (0x0E18) Client lookup reply: <ClientIDReply><Identification Unknown="0" ItemKey="0" ServerName="" ServerRemoteName=""><Machine><ClientID/><NetbiosName/></Machine></Identification></ClientIDReply> SMSPXE 10/4/2012 1:33:19 PM 3608 (0x0E18) PXE::CNotifyTimer::TimerSignalFunc SMSPXE 10/4/2012 1:33:47 PM 5796 (0x16A4) PXE::CNotifyTimer::ProcessTimer SMSPXE 10/4/2012 1:33:47 PM 5796 (0x16A4) PXE::CBootImageManager::PerformMaintenenceTasks SMSPXE 10/4/2012 1:33:47 PM 5796 (0x16A4) PXE::CBootImageManager::PurgeOldImages SMSPXE 10/4/2012 1:33:47 PM 5796 (0x16A4) PXE::CNotifyTimer::Init SMSPXE 10/4/2012 1:33:47 PM 5796 (0x16A4) PXE::CNotifyTimer::CancelTimer SMSPXE 10/4/2012 1:33:47 PM 5796 (0x16A4) PXE::CNotifyTimer::RegisterTimeout SMSPXE 10/4/2012 1:33:47 PM 5796 (0x16A4) PXE::CNotifyTimer::TimerSignalFunc SMSPXE 10/4/2012 1:43:47 PM 4540 (0x11BC) PXE::CNotifyTimer::ProcessTimer SMSPXE 10/4/2012 1:43:47 PM 4540 (0x11BC) PXE::CBootImageManager::PerformMaintenenceTasks SMSPXE 10/4/2012 1:43:47 PM 4540 (0x11BC) PXE::CBootImageManager::PurgeOldImages SMSPXE 10/4/2012 1:43:47 PM 4540 (0x11BC) PXE::CNotifyTimer::Init SMSPXE 10/4/2012 1:43:47 PM 4540 (0x11BC) PXE::CNotifyTimer::CancelTimer SMSPXE 10/4/2012 1:43:47 PM 4540 (0x11BC) PXE::CNotifyTimer::RegisterTimeout SMSPXE 10/4/2012 1:43:47 PM 4540 (0x11BC) PXE::CNotifyTimer::TimerSignalFunc SMSPXE 10/4/2012 1:53:47 PM 7112 (0x1BC8) PXE::CNotifyTimer::ProcessTimer SMSPXE 10/4/2012 1:53:47 PM 7112 (0x1BC8) PXE::CBootImageManager::PerformMaintenenceTasks SMSPXE 10/4/2012 1:53:47 PM 7112 (0x1BC8) PXE::CBootImageManager::PurgeOldImages SMSPXE 10/4/2012 1:53:47 PM 7112 (0x1BC8) PXE::CNotifyTimer::Init SMSPXE 10/4/2012 1:53:47 PM 7112 (0x1BC8) PXE::CNotifyTimer::CancelTimer SMSPXE 10/4/2012 1:53:47 PM 7112 (0x1BC8) PXE::CNotifyTimer::RegisterTimeout SMSPXE 10/4/2012 1:53:47 PM 7112 (0x1BC8) PXE::CNotifyTimer::TimerSignalFunc SMSPXE 10/4/2012 2:03:47 PM 932 (0x03A4) PXE::CNotifyTimer::ProcessTimer SMSPXE 10/4/2012 2:03:47 PM 932 (0x03A4) PXE::CBootImageManager::PerformMaintenenceTasks SMSPXE 10/4/2012 2:03:47 PM 932 (0x03A4) PXE::CBootImageManager::PurgeOldImages SMSPXE 10/4/2012 2:03:47 PM 932 (0x03A4) PXE::CNotifyTimer::Init SMSPXE 10/4/2012 2:03:47 PM 932 (0x03A4) PXE::CNotifyTimer::CancelTimer SMSPXE 10/4/2012 2:03:47 PM 932 (0x03A4) PXE::CNotifyTimer::RegisterTimeout SMSPXE 10/4/2012 2:03:47 PM 932 (0x03A4) PXE::CNotifyTimer::TimerSignalFunc SMSPXE 10/4/2012 2:13:47 PM 5376 (0x1500) PXE::CNotifyTimer::ProcessTimer SMSPXE 10/4/2012 2:13:47 PM 5376 (0x1500) PXE::CBootImageManager::PerformMaintenenceTasks SMSPXE 10/4/2012 2:13:47 PM 5376 (0x1500) PXE::CBootImageManager::PurgeOldImages SMSPXE 10/4/2012 2:13:47 PM 5376 (0x1500) PXE::CNotifyTimer::Init SMSPXE 10/4/2012 2:13:47 PM 5376 (0x1500) PXE::CNotifyTimer::CancelTimer SMSPXE 10/4/2012 2:13:47 PM 5376 (0x1500) PXE::CNotifyTimer::RegisterTimeout SMSPXE 10/4/2012 2:13:47 PM 5376 (0x1500) What the hell does this say? I get the same message as above. Please help me out. I've already checked the everything is deployed to the DP. The only thing that has changed since I first discovered PXE broken (again) is that I deleted the adverts for the task sequence that pushes the image and re-deployed it. It says 0% compliant. I don't think this is a problem because pxe wasn't working before this, but just thought I'd throw it out there. What does that 0% compliant even mean?

Any good resources for setting up Data Protection Manager in 2012?

For those of you following my little saga (palpable silence) the BIOS setting on the alienware was the key. Once I changed the bios setting from UEFI to Legacy and re-built the OS on top, everything else remaining the same, the capture media worked. I have successfully captured the image. Now...if I can deploy it to another machine.... Thanks for all the comments. They did help. Once again, Niall's most often posted comment "what does the smsts.log say" paid off. It's been a long frustrating week. All you admins out there have a beer on me.

Have you run into this issue before?

I have tried to push the image to it. It fails, not sure when though. The VM build up is a good idea and I might try that if my experiment today doesn't work. I have the NIC drivers as well as the storage drivers in this boot image. I thought you needed both. If I'm capturing don't I already have the drivers for the OS? I'm doing the capture from media, not sure how or why I would need to add drivers to a reference image I am capturing. I have created so many capture ISOs it's hilarious. I have done what your talking about before though. Now I make sure to create a new one right after I update the DP. I tried to use the USB version, but it won't autorun and I didn't feel like negotiating another bug. So, I've just been burning discs. In the log it mentions the issue with the BIOS settings. So, I'm hoping changing that from UEFI to Legacy will be the solution.

Anyone had a crack at this one yet? Today I'm going to try booting from "Legacy" mode on the Alienware, installing the OS and try the capture again.

So this has been just a real treat. I'm attaching the log for the failed capture, but here is an interesting bit. <![LOG[Failed to install boot sector. C:\_SMSTaskSequence\WinPE\SMS\bin\i386\bootsect.exe /NT60 SYS /MBR failed (1) stdout: This tool can only be run on systems booted using a PC/AT BIOS. This systemwas booted using EFI or some other firmware type. stderr: ]LOG]!><time="17:41:25.149+360" date="09-13-2012" component="TSManager" context="" type="3" thread="2596" file="bootsector.cpp:83"> <![LOG[Failed to install boot image. Unspecified error (Error: 80004005; Source: Windows)]LOG]!><time="17:41:25.149+360" date="09-13-2012" component="TSManager" context="" type="3" thread="2596" file="bootimage.cpp:646"> <![LOG[Failed to install boot image CCM0001A. Unspecified error (Error: 80004005; Source: Windows)]LOG]!><time="17:41:25.149+360" date="09-13-2012" component="TSManager" context="" type="3" thread="2596" file="engine.cxx:826"> <![LOG[Failed to reboot the system. Error 0x(80004005)]LOG]!><time="17:41:25.149+360" date="09-13-2012" component="TSManager" context="" type="3" thread="2596" file="engine.cxx:939"> This is the part where everything starts to go pear shaped. Any help would be superb. smsts.log

Excellent, thanks for the feedback! Glad to know I'm doing something correctly. I'm currently going BONKERS trying to capture and image for an Alienware R4. If your super bored and not quite tiring of answering questions have a peep at my current issue here - http://www.windows-noob.com/forums/index.php?/topic/5070-how-can-i-capture-an-image-using-capture-media-in-configmgr-2012/page__st__20#entry23589 I have no idea why it's not working. Thanks, again

I'm having this exact issue with an Alienware R4. The capture media runs fine until the end of the sysprep routine. At some point it dumps the NIC completely and results in a 0x80004005. I have created a boot image specifically for this PC which has the realtek 64 bit driver for the NIC and the storage drivers, Intel C600 series chipset SATA AHCI Controller driver (iaAHCI.inf and iaStorA.inf). I have tried everything, been working on it for three days now. All aspects of OSD are working properly for other PCs (HP elitebook 8560w). I'm at a complete loss. Everything I have read to this point had said DO NOT install the ccm client, but these instructions say you should. So, I am going to try that now. We'll see, I guess.

Just a quick question: Is it completely unheard of to use separate boot images for different PC model's driver packages? It seems like it should be unnecessary, but I have HP elitebooks (99% of our environment) and then about a dozen Alienware R4s I recently became responsible for and the last time I tried to use those drivers in my x64 boot image it broke the OSD operation for the HPs and I ended up having to nuke my boot image and rebuild it. I have everything fixed now and image deployment works again for the HPs, but I need to capture an Alienware image with totally different NIC and storage drivers and don't want it to screw up the working boot image.

I've been running SQL 2008 Standard since SCCM 2012 RC1, and installing each new iteration of CM on top of it, but as you can guess it started to get a bit quirky, mostly with Reporting. So, I'm actually thinking of clean installing both. Upgrading from SQL standard to standard R2 SP2 should suffice I think unless it doesn't include CU6, I guess. The reason I want to do both clean installs is the SQL upgrade I did before worked, but it wasn't very fun to do. Since my last post I have reverted back to a snap shot (vmware) that I took before I upgraded SQL (which was after I upgraded CM to RTM) and things are a bit strange. In the CM console it's telling me it is RC v.5.0.7703.0, but when I look at the attributes of SMS-MP-CCM-SERVER.MYDOMAIN.COM in AD, on the mSSMSCapabilities attribute it has Version 5.00.7711.0000. So, I'm not really sure what's going on. I'd rather not rebuild everything, but I can't be sure things are working correctly. On a side note, if upgrade from RC2 to RTM is not supported, WHY is there an upgrade option when you run the install for the RTM version? I don't mean that in a smart-assy way. I would just really like to know. Thanks for the input.

Ok, how about this? Can you tell me whether I should clean install SCCM and then upgrade SQL or upgrade SQL then install SCCM?

Not a big environment - about 500 clients. Well, that is a bummer. I guess the thing that worries me the most is how the current SQL stuff is going to react if I do a clean install of SCCM 2012. I am even more ignorant concerning SQL. Any advice other than what you have already stated concerning the clean install? I plan on using the exact same settings as I did when I first installed SCCM 2012.

Oh, man. I upgraded from the last release candidate version to RTM. I do have "Deploy this boot image from the PXE service point" box checked - Info from properties on Boot image (x64) Strangely, today I just PXE-booted successfully. The only thing that I did last night was remove all clients from my Image Deployment device group. I don't really see how that would change anything though. I am concerned now about your upgrade comment. Should I just start over and do a clean install of SCCM 2012? Everything looks healthy. As I mentioned, Component status view gives me green across the board, but I guess it could be inaccurate.

SMSPXE.log - This is new this morning: Begin validation of Certificate [Thumbprint 76A1F747FFA33163E7DB0DEC217D11D17DDE96C6] issued to '{A36E2639-05CC-4D5E-A4B4-4CEECA42C58A}' SMSPXE 9/5/2012 8:05:08 AM 5316 (0x14C4) Completed validation of Certificate [Thumbprint 76A1F747FFA33163E7DB0DEC217D11D17DDE96C6] issued to '{A36E2639-05CC-4D5E-A4B4-4CEECA42C58A}' SMSPXE 9/5/2012 8:05:08 AM 5316 (0x14C4) PXE::CNotifyTimer::Init SMSPXE 9/5/2012 8:05:08 AM 5316 (0x14C4) PXE::CNotifyTimer::CancelTimer SMSPXE 9/5/2012 8:05:08 AM 5316 (0x14C4) PXE::CNotifyTimer::RegisterTimeout SMSPXE 9/5/2012 8:05:08 AM 5316 (0x14C4) PXE::CNotifyTimer::TimerSignalFunc SMSPXE 9/5/2012 8:15:08 AM 3404 (0x0D4C) PXE::CNotifyTimer::ProcessTimer SMSPXE 9/5/2012 8:15:08 AM 3404 (0x0D4C) PXE::CBootImageManager::PerformMaintenenceTasks SMSPXE 9/5/2012 8:15:08 AM 3404 (0x0D4C) PXE::CBootImageManager::PurgeOldImages SMSPXE 9/5/2012 8:15:08 AM 3404 (0x0D4C) PXE::CNotifyTimer::Init SMSPXE 9/5/2012 8:15:08 AM 3404 (0x0D4C) PXE::CNotifyTimer::CancelTimer SMSPXE 9/5/2012 8:15:08 AM 3404 (0x0D4C) PXE::CNotifyTimer::RegisterTimeout SMSPXE 9/5/2012 8:15:08 AM 3404 (0x0D4C) Set media certificate in transport SMSPXE 9/5/2012 8:15:46 AM 3272 (0x0CC8) Set authenticator in transport SMSPXE 9/5/2012 8:15:46 AM 3272 (0x0CC8) Set authenticator in transport SMSPXE 9/5/2012 8:15:46 AM 3272 (0x0CC8) Client lookup reply: <ClientIDReply><Identification Unknown="0" ItemKey="0" ServerName="" ServerRemoteName=""><Machine><ClientID/><NetbiosName/></Machine></Identification></ClientIDReply> SMSPXE 9/5/2012 8:15:46 AM 3272 (0x0CC8) PXE::CBootImageManager::FindMatchingArchitectureBootImage SMSPXE 9/5/2012 8:15:46 AM 3272 (0x0CC8) Getting boot action for unknown machine: item key: 2046820352 SMSPXE 9/5/2012 8:15:46 AM 3272 (0x0CC8) Set media certificate in transport SMSPXE 9/5/2012 8:15:46 AM 3272 (0x0CC8) Set authenticator in transport SMSPXE 9/5/2012 8:15:46 AM 3272 (0x0CC8) Set authenticator in transport SMSPXE 9/5/2012 8:15:46 AM 3272 (0x0CC8) 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 9/5/2012 8:15:47 AM 3272 (0x0CC8) Client Identity: {A36E2639-05CC-4D5E-A4B4-4CEECA42C58A} SMSPXE 9/5/2012 8:15:47 AM 3272 (0x0CC8) Set media certificate in transport SMSPXE 9/5/2012 8:15:47 AM 3272 (0x0CC8) Set authenticator in transport SMSPXE 9/5/2012 8:15:47 AM 3272 (0x0CC8) Set authenticator in transport SMSPXE 9/5/2012 8:15:47 AM 3272 (0x0CC8) 2046820352 - This is the "x86 Unknown Computer" that is located in the Devices group by default, but is also in my End Users device group. What is going on? Is this supposed to do this?

I have been running SCCM 2012 since beta with SQL 2008 Standard. I recently upgraded to SCCM 2012 RTM and everything still worked, but then I upgraded to SQL 200 R2 SP1 + CU6 (three days ago) and can't quite tell if it's working well or not. Yesterday I experienced the symptom of loosing the ability to PXE- boot clients to receive an image. I googled around and searched the forum a bit, but found the usual solutions, all of which I had seen before and as it has been working great until the SQL upgrade didn't think they were applicable. I also had a few errors in the component status view which I hadn't seen before, but looking at it this morning everything seems "normal" again. I did have a look at the smspxe.log, but even after about a year of working with SCCM I am still clearly a noob. So, I'm going to attach the entire log as text if someone would be so kind as to look at it and see if anything seems strange. Also, if there is a good resource that someone could provide that might help explain what I'm looking at in this particular log file it would be greatly appreciated. The only thing I see that is a glaring error is this: RequestMPKeyInformation: Send() failed. SMSPXE 9/4/2012 6:04:51 PM 2976 (0x0BA0) Failed to get information for MP: http://MYSCCMSITE.domain.com 80004005. SMSPXE 9/4/2012 6:04:51 PM 2976 (0x0BA0) PXE::DB_InitializeTransport failed; 0x80004005 SMSPXE 9/4/2012 6:04:51 PM 2976 (0x0BA0) PXE::DB_LookupDevice failed; 0x80004005 SMSPXE 9/4/2012 6:04:51 PM 2976 (0x0BA0) PXE Provider failed to initialize database connection. Unspecified error (Error: 80004005; Source: Windows) SMSPXE 9/4/2012 6:04:51 PM 2976 (0x0BA0) But this only happened yesterday and not today when I looked at it again. I'm going to try and PXE-boot again right now as my original intent was to troubleshoot the component errors which are mysteriously gone today. Thanks in advance for any help. smsPXElog.txt