We currently run SharePoint 2010 Enterprise in our production environment and are looking at updated our build and deploy framework that is written in PowerShell. It would be nice to take advantage of PowerShell v3 in some instances, however, with all that I have read warning not to install PowerShell v3 in a PowerShell 2010 environment I am wondering if there are other opertaions that might be affected by this install as well. With some of the warnings about installing PowerShell v3 with SharePoint 2010 I can think of workarounds, as will some others in my IS group, so to be prepared I would like to get an idea about the background operations that SharePoint does and what is affected.
Working around the issues with the Management Console is possible by changing shortcuts, the Remoting we would be doing would need updating, but so long as we have the final version of the WMF in place that should not be an issue. So I would like to know if:
- Are there SP Jobs or processes that utilize PowerShell at all? Many of the cmdlets we use to get details on SP Content Databases or processes could potentially be used by the various background jobs that run, but I do not know for sure.
- Do the Scheduled Jobs use PowerShell at all? I do not know all the details of the Jobs as I usually deal with SP on an Administrative level using the Central Admin Console and only use the Management Console when troubleshooting issues.
- Are there areas that might be affected that I have not touched on? SP is complex, and has many moving parts I do not normally deal with, so I do not want to forget something else.
- If we updated to SharePoint 2013 would these issues be resolved? I realize this is a bigger project, but it would be nice to have some information on this for anyone who is using SP 2013.