SharePoint 2013 includes a ton in common with older versions, especially its love of PowerShell and connected security controls. If you are attempting to run some native 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.”

SharePoint-2013-Hosting1-e1415845299929
1
This isn’t much totally different in 2013. just as in SharePoint 2010, this happens for one of 2 reasons:

  1. The native account does not have rights to the SharePoint_Config database (dbo or sa)
  2. You launched PowerShell or the PowerShell ISE without choosing Run as Administrator.

Quick tip – Windows 8 and Windows Server 2012, with the modern UI, create it very easy to miss the Run as Administrator option. From the start Menu screen, right mouse clock in an open area to crop 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:

2

Select Run as administrator and you should be PowerShell-ing like a SharePoint champion.