amakusa007

I am in need of help here. We have recently discovered that all of our client are showing as inactive since 7/10/2020. The only thing we had back then was the certificate authority renewal of certificates for all computers. we have renew all certificates on all the computers and servers but no luck on sccm. I have updated the certificate inside the distribution point with the new certificate and still showing inactive on all clients/servers. I have tried switching between HTTP and HTTPS as well in the distribution point under administration > server and site roles and nothing. Rebooted the server also and no changes. all certificates as well on the mmc certificate console panel are updated as well.

I did a UEFI deployment on one of my successful older computer and both Legacy and UEFI worked perfectly. I seems to these new laptops and desktop are the one giving me problems. I have injected the drivers using the sccm and will test on that process. The problems I am experiecing are on optiplex 7070, precision tower 3630 & latitude 5400.

I tested today my deployment using an older computer in legacy boot and it doesnt give me problems during task sequence. All packages installed fine. I seems to be either related to the new computers or UEFI settings. Any help would be appreciated it.

The behavior I am seeing is that the application will continue cycle inside sccm but when finished and you log in on the computer, no application was installed at all. On packages I get the error 0x8007002 on all of them No changes were made to the accounts, packages show green and the package folders show updated. Boot PXE is 1903 version with windows 10 1809. I have updated the windows 10 image to see if it does anything different and also check the network accounts to make sure they are not locked out in anyway.

I been getting issues with the task sequence on all packages & applications inside sccm. The version I am using is 1910 on a windows server 2016 performing pxe boot in uefi. My last known good deployment was on March and the only thing we did on this server is windows updates. Has anyone else been having this issue?

resolved this issue. The command line listed above installed the client with no issues. The pki issue was that the domain controller was missing the pi certificate on it. For some reason it doesn't like to auto-enroll on domain controllers so I needed to go through the portal and manually select the certificate to installed. Now client working properly.

so I was able to install the client using the command line ccmsetup.exe SMSSITECODE=SITE1 /skipprereq:WindowsUpdateAgent30-x64.exe. It shows my site code but my pki client certificate shows as None.

It was my boot image needed to be updated to a later version that was causing the problem. Once I got an newer version it fixed the issue.

do you have another adapter to test? I have similar issues it turned out if was my adapter stopped working. I used the dell adapter and once we got new ones it worked fine.

