Because it’s a public download

You’ll find it at the MS Download Center:

SharePoint Designer 2010 64-bit:
http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=566d3f55-77a5-4298-bb9c-f55f096b125d

SharePoint Designer 2010 32-bit:
http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=d88a1505-849b-4587-b854-a7054ee28d66

Furthermore you can also give SharePoint Foundation 2010 (the follower of WSS3.0) a try. It’s still free: http://www.microsoft.com/downloads/details.aspx?FamilyID=49c79a8a-4612-4e7d-a0b4-3bb429b46595&displaylang=en

First of all you have to start the required Web Service. So within the Central Administration click on the link “Manage services on server“.

There you’ll find the “Managed Metadata Web Service“. Use the “Start“-Link on the right side to start it.

Now we have to create a service application which handles the managed metadata. In Central Admin within the Application Management use the Manage service applications link to get an overview of the currently created service applications.

Side Note: Service Applications are the follower of the Shared Service Provider (SSP) in SharePoint 2007.

Use the New Button at the Service Applications Ribbon and choose “Managed Metadata Service“.

Enter your desired options. The options are self-explaining.

After the creation process you find your new service application in the list. Click on the Name of the Service Application or highlight it and use the Manage Button within the Service Applications Ribbon to enter the Term Store Management Tool.

First of all we have to create a new group for our Term Sets. When moving the pointer over the name of your Service Application (in my case its “Managed Metadata Service SA”) a little arrow appears. After clicking on this arrow the below showed menu appears. Now use the New Group link and enter the name of the group.

After entering the name you can hit Enter and the properties of this group are displayed. I think the options here are self-explaining as well.

Now create a Term Set which will hold our Terms (Metadata). The Term Set is the part which will be used in a column. Basically it’s the same process as the creation of the group. Move the pointer over your group, click on the small arrow and choose New Term Set. It’s also possible to import a CSV-File.

After hitting Enter again you’ll find yourself in the properties of this new Term Set. Especially the “Submission Policy” setting is interesting. If you want a dynamic list (which is extendable by your users) you have to change this option to Open.

Once again, we have to use our little arrow to create new Term’s inside this Term Set.

You can define multiple synonyms for each term. If this synonym is typed by one of your users the right Term will be displayed as suggestion.

So, after all you Term Set was created we should also use it

Create a new column in a List or Document Library within your Site Collection.

Enter a Column name and choose “Managed Metadata” as information type.

Puhuu, what’s that? I’m not sure if it’s just a bug within the RC1-Edition, but we have to enable the Term Navigation through PowerShell. Yep, the required feature isn’t available through the “Site Feature” list inside the “Site Settings”.

Start PowerShell and add the SharePoint SnapIn so the required cmdlets are available.

Get-PSSnapin –Registered
Displays all PowerShell-Snapins which are available on your machine

Add-PSSnapin Microsoft.SharePoint.Powershell
Adds the SharePoint-Snapin to this PowerShell session

If you don’t trust me that you have to enable the feature you can check it

Get-SPFeature –Site <URL to your Site Collection>
Displays a list of all already enabled Site Features

Enable-SPFeature -Identity 73EF14B1-13A9-416b-A9B5-ECECA2B0604C -Url <URL to your Site Collection>
Enables the “TaxonomyFieldAdded” feature for the specified Site Collection. This one is required for the Taxonomy Browser.

Get-SPFeature | where {$_.displayname –like “*tax*”}
A list of all available features on this Farm are displayed which have tax in their name. This would be an option to get the ID of the feature. The other option would be to try to create a column while this feature is disabled. You will receive the error: “The Taxonomy feature (Feature ID “73EF14B1-13A9-416b-A9B5-ECECA2B0604C”) has not been activated.<br>A term set or anchor point was not selected”.

So, feature is activated and we’re ready to use it. Refresh the page. Now your Managed Metadata Service Application with the Group and Term Set is display.

If you want the Term Set to be dynamically extendable set “Allow ‘Fill-in’ choises” to “Yes“.

