Closed terjohnny closed 5 years ago
Thanks @terjohnny for taking the time to share this with the Configuration Manager documentation team. I’m sorry that you’re having problems, and I want to make sure it gets to the right people that can help. There are a couple of options available to provide the best level of support for this:
I'm closing this issue as there's nothing actionable for docs at this time.
Actually there is something that you should update in the documentation. Although you mention that some features work only with Powershell 5.0, you don't mention the minimum version to use other features. In my case, I had windows 7 with Poweshell version 2.0 and nothing works. I upgraded to version 4.0 and most commands work. Can you add a minimum powershell version required by CMPivot?
Thanks for the followup. I'm reopening this issue, and will check on the prereq.
There might be some functions that work with an older version, but we're going to go with PowerShell v4 as a baseline prerequisite. Thanks for calling this out @terjohnny.
Beware if you use bit9 or similar technologies, you'll get alerts (and a lot of helpdesk calls!) from all clients about a script being blocked in c:\windows\ccm\scriptstore as well which can also prevent successful execution of the CMPivot scripts.
Thanks @russrimm, good tip!
This issue is closed because @mestew made changes to this article, which should publish later today.
I have a weird issue regarding CMPivot, it runs but it returns failure on most computers in the environment. The one that work are just random and a small percentage of the PCs (10%), all the logs seem to look OK. Are there any known bugs to this? Any checks worth doing?
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.