First of all I want to thank Jaap Vossers (twitter: @jvossers) for putting a great jQuery script and solution on CodePlex for this. More info on CodePlex
My client wanted a more advanced kind of column filter for a SharePoint list. They have a assets library with a lot of items in it and they did not want to scroll through the complete list of all choices when they choose “show filter choices” (see below).
After searching the internet I found Jaap Vossers’ InstantListFilter. Putting a CEWP with jQuery in the source field is all you need to make this work. I would like to make one remark.
The list can not be grouped by filter (see below)
It only works (as far as I have tested it) with a expanded list.
The solution looks like this:
With Windows Azure Drive, your Windows Azure applications running in the cloud can use existing NTFS APIs to access a durable drive. This can significantly ease the migration of existing Windows applications to the cloud, enabling customers a more seamless migration experience while simultaneously reducing the amount of time it takes to move their applications from your own Windows environment to a Windows Azure environment. The Windows Azure application can read from or write to a drive letter (e.g., X:\) that represents a durable NTFS volume for storing and accessing data. The durable drive is implemented as a Windows Azure Page Blob containing an NTFS-formatted Virtual Hard Drive (VHD).
Read more at the source.
Tags: Azure, Cloud computing, Online Services
When I was looking on the internet for some info about User Profile import in SharePoint 2007 I found the blogpost of Duarte Nobrega about LDAP User Filters. Some examples of the filters are:
Default user filter:
(&(objectCategory=Person)(objectClass=User))
Exclude accounts with no email address:
(&(objectCategory=Person)(objectClass=User)(!(userAccountControl:1.2.840.113556.1.4.803:=2))(mail=*))
Exclude disabled accounts:
(&(objectCategory=person)(objectClass=user)(!userAccountControl:1.2.840.113556.1.4.803:=2))
Read more at the source.
Tags: AD
I was looking for some info about SharePoint item limits but stumbled upon a post about changing the size limit of site template. I always thought why it is only 10 MB. In the past there were several situations where I could do with more.
In this post on Mike Gannotti’s blog there is a post about changing this size. The command to use is:
stsadm -o setproperty -pn max-template-document-size -pv 20000000
(Where max-template-document-size is in Bytes; in this an example the size is changed to 20MB)
Tags: stsadm
SharePoint Prerequisites
In this second part I’ll let you see how to install the prerequisites that are needed for a successful SharePoint 2010 installation.
In part 1 of these series you might have read that I install everything on one server. Windows 2008 R2, Active Directory and SQL 2008 R2 CTP. When you’re in the same situation you don’t have to install the SQL Client tools (sqlncli.exe) and the SQL 2008 ADOMD 1.0 (SQLSERVER2008_ASADOMD10.msi).
The PowerShell script (copy script below to text file and save as .ps1 file) will be like:
#Execute prerequisiteinstaller.exe with the unattended parameter to install SharePoint prereqs
& ‘<path to SP2010 install files>\prerequisiteinstaller.exe’ ‘/unattended’ ‘/ChartControl:<path>\MSChart.exe’ ‘/IDFX:<path>\MicrosoftGenevaFramework.amd64.msi’ ‘/Sync:<path>\Synchronization.msi’ ‘/FilterPack:<path to SP2010 install files>\PrerequisiteInstallerFiles\FilterPack\FilterPack.msi’
& ‘iisreset’
If SQL is installed on another server you have to add the following parameters in the script behind “/unattended”:
‘/SQLNCLi:<path>\sqlncli.msi’ ‘/ADOMD:<path>\SQLSERVER2008_ASADOMD10.msi’
When you do not already have installed the IIS serverrole and/or Application serverrole, the prerequisitesinstaller starts the installation by installing both these roles (see screenshot)
The installation continues with all the other software:
Microsoft Geneva Framework
Microsoft SQL Server 2008 Analysis Services ADOMD.NET
Finally, your Programs and Features will show all installed prerequisites:
The series:
Part 2: SharePoint 2010 prerequisites
Part 3: SharePoint 2010 server installation (coming soon)
Tags: beta, installation, powershell
At the moment I’m busy investigating the installation of SharePoint 2010 through PowerShell scripting. Although I am a newbie to PowerShell I got a long way thanks to several sites on the internet. I shall list all the sources I used in the last post of this series.
In this series of posts I shall describe how install a single server SharePoint 2010 farm on Windows Server 2008 R2. On the same server I have installed SQL Server 2008 R2 CTP (this will not be described). So, I start with a Windows 2008 R2 server with SQL 2008 R2 and Active Directory installed. Nothing Else.
Before you can run a PowerShell script you first have to run a cmdlet to change the PS execution policy. To do so, open PowerShell and run this:
Set-ExecutionPolicy Unrestricted
The first script (copy script below to text file and save as .ps1 file) is executed to set some DC prerequisites:
$acl = Get-Acl HKLM:\System\CurrentControlSet\Control\ComputerName
$person = [System.Security.Principal.NTAccount]“Users”
$access = [System.Security.AccessControl.RegistryRights]::FullControl
$inheritance = [System.Security.AccessControl.InheritanceFlags]“ContainerInherit, ObjectInherit”
$propagation = [System.Security.AccessControl.PropagationFlags]::None
$type = [System.Security.AccessControl.AccessControlType]::Allow
$rule = New-Object System.Security.AccessControl.RegistryAccessRule($person, $access, $inheritance, $propagation, $type)
$acl.AddAccessRule($rule)
Set-Acl HKLM:\System\CurrentControlSet\Control\ComputerName $acl
Write-Host “DC prerequisites are set”
The series:
Part 1: DC prerequisites
Part 2: SharePoint 2010 prerequisites
Tags: installation, powershell
Best wishes to all my readers for this new year. Also this year I will try to keep you informed about SharePoint features, issues, flaws, solutions and news. My main focus will be on Sharepoint 2007 and 2010 (again, but no surprise off course 
), Infopath and Nintex workflow.
If you have any questions or remarks about posts don’t be shy and be so kind to posts it in the comments. I will always react to serious comments.
UPCOMING: a series of posts about scripting a SharePoint 2010 installation with PowerShell.
I’ve done Infopath all day and found some limitations I would like to share. I’m designing some browser based forms so they have limitations I know off but today I found out about some unpleasant features (at least for me and my ideas how to build the forms). I have not encountered them before.
I wanted to hide a checkbox based on some conditional formating. This was not possible unfortunately.
I also wanted to apply a rule to a check box, that is possible but I was only able to apply 5 conditions to that rule.
Tags: browser based form
At a client SharePoint 2007 farm, installed on Windows Server 2008 servers, I had to install SQL Server Reporting Services Add in for Sharepoint. I already know that one has to install with elevated privileges at 2008 but this installation required some specific steps to complete.
At first I tried this installation:
- Open a command prompt with elevated privileges (run as administrator)
- Run this command: msiexec /i “<path to msi>\rsSharePoint_x64.msi”
But this did not work. The installation failed and did a roll back. In the log file (%temp%\RS_SP_0.log) there was logged:
User: SYSTEM Installing Report Server feature. SSRSCustomActionError: SharePoint is installed, but not configured.
Also in the SQL logs there was an error: “login failed for user: <domain>\machine account$”
So the CustomAction generated an error. After some searching on the internet I found some info that finally led to the correct installation. You have to install SSRS 2008 Add in as follows:
- Open a command prompt with elevated privileges
- Run this command: msiexec /i “<path to msi>\rsSharePoint_x64.msi” SKIPCA=1
- Open Start > Run, type %temp% to open your temp directory and check if there is a file in there called rsCustomAction.exe
- Again in the command prompt, go to the temp directory and run this command: rsCustomAction.exe /i. See the screenshots about what happens next.
Execute this installation on every WFE in your SharePoint farm and the Add in will be installed.
Tags: Howto, installation, Report Server