I am having issues installing the sccm client on the server. I have tried deployment from the console and selecting domain controllers to install and it tries to go through fails. I also tried command line installation, uninstalling using ccmsetup.exe /uninstall and even used ccmclean.exe. I can see that the registry is cleared, all files deleted on the windows folder and no services showing running. All other computers are updating properly and only this domain controller is giving me problems. The domain controller is on AD with another domain controller which is the same version of OS and it updates/install properly. This domain controllwe which I am now having issues used to have an older version that has been removed using ccmsetup.exe /uninstall via command prompt. This is what I am seeing at the end of the logs ']LOG]!><time="13:40:00.188+240" date="09-27-2019" component="ccmsetup" context="" type="0" thread="4436" file="ccmhttplib.cpp:215"> <![LOG[IsSslClientAuthEnabled - Determining provisioning mode state failed with 80070002. Defaulting to state of 63.]LOG]!><time="13:40:00.188+240" date="09-27-2019" component="ccmsetup" context="" type="1" thread="4436" file="CcmUtilLib.cpp:2530"> <![LOG[Client is on internet]LOG]!><time="13:40:00.188+240" date="09-27-2019" component="ccmsetup" context="" type="0" thread="4436" file="requestresponse.cpp:228"> <![LOG[Client is set to use webproxy if available.]LOG]!><time="13:40:00.188+240" date="09-27-2019" component="ccmsetup" context="" type="0" thread="4436" file="requestresponse.cpp:240"> <![LOG[IsSslClientAuthEnabled - Determining provisioning mode state failed with 80070002. Defaulting to state of 63.]LOG]!><time="13:40:00.188+240" date="09-27-2019" component="ccmsetup" context="" type="1" thread="4436" file="CcmUtilLib.cpp:2530"> <![LOG[Begin searching client certificates based on Certificate Issuers]LOG]!><time="13:40:00.188+240" date="09-27-2019" component="ccmsetup" context="" type="1" thread="4436" file="CcmCert.cpp:4974"> <![LOG[Certificate Issuer 1 [CN=XXXXXXXXXXX Root Certification Authority]]LOG]!><time="13:40:00.188+240" date="09-27-2019" component="ccmsetup" context="" type="1" thread="4436" file="CcmCert.cpp:4990"> <![LOG[Finding certificate by issuer chain returned error 80092004]LOG]!><time="13:40:00.188+240" date="09-27-2019" component="ccmsetup" context="" type="2" thread="4436" file="CcmCert.cpp:5025"> <![LOG[Completed searching client certificates based on Certificate Issuers]LOG]!><time="13:40:00.188+240" date="09-27-2019" component="ccmsetup" context="" type="1" thread="4436" file="CcmCert.cpp:5054"> <![LOG[Unable to find any Certificate based on Certificate Issuers]LOG]!><time="13:40:00.188+240" date="09-27-2019" component="ccmsetup" context="" type="2" thread="4436" file="CcmCert.cpp:5237"> <![LOG[Failed to get client certificate for transportation. Error 0x87d00215]LOG]!><time="13:40:00.188+240" date="09-27-2019" component="ccmsetup" context="" type="3" thread="4436" file="requestresponse.cpp:280"> <![LOG[[CCMHTTP] ERROR: URL=https://xxxxx.xxxxxxx.local/ccm_system/request, Port=0, Options=63, Code=0, Text=CCM_E_NO_CLIENT_PKI_CERT]LOG]!><time="13:40:00.188+240" date="09-27-2019" component="ccmsetup" context="" type="1" thread="4436" file="ccmhttperror.cpp:306"> <![LOG[[CCMHTTP] ERROR INFO: StatusCode=200 StatusText=]LOG]!><time="13:40:00.188+240" date="09-27-2019" component="ccmsetup" context="" type="1" thread="4436" file="ccmhttperror.cpp:317"> <![LOG[Failed (0x87d00454) to send location request to 'xxxxx.xxxxx.local'. StatusCode 200, StatusText '']LOG]!><time="13:40:00.203+240" date="09-27-2019" component="ccmsetup" context="" type="3" thread="4436" file="ccmhttplib.cpp:322"> <![LOG[Failed to send location message to 'HTTPS://xxxxx.xxxxx.local'. Status text '']LOG]!><time="13:40:00.203+240" date="09-27-2019" component="ccmsetup" context="" type="3" thread="4436" file="siteinfo.cpp:163"> <![LOG[GetDPLocations failed with error 0x87d00454]LOG]!><time="13:40:00.203+240" date="09-27-2019" component="ccmsetup" context="" type="3" thread="4436" file="siteinfo.cpp:622"> <![LOG[Failed to get DP locations as the expected version from MP 'HTTPS://xxxxx.xxxxx.local'. Error 0x87d00454]LOG]!><time="13:40:00.203+240" date="09-27-2019" component="ccmsetup" context="" type="2" thread="4436" file="ccmsetup.cpp:11872"> <![LOG[Sending state '101'...]LOG]!><time="13:40:00.203+240" date="09-27-2019" component="ccmsetup" context="" type="1" thread="4436" file="state.cpp:72"> <![LOG[Updating MDM_ConfigSetting.ClientDeploymentErrorCode with value 0]LOG]!><time="13:40:00.203+240" date="09-27-2019" component="ccmsetup" context="" type="1" thread="4436" file="CcmUtilLib.cpp:3785"> <![LOG[OS is not Win10RS3+, ENDOK.]LOG]!><time="13:40:00.203+240" date="09-27-2019" component="ccmsetup" context="" type="1" thread="4436" file="CcmUtilLib.cpp:3790"> <![LOG[Failed to get client version for sending state messages. Error 0x8004100e]LOG]!><time="13:40:00.203+240" date="09-27-2019" component="ccmsetup" context="" type="2" thread="4436" file="state.cpp:169"> <![LOG[[] Params to send '5.0.8853.1000 Deployment Error: 0x0, ']LOG]!><time="13:40:00.203+240" date="09-27-2019" component="ccmsetup" context="" type="0" thread="4436" file="state.cpp:214"> <![LOG[A Fallback Status Point has not been specified and no client was installed. Message with STATEID='101' will not be sent.]LOG]!><time="13:40:00.203+240" date="09-27-2019" component="ccmsetup" context="" type="1" thread="4436" file="state.cpp:241"> <![LOG[Failed to send status 101. Error (87D00215)]LOG]!><time="13:40:00.203+240" date="09-27-2019" component="ccmsetup" context="" type="3" thread="4436" file="state.cpp:254"> <![LOG[Next retry in 10 minute(s)...]LOG]!><time="13:40:00.203+240" date="09-27-2019" component="ccmsetup" context="" type="0" thread="4436" file="ccmsetup.cpp:9662"> Also on the Event viewer I get the 1603 error client installer failed. Any help would be appreciate it.

