If using the “Open with Windows Explorer” option in SharePoint is slow use the following procedure to fix this and increase the performance:

1. Open Internet Explorer
2. Go to the Menu “Tools” > “Internet Options” then go to the “Connections” tab
3. Click on button “LAN Settings”
4. Uncheck the box “Automatically detect settings” (culprit)
5. Close and restart all running Internet Explorer processes
6. Restart the “Web Client” Service, if needed.
7. Try it again!

via Open with Windows Explorer in SharePoint (Fix Slow WebDAV Performance on Windows 7 / Vista)

The Windows PowerShell Command Builder for SharePoint 2010 Products and Office 365 is a Silverlight application that enables IT pros and power users to visually assemble commands in the browser and then take those commands to their respective products.

Click to open the Windows PowerShell Command Builder in a new browser window.

For additional information, see the Getting Started Guide.

If you get an error like the one in the image below, recycle your website’s application pool.

GDI+ Is Not Properly Initialized (GDI+ Error)

Tobias Zimmergren has a great post on his blog that explores the User Information List. 

Here is an excerpt:

The User Information List can be accessed (Only if you’re admin) via the browser by navigating to /_catalogs/users/simple.aspx from your site. (Ex: http://zimmergren/_catalogs/users/simple.aspx)

This works for both Windows SharePoint Services 3.0 (WSS 3.0) and Microsoft Office SharePoint Server 2007 (MOSS 2007)

Tobias Zimmergren has a great post on his blog that explores the User Information List. 

Here is an excerpt:

The User Information List can be accessed (Only if you’re admin) via the browser by navigating to /_catalogs/users/simple.aspx from your site. (Ex: http://zimmergren/_catalogs/users/simple.aspx)

This works for both Windows SharePoint Services 3.0 (WSS 3.0) and Microsoft Office SharePoint Server 2007 (MOSS 2007)

Nick Grattan has a great post about the location of the SharePoint 2010 Global Resource File Locations. 

:\\VirtualDirectories\\App_GlobalResources C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\Resources C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\CONFIG\Resources

And how they are used:

• Resources files in App_GlobalResources are used when code in an ASPX page refers to a resource, e.g.
  
• Resources files in the Resources folder are used when referencing resources using the SharePoint object model, e.g.

btnExport.Text = SPUtility.GetLocalizedString("$Resources:GlobalSiteResources, Tab_Export", "GloablSiteResources", language);

• Resources files in the Config/Resources are copied into the App_GlobalResources folder whenever a new web application is created. By adding the resx files here you will ensure your application will be able to access its global resource files in new web applications.

Joel Oleson,  aka SharePoint Joel, has an interesting article about how the LDS Church uses SharePoint & Social Networks to get their message to the masses.

Now I don’t endorse the LDS Church, but they are more advanced than any other religious organization when it comes to being where the people are.

Some quick facts about the LDS Church’s social network efforts from Joel’s post:

• Facebook: 5 pages with a total of over 1 million fans
• YouTube: 5 channels with a total of almost 30 million views
• Twitter: At one point, #ldsconf accounted for .14 percent of all tweets (~70 million per day), according to trendistic.com
• LinkedIn: LDS Professionals group with over 13,000 members

Pretty impressive!

Security – Archives – Space

Those three reasons to get a handle on your SharePoint installation are all tied in to governance.  Jake Frazier, CIO Update, wrote an article, “Prolific SharePoint Sites Undermine Governance”  that addresses each aspect pretty well.

The only real question I have is on the second page:

…the licenses for SharePoint are “free” or at least relatively inexpensive.

What?  Jake, you can’t be serious.  If you only have 10 users, it’s not too bad.  However, the price doesn’t usually scale very well no matter how much of a volume discount you get.  The good part is, this one little sentence definitely was not the main idea of a very well written article.

Thanks, Jake!

Whenever I create a new MOSS site this is going to use the Office SharePoint Server Publishing feature I get an “Access Denied” error when I try enable it.

So, I am finally posting the solution:
[code lang="dos"]stsadm -o activatefeature -name PublishingResources -url [/code]
*Be sure to include the “http://” in the <site>

Hope this helps!

One day, we noticed that our search was not working.   Well really, one of the applications managers noticed that it wasn’t working.  Anyway, we found the following errors in the event viewer on our SharePoint 2007 Server:

Event Type:      Warning
Event Source:      Windows SharePoint Services 3 Search
Event Category:      Gatherer
Event ID:      2436
Date:            4/11/2009
Time:            11:45:02 PM
User:            N/A
Computer:      <servername>
Description:
The start address <{somesite}> cannot be crawled.

Context: Application ‘Search index file on the search server’, Catalog ‘Search’

Details:
Access is denied. Check that the Default Content Access Account has access to this content, or add a crawl rule to crawl this content.   (0×80041205)

Apparently, this error was caused by a recent Microsoft Windows Update that was installed that affected the "Loopback Check" in order to make the system more secure.

In order for the SharePoint Search Services to work we needed to add the following registry entry with a REG_DWORD value of 0×00000001 (1):

HKEY_LOCAL_MACHINESYSTEMCurrentControlSetControlLsaDisableLoopbackCheck

Have you ran into this issue or one like it?