DiagnosticMonitorConfiguration config = DiagnosticMonitor.GetDefaultInitialConfiguration();
config.Logs.ScheduledTransferLogLevelFilter = Microsoft.WindowsAzure.Diagnostics.LogLevel.Verbose;
DiagnosticMonitor.StartWithConnectionString("Microsoft.WindowsAzure.Plugins.Diagnostics.ConnectionString", config);

It took me a while to realize what was going on! Just before leaving for Christmas vacation I had updated to Azure SDK 2.5 and only since then I had not looked at the traces much. The cause for my problem was that Azure SDK 2.5 has breaking changes which disable setting diagnistics settings using code, instead you need to use an XML config file which is deployed to Azure. See https://msdn.microsoft.com/en-us/library/azure/dn873976.aspx#BKMK_breaking for details and links to samples.

First I downloaded the diagnostics XML file from Azure using: Get-AzureServiceDiagnosticsExtension -ServiceName <<service name>>

Then I (almost) got the file below. Almost, because for some reason it was mssing the PublicConfig element and I had to add it manually to be able to upload it back to Azure.  I changed the scheduledTransferLogLevelFilter to Information, that is all.

<?xml version="1.0" encoding="utf-8" ?>
<PublicConfig xmlns="https://schemas.microsoft.com/ServiceHosting/2010/10/DiagnosticsConfiguration">
<WadCfg>
  <DiagnosticMonitorConfiguration overallQuotaInMB="4096">
    <DiagnosticInfrastructureLogs scheduledTransferLogLevelFilter="Error" />
    <Directories scheduledTransferPeriod="PT1M">
      <IISLogs containerName="wad-iis-logfiles" />
      <FailedRequestLogs containerName="wad-failedrequestlogs" />
    </Directories>
    <WindowsEventLog scheduledTransferPeriod="PT1M">
      <DataSource name="Application!*" />
    </WindowsEventLog>
    <CrashDumps>
      <CrashDumpConfiguration processName="WaIISHost.exe" />
      <CrashDumpConfiguration processName="WaWorkerHost.exe" />
      <CrashDumpConfiguration processName="w3wp.exe" />
    </CrashDumps>
    <Logs scheduledTransferPeriod="PT1M" scheduledTransferLogLevelFilter="Information" />
  </DiagnosticMonitorConfiguration>
</WadCfg>
</PublicConfig> 

To upload the file back to Azure I used these simple Powershell commands:

Add-AzureAccount
$storage = New-AzureStorageContext -StorageAccountName <<storage Account name>> -StorageAccountKey <<key>>
Set-AzureServiceDiagnosticsExtension -ServiceName <<service name>> -StorageContext $storage -Role <<role name>> -Slot Production -DiagnosticsConfigurationPath <<full path to XML config file>>

My own experience is that this is not required! We recently configured SharePoint 2010 User Profile Synchronization against Novell eDirectory 8.8 SP6 without having write permissions, see security settings for the account below.

This non-compliance was discovered during installation of a new test environment when we had problems synchronizing user profiles. I asked for validation of permissions and the eDirectory team came back with the picture above, along with the information that this is how it looked in both QA and Prod. When I later identified the real reason for the synchronization problem everything worked fine, even though we do not have Write permissions.

I have no idea if the same applies for Active Directory or the SunOne directory. But from a least privilege perspective it may be worth testing if you get the chance!

Typically you execute something like this to fix the problem:
Add-SPShellAdmin –UserName contoso\mattias