After using the “OK-Button” to create the new column just upload a document. Our column is displayed and while you’re typing a value relevant suggestions are displayed. You can also click on this tiny cards (or whatever it should be) on the right side of the input box to display all available Terms. This is also the required step if you want to add a new Term.

Use the “Add New Item” to, what a surprise, add a new term

That’s it You can also try to add a column which is using your Term Set on another Document Library and even on a DocLib within another Site Collection and you’ll find all Terms.

There are still some open questions for me where I have to play more with this feature. Especially with permission on the Term Sets and Groups. But all Managed Metadata would solve a lot of troubles we all had with SharePoint 2007.

In my opinion it’s just important to clearly understand the impact of Managed Metadata and to plan it carefully. It’s like with Content Types => A good concept is everything

However, I thought it must be possible through the setup Config-Files.

To see the predefined files you first have to extract the setup bits.

So fire up an command prompt and go to the directory where the big executable is in.

Then run: file.exe /extract:<DESTINATION PATH>

After a few seconds you’ll find a lot of folders inside the destination folder. We have to concentrate on the “Files” folder. Inside that one you’ll find a couple of folders which are for different setup scenarios.

You can edit one of the predefined ones or just copy and edit it. I took the Config.xml from the SetupFarm folder.

There you’ll find some interesting options. First of all you can provide your License Key within the <PIDKEY> Tag. But more interesting is the <Setting ID=”SERVERROLE”> Tag. There you’ll find a value of “APPLICATION”. This setting basically means a full installation. You’ll find a detailed list of all options in TechNet http://technet.microsoft.com/en-us/library/cc261668.aspx

So after made the desired changes we can fire up setup with the /config parameter. There we have to specify our config.xml

The rest of the setups are just the default steps. Don’t panic, the screen of the component selection won’t appear, but it will do the right stuff like specified in config.xml

,

Voila, as seen on the last screenshot, just my default instance of MS SQL2008 is running.

I’m not sure if this is a bug or just because of the setup where I have everything on one machine. Maybe I’ll find the time to try the setup again on multiple machines

I tried to create an Enterprise Search Center within a site collection in SharePoint 2010. But I’ve received this error message all the time. I’ve also tried to create a new site collection, but without success.

Suddenly I had the idea to try it with SharePoint Designer. And voila, I’ve got an error message I can work with.

So the next step was to enable the Publishing Infrastructure feature. Site Actions -> Site Settings -> Site collection features -> SharePoint Server Publishing Infrastructure and click on “Activate”

After this step you can also create the Enterprise Search Center without any error messages

I had the most troubles with the User Profile Service Application. This Service Application sucks data from a User Directories (Active Directory, LDAP, BDC) and provides this informations within SharePoint. You’ll need this user profile data for example for the MySites to show the organization structure, phone numbers and so on.

I assume you already created a User Profile Service Application inside the Central Administration. I will just enlist the troubles I had to get It up and running with the solution which worked for me.

Background-Information: The profile synchronization task is done Microsoft FIM 2010 (Forefront Identity Management).

If the User Profile Service Application Proxy hangs at state “Starting” (Central Admin) and both FIM-Services (services.msc -> Forefront Identity Manager Service and Forefront Identity Manager Synchronization Service) are not started too or have strange or no service accounts entered try the following:

1. First of all: If not already done, install the WCF Hotfix KB976462: http://support.microsoft.com/kb/976462/en-us If you build your farm without this hotfix and the services still don’t start you may have to recreate your Farm (I had this case)
2. Is the service account a local admin?
3. Is there a Windows-Userprofile created for this service account? (Just logon with the service account)

If the FIM Services are running fine (Forefront Identity Manager Service, Forefront Identity Manager Synchronization Service) and both Service Applications are up (User Profile Service Application and User Profile Service Application Proxy) you’re one step closer to success

First of all: Don’t panic when you realize that you can’t edit or delete Synchronization Connections. It IS possible to edit and delete them, but not inside Central Admin (remember, it’s a Beta)

Because the synchronization is handled by FIM it’s the easiest to use its management tools. Run the “Synchronization Service Manager” (“%programfiles%\Microsoft Office Servers\14.0\Synchronization Service\UIShell\miisclient.exe”). Within the tab “Management Agents” you should find three Agents

