jfdensmore

Ok, thanks again. Truly appreciate the time you guys take helping us out! Have a great rest of your week.

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...

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.

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

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.

Sure let me get it installed. Sorry, Sent you a PM incase you were waiting on me.

Sure let me get it installed.

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?

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.

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.

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?

Well damn. I must have missed something, Thank you so much for going through the trouble. I'm looking at this again now.

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

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.

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)

Sorry bad terminology on my part, we run primary, not CAS. Thanks for the info! I have actually seen some of Johan's trainings, i will take you up on that and see what i can get my work to approve! I actually do have intune installed doing co-management, but i don't do anything with it as i haven't had time to educate myself. SCCM and Intune is a big project for me in the near future. Back to initial problem, I have verified your instructions and i appear to have everything correct. Still not getting past the Splash screen. Ill try to locate your guide on using ConfigMgr to handle our PXE Service. That sounds like the proper way to do it.

Thank you! I will check this out asap! Before i go too far, which of these methods do you recommend? Our environment consists of 3 physical locations that in the future will each contain their own distribution point, one central server ("To rule them all"), and i would to PXE at these other locations at some point as well. Any advice would be greatly appreciated! @anyweb Do you guys recommend any training courses for SCCM? I have been using SCCM for about 6 years now and i love it for what we use it for. But i feel like i have never been able to get completely comfortable with all it can do. Currently i have learned all i know from awesome people like you and those on these sites. But say i wanted to become Certified in it which route should i take?

What i mean is, i had PXE working just fine using DHCP Scope options. Just last week i converted my Site to "HTTPS Only" and everything went great and is working well except for PXE Booting. Currently I can get a computer to PXE and then get to the SCCM Splash screen, put in a password, then it sits there at retrieving policy for a few minutes, then reboots. After trouble shooting this for a bit im wondering if i need to rethink how i configure PXE booting. Is the DHCP WDS method outdated? Or perhaps does it not work with HTTPS? is there a definitive guide out there to set this up?? Working with HP Switches. Thank you for taking some time to check this out, Appreciate all your help out there!

Hello again Garth, i want to ask you this before i create a new post in se it is a related issue to this previous one...... I noticed in my devices list i am starting to see users populating in my "Currently Logged on User" field. But there arent very many. Is there something that might be preventing this information from populating on most of my machines?

Good enough for me! Thank you very much for your time on this. Greatly appreciated!

Sorry, yes it did work. the build numbers are being corrected and filtered out of the group. My question was, what is causing my inventory to be confused like that?

Bingo! That is clearing them right up! Now my next question, what is causing that? My sccm clients are all up to date, and i didn't see any log files that identified this issue?

Well, dang! How do you explain that? Indeed using resource explorer it is listed as 16299! So what is wrong here?

Ha, It's crazy i know , i have rebuilt it a few times, but it constantly returns the same group of 1803 computers. I have also verified that those computers were running 1803 as well. I don't know what the heck to do. Thanks a bunch for double checking my work though.

Sure, Thank you for taking a look at this! Do you want the Query Statement? select SMS_R_SYSTEM.ResourceID,SMS_R_SYSTEM.ResourceType,SMS_R_SYSTEM.Name,SMS_R_SYSTEM.SMSUniqueIdentifier,SMS_R_SYSTEM.ResourceDomainORWorkgroup,SMS_R_SYSTEM.Client from SMS_R_System inner join SMS_G_System_OPERATING_SYSTEM on SMS_G_System_OPERATING_SYSTEM.ResourceID = SMS_R_System.ResourceId where SMS_G_System_OPERATING_SYSTEM.BuildNumber = "16299"