The new server build process seemed to have changed slightly for my most recent SharePoint 2010 server. Everything looked for the most part as it should, but there were still a couple of minor things here and there that just seemed slightly different.
Fast forward in time – I have SharePoint installed, patched, and configured. Now I need to run some PowerShell commands to check a few things – but there aren’t any PowerShell items under All Programs > Administrative Tools as there is on my other servers. Sure, I have the basic “Windows PowerShell” folder under “Accessories,” but that’s about it.
Normally I’d say “ok, no problem” and move on, but I wasn’t even able to add my SharePoint snapin in a normal PowerShell window as a work around:
PS C:\>add-pssnapin microsoft.sharepoint.powershell
The local farm is not accessible. Cmdlets with FeatureDependencyId are not registered.
After a bit of research I found that it’s an issue with some combination of Windows Server 2008 R2 SP1, .NET 4, and PowerShell 3. Doesn’t Microsoft make all 3 of these? Why can’t they play well?
Anyway. No need to uninstall .NET 4 or any crazy work-arounds. Just go to Control Panel > Uninstall a Program > View installed updates > and search on “Windows Management Framework.” You’ll likely have “Microsoft Windows Management Framework 3.0 (KB2506143)” installed.
Uninstall it and reboot when finished.
Like magic, I now have my “Windows PowerShell Modules” app link that loads everything I need, as well as the “SharePoint 2010 Management Shell” under the SharePoint folder!
Thanks to Trevor’s answer in this thread for saving my day. I figured I’d post this here for my own future reference, and also because my scenario started out slightly different than original topic in that thread.