Thanks for those links, that is exactly the issue I was having! However, changing the shortcut path only partly resolved the issue. First though, some background.
Server: Server 2008 R2 SP1
User Account: Is a Farm Admin, Local Admin, has all appropriate rights to the SP_Config Database
When I run the Sharepoint 2010 Management Shell as Administrator, I can execute SP commands with no issue. When I run either Powershell or Powershell ISE as Administrator, I continue to get “The local farm is not accessible. Cmdlets with FeatureDependencyID are not supported.”
The error when running a command is the following, with the only difference I can see from the articles you linked is that the version of .NET Framework is slightly different.
Get-SPFeature : Microsoft SharePoint is not supported with version 4.0.30319.261 of the Microsoft .Net Runtime.
At line:1 char:1
+ CategoryInfo : InvalidData: (Microsoft.Share...mdletGetFeature:SPCmdletGetFeature) [Get-SPFeature], Pla
+ FullyQualifiedErrorId : Microsoft.SharePoint.PowerShell.SPCmdletGetFeature
Edit: The reason I am trying to run the commands in Powershell ISE is that the SharePoint developers have created custom PowerShell scripts to run to deploy code for their custom application. In the past I have run these in PowerShell ISE, but I may have to just run them in PowerShell from now on. If I add -Version 2.0 to the PowerShell shortcut, everything loads fine and there are no errors. But if I try the same flag with PowerShell ISE shortcut, it freaks out. Doing some research it seems that it is not possible to run PowerShell ISE in 2.0 mode.
Thanks again for the links.