PowerShell - AD for SP2010

Can't remember where I got this from but it's useful:

When creating SharePoint test environments, one of the prerequisites is to have the necessary SharePoint service accounts. The powershell script below will enable you to create the AD accounts and ready for use when configuring the SharePoint farm. These accounts relate to SharePoint farm configuration, web application pool accounts, service application accounts, search service and content access accounts, user profile synchronisation accounts and object cache accounts. By all means you can modify the values to suit your requirements.

# Get the logged-on user's domain in DN form
$mydom = (get-addomain).distinguishedname

# Specify the OU we want to create the users in
$ouName = "SP Service Accounts"

# Build the full DN of the target OU
$oudn = "OU=$ouname,$mydom"

# Check if the target OU exists. If not, create it.
$OU = get-adorganizationalunit -Filter { name -eq $ouname }
if($OU -eq $null)
{New-ADOrganizationalUnit -Name $OUName -Path $mydom}
else
{write-host "The OU" $ou "already exists."}

# Create users
New-ADUser –Name "SP_Farm" –SamAccountName "SP_Farm" –DisplayName "SP_Farm" `
-Path $oudn –Enabled $true –ChangePasswordAtLogon $false `
-AccountPassword (ConvertTo-SecureString "pass@w0rd" -AsPlainText -force) -PassThru
New-ADUser –Name "SP_ServiceApp" –SamAccountName "SP_ServiceApp" –DisplayName "SP_ServiceApp" `
-Path $oudn –Enabled $true –ChangePasswordAtLogon $false `
-AccountPassword (ConvertTo-SecureString "pass@w0rd" -AsPlainText -force) -PassThru
New-ADUser –Name "SP_Portal" –SamAccountName "SP_Portal" –DisplayName "SP_Portal" `
-Path $oudn –Enabled $true –ChangePasswordAtLogon $false `
-AccountPassword (ConvertTo-SecureString "pass@w0rd" -AsPlainText -force) -PassThru
New-ADUser –Name "SP_MySites" –SamAccountName "SP_MySites" –DisplayName "SP_MySites" `
-Path $oudn –Enabled $true –ChangePasswordAtLogon $false `
-AccountPassword (ConvertTo-SecureString "pass@w0rd" -AsPlainText -force) -PassThru
New-ADUser –Name "SP_Search" –SamAccountName "SP_Search" –DisplayName "SP_Search" `
-Path $oudn –Enabled $true –ChangePasswordAtLogon $false `
-AccountPassword (ConvertTo-SecureString "pass@w0rd" -AsPlainText -force) -PassThru
New-ADUser –Name "SP_SearchAccess" –SamAccountName "SP_SearchAccess" –DisplayName "SP_SearchAccess" `
-Path $oudn –Enabled $true –ChangePasswordAtLogon $false `
-AccountPassword (ConvertTo-SecureString "pass@w0rd" -AsPlainText -force) -PassThru
New-ADUser –Name "SP_UPSync" –SamAccountName "SP_UPSync" –DisplayName "SP_UPSync" `
-Path $oudn –Enabled $true –ChangePasswordAtLogon $false `
-AccountPassword (ConvertTo-SecureString "pass@w0rd" -AsPlainText -force) -PassThru
New-ADUser –Name "SP_SuperUser" –SamAccountName "SP_SuperUser" –DisplayName "SP_SuperUser" `
-Path $oudn –Enabled $true –ChangePasswordAtLogon $false `
-AccountPassword (ConvertTo-SecureString "pass@w0rd" -AsPlainText -force) -PassThru
New-ADUser –Name "SP_SuperReader" –SamAccountName "SP_SuperReader" –DisplayName "SP_SuperReader" `
-Path $oudn –Enabled $true –ChangePasswordAtLogon $false `
-AccountPassword (ConvertTo-SecureString "pass@w0rd" -AsPlainText -force) -PassThru

#End

Optimize SQL FOR SP2010

• Respect software boundaries & limits, review the support article and read the maintenance whitepaper
• Use PowerShell to create your farm, the farm configuration wizard is bad
• Dedicate a SQL instance to SharePoint
• Differentiate between & prioritize your disks: tempdb, logs, search, other
• Align all partitions correctly (1024K)  and format SQL partitions with the right cluster size (64K)
• Test your SQL disks before using them with sqlio
• Only install the features you need (database engine & maintenance tools at minimum)
• Use a domain user for service account
• Enable instant file initialization
• Configure maximum memory
• Fill factor to 80
• MAXDOP to 1
• Consider multiple data files for your content databases
• Tune autogrowth to a fixed number
• Presize your data & log files
• Use SQL aliases to connect SharePoint to SQL
• Check database integrity weekly with dbcc checkdb
• Learn about index fragmentation, how SharePoint deals with it and what you need to do manually
• Don’t shrink databases unless you’re very sure (causes fragmentation)
• Autoshrink is pure evil, never activate it – certainly not with SharePoint
• Learn about the full & simple recovery models and take a look at how logging & recovery works
• In full recovery model you always need to take log backups or your log file will grow indefinitely  – no matter how many full backups you run

Change the location of the IIS log files - IIS7

At some point - you'll need to stop IIS logging to the C:\

Open the SharePoint 2010 Management Shell

 The IIS snap-in first needs to be loaded using Import-Module WebAdministration

 Here is the command to change the log file directory for the default web site:

Set-ItemProperty 'IIS:\Sites\Default Web Site' -name logFile.directory -value 'D:\IISLogs'

Now, open up the IIS Manager console, expand Sites, click on the site you changed the log directory for and double click on Logging under the IIS section. You should see the new directory location under Log File

 You will need to perform this on each server in the farm.