Hello We currently have over 30 desktops, laptops and tablets models and never have any issues with sccm. Using currently version 1906 with 1809 boot image using windows 10 image. All computers go through the process with no issues except this new model of dell tablets. We are able to deploy just fine on the 5285 with no issues and they use m.2 sata drives. This new model is using nvme with is the only difference I see between these. When I try to boot up, it searches just fine using either legacy or uefi but right when its about to find the boot image to run before tasking task sequence, it goes to the menu where it is asking to retry boot pressing f1, got to bios f2, etc... I have tried pretty much everything I can thing of including injecting the newest dell windows pxe drivers and no luck. The options dell provide for this laptop to make changes in the bios didnt work either. I am able to see ipv4 and ipv6 just fine when pxe it just doesnt go pass the package where it grabs the boot image. I am not able to find logs for this since it all happens right before the task sequence starts. Any help would be appreciate it.

I was finally able to deploy my windows 10 LTSB Task sequence to the Surface pro 4 after finally getting the PXE fixed on it. Now I am getting this error when applying operating system on the SP4. I have used this TS before on multiple computers and this is the 1st time I get this error. Any tips?

I am trying to PXE boot surface pro 4 and for some reason it does not boot. It tries to PXE over IP v4, then reaches my correct DP that has PXE and WDS, it finds the correct NBP file SMSBoot\x64\wdsnbp.com, then without prompting to press Enter key for PXE boot, it moves to IPV6, then it resets and goes to boot to hard drive. I was able to get it to boot through usb with no issues but were looking to have this working with sccm 2012 r2 sp1 cu3 so we can deploy to more units in the future. I have tried: Upgrade firmware to latest DHCP option are not set, ALL systems are on the same vlan Booting from Ethernet Adapter Added surface pro adapter successfully to the X64 boot image I can PXE boot all other system except for this model only with no issues. Has anyone got it to work? SCCM 2012 R2 SP1 CU3 Boot Image 10.0.26624.0 SCCM NOTE: Found that device was attached to an already imaged SP4 listed in SCCM. I found this on SMSPXE.log. found this page useful to determine which device it was attached to. Also had some good useful reporting logs to use. I did the excluded adapter device in regedit to make sure I am able to reuse the device. https://blogs.technet.microsoft.com/configurationmgr/2015/08/27/reusing-the-same-nic-for-multiple-pxe-initiated-deployments-in-system-center-configuration-manger-osd/

I also had some issues with that current network card, this is what resolved my issue on multiple computers using that nic. https://www.windows-noob.com/forums/topic/13456-issues-with-boot-images/

