SanAntonioITGuy
-
Posts
9 -
Joined
-
Last visited
SanAntonioITGuy's Achievements
Newbie (1/14)
0
Reputation
-
Thanks Peter.. just saw your post as I submitted mine. appreciate the info!!
-
Detection method is fine. I ended up figuring it out yesterday evening then proceeded to drink both our shares of single malt. I intentionally changed the test to be non-compliant "not equal to" and discovered that the detection method looks at two places in the registry... even if specifically pointing it to the registry path in this case: HKLM:\Software\Microsoft\Windows\CurrentVersion\OEMInformation. The detection also looks at the 32bit side of the house: HKLM:Software\Wow6432Node\Microsoft\Windows\CurrentVersion\OEMInformation. Checked the box "This registry value is associate with a a 64-bit application" and all is right with the world. Thanks to Jason Sandys's post I also added %windir%\sysnative\WindowsPowerShell\v1.0\powershell.exe to my scripts in SCCM to make sure they always run at the architecture level of the OS. Appreciate the help Garth.
-
nothing changed from adjusting the detection time.
-
Okay, I can adjust those to a point, however one of the items is the support website. I just used the SupportHours item as an example of the typical format of each item. I will make the time changes shortly.
-
Compliant.
-
I am sure there are not two computers with the same name. I have forced the client to recheck and nothing changes. Also, this has been going on for a few weeks so the scheduled check would/should have picked it up as well. Thank you again for your time. It is much appreciated.
-
it is in this group. Hope this helps.
-
Thank you Garth for responding back so quickly! Yes the CM shows the object as compliant.
-
Hello other WIndows-noobians! I am having a configuration item issue. I have many objects that show compliant but they are not. There is a lot of sites that show how to create Configuration Items but troubleshooting seems to evade my google foo. This initial screenshot is the message shows “compliance”. Clearly not in compliance... ...very sad the CI settings: These settings are built into the task sequence but when things change (like switching the support site to https later this year) it would be nice to come here and edit the CI and have the systems update when necessary. The system described here is a large portion of systems that were imaged before SCCM was in place. I'd rather do the changes through SCCM and not a GPO. Any assistance you can provide would be greatly appreciated. Thank you for your time. Steven
