Can’t Find PowerShell Modules Shortcut

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 Windows Management Framework 3

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.

Forum Fixed

Sorry it took so long for what turned out to be a quick & easy fix.

It looks like there’s a new version that may work better than what I have now. Need to look into that and see if my plugins will work, or if there are work-arounds that’ll take care of those features for me.

Forum Errors

Oh heck! Something broke the forum. I’ll have to look into that…

SharePoint 2010 ‘allowInsecureTransport’ error

I’ve been working with SharePoint 2010 and Word Automation Services quite a bit these days. I recently ran into an error that I just could not figure out. There’s very little out there on teh interwebs, and the only solution that I found sounded perfect. At first.

When attempting to convert a file from .docx to .pdf via Word Automation Services we were receiving:

Unrecognized attribute ‘allowInsecureTransport’. Note that attribute names are case-sensitive. (D:\Program Files\Microsoft Office Servers\14.0\WebServices\WordServer\Proxy.config line 77)

This was a brand new SharePoint install and everything appeared to be configured correctly. The ONLY solution that I could find was to apply a .NET hotfix (KB976462). It made sense. It sounded perfect! However… the .dlls that the hotfix wanted to apply were at an older version than what was already on the SharePoint server. At this point, we opened a case with Microsoft… (more…)

Make the Most of Your SharePoint 2007 Wiki

On a normal day lately, I’ve been either migrating old 2003 sites to 2007, or finding ways to implement functionality that’s not exactly “out of the box” to accommodate various needs. This usually involves a few “related” lists, maybe some custom SPD workflow, and a DVWP or two. It’s fun! And then… I need to document what I’ve done for either the users to understand how to use it, and what to expect. Or more likely, for myself to refer to down the line when someone asks me to go back and support it 😉

Sure, you can use the SharePoint wiki as-is. It’s fine. It “works”. But I like to take it a step or two further. Here are some “extras” that I implement on most wikis that I create these days. (more…)