SharePoint etc.

Initially I published an article Working with Managed Metadata in SharePoint 2010 here I want to illustrate some core functionality that is available when you want to manage Managed Metadata. In the Site Settings select "Term store management" item: Then select the term set you would like to manage. In my scenario I want to create a term set to store Document Categories. For example I have two categories: Accounting, Technical. So first I select a metadata group that you want to update and select "New Term Set" command: I call it Document Categories and Save it. Then I select this new term set and choose "Create Term" command: To create "Accounting" term: Then create as many terms as I want to get Accounting and Technical as I wanted: You can also do other command with your terms - Copy, Reuse, Merge, Deprecate, Move, Delete: After that I add Managed Metadata to my content type that I use for documents, select Document Categ

Last week I worked 2.5 days doing SharePoint 2010 using Ubuntu 10.04 installed on my 6 yo laptop. Laptop: Samsung P28, Intel Celeron M, 1Gb RAM, 40Gb HDD, WiFi network adapter. Browser: Mozilla Firefox for Ubuntu canonical 1.0 Tasks I was able to do in regard to SharePoint implementation: - Document management. Creating documents using OpenOffice then uploading them into SharePoint via browser. - Management of custom lists, content types, site columns, views etc. All site settings available from Web browser UI. - Forms Authentication and Search set up. I used rdesktop to connect remotely to the SharePoint Web and Application server. Positive: - I have got most of the new features of user experience: ribbon, menus, styles etc. - If I don't need custom Web applications development for SharePoint or SharePoint Designer work on my laptop or other client machine I can use Open Source and free software easily. Anyway Visual Studio and SharePoint Designer could be installed st

I have recently set up a standalone SharePoint 2010 environment. The Web application was created with host header and the site collection is accessible from the client machines, but not internally. That was because of using FQDN to access the Web site. The error when I tried to access site internally was similar to the one described here: You receive error 401.1 when you browse a Web site that uses Integrated Authentication and is hosted on IIS 5.1 or a later version And the search returned the following error in the Event Log: "The start address    cannot be crawled. Context: Application 'Search_Service_Application', Catalog 'Portal_Content' Details: This item could not be crawled because the crawler could not connect to the repository." One of the suggestions was to disable the loopback check, but that would compromise the Web server. So what I have done was: 1. Added a binding to my IIS Web site for a different port. Let's say my Web