Feeds:
Posts
Comments

Archive for December, 2010

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

Advertisements

Read Full Post »

Dear all,

Just a short one on how to install language packs for SharePoint 2010. First of all, you need to install the appropriate language packs on Windows Server 2008 x64 (R2). You can obtain these from the Microsoft Download Center, specifically here:

Windows Server 2008 R2 Multilingual User Interface Language Packs

Just change to the language you need to install, and click “Change”. Afterwards, you can proceed with the download (~60MByte). For this example, I chose “French”

 

After the download, you can install the language pack using a doubleclick, and the rest goes automatically.

 

image

 

As a result, under Region and Language | Keyboards and Languages, you should see your newly added language (in this case, French):

 

image

 

This is enough as of prerequisites fulfillment on Windows Server 2008. Now, let’s step on to the installation of the corresponding language pack of SharePoint 2010:

Download the language pack from here:

http://www.microsoft.com/downloads/en/details.aspx?FamilyID=046f16a9-4bce-4149-8679-223755560d54&displaylang=en

After downloading the ~160 MByte executable file, just run it by doubleclicking – the rest of the installation goes without any interaction.

 

image

 

At the end of the installation, we’ll be prompted to run the SharePoint 2010 Products Configuration Wizard. This is crucial, since otherwise the installation of the language cannot be completed. So, we must execute this step.

 

Important: The Products Configuration Wizard will ask you whether to remove the server or not from the server farm. It is not recommended to remove it, if you are running SP 2010 on a server farm.

 

Caution: The wizard will restart several services during configuration. Please look careful at the wizard’s suggestions before actually executing it.

 

image

 

After the configuration finishes, we open the Central Administration and attempt to create a new Site Collection for an existing (or new) SP 2010 web application.

 

Now, after the language pack installation, it can clearly be seen, that in the “Select a language” Drop-Down-List our new language is present. Moreover, if we select this one, all the template descriptions will change, accordingly.

 

image

 

That was straightforward, right?

Stay tuned till next time!

 

Best regards,

Martin

Read Full Post »