Out of the box there is a refinement panel for ‘Result Type’ however this is different to the content type, e.g. Word as opposed to Proposal. So the challenge was to create a new refinement panel to replace the Result Type refinement panel. Note, it was to replace in my case but there’s no reason why it can’t be in addition to:
Great article on getting this done:
http://www.glynblogs.com/2011/01/create-a-content-type-search-refinement-panel-in-sharepoint-2010.html
http://www.sharepointinnovations.com
Enjoy!
Wednesday, May 25, 2011
Monday, May 16, 2011
Microsoft SharePoint 2010 Administration Toolkit v2.0
The Microsoft® SharePoint® 2010 Administration Toolkit contains functionality to help administer and manage Microsoft® SharePoint® Foundation 2010 and Microsoft® SharePoint® Server 2010.
SharePoint Diagnostics Studio is awesome!
Download the toolkit from http://www.microsoft.com/downloads/en/details.aspx?FamilyID=718447d8-0814-427a-81c3-c9c3d84c456e&displaylang=en
P.S. Try it on your dev/test farm before moving to production...
Enjoy!
http://www.sharepointinnovations.com
SharePoint Diagnostics Studio is awesome!
Download the toolkit from http://www.microsoft.com/downloads/en/details.aspx?FamilyID=718447d8-0814-427a-81c3-c9c3d84c456e&displaylang=en
P.S. Try it on your dev/test farm before moving to production...
Enjoy!
http://www.sharepointinnovations.com
SharePoint 2010 Service Pack 1 - Arriving in June 2011
Service Pack 1 in late June 2011 .. Site Recycle Bin, StorMan is back :-)
Enjoy SP 2010 SP1
http://www.sharepointinnovations.com
Enjoy SP 2010 SP1
http://www.sharepointinnovations.com
SharePoint 2010 Reporting Services Integration Authentication Fix
Server 1 (WFE), Server 2 (APP & Central Admin), Server 3 (DB w/ Report Server) - NTLM install
In SharePoint Central Administration -- General Application Setting - Reporting Services Integration
Selected the RS URL and "Trusted Account", domain user name & password (Server 3, local admin domain account for RS access)
Everything will work fine including activation of the features on existing site collections BUT when you click on Set Server Defaults, you will end up getting The request failed with HTTP status 401: Unauthorized
Fix
KB article has the answer: http://support.microsoft.com/kb/871179/en-us
On Server 2 (App & Central Admin)
To work around this behavior if you have multiple application pools that run under different domain user accounts, you must force IIS to use NTLM as your authentication mechanism if you want to use Integrated Windows authentication only. To do this, follow these steps on the server that is running IIS:
http://www.sharepointinnovations.com
In SharePoint Central Administration -- General Application Setting - Reporting Services Integration
Selected the RS URL and "Trusted Account", domain user name & password (Server 3, local admin domain account for RS access)
Everything will work fine including activation of the features on existing site collections BUT when you click on Set Server Defaults, you will end up getting The request failed with HTTP status 401: Unauthorized
Fix
KB article has the answer: http://support.microsoft.com/kb/871179/en-us
On Server 2 (App & Central Admin)
To work around this behavior if you have multiple application pools that run under different domain user accounts, you must force IIS to use NTLM as your authentication mechanism if you want to use Integrated Windows authentication only. To do this, follow these steps on the server that is running IIS:
- Start a command prompt.
- Locate and then change to the directory that contains the Adsutil.vbs file. By default, this directory is C:\Inetpub\Adminscripts.
- Type the following command, and then press ENTER: cscript adsutil.vbs set w3svc/NTAuthenticationProviders "NTLM"
- To verify that the NtAuthenticationProviders metabase property is set to NTLM, type the following command, and then press ENTER: cscript adsutil.vbs get w3svc/NTAuthenticationProvidersThe following text should be returned:
NTAuthenticationProviders : (STRING) "NTLM"
http://www.sharepointinnovations.com
Thursday, May 12, 2011
SharePoint Taxonomy Governance Policies - Information Architecture
How to create a taxonomy governance policy:
- Identify all of the data collected within your organization’s portal. (You should already have the list from previous exercises).
- Next, you will “structure” the data, organizing it by the following categories:
- Structured Data – Data that is organized, either hierarchically or in an existing taxonomy of some sort. This is data such as databases, Excel spreadsheets, Access databases, or even SharePoint lists that are organized and searchable by data types within the content (i.e. Name, Address, Phone, etc).
- Unstructured Data – This is ad-hoc data contributed freely by end users. Examples of unstructured data include emails, Word documents, PowerPoint presentations, audio/video files, images, etc. In other words, things that are not searchable (unless you added metadata or they get “crawled”, such as by an Index Server).
- Semi-structured data – This is unstructured data that has been organized and/or has metadata attached. Examples of semi-structured data include SharePoint lists, Document libraries, Project and Team Sites, etc.
- Once organized, determine who views the content vs. who contributes the content. For example(s):
- MySites – Everyone can view them and everyone can contribute to their own.
- News and Announcements – Everyone can view them, but only Admins or Division heads can contribute.
- Division Portals – Some people can view them, and some people can contribute to them.
- Team or Project Sites – Select people can view them and contribute equally.
- Lastly, you will create a Policy, stating WHO owns and manages this content. The intent here is to hold people accountable (at various levels) for keeping the data properly organized throughout the Portal’s lifecycle.
Topologies for SharePoint Server 2010
Here is a really PDF from MS on SP 2010 topologies and service application assignments.
http://www.microsoft.com/downloads/en/details.aspx?FamilyID=FD686CBB-8401-4F25-B65E-3CE7AA7DBEAB&displayLang=en
Happy Thursday!
http://www.sharepointinnovations.com
http://www.microsoft.com/downloads/en/details.aspx?FamilyID=FD686CBB-8401-4F25-B65E-3CE7AA7DBEAB&displayLang=en
Happy Thursday!
http://www.sharepointinnovations.com
Saturday, May 7, 2011
SharePoint 2010 and SQL Server 2011 - Reporting Services
Project Crescent is designed to be highly interactive and is targeted at all reporting users from CEOs to power users. Crescent provides drag and drop ad-hoc reporting functionality and was built entirely on Silverlight.
One of the interesting features is called Storyboarding. This features allows users to embed charts and graphs in Microsoft PowerPoint. The cool thing is the live link between PowerPoint and the underlying data. It does appear that Crescent will require SharePoint 2010 to run, which might be too complex for small IT organizations. Crescent will leverage Microsoft PowerPivot, which was released with SQL Server 2008.
Project Crescent is expected in SQL Server 2011 (Denali) CTP2, which could be out in April. In the meantime, check out the YouTube video Introducing Project Crescent, which shows us a few of the visualizations.
Have a great weekend!
http://www.sharepointinnovations.com
One of the interesting features is called Storyboarding. This features allows users to embed charts and graphs in Microsoft PowerPoint. The cool thing is the live link between PowerPoint and the underlying data. It does appear that Crescent will require SharePoint 2010 to run, which might be too complex for small IT organizations. Crescent will leverage Microsoft PowerPivot, which was released with SQL Server 2008.
Project Crescent is expected in SQL Server 2011 (Denali) CTP2, which could be out in April. In the meantime, check out the YouTube video Introducing Project Crescent, which shows us a few of the visualizations.
Have a great weekend!
http://www.sharepointinnovations.com
Subscribe to:
Posts (Atom)