Can someone point me in the right direction please? I am new to sccm and I have installed the 1802 version, using the guides on this site, which are excellent and then done an in place upgrade to 1810. When i am trying to push the client to a few test machines, by selecting them individually in Devices I am getting errors. IsSslClientAuthEnabled - Determining provisioning mode state failed with 80070002. Defaulting to state of 1504.
Client is not allowed to use or doesn't have PKI cert while talking to HTTPS server.
Failed (0x87d00454) to send location request to 'serverfqdn'. StatusCode 200, StatusText ''
Failed to send location message to 'HTTPS://serverfqdn'. Status text ''
GetDPLocations failed with error 0x87d00454
Failed to get DP locations as the expected version from MP 'HTTPS://serverfqdn'. Error 0x87d00454
Failed to find DP locations from MP 'HTTPS://serverfqdn' with error 0x87d00454, status code 200. Check next MP.
Have already tried all MPs. Couldn't find DP locations.
IsSslClientAuthEnabled - Determining provisioning mode state failed with 80070002. Defaulting to state of 1504.
Client is not allowed to use or doesn't have PKI cert while talking to HTTPS server.
DownloadFileByWinHTTP failed with a non-recoverable failure, 0x87d00454
DownloadFileByWinHTTP failed with error 0x87d00454
Failed to get client version for sending state messages. Error 0x8004100e
Failed to send status 308. Error (87D00215)
Could not open Wmi_Bridge_Server kegistry key.
Failed to connect to policy namespace. Error 0x8004100e
Failed to revoke client upgrade local policy. Error 0x8004100e
CcmSetup failed with error code 0x87d00454   I know there are a lot of errors here but I am very new to SCCM and would like to try and get it sorted.  Thanks
 

We've had a lot of interest in the latest Tranxition Migration Manager SCCM Integration Guide.   It was recently updated to the latest branch.  You can find it in the blog section on the Tranxition website or at the link below.  Thanks everyone! https://tranxition.com/2019/01/tranxition-releases-sccm-integration-guide/

Hi All, SCCM 1802. I have two boot images, 32 and 64 bit. Both have Enable Command Support ticked. I have one build TS and it is booting the 64 bit boot image. The laptop is set to UEFI. At boot it displays the TS list, we select the only one there and the laptop begins running the TS. It gets to a point "Applying OS to C drive" and errors. Timeout is 14 mins and if we press F8 nothing happens. I really need to get the logs off this machine but I am remote to it. Ive tried adding some steps into the TS to collect the logs but thats failing to create anything in my share. I dont understand why the F8 key press is not working though. Does anyone have any advice they can offer?

We are facing issue with content distribution on a new DP.