Ok I finally got it to work with the I2I7-LM cards on optiplex 7040. My issue was that the link of the ADK that you gave me rocket had a different version of the RTM that you listed. I deleted that ADK and had to search for the RTM version you listed and added to sccm 2012 R2 CU3. At first I was getting that I couldn't add the boot image due to not finalized but once I completed the copype cmd with the ADK tools, I was able to get it to work. After completed, I used sccm 2012 to inject only the I2I7-LM driver from direct optiplex 7040 network folder and the computer was able to boot properly and went to the password option and beyond. I am testing the rest of the process to make sure I get a full complete process but I believe we got it. for future reference for those having problems with I2I7-LM card computers I used: BOOT Image both x86 and x64 : 10.0.26624.0 RTM OS Version 10.0.10240.16384 I2I7-LM Drivers : 12.13.17.4 INF file E1D65x64.inf Tested on SCCM 2012 R2 CU3 Thanks for the help Rocket-Man. I was able to get a lot more done this way.

Ok I created new boot images from the ADK that you mentioned ans just added the drivers through sccm 2012 r2 cu3 and the same results as before. right before when prompted to enter password that part on the menu doesn't not show up. the drivers that were added were directly from the dell optiplex 7040 network drivers. I tried to add only the I2I9-LM and also with adding all of them and both results were the same.

check the bios clock and it's correct. downloaded the network drivers and injected them using dsim to the winpe.win and the system still doesnt get to the login screen to input the password. I even /recurse using dsim all of the network drivers for this specific model and still nothing.

Tried what you recommended rocket, when and got a new boot.wim from the adk 10 and injected only the I2I7-LM drivers from WinPE listed on the dell websites in cabs and still the 7040 is canceling the boot image process right before when prompted to enter password. All other machines pxe boot just fine. So far I am having problems on the panasonic CF-311 models and these dell optiplex 7040 models.

I just got 6 dell optiplex 7040 and 1 micro and it uses the Intel Ethernet Connection I219-LM. I added the WinPE 5.0 and those successfully were added to the Boot Image x86 and x64. The system will start the boot process in Bios and goes to the screen were I can press F12 to the sccm 2012 splash screen and it goes blank right before entering the password set up in my manager. I have tried fresh image with no drivers and only installing the I2I9-LM, tried using winpe 5.0 and winpe 10.0 and nothing. I even dism and injected the drivers successfully to the boot.wim and the import that to sccm and still nothing. I have downloaded the network cd from intel to add the drivers and used the drivers cab from dell and nothing. I am running SCCM 2012 R2 SP1 CU3 with Windows 10 ADK 10.0.10586.0. It seems also that the same issue is happening with the same nic card on my cf-311 models from panasonic as well.

I get the same message when trying to deploy on one of my sp4. the other sp4 I got actually goes pass this point but does nothing after splash screen and goes back to start all of the pxe boot process again with no success.

Do you have a guide for windows 10 on surface pro 4? also what logs you need so I can attach them. The problem I am experiencing is that we have a windows 10 image that we deploy to various machines here that works using task sequence, when trying to deploy to the surface pro 4, the system goes to the process to pxe boot on one machine and goes all the way to the spash screen but no process gets started. On the other tablet, it does even start pxe boot. I been trying to look for a guide for specific windows 10 to surface pro 4 and cant seem to find one. I usually start looking here first since most of my deployment I created are from guides found here for guidance. We currently using sccm 2012 cu2. we dont use MDT 2013 or any other products.

I Been having some issues when trying to deploy my windows 10 image to the surface pro 4. The image seems to be working fine when deployment is done to all other desktop machines. I embedded the surface Ethernet adapter drivers to the boot image and updated the distribution point with it as well. We only have 1 distribution point at the moment and 1 DHCP. On 1 surface pro 4 when tested, the process goes all the way till the splash screen of sccm 2012 but nothing happens. The other surface pro 4 tablet, does go past the pxe boot process after we updated the firmware on it as mentioned by Microsoft that resolved the issue with pxe boot. Has anyone had a successful deployment to the surface pro 4 using a windows 10 x64 image?