Recently I was working with a customer who named all admin-accounts with a leading $-character, i.e. contoso\$mattias. Not being a true PS professional it took me some time to figure out that $ is a control character i PS. To be able to add an account with a leading $-character you need to add the escape character backward apostrophe (`).

So when using $-accounts you need to execute:
Add-SPShellAdmin –UserName contoso\`$mattias

Some research revealed that when Active Directory is running in Windows 2000 functional level there is no Delegation tab, it only appears when running AD in Windows 2003 (or higher) functional level. We were using Windows 2008 functional level so that was not the problem.

However, further research also revealed that the Delegation tab is only displayed when there is at least one value set in the servicePrincipalName attribute. At that was the solution to our problem!

Side note 1: Setting a ServicePrincipalName (SPN) can be performed in a number of ways; ADSIEdit, Attribute Editor in ADCU and SETSPN.EXE. I like creating things that can be easily repeated in other environments (dev, verification, production, …) so I prefer creating BAT-files using SETSPN.EXE, but YMMV.

Side note 2: Now I also realize why the guides around Kerberos configuration tell you to first set the SPNs and then enable Delegation on the service accounts…

Below are some screenshots from my virtual development enviornment to illustrate the topic below. The first screenshot show my service account with no SPN set.

The next screenshot show that if you turn on Advanced Features in ADCU you can edit object attributes directly in the Properties dialog, using the Attribute Editor tab. You can either enter this value directly in this dialog or you can run SETSPN.EXE http/lom KRYSS\sqlservice.

So when you set at least one SPN for the object you get the Delegation tab. Nice and easy!

När jag undersökte default.aspx så klickade jag på Show Related Resources och såg då nästan direkt att det fanns en Broken Link. I detta fall var det länken till min master page som jag hade lyckats skriva fel i, och om master page är fel så kan jag acceptera att SharePoint har lite svårt att visa sidan…

Så glöm inte att SharePoint Designer kan vara till nytta även vid felsökningar, inte bara för att förändra utseende och innehåll på en site.

• Förbättringar i gränssnitt
• Nya programmerings modeller såsom LINQ och Client Object Model
• Business Connectivity Services för att använda external datakällor
• PerformancePoint Services
• Förbättringar i SharePoints sökfunktioner, arvet från FAST…
• Den nya arkitekturen för delade tjänster i SharePoint, här ingår det som tidigare ingick i Shared Service Provider (SSP) samt flera nyheter såsom en central tjänst för att hantera taxonomier
• Integration med Visual Studio

Du kan även ladda ner Sharepoint 2010 Beta Developer Training Kit från https://www.microsoft.com/downloads/details.aspx?familyid=BFD1603B-7550-4B8E-BE85-4215A5069B90&displaylang=en, den ger dig tillgång till ytterligare material som du kan använda när du rampar upp mot SharePoint Server 2010.

Du kan också ladda ner ytterligare material från https://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=f1599288-a99f-410f-a219-f4375dbe310c. Nerladdningen ger dig tillgång till labbar (inkl källkod) och PowerPoint presentationerna från web casts, det kommer även med en sida med länkar till alla web casts. De labbar som är med är:

• Getting Started with Office 2010 Development
• Office 2010 UI Customizations
• Client Workflow
• Security and Deployment
• Open XML
• InfoPath and Forms Services
• Business Connectivity Services
• Office 2010 Service Applications
• Developing BI Applications

Mer information om utveckling på Office 2010 hittar du på Office Developer Center, https://msdn.microsoft.com/sv-se/office/default(en-us).aspx.

When running the SharePoint Products and Technologies Configuration Wizard we got the error “Failed to create the configuration database” along with the detailed error “User cannot be found”, the error occurred during Step 2 of 9 of the wizard but we could see that two databases were created on the database server before the wizard failed. After extensive error checking we finally found the problem when examining the firewall logs, we saw that SharePoint were trying to access an incorrect domain controller (DC). The DC that was being accessed was not open for access so all requests to it were denied, hence we got “User cannot be found”.

The reason the DC was not accessible is that we have multiple VLANs and for each access across VLAN boundaries we need to set firewall rules to open the specific ports between the machines. We also have two separate domain controllers, one “master” DC and one read-only DC, and normally all access should be made to the read-only DC. However, in this case SharePoint (and the server) were configured to use the “master” DC to which no one can communicate as all ports were locked down.

So the lesson learned is that if you get “User cannot be found” during the SharePoint Products and Technologies Configuration Wizard you may have a problem accessing the domain controller.

Först pratade Niklas Goude om hur PowerShell kan användas i samband med SharePoint. Han visade hur man kan scripta skapandet av hela siter, inkl skapa nya listor och kolumner och innehåll… Du kan ladda ner Niklas coola PowerShell script och testa själv!

Efter pausen gjorde Wiktor Wilén en mycket bra demo av hur man skapar dashboards i PerformancePoint Server (PPS) och publicerar dem i SharePoint. Om du har missat det så kommer SharePoint Server 2010 att innehålla en tjänst kallad PerformancePoint Services som kommer ersätta en stor del av den funktionalitet som idag finns i PPS.

Tack för ett mycket bra arrangemang! Jag ska definitivt delta fler gånger!