In March 2017 I blogged a method to allow you to forcefully upgrade your Windows 10 (or Windows 7) computers  to the latest version of Windows 10 using a popup (HTA) that gives the user some form of control (5 deferrals). This was very popular and spawned different versions of the same original concept by other MVP’s and the community at large. I always wanted to update mine, but never had time, however what I have done is incorporate bug-fixes and features, and rewritten the original VBS wrapper code to PowerShell. In the next version I’ll replace the HTA with a PowerShell gui. So how about listing the features of this solution. Designed to run as required Runs before the task sequence starts Shows the user a popup with options Can run on Windows 7 or Windows 10 Allows deferrals After deferrals run out, starts a 4 hour timer If the user ignores the popup, subtracts one deferral after 8 hours Checks for Power Checks for hard disc free space Checks for Supported Model Checks for VPN Is easy to Brand with your company details Has several checks to ensure it won’t run by accident So that’s enough of the features, here’s a look at what it will look like to the end user running either Windows 10 or Windows 7. Time to upgrade In the above screenshot, the user sees the popup daily at a time that you decide eg: 11am. The user has a number of choices: Upgrade now by clicking on the box ‘my files are backed up’, and then selecting Upgrade now Upgrade later by clicking on Defer Cancel, by clicking on the X in the top corner, this will remove one deferral. Note that this verifies how many deferrals are left and if there are none left, will start the task sequence Do nothing. The popup will auto close after 8 hours and remove one deferral. Kill it with Task Manager, this will remove one deferral. If the user runs out of deferrals the 4 hour timer will start. If the user still does nothing, when the 4 hours runs out the task sequence will begin. They can of course click the checkbox and select Upgrade now to start it at any time. Branding So how can you add your branding to it ? start with the banner.png. Open it in MSPaint and replace the windowsnoob logo with your own, try and keep it to 500×65 pixels otherwise you’ll need to edit the Upgrade.HTA code also. Next, open the wrapper.ps1 in PowerShell ISE. Edit CompanyName in line 15 to suit your Company Name. Save the changes, next, open upgrade.hta in Notepad ++. Edit CompanyName in line 50 to suit your company name.   edit line 395, and put your company name in       Troubleshooting The popup creates 3 log files in C:\ProgramData shown below Windows10RequiredUgradeHTA.log Windows10RequiredUgradeWrapper.log Windows10RequiredUpgradeStart-Upgrade.log The process creates registry keys (and deletes them upon successful closure of the HTA before starting the task sequence). For more details about how to set this up in your environment, please see the following blogpost. I’ve updated that blogpost to include the new files and the PowerShell wrapper.ps1. Note: To download the files included, you need to be a registered member of windows-noob.com   cheers niall

I just installed the 1810 update and was looking through the 'What's New in 1810' post.  I came across the item about LifeCycle Report 'LifeCycle 05A', but I don't see that report listed in my Reporting folder under Monitoring. Is there a way to get that report ?  I am thinking if I remove/re-add my Reporting Point?  But if I do that, I will probably lose any customized reports? thanks, James

Hey everyone, Im hoping someone out there has had a similar issue and can provide assistance. Here are our versions SCCM CB 1806 Build 8692
Using USMT 5.0 on Windows 10 1803
Leveraging SMP on SCCM. The whole process is working as expected. The users state gets uploaded to the server, and then restored back on to the PC through the rebuild task sequence. What isn't working is the USMT node in SCCM. It is always empty. We had a machine listed once, but I have not been able to see anything in there ever since deleting the User Data from that first instance. I have tried removing the role and re-installing it and still have no success. the smpmgr.log only has the following entries: Any assistance would be greatly appreciated. Thank you very much MDS  

Hi,

I have upgraded my lab to 1810 recently. And I think something is broken.

The lab is setup in Hyper-V and used to work fine before.

Ever since I've upgraded, my deployments are not working.

A couple of errors from smsts.log:
"Network access account credentials are not supplied or invalid."
"Failed to get client identity (80004005)"
"failed to request for client"
"SyncTimeWithMP() failed. 80004005."
"Failed to get time information from MP: http://LAB-CFG.Domain.com."

Now, I've seen this error before in our Live environment and back then it was an issue with the date and time on the clients.
I solved that with a pre-start script that syncs the time.
However, in this case, the VM's time is correct. So it's not a problem with the date and time.

The Network Acces account is obviously configured correctly. Tripple checked this.
I can ping the server. I mapped a network share with the Network Access account from WinPE successfully, password is not expired...
I've also reset the password of the NAA and tried with that. But no changes here as well.

I've checked certificates of the DP and the Boot Media. Both are still valid.
I have this problem when I PXE boot and when I boot from a Boot Media ISO.

I even created a new Boot Image, distributed content and Updated DP.
PXE and new ISO still same issue.

I've then created a new DP on a separate computer (used to be a role on the Site Server) but still same issue.

Boundaries are correct.

I don't see errors in the Component Status.

Any idea where I have to look next?
It's in a lab, so not critical, but I've put a lot of effort into setting up this lab and don't really want to start from scratch.

Also, this makes me think, it started after I've updated to CM 1810. I'm afraid this might happen in Live env as well.
So I want to sort this out before I upgrade my live environment.   smsts.log file attached smsts.log