Fejl i SharePoint Navigationen

Når jeg står på et subsite og gerne vil se alle mine ”lister” på det gældende subsite, så tidligere trykkede jeg bare på ”lists” og så kunne jeg vælge den liste jeg nu ønskede. Efter vi ominstallerede, så springer den op på hovedsitet og viser de lister der måtte ligge der, i stedet for at jeg får de lister jeg har lavet under subsitet. Jeg tror måske det kan have noget med rettigheder at gøre, da jeg får fejl hvis jeg forsøger at vælge site action – site permissions så fejler den nemlig også. Så tror måske der er noget med sikkerheden på mine subsites.
Alternate Mapping Access !!!

Sharepoint videos
Klik her

Image Rotator:

Show Hide fields:

Quick Fix: Remove Libraries, Lists From ToC | SharePoint Sharpener

Read it online:



Overblik over Service Applications

Service applications


SharePoint Foundation 2010

SharePoint Server 2010 Standard

SharePoint Server 2010 Enterprise

Access Services

Lets users view, edit, and
interact with Access 2010 databases in a Web browser.


Business Data Connectivity service

Gives access to
line-of-business data systems.




Excel Services Application

Lets users view and interact withExcel 2010 files in a Web browser.


Managed Metadata service

Manages taxonomy hierarchies,
keywords and social tagging infrastructure, and publish content types across
site collections.



PerformancePoint Service Application

Provides the capabilities of

Search service

Crawls content, produces
index partitions, and serves search queries.



Secure Store Service

Provides single sign-on
authentication to access multiple applications or services.



State service

Provides temporary storage
of user session data for SharePoint Server components.



Usage and Health Data
Collection service

Collects farm wide usage and
health data, and provides the ability to view various usage and health




User Profile service

Adds support for My Site Web
sites, profile pages, social tagging and other social computing features.



Visio Graphics Service

Lets users view and refresh
published Visio 2010 diagrams in a Web browser.


Web Analytics service

Provides Web service interfaces.



Word Automation Services

Performs automated bulk
document conversions.



Microsoft SharePoint
Foundation Subscription Settings Service

Provides multi-tenant
functionality for service applications. Tracks subscription IDs and settings
for services that are deployed in partitioned mode.
Deployed through Windows PowerShell only.




Some services are provided by
other Microsoft products, including the services listed in the following table.

Service application


Office Web Apps services:

Viewing Service


Excel Calculation Services

Office Web Apps is a
Web-based productivity offering from Microsoft Office 2010 suites. Office Web
Apps services include companions to Microsoft Word 2010, Microsoft Excel
2010, Microsoft PowerPoint 2010, and Microsoft OneNote 2010. These Web-based
applications are stand-alone applications focused on offering access to Word
2010, PowerPoint 2010, Excel 2010, and OneNote 2010 documents through any
browser across multiple platforms, lightweight creation and editing
capabilities in standard formats, sharing and collaboration on those
documents through the browser, and various Web-enabled scenarios. Documents
created by using Office Web Apps are no different from documents that were
created by using the corresponding desktop applications. The associated
services are used to prepare documents for viewing and editing in a Web

Microsoft Project Server 2010

Microsoft Project Server
2010 hosts one or more Microsoft Project Web Access instances, exposes
scheduling functionality and other middle-tier calculations on Microsoft
Project data, and exposes Web services for interacting with Microsoft Project
2010 data.



If you are a SharePoint developer or administrator,
then start learning Power Shell. It’s a must have skill for dealing with
SharePoint from now on wards.

Windows Power Shell is an interactive command
line and task based scripting technology which allows administrators to
automate administrative tasks.

From SharePoint viewpoint, Power Shell has significant
performance benefits:

Here is the Power Shell script to enable a feature on
every SPSite:

$rawdata = stsadm.exe -o enumsitesurl $WebAppURL  

$sitexml = [XML]$rawdata

