During this session I found it interesting how much time was spent talking about mirroring. Mirroring is now considered a deprecated technology but is still supported by SharePoint 2013. Today I’d like to break down the session and talk about my thoughts on each point.
We’re out at the SharePoint Conference 2012 this week and learning a ton about the new features of SharePoint 2013. One of particular interest to the IT pros should be the introduction of PowerShell 3.0. There are a number of new features available in PowerShell 3.0 not to mention the cmdlets!
During yesterday’s breakout sessions, I attended Sean Livingston’s session on SharePoint 2013 Upgrade. A few minutes into the presentation, Sean offered up a quip that is certainly true across any platform level migration: “Upgrades lead to unpleasant feelings between the users and the IT staff.”
To be fair, upgrades bring “new stuff,” which often the users are clamoring for. However the process of designing, engineering, implementing and provisioning the upgrade tends to be long running, particularly where large blocks of content must be migrated from one version to another. Upgrade plans must carefully balance the run times required to upgrade the content, training time for users and other background tasks against the need to keep serving up content through the transition. Migrations can be a headache from start to finish. However, several features in SharePoint 2013 aim to ease the upgrade process, if not completely avoid all headaches.