CMPIVOT was working and then all of a sudden almost all respond as a failure "Unsupported Powershell Version". The few that do return results have the exact same version of powershell as the PC or server. Cannot find where this is coming from. If I go into MECM and look at Client Operations those same cmpivot queries show no failures. Thanks for the help
Would like to add that the Microsoft Code Signing PCA 2011 expired 12/21. Exported certificate from C:\Program Files (x86)\Microsoft Endpoint Manager\AdminConsole\bin\cmpivot.exe. Imported and still receiving same error.
Try reviewing the scripts.log on the clients with the failure for more info (CMPivot is mainly just a really cool PowerShell script that ConfigMgr runs on the clients).
Scripts.log shows all steps running without any errors. Also if I look at "Client Operations" under Monitoring and look at the cmpivot results it does not show any errors but in the cmpivot results there are nothing but failures or offline
Hi @TomShelton-4927，
Target clients require a minimum of PowerShell version 4.
To gather data for the following entities, target clients require PowerShell version 5.0:
Administrators
Connection
IPConfig
SMBConfig
Here is the article we could refer to:
https://docs.microsoft.com/en-us/mem/configmgr/core/servers/manage/cmpivot#prerequisites
Agree with Jason, please check scripts.log to see any error in it. Besides, we could check if the version of powershell is supported.
If the answer is the right solution, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.
Hi,
Just checking in to see if there is any update. We haven't heard from you for a few days and would like to know the current status of the problem. Is the problem solved? Do you need any further assistance? Look forward to hearing from you.
Thanks for your time.
Best regards,
Amanda
No errors in scripts.log, client operations shows that cmpivot was successful showing no failures even though cmpivot shows failure.
After doing the 2107 upgrade this apparently changed the path of the MS PCA 2011 signing certificate to different serial number. When we compared serial numbers from their lab and our environment of the PCA 2011 cert they were different. Microsoft provided the required certificate with the correct serial and all is good now.
Thanks
We just ran into this exact same issue; our cmpivot queries are all broken now. Is there anywhere where we can all get the cert and where did you replace it?
4 people are following this question.