$sitesxml.Sites | foreachobject{ $_.Site } | foreach-object{

  stsadm -o activatefeature
$_.url -filename $featureFileName

$lastexitcode -ne 0 ){

Write-Host “Failure:$lastexitcode `n” -Fore Red;

$failure = $true;




It will take 12+ hours for 5300 SharePoint sites.
Whereas same code in Power Shell would be like following:

Get-SPSite –Limit ALL –WebApplication
$WebAppNameorUrl |%{

   Enable-SPFeature $FeatureIdOrNameurl $_.Url


And this will take only 30 minutes for same 5300 sites

So learn Power Shell and start rolling with all new
652 power shell cmdlets in SharePoint 2010 as
compared to STSADM based 182 commands in SharePoint




Get– Help Kommando (Hjælp om en speciel commando)

Get (henter information f.eks Get-SPSite

Set (Sætter

Select vælger property — F.eks. Get-Spsite url/(*)  Select Url,
Owner,  SecondaryContact
(Viser url for site(s)
Owner og Secondary Owner

| sender værdier feks fra Get



F.eks. for at oprette underwebs af en betsem type i en stribe sites:

Get-SPsite Url/* (* wildcard
tager alle med) | Foreach-object {new-spweb url
<$_.url + “/blog”> -template SItetemplate (f.eks sts#0 for
temasite eller blog#0 for blog}


Eller for at sætte en secondary owner i en stribe sites

Get-SPSite url/* -limit all | Set-SPSite
secondaryowneralias domain\username


For at se resultatet prøv

Get-SPSite url/*  | select url, owner,

Enable en feature på alle sites

Get-SPSite –Limit ALL –WebApplication
$WebAppNameorUrl | { Enable-SPFeature $FeatureIdOrNameurl $_.Url}



Avanceret til jeres brug (Multi Tenancy fra nettet
Multi Tenancy )

hosting requires powershell so the steps are all
based off of using it.

1. Create a
subscription and assign sites to it:

$sub = new-spsitesubscription


2. Pulling the
site collection or set of site collections you wish to join to the site group:


$site = get-spsite | where {$_.url –eq


you have two variables.  Variable 1 $sub object contains a new spsitesubscription.  Variable 2 $site contains a site

3. Add  the site collection $site, to the newly created site
subscription $sub.

set-spsite -identity $site –sitesubscription $sub

Check whether it
has been added correctly by doing the following:


If a database ID
exists, then you can type the following

get-spdatabase | where-object {$ -match
“full or partial guid“}

Will output the results of the associated site

4. Create a
secondary subscription and associate a different site collection within same
web application for demonstration purposes using the steps above.

5. Create a SubscriptionSettings Service Application and Proxy

Start the WSS Subscription Settings Service

B. Create
Service Application and Proxy via PowerShell

$appPool  =  New-SPIISWebServiceApplicationPool -Name SettingsServiceApppool
-Account domain\use

$sa = new-spsubscriptionsettingsserviceapplication
–Name SubscriptionSettingsServiceApplicationDatabasename SubscriptionSettingsServiceApplicationDB
applicationpool $appPool

$sap = new-SPSubscriptionSettingsSericeApplicationProxyServiceApplication $sa

6. Creating the
Tenant Admin Site for each site group

= get-spsitesubscription –identity “http://server”

$tasite = new-spsiteurlhttp://test/sites/tasite1” –template “tenantadmin#0” –owneralias domain\username –sitesubscription

7. Provision a
search service application in hosting mode.  Please see the Configure
Search Service application using Powershell blog.

8. Feature’s and

Once a feature
has been installed into the farm, it’s available to all sites and can be
activated through manage features pages.  The way to control this in a
hosting scenario is you only provide the features available to a given site
group through various PowerShell commands.  Any features not listed are
excluded and not available for all site collections that belong to the
corresponding site group.  Steps are below:

Create a feature

$fs =New-SPFeatureSet

Adding features
to a feature set:  

$farm =

$feature1 =$farm.FeatureDefinitions | where{$_.ID
eq “02464c6a-9d07-4f30-ba04-e9035cf54392”}

Add-SPFeatureSetMember -Identity $fs
FeatureDefinition $feature1

Adding feature
set to subscription:

Set-SPSiteSubscriptionConfig -Identity $sub –FeatureSet $fs