Steve_BE

Hello Running SCCM2012 SP1 with an MP/DP in a datacenter and a DP in 3 local offices. All has been working fine since the beginning mostly thanks to the guides here. But since this monday when deploying new laptops, I get an error message when PXE booting: Recovery Your PC needs to be repaired The Boot configuration Data for your PC is missing or contains errors File:\boot\bcd Error code: 0xc000000f Checking the logs on the local DP where I reside i see the following: [TSMESSAGING] AsyncCallback(): WINHTTP_CALLBACK_STATUS_SECURE_FAILURE Encountered SMSPXE 4/25/2013 11:50:20 AM 3416 (0x0D58) [TSMESSAGING] : dwStatusInformationLength is 4 SMSPXE 4/25/2013 11:50:20 AM 3416 (0x0D58) [TSMESSAGING] : *lpvStatusInformation is 0x1 SMSPXE 4/25/2013 11:50:20 AM 3416 (0x0D58) [TSMESSAGING] : WINHTTP_CALLBACK_STATUS_FLAG_CERT_REV_FAILED is set SMSPXE 4/25/2013 11:50:20 AM 3416 (0x0D58) [TSMESSAGING] AsyncCallback(): ----------------------------------------------------------------- SMSPXE 4/25/2013 11:50:20 AM 3416 (0x0D58) sending with winhttp failed; 80072f8f SMSPXE 4/25/2013 11:50:20 AM 3416 (0x0D58) Failed to get information for MP: https://ASPSCCML01.company.com. 80072f8f. SMSPXE 4/25/2013 11:50:20 AM 3416 (0x0D58) PXE::MP_InitializeTransport failed; 0x80004005 SMSPXE 4/25/2013 11:50:20 AM 3416 (0x0D58) PXE::MP_ReportStatus failed; 0x80004005 SMSPXE 4/25/2013 11:50:20 AM 3416 (0x0D58) PXE Provider failed to process message. Unspecified error (Error: 80004005; Source: Windows) SMSPXE 4/25/2013 11:50:20 AM 3416 (0x0D58) 6C:3B:E5:F6:F8:AE, A482B6CF-43F9-11E2-830B-A064B90000ED: Not serviced. SMSPXE 4/25/2013 11:50:20 AM 3416 (0x0D58) WINHTTP_CALLBACK_STATUS_FLAG_CERT_REV_FAILED points to the CRL validation but it was not checked in the configuration. So I did check it, save, rebooted the server, uncheck it again, reboot again … to no avail Next error I checked is : Failed to get information for MP: https://ASPSCCML01.company.com. 80072f8f. Error code 80072f8f would means ERROR_INTERNET_SECURE_FAILURE ErrorClockWrong But all servers and client shows the correct time (all servers/clients (bios) configured with GMT+1) Next I tried the following: I redistributed the boot image (x64 - did not recreate them). I exported the root CA chain from the internal root CA and re assigned it in \Administration\Overview\Site Configuration\Sites - Properties - tab 'Client Computer configuration' I requested a new web server certificate for use in IIS (as described at http://technet.microsoft.com/en-us/library/gg682023.aspx#BKMK_webserver2008_cm2012) I requested a new DP certificate, exported it with the private key and configured it in \Administration\Overview\Site Configuration\Servers and Site System Roles - distribution point - properties - tab 'General and import the certificate (again as described at http://technet.microsoft.com/en-us/library/gg682023.aspx#BKMK_clientdistributionpoint2008_cm2012) I then went back to the original error: WINHTTP_CALLBACK_STATUS_FLAG_CERT_REV_FAILED and from http://msdn.microsoft.com/en-us/library/aa383917(VS.85).aspx it would means: Certification revocation checking has been enabled, but the revocation check failed to verify whether a certificate has been revoked. The server used to check for revocation might be unreachable I thus checked further the PKI implementation and in AD Sites and services -> /Services/Public Key Services/CDP/ASP-SELLROOTCA/Company Internal ROOT CA -> Properties -> Tab object And I see that the last Modified date is from Monday 22/04 (Created 24/9/2010, Modified 22/04/2013 - USNs current 12017227, Original 17735) This coincide with the time OSD didn’t work anymore Here I am stuck on how to resolve this: Either have SCCM not check the CRL (as I believe we configured it) or have CRL access available when PXE booting. Any hint / suggestion is welcome Steve

