
jfdensmore
Established Members-
Content Count
49 -
Joined
-
Last visited
-
Days Won
2
jfdensmore last won the day on June 8 2017
jfdensmore had the most liked content!
Community Reputation
3 NeutralAbout jfdensmore
-
Rank
Advanced Member
- Birthday 02/22/1980
Profile Information
-
Gender
Male
-
Location
Freeport Pa.
-
Device name mix up?
jfdensmore replied to jdensmore's topic in System Center Configuration Manager (Current Branch)
Ok, thanks again. Truly appreciate the time you guys take helping us out! Have a great rest of your week. -
Device name mix up?
jfdensmore replied to jdensmore's topic in System Center Configuration Manager (Current Branch)
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 Co
-
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)