Use the following PowerShell script to move a Site Collection to a different Content Database:

 Move-SPSite <http://ServerName/Sites/SiteName> -DestinationDatabase <DestinationContentDb> 

The information below is found in Microsoft Technet:

Site names, subsite names, or site group names

• You cannot use the following characters anywhere in a site name, in a subsite name, or in a site or Active Directory group name:
• tilde (~)
• number sign (#)
• percent (%)
• ampersand (&)
• asterisk (*)
• braces ({ })
• backslash (\)
• colon (:)
• angle brackets (< >)
• question mark (?)
• slash (/)
• plus sign (+)
• pipe (|)
• quotation mark (")
• You cannot start a site name, subsite name, or a site group name with an underscore (_) character or with the period character.
• You cannot use the period character consecutively in the middle of a site name, a subsite name, or a site group name.
• You cannot use the period character at the end of a site name, a subsite name, or a site group name.

Folder names

• You cannot use the following characters anywhere in a folder name or a server name:
• tilde
• number sign
• percent
• ampersand
• asterisk
• braces
• backslash
• colon
• angle brackets
• question mark
• slash
• pipe
• quotation mark
• You cannot use the period character consecutively in the middle of a folder name.
• You cannot use the period character at the end of a folder name.
• You cannot start a folder name with the period character.

File names

• You cannot use the following characters anywhere in a file name:
• tilde
• number sign
• percent
• ampersand
• asterisk
• braces
• backslash
• colon
• angle brackets
• question mark
• slash
• pipe
• quotation mark
• You cannot use the period character consecutively in the middle of a file name.
• You cannot use the period character at the end of a file name.
• You cannot start a file name with the period character.
• In addition, file names and folder names may not end with:
• .files
• _files
• -Dateien
• _fichiers
• _bestanden
• _file
• _archivos
• -filer
• _tiedostot
• _pliki
• _soubory
• _elemei
• _ficheiros
• _arquivos
• _dosyalar
• _datoteke
• _fitxers
• _failid
• _fails
• _bylos
• _fajlovi
• _fitxategiak

There is a great article at LogicWorm.com that explains how to fix the slowness encountered when transferring files to/from SharePoint 2010 using Windows Explorer:

SharePoint users and likewise other application users that use WebDav Explorer mode on Windows 7 and Windows Vista PC’s may experience very slow file browsing, opening and modification (e.g. SharePoint Explorer View using WebDAV).

How simple would it be to just uncheck a certain option in IE and fix this brain busting issue, especially for Network Admins and SP Admins?

Solution

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. Start browsing again…!

Now for a bit of knowledge building

What is the “Automatically Detect Settings” option in IE?

The “Automatically detect settings” option is there to help the user in configuring a web proxy automatically. It actually makes use of the WPAD protocol to discover a web proxy.

1. If the PC is configured to do DHCP, then it will query the server. If the response includes a string with id 252, then it uses this to retrieve a configuration file.

2. If this fails, then the PC will attempt to resolve the name wpad. It will start in its current domain, and work back through. Eg, if the PC is called bob.cs.anu.edu.au, it will attempt to resolve wpad.cs.anu.edu.au, followed by wpad.anu.edu.au, etc. If this resolves the name wpad, then IE will attempt to retrieve wpad.dat via http from the root of the server. You should probably redirect this to the configuration file.

3. If this yields no success, then IE goes direct.

Now here is your delay, when Step 1 and Step 2 are running, time-out – finally deciding to open your WebDav folders directly. Phew!

Skip it… if you do not require the auto-discovery feature. Ask your network admin to push a GPO to turn-it-off or uncheck it by default!

The following is taken from Configure Remote PowerShell in SharePoint 2010

Setup your Remote Server
There are a few steps you have to take on your server to initialize and set it up running for remoting. once.
First, you need to run the following command on your server — Enable-PSRemoting

Next you need to let powershell know that your server machine or remote machine will act as the server.

Enable-WSmanCredSSP -Role Server

Setup your Client Computer
There are also a few one time setup steps you need to take on your client computer. You only have to do this once. The first thing to do, if you are going to use the logged in user’s credentials to make a remote session in powershell, is to enable client credentials delegation. This can be achieved by changing the group policy.
First, edit group policy on your client computer to all credential delegation. Using gpedit.msc, enable both of the following (Under Local Computer Policy–> Computer Configuration–> Administrative Templates–> System–> Credentials Delegation):

• Allow Delegating Fresh Credentials
• Allow Delegating Fresh Credentials with NTLM-only Server Authentication

Note: In case you are going to explicitly specify the credentials, you can skip the above step.

Second, run the following command
Enable-PSRemoting

Third, enable WSMan CredSSP with the following command:
Enable-WSManCredSSP -Role Client –DelegateComputer “NameOfServer”

Once you have configured remote powershell, now you are all set to run remote commands.

Create and enter a remote session of Windows PowerShell
If your current user on client machine has permission to the SharePoint farm and Windows PowerShell on the remote box, you can use Enter-PSSession to create and enter the remote session.
For example, connecting to machine SpServer…

Enter-PSSession -ComputerName SPServer
If it works, the command prompt will be changed to [SPServer]: PS C:\Users\Administrator\>.
The session will be closed when you type exit or Exit-PSSession.

To connect to a machine with CredSSP and a different credential, you can use
Enter-PSSession -ComputerName SPServer -Authentication CredSSP –Credential domain\username
This will open up a dialogue for you to type in password. Type in the password and press enter and your remote session will be created.

Store and use credentials for scripting

First, use the following command to covert password from keyboard input to a secure string in a text file.

Read-Host -AsSecureString | ConvertFrom-SecureString | out-file C:\crd-sharepoint.txt

As soon as you type the command, start typing the password.

When you need to create a credential object, read this password (the secure string) from the file and create the credential with the following command:

$pwd = Get-Content C:\crd-sharepoint.txt | ConvertTo-SecureString

then create the credential (replace #### with your domain\username):

$crd = New-Object -TypeName System.Management.Automation.PSCredential -ArgumentList "####",$pwd

Then you will be able to use this credential in the command line without any dialogue.

$session = New-PSSession -computername "SPServer" -Authentication CredSSP -Credential $crd

Start Remoting on you Client Computer

Now your client computer is ready to actually create the session and import the SharePoint commands from the Server.

The next command adds the SharePoint PowerShell commands to your session.

Invoke-Command -Session $session -ScriptBlock{Add-PsSnapin Microsoft.SharePoint.PowerShell}

Note, that at this point, you can run whatever administrative PowerShell commands you need to run by using the Invoke-Command -Session $session -ScriptBlock{} syntax.

Importing remote commands into local session

Let’s see how one can import a remote command into a local session. First – let’s ask Import-PSSession cmdlet to look in the remote session $s, take all the remote commands matching "*-SPFarm" wildcard, add a "Remote" prefix to their noun, and then present them to me as if they were local commands:

Import-PSSession -Session $session -CommandName *-SPFarm -Prefix Remote

So, now we can run Get-RemoteSPFarm

Thanks again Configure Remote PowerShell in SharePoint 2010

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.

The SharePoint 2010 Auto Installer (AutoSPInstaller) has released a new version 2.5.

Automated SharePoint 2010 Powershell-based installation script.

AutoSPInstaller works with and now leverages enhancements in SharePoint 2010 Service Pack 1 (with or without the June 2011 CU)! It takes advantage of some of the cmdlet updates in SP1, while remaining backward-compatible with non-SP1 deployments.

Versions 2.5.x and up include several updates to the input file XML schema from version 2.0 so make sure you compare any of your existing XML files to the new AutoSPInstallerInput.XML. See below for highlights of changes in v 2.5.x.

Thank you, Heather Solomon For your awesome SharePoint 2010 CSS Reference Chart.

The following CSS Reference Chart highlights the major styles used in SharePoint Foundation 2010 and SharePoint Server 2010. CSS styles are grouped by area of the page and include the class/ID value, an explanation of how it is used in SharePoint and other related information including a screenshot where appropriate. Code (and file location) for the style statement is included.

• Some classes/IDs are not utilized in SharePoint style statements. But they can be used in your custom branding!
• When working with a custom master page you can manipulate some class/ID assignments. The chart notates where.
• It is crucial to understand how descendent and child selectors work.
  • Learn about descendent selectors
  • Learn about CSS child selectors
• Many styles are dependent on parent selectors and may not apply to your custom master page.
• Code listed for each entry does NOT include statements when the class/ID is a parent in descendent or child selector style statements.
• OOTB stands for "out of the box". This is what SharePoint comes with by default.

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)