SharePointHint – A community-built collection of SharePoint hints

Recently I stumbled upon browsing Technet over some tables of limitations of SharePoint 2010 which are good to know. Here are some of the most useful examples.

Web Application limits:

Read the full post…

In SharePoint 2010 is new a passphrase needed. You can compare a passphrase with a password, but it is longer to raise security. With a passphrase, the account information which are registered in SharePoint 2010, are being encrypted.

An example: If you want to add a new role to your SharePoint farm through the configuration assisstant and you have forgot the passphrase, the only way to resolve this problem is to reset the passphrase. You cannot fetch the passphrase from somewhere else because of security reasons.

Technet recommends following security criterias while entering a passphrase:

• Passphrase must be at least 8 digits
• Passphrase contains at least three of the following character groups:
• Capital letter (A to Z)
• Letters (a to z)
• Nummernzeichen (0 bis 9)
• Non alphabetic characters (E.g. !, $, # oder %)

If you want to reset a passphrase open as an administrator the “SharePoint 2010 Management Shell”. Enter following commands to reset the passphrase:

1. $passphrase = ConvertTo-SecureString -asPlainText -Force
2. Insert new passphrase and accept with “Enter”
3. Set-SPPassPhrase -PassPhrase $passphrase -Confirm
4. Re-enter new passphrase and accpept with “Enter”
5. Type Y (Yes) and “Enter”, now you have reseted your passphrase

During this week we have studied a lot about SharePoint migration. This is already now a very hot topic at our customers. We have migrated an Office SharePoint Server 2007 environment to SharePoint Server 2010 (Beta). In this article we’d like to describe what we have done, what kind of environment we have used and would also like to write some words about the whole migration process in a short summary.

Environments

Both SharePoint environments are running virtualized on the product Virtual Box from Sun, which has got a free license and therefore it can be used without any costs. As a host system we have used a Windows 7 64 Bit Ultimate with 6 GB RAM.

Read the full post…

As soon as you have installed a second language pack on the SharePoint Server 2010, you can change the language dynamically on the fly while browsing your site. Well now you should be also able to translate the terms and keywords to the chosen language. Unfortunately the additional language is not yet available in the “Term Store Management Tool”.

That you can choose the new installed language you need to add on the root level (Managed Metadata Service) a “Term Store Administrator”.

As soon you have this done, you can choose the installed language and the Terms can be translated

The Artefact „i:0#.w|“ might be some Beta-thing. Some similar artefacts like (c:0(.sltrue) appear also elsewhere in connection with authentificated users.

If you click in SharePoint Server 2010 Beta on the personal menu, the MySite will not be displayed. Also the “I like it” button is missing (what we have seen in the technical preview of SharePoint Server 2010).

To get the MySite and the Social Media functions (Tags, I like it) of SharePoint 2010 up and running, you need to configure the profile import first. How this is being done, I describe in this blogpost. If you have the profile import running, you can start to care about your MySites. Somehow the MySites seems to be a bit off the scale in this Beta .

Here are the steps what needs to be done:

• Create and configure a new MySite host
• Assign the “User Profile Service” to the actual web application

1: First you need to create a new MySite host. This happens quite in the similar way how it has been done in SharePoint Server 2007. In the Central Administratio go to Application Management – Manage web applications. Here you choose your Web Application and choose in the Ribbon “Managed Path”.

Here you define two “managed path”. For “MySite” you create an “Explicit inclusion” path. For the path “personal” you create a “Wildcard inclusion”.

2: After you have done this, go back to Application Managemet. Choose now from there Site Collections – Create site collection. The page to create a new site will now be opened. The name of the site does not matter (e.g. mysitehost). Under “Web Site Address” you need to choose “mysite” (as defined in step 1). As a template you choos in the “Enterprise” tab, “My Site Host”.

3: Now you need to fix in the MySite configuration a small beta bug and add the new MySite host there. To do this navigate to Central Administration – Application Management – Manage service application – User Profile Service Application and there MySite Settings – Setup MySite.

In the MySite configuration you change the entries “MySiteHost” to “http://server1:80/mysite” and “Personal Site Locatin” to “personal”. At the same time you can delete the cryptic user on the “Read Permission Level”, that just your SharePoint Admin User Account or similar appears.