PowerShell script to list down all the site collection owner at web app level

copy from : http://geekswithblogs.net/bjackett/archive/2011/03/25/powershell-script-to-display-all-sharepoint-site-collection-administrators-in.aspx

=======================================================================

$siteUrl = Read-Host "Enter Site URL"

$rootSite = New-Object Microsoft.SharePoint.SPSite($siteUrl)
$spWebApp = $rootSite.WebApplication

foreach($site in $spWebApp.Sites)
{
    foreach($siteAdmin in $site.RootWeb.SiteAdministrators)
    {
        Write-Host "$($siteAdmin.ParentWeb.Url) - $($siteAdmin.DisplayName)"
    }
    $site.Dispose()
}

========================================================================

The script appears to run outside administrator context

Scenario :

• Running ROIScan.vbs and show the error message below 
• Running PowerShell script check the serrver hard disk space unable to remote in

Error message  :

• ROIScan.vbs : The script appears to run outside administrator context
• PowerShelll : Get-WmiObject : Not found

Solution : copy from here

1. winmgmt /verifyrepository
 - Got error Repository inconsistent
2. winmgmt /salvagerepository
 - Once successful everything started working fine
/verifyrepository []
        Performs a consistency check on the WMI repository. When you add the
        /verifyrepository switch without the argument, then the live
        repository currently used by WMI is verified. When you specify the path
        argument, you can verify any saved copy of the repository. In this
        case, the path argument should contain the full path to the saved
        repository copy. The saved repository should be a copy of the entire
        repository folder.
/salvagerepository
        Performs a consistency check on the WMI repository, and if an
        inconsistency is detected, rebuilds the repository.  The content of the
        inconsistent repository is merged into the rebuilt repository, if it
        can be read. The salvage operation always works with the repository
        that the WMI service is currently using. MOF files that contain the
        #pragma autorecover preprocessor statement are restored to the
        repository.

PowerShell Script : copy file to multiple target Computer/Server

Scenario to be done :  Copy 4 file (ROIScan.vbs ,MspFixUp.vbs , wiCollectFiles.vbs, run fixup.txt) to target server.

target server list keep at "C:\Users\Desktop\Computers.txt"

Save below file as powershell file format .ps1 . run it . done.
========================================================================

$ServerName = Get-Content "C:\Users\Desktop\Computers.txt"


foreach ($Server in $ServerName) {

Copy-Item -Path D:\software\ROIScan.vbs         -Destination \\$Server\d$\software\
Copy-Item -Path D:\software\MspFixUp.vbs         -Destination \\$Server\d$\software\
Copy-Item -Path D:\software\wiCollectFiles.vbs    -Destination \\$Server\d$\software\


}
========================================================================

Script Creating SharePoint User MySites using PowerShell

While working on a large migration project (SharePoint 2010 to SharePoint 2013), I had a requirement to script the creation of user MySites for hundreds of users. I knocked this little PowerShell function together to do just that!

Function Create-MySite            
{            
 [CmdletBinding()]            
 Param            
 (            
  [Parameter(Mandatory = $True,Position=2,valueFromPipeline=$true)][String]$Username,            
     [Parameter(Mandatory = $True,Position=1)][String]$MySiteRootURL              
 )            
 [void][reflection.assembly]::Loadwithpartialname("Microsoft.Office.Server");               
 $site=new-object Microsoft.SharePoint.SPSite($MySiteRootURL);            
 try            
 {            
  $serviceContext = Get-SPServiceContext $site;            
  $upm = new-object Microsoft.Office.Server.UserProfiles.UserProfileManager($serviceContext);             
  if($upm.UserExists($Username) -eq $false)            
  {            
   Write-Host "User $Username was not found in the profile store." -f yellow;            
   return;            
  }            
  $userProfile = $upm.GetUserProfile($Username);            
  if($userProfile.PersonalSite -eq $Null)            
  {            
   Write-Host "Creating MySite for user $Username" -f darkyellow;            
   $userProfile.CreatePersonalSite();                  
   Write-host "Successfully created MySite for user $Username" -f green;            
  }            
  else            
  {            
   Write-Host "User $Username already has a MySite." -f darkgreen;            
  }            
 }            
 catch            
 {            
  Write-Host "Encountered an error creating a MySite for user $Username. Error:"$_.Exception -f Red;            
 }            
 finally            
 {            
  $site.Dispose();            
 }            
}

You can call the function like this (for a single user):

#Example - Create a MySite for user  "tonyj"            
Create-MySite -MySiteRootURL "http://mysite.bigintranet.com.au" -Username "tonyj"

Or call it like this, for a batch of users:

#To Create for an array of users            
$users = @('tonyj','bobh','markf','billd')            
$users | Foreach {Create-MySite -MySiteRootURL "http://mysite.bigintranet.com.au" -username $_}

this article copy from : Matthew Yarlett

Disable incoming email settings pages for SharePoint server 2007

TO restrict user to change incoming email settings, we must customize some of aspx files.

Implementation Instructions

1.         Logon to the servers, and open “C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\template\LAYOUTS”.

2.         Take back up following 2 aspx files, and place them on same directory.
* new.aspx
* EmailSettings.aspx

3.         Change file name that you back up now as below
* new.aspx                                               →           new_xxx.aspx
* EmailSettings.aspx                             →           EmailSettings_xxx.aspx

4.         Open new.aspx(Original). And add “disabled="disabled"” in the following code.

Around line 412…

disabled="disabled"

>
disabled="disabled">


Around line 504….

disabled="disabled">
disabled="disabled">

5.         Save and close.

6.         Open EmailSettings.aspx(Original). And change code as following.

Around line 97…
Original
function _spBodyOnLoad()
{
SetControlsDisabled(document.getElementById("<%= EnabledFalse.ClientID %>").checked);
}

New
function _spBodyOnLoad()
{
//SetControlsDisabled(document.getElementById("<%= EnabledFalse.ClientID %>").checked);
SetControlsDisabled(document.getElementById("<%= EnabledFalse.ClientID %>").disabled = true);
SetControlsDisabled(document.getElementById("<%= EnabledTrue.ClientID %>").disabled = true);
}

7.         Save and close.

8.         Repeat above step for all WFEs.

how to open the setting page 

1.       Open the document library you just created.

2.       Click Settings – document library settings.

3.       Under Communication Settings click E-Mail Settings.

4.       Change URL as below.
http:/xxx/sites/xxx/_layouts/EmailSettings.aspx?List=xxx
　　　　　　↓
http:/xxx/sites/xxx/_layouts/EmailSettings_xxx.aspx?List=xxx