Feeds:
Posts
Comments

Posts Tagged ‘PowerShell’

UPDATED: Find the new Youtube Link below!

Dear all,

episode 4 of SP5 is ready! This time it is dealing with the topic of moving site collections from one content database to another. Click below to watch the video (UPDATED):

Remark: If you want to create a new site collection using a specific content database, you need to use PowerShell, specifically the New-SPSite cmdlet:

New-SPSite –ContentDatabase <DBName>

This cannot be done from within Central Administration.

The involved cmdlets are:

Get-SPSite (lists site collections)
Get-SPContentDatabase (list content databases)
Move-SPSite (list content databases)
New-SPSite (create new site collection, specify content DB)

Important: After moving a site collection from one content DB to another, an iisreset is required. Be aware that this will cause a service disruption for some time (depending on your server’s configuration). Be sure to execute this only if you are fully aware that this will cause all websites to be inaccessible for some time.

Disclaimer: All tutorials are provided as is. You are responsible for any changes undergoing your system that derive from following this tutorial. It is hence recommended to consult your administrators and verify that the changes cannot harm your IT environment in any way.

Stay tuned till the next time!

Martin

Read Full Post »

Dear all,

the same way that you can Toggle the Developer Dashboard using STSADM.exe, you can also toggle it using PowerShell. It is slightly more complicated, but works just as fine and it’s also faster than the STSADM command. Let’s have a look:

$service = [Microsoft.SharePoint.Administration.SPWebService]::ContentService
$ddSettings =$service.DeveloperDashboardSettings
$ddSettings.DisplayLevel = [Microsoft.SharePoint.Administration.SPDeveloperDashboardLevel]::OnDemand
$ddSettings.Update()

What it does, is retrieving the content web service, then retrieve the service’s dashboard developer settings and setting their display visibility level. It can be set to either of these:

[Microsoft.SharePoint.Administration.SPDeveloperDashboardLevel]::On
[Microsoft.SharePoint.Administration.SPDeveloperDashboardLevel]::Off
[Microsoft.SharePoint.Administration.SPDeveloperDashboardLevel]::OnDemand

If you execute script, do it line by line or store them as a scripted .ps1 file before. There will be no success messages, but if you don’t get an error or warning from the PowerShell

Make sure you run these in a SharePoint Management Shell that you started with “Run as administrator”. Otherwise it will not work. Also, using the SharePoint Management Shell saves you from needing to add the SharePoint library using the Add-PSSnapin cmdlet. If  you should decide to open just a “normal” PowerShell command interface, make sure to execute the following:

Add-PSSnapin Microsoft.SharePoint.Powershell

Then run the above mentioned script, it should work fine. Please make sure to test any scripts before running them in a production environment. As usual, I cannot take responsability for any damage caused by scripts on this page. They are provided as-is. Adaptations could be necessary to make it run successfully.

Best regards and stay tuned till the next time!

Martin (currently enjoying the sun in Calabria!)

Read Full Post »

Dear all,

The developer dashboard is a very handy tool in Microsoft SharePoint Server 2010, when it comes to analyzing how your site is loading and finding potential bottlenecks. It displays information about databases, webservices, the current page itself and so on. You can see an example of the developer dashboard here. Once enabled, it can be found scrolling at the bottom of the page you want to analyze.

The Developer Dashboard

There are three states the developer dashboard can be in:

  • On: Displayed
  • Off: Not displayed
  • On Demand: Can be toggled by the user.

And you have three possibilities of turning it on or off:

  • STSADM.exe
  • PowerShell
  • SharePoint COM

In this post, we’ll just focus on the STSADM.exe method, since it is the fastest one. STSADM.exe is located in the HIVE folder of SharePoint 2010 (usually “C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\”, and there in the “BIN” folder).

The STSADM.exe Method:

On:  stsadm -o setproperty -pn developer-dashboard -pv on

Off:  stsadm -o setproperty -pn developer-dashboard -pv off

On Demand:  stsadm -o setproperty -pn developer-dashboard -pv ondemand

Turning it on “On Demand” creates a new button in the menu, which is shown in the following picture:

On Demand Developer Dashboard Toggle Button

On Demand Developer Dashboard Toggle Button

That’s it! The command takes a few seconds to run and then quits with a “Operation successful” message.

Best regards and stay tuned till the next time,

Martin

Read Full Post »

Hi all,

After a fresh installation (or upgrade from a MOSS 2007), there are a couple of configuration steps that need to be performed. One is the configuration of the usage and health data collection. This can be done either using the Central Administration or PowerShell. This post focuses on how to do the configuration using powershell.

 

As the very first step we would need to bring up the SharePoint 2010 Management Shell.

Then, by issuing the cmdlet:

 

Set-SPUsageService

 

we can specify multiple parameters in order to set the data collection up:

 

  • -LoggingEnabled (1 or 0)
  • -UsageLogLocation (file path)
  • -UsageLogMaxSpaceGB [1-20]

More parameters exist, however: these are the most interesting ones. So, for example, issuing the following command:

 

Set-SPUsageService –LoggingEnabled 1 –UsageLogLocation C:\Logs -UsageLogMaxSpaceGB 3

 

would enable the usage data collection and write the corresponding logs to C:\Logs, up to amount of 3 GB. Please bear in mind that the logs max space must be within the interval [1-20].

 

image

 

There is also a way of specifying the usage data collection for a single event type, using the following cmdlet:

Set-SPUsageDefinition

 

The parameters of interest are here:

  • -Identity <GUID>
  • -Enable
  • -DayRetained [1-30]

An example command would be like follows:

 

Set-SPUsageDefinition -Identity 0a79e3a1-c60d-473b-82b7-
f43c2b4da -Enable -DaysRetained 15

 

This would set the event type with the GUID to be kept in the logs for 15 days.

 

Until here, we could have done the same operations using the Central Administration. However, there is a configuration that can only be performed using PowerShell:

 

Usage Logging in a Different Database.

 

As we might have guessed, another cmdlet is needed for this operation:

 

Set-SPUsageApplication

It uses the following parameters of interest:

  • -DatabaseServer <Server>
  • -DatabaseName <DBName>
  • -DatabaseUsername <User>
  • -DatabasePassword <PWD>

The latter two parameters, –DatabaseUsername and –DatabasePassword, are only required if our DB user differs from the user we are currently logged on as.

 

What else there is to mention? Well, do test the above commands thoroughly before applying them in any productive environment. They affect the logging and hence may have a negative and severe impact if applied the wrong way (or just as they are –please DO NOT copy paste and execute them – the parameters need to be adapted to your needs).

 

For all three methods, there exists also an additional –Verbose parameter, that tells you about success or failure of the application.

 

Best regards & happy SP-configuring!

Martin

Read Full Post »