• ILMMA
• MOSS-<Name of your User Profile Service Application>
• MOSSAD-<Name of your synchronization connection> (If you haven’t created one stop reading and proceed afterwards here)

You can also switch to the “Operations”-Tab. There you’ll find a history of ran jobs and what they did.

Something like that would be our goal:

I think the most information in the screenshot is self-explaining. Basically it’s tell us that a DS_FULLIMPORT ran from Management Agent “MOSSAD-CONNECTION”. It added 11190 AD-Objects to a local “staging area”. If something is wrong you’ll find the information here or on the Management Agents Tab.

In my case the first error was an “Access Denied”. This was because I forgot to grant “Replicating Directory Changes” to the service account. See http://technet.microsoft.com/en-us/library/ee721049(office.14).aspx and http://technet.microsoft.com/en-us/library/ee721049(office.14).aspx

After the change was made I’ve got just success from the tasks, but every import just returned two objects. Hmm. The properties from the “MOSSAD-<CONNNAME>” gave the reason. So right click on this Management Agent -> Properties and switch to “Configure Directory Partition”. There you’ll find your chosen Domain to sync from. Just hit “Containers” and check if the desired OU’s are selected. The selection box inside Central Admin is a little bit “tricky”. In my case the selection of the Domain wasn’t recursive.

Every Management Agent has multiple “Run Profiles” defined. You’ll find them with a right click on the Management Agent -> “Configure Run Profiles”.

MOSSAD-<CONNAME> => Connects to AD
MOSS-<Name of Service Application> => Connects to the User Profile Webservice (http://hostname:port/_vti_bin/ProfileImportExportService.asmx?ApplicationID=<APPID>)
ILMMA => Connects to the Farm Sync-DB

For a Full AD-Import the following Tasks (Management Agent – Run Profile) are running:

1. MOSSAD-<CONNNAME> – DS_FULLIMPORT
2. MOSS-<Name of Service Application> – MOSS_FULLIMPORT
3. MOSSAD-<CONNNAME> – DS_FULLSYNC
4. MOSS-<Name of Service Application> – MOSS_FULLSYNC
5. MOSS-<Name of Service Application> – MOSS_EXPORT
6. MOSSAD-<CONNAME> – DS_EXPORT

I’m not sure what every task exactly does. For my understanding it’s something like:

1. Get all AD objects (with a subset of properties) and load them to the temporary staging area in Memory (Connector Space)
2. Get all Sharepoint-User Profile Data from the Webservice and load them to the temporary staging area in Memory (Connector Space)
3. Syncing all new or updated objects (with the configured attributes) from AD Connector Space to the FIM Metaverse (Farm Sync DB)
4. Syncing all new or updated objects (with the configured attributes) from MOSS Connector Space to the FIM Metaverse (Farm Sync DB)
5. Push the new or updated data back from the FIM Metaverse to the MOSS Webservice
6. Push any changes back to AD (strange?!)

I have no experience with FIM, but that’s a short info I’ve got from Help

Basically if all Tasks ran successful you should have your profiles now available in Central Admin. Easy, isn’t it

BTW: If you accidentally created Synchronization Connections within Central Admin you can delete them with the FIM Synchronization Service Manager. Just delete the unnecessary “MOSSAD-<Name” Management Agents and they will disappear in MOSS as well.

Hope this post was a little helpful. Please let me know if it’s too short or not understandable

Here you’ll find additional informations:
http://technet.microsoft.com/en-us/library/ee721049(office.14).aspx

http://blogs.msdn.com/alimaz/archive/2009/11/09/configuring-user-profile-service-application-in-sharepoint-server-2010.aspx

http://blogs.msdn.com/sharepoint/archive/2009/11/18/path-to-user-profile-synchronization-success-in-sharepoint-2010-beta.aspx

http://blogs.msdn.com/opal/archive/2009/11/19/user-profile-sync-setup-in-sharepoint-server-2010-beta.aspx

http://sharepoint.mindsharpblogs.com/Kathy/Lists/Categories/Category.aspx?Name=SharePoint%20Server%202010