Jump to content


Established Members
  • Posts

  • Joined

  • Last visited

  • Days Won


jfdensmore last won the day on June 8 2017

jfdensmore had the most liked content!

About jfdensmore

  • Birthday 02/22/1980

Profile Information

  • Gender
  • Location
    Freeport Pa.

jfdensmore's Achievements


Newbie (1/14)



  1. Ok, thanks again. Truly appreciate the time you guys take helping us out! Have a great rest of your week.
  2. Well that appears to be the issue! Thanks. Now could you kindly point me to a process on how to remediate this? I have searched for ways to fix duplicate GUID's but everything seems outdated or very vague...
  3. We recently purchased another company, and we haven't merged them into our domain yet. So they are in a separate forest. I can ping their devices from SCCM, and i can C$ to them. But i cannot get SCCM to detect them. I would like to start managing their computers. Is there a way for me to do this? If so what is the recommended solution? Currently i have a boundary configured to use their IP Range. And i have added it to my Boundary Group. But still nothing.
  4. So I have tried everything i can to get this working but i keep getting the same results. (See smsts.log attached) Earlier you had me double check all my Settings, and i did. Then you caught this little bit in my smsts.log: So i went through it again today, and... In reviewing your documentation i see in step 3 of your "How can I configure System Center Configuration Manager in HTTPS mode (PKI) - Part 1" That you refer to Part 8, Step 3 of your: How can I configure PKI in a lab on Windows Server 2016 - Part 8 And in this step i see here that in your CDP Container, you have 3 Certs, one being a "Root CA" . Now when i compare this to mine, i don't see this "Root CA" Could this be the "Root" of my problem (Pardon the pun) I am not knowledgeable at certificates, nor is the person here who set them up. So im wondering if something has been missed or if something needs to be created?? Just looking for direction at this point. Thanks again in advance. smsts.log
  5. Not a problem. I was simply moving my SCCM configuration over to "HTTPS only". Was not doing it just to get PXE to use HTTPS directly? This just started happening once I completed the change over. And i cant figure out why.
  6. Sure let me get it installed. Sorry, Sent you a PM incase you were waiting on me.
  7. It was in trouble shooting, but we are distributing 1903 so I needed to at some point anyway. Should i maybe revert to see if there is an issue there?
  8. Once i enabled HTTPS, i had everything working, a day later i had to do an OSD via PXE and that is when i noticed it failing at the splash screen after i put in our password. In troubleshooting this, one of the first things i did was update the boot images*. Then i came here for help.
  9. Absolutely, both Step by step! Twice! That is what is driving me batty! Don't know if it matters, but these are "Unknown" Computer's i am pxebooting in this case. Gonna look at the other method now.
  10. Well after reviewing i cant see where i am going wrong! i went through step by step. and have done everything. But you said missing certs in the "Boot Image" At what point are the certs imported to the Boot image, maybe that will help me understand what is going on?
  11. Well damn. I must have missed something, Thank you so much for going through the trouble. I'm looking at this again now.
  12. Well i thought it might be a time issue, since it was set to PST, So i changed it to our local time and it still failed. I do still see this in the SMSTS.log: SyncTimeWithMP() failed. 80072f8f. TSPxe 8/28/2019 12:46:36 PM 1100 (0x044C) Attached is complete SMSTS.log. smsts1.log
  13. I try this, but f8 does nothing for me, i have updated my boot images to 1903 , and verified the option is checked. Wow Noob moment there, I have to hit the FN key for F8 to function properly..... Sorry, checking log now. THanks.
  14. Perhaps this will tell you something: When i look at my smspxe.log i get: WARNING: _SMSTSRootCACerts Not Set. This might cause client failures in native mode. SMSPXE 8/28/2019 7:41:03 AM 14064 (0x36F0) WARNING: _SMSTSCertStoreName Not Set. This might cause client failures in native mode. SMSPXE 8/28/2019 7:41:03 AM 14064 (0x36F0) WARNING: _SMSTSCertSelection Not Set. This might cause client failures in native mode. SMSPXE 8/28/2019 7:41:03 AM 14064 (0x36F0)
  • Create New...