Better explanation than Technet about Export-SPWeb

technet site for Export-SPWeb :  https://technet.microsoft.com/en-us/library/ee428301.aspx

this site look like not so helpful for me to export the list ...

i prefer this more detail site explanation :

http://blog.blksthl.com/2013/09/05/export-a-document-library-using-export-spweb-and-itemurl/

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

Export-SPWeb

(This is my better version of the TechNet articles on the same CMDlet that does a poor job with the details, I hope that it will help some of you)
SharePoint 2010 | SharePoint 2013

‘

Applies to:  SharePoint Foundation 2010 | SharePoint Server 2010 | SharePoint Foundation 2013 | SharePoint Server 2013 

‘

Exports a site, list, or library.

‘
Export-SPWeb [-Identity]  -Path  [-AssignmentCollection ] [-CompressionSize ] [-Confirm []] [-Force ] [-HaltOnError ] [-HaltOnWarning ] [-IncludeUserSecurity ] [-IncludeVersions ] [-ItemUrl ] [-NoFileCompression ] [-NoLogFile ] [-UseSqlSnapshot ] [-WhatIf []]

‘

——————–EXAMPLE———————–

Export-SPWeb http://site –Path "c:\temp\site export.cmp" -ItemURL "/subsite/documents"

This example exports the document library at http://site/subsite/documents to a new file called ‘site export.cmp' in the ‘C:\temp’ directory.

powershell copy folder to remote computer

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


foreach ($Server in $ServerName) {

$server

New-Item -ItemType directory -Path "\\$server\d$\software\SP2010 SP2\SP2 LP"

Copy-Item  "D:\software\SP2010 SP2\SP2 LP\*"  "\\$Server\d$\software\SP2010 SP2\SP2 LP" -Recurse -force



}

Get Site Collections per Content Database one-liner

Copy from Here

Get-SPContentDatabase | %{Write-Output "- $($_.Name)”; foreach($site in $_.sites){write-Output $site.url}}

Now let’s say you want to save this output to a .txt file, you can add “> C:\sitecollections.txt”.

The full command would be:

Get-SPContentDatabase | %{Write-Output "- $($_.Name)”; foreach($site in $_.sites){write-Output $site.url}} > C:\sitecollections.txt

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.