Incorrect Discovery Method Status reported

paulwetter / DocumentConfigMgrCB

This script attempts to document your entire Configuration Manager (MEMCM/SCCM) environment

https://wetterssource.com/documentconfigmgrcb

174 stars 45 forks source link

Incorrect Discovery Method Status reported #57

Closed Skatterbrainz closed 4 years ago

Skatterbrainz commented 4 years ago

The site discovery methods is showing "disabled" for all methods, even though all but network discovery are enabled.

paulwetter commented 4 years ago

Hmmmmm. I will take a look this weekend. If probably have a decimal point in the wrong place somewhere. I always miss some mundane detail. 🙂

paulwetter commented 4 years ago

Hmmm.... I am not seeing this at my end.... Server OS, CM build, and PowerShell version you running against?

ChadSimmons commented 4 years ago

I could not reproduce the issue. Windows Server 2012 R2, CM 1906 (5.0.8853.100), PoSH 5.1.14409.1018

Alpanama commented 4 years ago

This issue could be produced by running the script from a computer, not from the MECM/SCCM server. Do you get the "Get-WmiObject : Invalid namespace "ROOT\SMS\site_XXX" error from the script? If so, try to run it from the server, mainly because the namespace "ROOT\SMS..." does not exist on a computer but in the MECM/SCCM server. This is what happened to me...

paulwetter commented 4 years ago

Thank you @Alpanama . This helps a bunch. I was missing the computername parameter on my WMI queries. Should be fixed in the latest push tonight. I has some other items in the build that I hope i had finished. (was working on Phased Deployments).

So hopefully everything is working in 3.52 now (9d47bbca56907a55084b680b7ab0935e6e1e2ff4)

paulwetter commented 4 years ago

So, closing. Pretty sure this is fixed.