Does SharePointDsc need PowerShell v4 support?

This post has been republished via RSS; it originally appeared at: SharePointDsc articles.

When SharePointDsc started, PowerShell v4 was heavily used. Because of the way the LCM worked in PowerShell v4 (all runs were started under the SYSTEM account), we had to implement a workaround to make sure we were able to access the databases. This meant we required CredSSP to be configured and Verbose logging to be supressed.


With the introduction of the PsDscRunAsCredential in PowerShell v5 all of this belonged to the past. You could not natively specify a RunAs account, which no longer required CredSSP. Another benefit was better performance and Verbose logging to function properly.


Over the past years, we have most environment being upgraded to PowerShell v5. Pretty much every issue created in the issue list is mentioning the use of PowerShell v5. The WMF5.1 framework (which contains PowerShell v5) is available for all currently supported operating systems, so all environment are theoretically able to run PowerShell v5.


That is why we are considering dropping the support for PowerShell v4. But to make sure we aren't overlooking anything, we are interested in what you think! Are you still using PowerShell v4? Is there a specific reason you are not upgrading to PowerShell v5? Do you see any reason for not dropping v4 support? Is there anything we might not have thought of?


Please join the discussion in the following issue in our issue list:

REMEMBER: these articles are REPUBLISHED. Your best bet to get a reply is to follow the link at the top of the post to the ORIGINAL post! BUT you're more than welcome to start discussions here:

This site uses Akismet to reduce spam. Learn how your comment data is processed.