Immediately starts any waiting administrative job on the local computer and triggers the jobs to run on all other servers in the farm if applicable.

Start-SPAdminJob2 [-Local [<SwitchParameter>]] [-AssignmentCollection [<SPAssignmentCollection>]]




Providing this parameter causes the cmdlet to behave just like the built-in Start-SPAdminJob cmdlet.


Manages objects for the purpose of proper disposal. Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used.

When the Global parameter is used, all objects are contained in the global store. If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur.

Detailed Description

Use the Start-SPAdminJob2 cmdlet to execute all administrative timer jobs immediately rather than waiting for the timer job to run.

When the process account for the SharePoint 2010 Administration service (SPAdminV4)) is disabled (necessary in some installations for security reasons), the Start-SPAdminJob2 cmdlet triggers all administrative tasks to run immediately on all servers to allow provisioning and other administrative tasks that SPAdmin ordinarily handles.

When you run this cmdlet in person (not in script), use the Verbose parameter to see the individual administrative operations that are run.

Copyright 2016 Falchion Consulting, LLC

> For more information on this cmdlet and others:


> Use of this cmdlet is at your own risk.

> Gary Lapointe assumes no liability.



PS C:\> Start-SPAdminJob2 -Verbose

This example runs all waiting administrative jobs on all servers and shows verbose output to the administrator.