search

paulwetter / DocumentConfigMgrCB

This script attempts to document your entire Configuration Manager (MEMCM/SCCM) environment
https://wetterssource.com/documentconfigmgrcb
174 stars 45 forks source link

Get-ClientSettingsConfigs is producing an error #88

Closed pcchenard closed 3 years ago

pcchenard commented 3 years ago

The script is producing the following error. Any guidance would be appreciated.

Get-ClientSettingsConfigs : The term 'Get-ClientSettingsConfigs' is not recognized as the name of a cmdlet, function,
script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is
correct and try again.
At C:\DocumentConfigMgrCB\DocumentCMCB.ps1:5211 char:5
+     Get-ClientSettingsConfigs -AgentConfigs $DefaultCS.AgentConfigura ...
+     ~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : ObjectNotFound: (Get-ClientSettingsConfigs:String) [], CommandNotFoundException
    + FullyQualifiedErrorId : CommandNotFoundException
paulwetter commented 3 years ago

Ahhhh... See it. Use the -ListAllInformation for now as a workaround. I put the function in the middle of a optional block and without that switch, it doesn't create the function. I'll move things around this weekend to fix it.

brunoramosdematos commented 3 years ago

Hi Paul - any chance you had the time to look at this bug yet? I did try running the command with the following parameters:

-ListAllInformation -CompanyName "Sisk Group" -AddDateTime -MaskAccounts

However, I am still getting same error message as specified by pchenard above.

Kind regs, Bruno

paulwetter commented 3 years ago

I haven't fixed it yet. Been distracted over the summer. However the workaround should do it. Please post the exact error text that you are receiving in case I missed something.

brunoramosdematos commented 3 years ago

I haven't fixed it yet. Been distracted over the summer. However the workaround should do it. Please post the exact error text that you are receiving in case I missed something.

Hi Paul - It follows the screenshot with the PowerShell output showing the error below:

FYI - it's showing a different line number but that's just because I deleted 4 line breaks to see if it would make a difference. The original error without making any modification to the PowerShell script is throwing the error at line 5211.

image

Kind Regs, Bruno

paulwetter commented 3 years ago

I updated but didn't test yet. Guessing this environment you are running against didn't have any custom client settings, only the default? Try latest 3.65 version just updated.

brunoramosdematos commented 3 years ago

I updated but didn't test yet. Guessing this environment you are running against didn't have any custom client settings, only the default? Try latest 3.65 version just updated.

Thanks Paul - I will test this out an let you know how it goes.

brunoramosdematos commented 3 years ago

I updated but didn't test yet. Guessing this environment you are running against didn't have any custom client settings, only the default? Try latest 3.65 version just updated.

Hi Paul,

That has definitely fixed it! :)

Thanks again!

Kind Regs, Bruno