I avoided the temptation to add titles like:
- Meet the New Boss, Same as The Old Boss
- What's New Is Old Again
- Hi, Remember Me?
SharePoint 2013 has a lot in common with older versions, especially its love of PowerShell and related security controls. If you're trying to run some local commands, even before you register SharePoint with:
Add-PSSnapIn Microsoft.SharePoint.PowerShell –erroraction SilentlyContinue
You may be faced with this error message: "The local farm is not accessible. Cmdlets with FeatureDependencyId are not registered."
This isn't much different in 2013. Just as in SharePoint 2010, this happens for one of two reasons:
- The local account doesn't have rights to the SharePoint_Config database (dbo or sa)
- You launched PowerShell or the PowerShell ISE without choosing Run as Administrator.
Quick tip - Windows 8 and Windows Server 2012, with the Modern UI, make it really easy to miss the Run as Administrator option. From the Start Menu screen, right mouse clock in an open area to pop up the All Apps charm at the bottom of the screen. Find the PowerShell ISE app and, again, right mouse click on it to fly in the Charms shown below:
Select Run as administrator and you should be PowerShell-ing like a SharePoint champion.