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.

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.

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!

Extended web applications are not listed in the web application list and cannot be deleted using the Delete Web Application link in Central Administration.

Use the following steps to delete extended web applications:

1. Start Central Administration
2. Go to Application Management
3. Click Remove SharePoint from IIS Web Site to get a page with a form similar to the following.
   
4. Select the web application that the extended web app was extended from
5. Select which extention/zone to delete
6. Select whether to keep or delete the IIS Web site
7. Finally click OK

There are several steps that you need to take in order to enable anonymous access.  Below are the steps taken from Microsoft TechNet.

Enable anonymous access for a zone of a Web application

1. From Administrative Tools, open the SharePoint Central Administration Web site application.

2. On the Central Administration home page, click Application Management.

3. On the Application Management page, in the Application Security section, click Authentication providers.

4. On the Authentication Providers page, make sure the Web application that is listed in the Web Application box (under Site Actions) is the one that you want to configure. If the listed Web application is not the one that you want to configure, click the drop-down arrow to the right of the Web Application drop-down list box and select Change Web Application.

5. In the Select Web Application dialog box, click the Web application that you want to configure.

6. On the Authentication Providers page, click the zone of the Web application on which you want to enable anonymous access. The zones that are configured for the selected Web application are listed on the Authentication Providers page.

7. On the Edit Authentication page, in the Anonymous Access section, select Enable Anonymous Access, and then click Save.

At this point, the Web application zone has been enabled for anonymous access.

Enable anonymous access for individual sites

Now you need to enable anonymous access for individual sites in the site collection.

Enable anonymous access for individual sites

1. Go to the site on which you want to enable anonymous access and click the Site Actions menu.

2. On the Site Actions menu, click Site Settings.

3. On the Site Settings page, in the Users and Permissions section, click Advanced Permissions.

4. On the Permissions page, on the Settings menu, click Anonymous Access. The settings for anonymous access lists three options:

   • Entire Web site   Select this option if you want to enable anonymous access for the entire Web site.

   • Lists and libraries   Select this option if you want to limit anonymous access to only the lists and libraries on your site.

   • Nothing   Select this option if you want to prevent anonymous access from being used on your site.

5. Click OK.

At this point, your site is configured for anonymous access based on the options that you have selected.

Enable anonymous access for individual lists

If you select Lists and libraries, enable anonymous access for individual lists.

Enable anonymous access for individual lists

1. Go to the home page of your Web site and, in the left navigation pane, click View All Site Content.

2. Click the list on which you want to enable anonymous access.

3. On the Settings menu, click List Settings.

4. On the Customize List page, in the Permissions and Management section, click Permissions for this list.

5. On the Permissions page, on the Actions menu, click Edit Permissions. A dialog box is displayed informing you that you are about to create unique permissions for this list. Click OK.

6. On the Settings menu, click Anonymous Access.

7. Select permissions for users who have anonymous access to the list, and then click OK.

At this point, users have anonymous access to the list you have configured. You can control whether users have anonymous access to other lists, the home page, or other pages on this site.

!!!*** NEVER, NEVER, NEVER, NEVER EVER STOP WINDOWS SHAREPOINT SERVICES WEB APPLICATION ***!!!

The Windows SharePoint Services Web Application is what identifies your server as a SharePoint Web Front-End.  If you stop this “service” it will remove all SharePoint websites and the directories from which they are served. 

So, unless you know exactly what you are doing, DO NOT STOP THE WINDOWS SHAREPOINT SERVICES WEB APPLICATION!!!