Hi all If you are running SCCM database on a SQL cluster: you will need to run the reporting server on a separate server (I couldn't get it running on a cluster node and I didn't like it anyway I went for a VM with not much ressources). After installing the SRSS service, you must configure it before going back to SCCM: Configure the service to start with the SCCM report user create the DB (point it to your clustered system center instance) Report server DB credential: use once again the SCCM report user Add the Report Manager url (at least http) Define the Execution Account with the SCCM Report user. I also added the sccm report user as local admin of the SRSS server (not sure it's really needed) Add the SCCM server computer account as local admin of the SRSS server (needed to configure the server). I'm not sure it's a 'production' valid setup regarding security but I couldn't find a way to get it working until i did all these steps. Once done, go back to the SCCM console (based on the following post: http://social.technet.microsoft.com/Forums/en-US/configmanagergeneral/thread/4479e73e-8a19-4c7e-9418-b36770656b9b) In CfgMgr, In the Administration workspace, expand Site Configuration, and then clickServers and Site System Roles. (....) you have to go to New site system and add the SSRS box. Then, on the Home tab, in the Server group, clickAdd Site System Role. The Add Site System Roles Wizard opens. Choose Reporting Point, and after verifying the connection to the CfgMgr DB, the instance name should populate. Then check back the installation process as described in the original post by anyweb. Hope this helps Steve

I just started with IE9 too and went the IEAK way as I need to add some trusted sites, modify the security level of these sites (and I also add the most used company related url in the fav bar). it smoothly created the msi but when I want to add it as an application I received a warning: I acknowledge the error and then add it as an application in my TS (a simple deploy win 7 x64). and same as you face I doesn't get installed. (no error message during the TS) I'm still trying to find which log(s) I should check for applications install (might be related to the publisher warning) I'll keep you posted should I find the solution

Hello From what you describe, the first thing that comes to mind in a Bios issue. What brand and model do you use, does it happen with different models, ... or did you already check for bios updates too ?

I finally found what went wrong: when first setting up the MP I installed it to use HTTPS only. I went on to configure the DP and so on and later on reconfigure on the MP to allow HTTP and HTTS requests. the error in smstslog on the DP is in fact pretty explicit: Initializing HTTP transport. OSDSetupHook 6/5/2012 11:05:42 AM 1928 (0x0788) Setting URL = https://CORPSCL01.company.com/NOCERT_SMS_DP_SMSPKG$/CCM0000A. OSDSetupHook 6/5/2012 11:05:42 AM 1928 (0x0788) Address=https://CORPSCL01.company.com, Scheme=https, Object=/NOCERT_SMS_DP_SMSPKG$/CCM0000A, Port=443. OSDSetupHook 6/5/2012 11:05:42 AM 1928 (0x0788) Setting Authenticator. OSDSetupHook 6/5/2012 11:05:42 AM 1928 (0x0788) Set authenticator in transport OSDSetupHook 6/5/2012 11:05:42 AM 1928 (0x0788) Setting Media Certificate. OSDSetupHook 6/5/2012 11:05:42 AM 1928 (0x0788) WinHttp credentials set OSDSetupHook 6/5/2012 11:05:42 AM 1928 (0x0788) CLibSMSMessageWinHttpTransport::Send: URL: CORPSCL01.company.com:443 PROPFIND /NOCERT_SMS_DP_SMSPKG$/CCM0000A OSDSetupHook 6/5/2012 11:05:42 AM 1928 (0x0788) In SSL, but with no client cert OSDSetupHook 6/5/2012 11:05:42 AM 1928 (0x0788) Error. Received 0x80072efd from WinHttpSendRequest. OSDSetupHook 6/5/2012 11:05:45 AM 1928 (0x0788) connect (sock, (struct sockaddr *) &SockAddrIn, sizeof (struct sockaddr_in)) == 0, HRESULT=8007274d (e:\nts_sccm_release\sms\framework\osdmessaging\libsmsmessaging.cpp,725) OSDSetupHook 6/5/2012 11:05:46 AM 1928 (0x0788) socket 'connect' failed; 8007274d OSDSetupHook 6/5/2012 11:05:46 AM 1928 (0x0788) hr, HRESULT=80072efd (e:\nts_sccm_release\sms\framework\osdmessaging\libsmsmessaging.cpp,8738) OSDSetupHook 6/5/2012 11:05:46 AM 1928 (0x0788) sending with winhttp failed; 80072efd OSDSetupHook 6/5/2012 11:05:46 AM 1928 (0x0788) oHttpTransport.Send((char*)S_DAVQUERY, (sizeof(S_DAVQUERY)/sizeof(S_DAVQUERY[0]))-sizeof(char), pReply, nReplySize), HRESULT=80072efd (e:\nts_sccm_release\sms\framework\tscore\downloadcontent.cpp,829) OSDSetupHook 6/5/2012 11:05:46 AM 1928 (0x0788) SendResourceRequest() failed with 0x80072efd OSDSetupHook 6/5/2012 11:05:46 AM 1928 (0x0788) SendResourceRequest(), HRESULT=80072efd (e:\nts_sccm_release\sms\framework\tscore\downloadcontent.cpp,572) OSDSetupHook 6/5/2012 11:05:46 AM 1928 (0x0788) oDavRequest.GetDirectoryListing(setDirs, setFiles), HRESULT=80072efd (e:\nts_sccm_release\sms\framework\tscore\resolvesource.cpp,2411) OSDSetupHook 6/5/2012 11:05:46 AM 1928 (0x0788) Retrying download... OSDSetupHook 6/5/2012 11:05:46 AM 1928 (0x0788) Based on the address it is trying to reach at: Address=https://CORPSCL01.company.com, Scheme=https, Object=/NOCERT_SMS_DP_SMSPKG$/CCM0000A, Port=443. It falls back to HTTP and then to SMB to no avail I investigated the the IIS settings on the DP and saw that no certificate was configured. I took our wildcard certificate (I beleive I could have use our internal CA too), install it and configure the default website to use it for https. And bingo, it could retrieve the CM client package I guess the DP never go the update to allow HTTP requests. cheers, Steve

Hello I renamed the task sequence to v1.1 and it is picked up when restarting the build & capture task sequence. But local amdinsitrator is still disabled when I try to log on The Task sequence (it's the only one created so far): But I also I have another issue (missed that one as I let it run overnight to only see the login page in the morning) Maybe it is linked to that as it doesnt properly finish the sequence ? Taks sequence fails at the "Setup Windows and Configuration Manager": CLibSMSMessageWinHttpTransport::Send: URL: CORPSCL01.comany.com:443 PROPFIND /NOCERT_SMS_DP_SMSPKG$/CCM0000A OSDSetupHook 6/5/2012 11:05:42 AM 1928 (0x0788) In SSL, but with no client cert OSDSetupHook 6/5/2012 11:05:42 AM 1928 (0x0788) Error. Received 0x80072efd from WinHttpSendRequest. OSDSetupHook 6/5/2012 11:05:45 AM 1928 (0x0788) connect (sock, (struct sockaddr *) &SockAddrIn, sizeof (struct sockaddr_in)) == 0, HRESULT=8007274d (e:\nts_sccm_release\sms\framework\osdmessaging\libsmsmessaging.cpp,725) OSDSetupHook 6/5/2012 11:05:46 AM 1928 (0x0788) socket 'connect' failed; 8007274d OSDSetupHook 6/5/2012 11:05:46 AM 1928 (0x0788) hr, HRESULT=80072efd (e:\nts_sccm_release\sms\framework\osdmessaging\libsmsmessaging.cpp,8738) OSDSetupHook 6/5/2012 11:05:46 AM 1928 (0x0788) sending with winhttp failed; 80072efd OSDSetupHook 6/5/2012 11:05:46 AM 1928 (0x0788) oHttpTransport.Send((char*)S_DAVQUERY, (sizeof(S_DAVQUERY)/sizeof(S_DAVQUERY[0]))-sizeof(char), pReply, nReplySize), HRESULT=80072efd (e:\nts_sccm_release\sms\framework\tscore\downloadcontent.cpp,829) OSDSetupHook 6/5/2012 11:05:46 AM 1928 (0x0788) SendResourceRequest() failed with 0x80072efd OSDSetupHook 6/5/2012 11:05:46 AM 1928 (0x0788) SendResourceRequest(), HRESULT=80072efd (e:\nts_sccm_release\sms\framework\tscore\downloadcontent.cpp,572) OSDSetupHook 6/5/2012 11:05:46 AM 1928 (0x0788) oDavRequest.GetDirectoryListing(setDirs, setFiles), HRESULT=80072efd (e:\nts_sccm_release\sms\framework\tscore\resolvesource.cpp,2411) OSDSetupHook 6/5/2012 11:05:46 AM 1928 (0x0788) Retrying download... OSDSetupHook 6/5/2012 11:05:46 AM 1928 (0x0788) It tries 2 times then switch to SMB: Tried all the available http based locations. SMB based locations will be attempted now. OSDSetupHook 6/5/2012 11:05:55 AM 1928 (0x0788) !saSMBContentSources.empty(), HRESULT=80070002 (e:\nts_sccm_release\sms\framework\tscore\resolvesource.cpp,2849) OSDSetupHook 6/5/2012 11:05:55 AM 1928 (0x0788) DownloadContentAndVerifyHash(pszPackageID, L"SMSPackage", saHttpContentSources, saSMBContentSources, saMulticastContentSources, sDestination, dwFlags, L"", 0, dwPackageFlags, pszUserName, pszUserPassword ), HRESULT=80070002 (e:\nts_sccm_release\sms\framework\tscore\resolvesource.cpp,3007) OSDSetupHook 6/5/2012 11:05:55 AM 1928 (0x0788) DownloadContentLocally(pszSource, sSourceDirectory, dwFlags, hUserToken, pszUserName, pszUserPassword), HRESULT=80070002 (e:\nts_sccm_release\sms\framework\tscore\resolvesource.cpp,3217) OSDSetupHook 6/5/2012 11:05:55 AM 1928 (0x0788) ResolveSource(pszSource, sSourceDirectory, dwFlags, 0, 0, 0), HRESULT=80070002 (e:\nts_sccm_release\sms\framework\tscore\resolvesource.cpp,3122) OSDSetupHook 6/5/2012 11:05:55 AM 1928 (0x0788) TS::Utility::ResolveSource(sClientPackageID, sClientPackagePath), HRESULT=80070002 (e:\nts_sccm_release\sms\client\osdeployment\osdgina\basesetuphook.cpp,1496) OSDSetupHook 6/5/2012 11:05:55 AM 1928 (0x0788) Failed to resolve package source "CCM0000A" OSDSetupHook 6/5/2012 11:05:55 AM 1928 (0x0788) Exiting ConfigureEx: 0x80070002 OSDSetupHook 6/5/2012 11:05:55 AM 1928 (0x0788) BaseSetupHook::configure(sWindowsDir), HRESULT=80070002 (e:\nts_sccm_release\sms\client\osdeployment\osdgina\osdsetuphook.cpp,290) OSDSetupHook 6/5/2012 11:05:55 AM 1928 (0x0788) Failed to configure OSD setup hook (0x80070002) OSDSetupHook 6/5/2012 11:05:55 AM 1928 (0x0788) Process completed with exit code 2147942402 OSDSetupWindows 6/5/2012 11:05:55 AM 472 (0x01D8) exitCode, HRESULT=80070002 (e:\nts_sccm_release\sms\client\osdeployment\setupwindows\setupwindows.cpp,635) OSDSetupWindows 6/5/2012 11:05:55 AM 472 (0x01D8) Configure hook failed with error code (80070002). OSDSetupWindows 6/5/2012 11:05:55 AM 472 (0x01D8) this->configureGina(this->sysDir), HRESULT=80070002 (e:\nts_sccm_release\sms\client\osdeployment\setupwindows\setupwindows.cpp,780) OSDSetupWindows 6/5/2012 11:05:55 AM 472 (0x01D8) this->installSetupHook(), HRESULT=80070002 (e:\nts_sccm_release\sms\client\osdeployment\setupwindows\setupwindows.cpp,452) OSDSetupWindows 6/5/2012 11:05:55 AM 472 (0x01D8) Failed to install setup hook (80070002) OSDSetupWindows 6/5/2012 11:05:55 AM 472 (0x01D8) setup.run(), HRESULT=80070002 (e:\nts_sccm_release\sms\client\osdeployment\setupwindows\setupwindows.cpp,1668) OSDSetupWindows 6/5/2012 11:05:55 AM 472 (0x01D8) Exiting with code 0x80070002 OSDSetupWindows 6/5/2012 11:05:55 AM 472 (0x01D8) Process completed with exit code 2147942402 TSManager 6/5/2012 11:05:55 AM 1108 (0x0454) !--------------------------------------------------------------------------------------------! TSManager 6/5/2012 11:05:55 AM 1108 (0x0454) Failed to run the action: Setup Windows and Configuration Manager. The system cannot find the file specified. (Error: 80070002; Source: Windows) TSManager 6/5/2012 11:05:55 AM 1108 (0x0454) I allowed HTTPS and HTTP and configured certificates (server, client and DP) as per http://technet.micro...y/gg682023.aspx) I'll need HTTPS later on as we have a few people who only pass by in an office once every 6 months. Also in tab 'Signing and encryption', 'Require SHA-256' is unchecked. About Package CCM0000A In Software Library -> package: It is the 'CM client upgrade' package created as the guide says. Package ID is also CCM0000A with a Readiness 'unknown'. When checking 'Content Status': it is distributed to MP (last status time 6/6) and DP (last status time 6/6) with description 'Distribution Manager successfully ditributed Package "CCM0000A" ...' On the Distribution point I do find ref of that package in DataLib, a .tar file in SMSSIG$, etc... Regards Steve I understand it's another issue but I rather mention here than open a new thread as it might be related to the first issue mentionned

Hello First of all thank you very much for all the guides and the help you provide here !!!! Now based on the guide found at http://www.windows-noob.com/forums/index.php?/topic/4468-using-sccm-2012-rc-in-a-lab-part-7-build-and-capture-windows-7-x64/, I made a small mistake and missed the "and that you DO enter an Administrator Password" when creating the task sequence. As the OS is not part of a domain or is another user configured ... I'm locked out .... So I modified the settings accordingly but I cannot get the client computer to see that modification. Topology is : one main server (in a datacenter) with a dedicated SQL instance and one disribution point in another physical building where I reside with my test computer. I tried by - Right click the task sequence and Deploy (to the same Collection) - I selected all references one by one and Update Distribution point (Bootimage package, OS installation package and CM client upgrade package) When I do 'Distribute Content' and select 'Add Distribution points', only the server in the datacenter is selectable. not my WDS on the client site (which means it is already valid for the task sequence right?) I'm pretty sure it's my distribution point that's missing the new info but I dont know how and where I can push the new version of the task sequence. Thanks for your help Steve