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
This CodePlex project creates a custom SharePoint lookup field that offers new functionalities to default SharePoint lookup field by allowing filters to be applied to retrieved data. Applied filters can be either dynamic CAML queries or pre-defined list views residing in source lists
Below is a few of the features offered by Filtered Lookup field over standard SharePoint Lookup field:
- Cross-site lookup (all sites within same site collection)
- Filter retrieved data using list views
- Filter retrieved data using dynamic/ad-hoc CAML queries. This means you don’t need to create a list view each time you want to apply a lookup filter to source data
- Supports retrieving data recursively using either list views or dynamic queries
- Supports MultiLookup with filtered data
- Same look and feel as default SharePoint Lookup and MultiLookup (i.e. in list forms)
Find the solution here.
Tags: solution
Today I wanted to download FAST Search to have a look at it, but seeing the requirements I can not install it on my VHD. Unfortunately! 
The requirements are:
Supported Operating Systems: Windows Server 2008 R2; Windows Server 2008 Service Pack 2
The requirements below apply to single server with built-in database installations and server farm installations that include a single server or multiple servers in the farm.
Hardware Requirements
Processor
Minimum: 64-bit, 4 CPU cores, 2.0 GHz
Recommended: 64-bit, 8 CPU cores, 2.0 GHz
RAM
Minimum: 4 GB
Recommended: 16 GB
Hard Disk
Minimum: 50 GB
Recommended: 1 TB RAID* across 6 spindles
Other
DVD Drive
In general, RAID5 configurations with 128 KB stripe size provides a good combination of performance and reliability as content storage for FAST Search Server 2010 for SharePoint. Different RAID controllers have varying sweet spots for operation. SAS disks are recommended over SATA. Within a fixed power and cost budget, performance will be better with a larger number of 10k RPM disks compared to a smaller number of 15k RPM disk.
Software Requirements
Windows Server 2008 SP2 x64
Windows Server 2008 R2 x64
The server must be fully patched and restarted before you install FAST Search Server 2010 for SharePoint.
Tags: beta, FAST Search, Infrastructure, installation
There are more Microsoft 2010 (beta) products available for download.
SharePoint Foundation
SharePoint Foundation 2010 is the new version of Windows SharePoint Services.
You can download it here.
FAST Search
FAST Search Server 2010 for SharePoint Beta provides powerful high-end search delivered through SharePoint. It includes all the search features and integration capabilities of SharePoint Server 2010, plus the use of context to provide specific search experiences for different needs, and advanced content processing capabilities that create metadata and add structure to unstructured content.
You can download in here.
Source is Technet Newsletter.
Tags: beta, FAST Search, SharePoint Foundation
Microsoft is set to launch an entirely new updated wave of Office applications in June 2010. The Office suite will be updated for Windows, including ribbon support for all products, and will also be launching Office 2010 for Mac OS X sometime in 2010.
Office 2010 Professional Plus, which is available for public beta, will offer all of the office products, excluding Visio 2010 and Project 2010. Microsoft will be releasing Office 2010 with a full version and upgrade version, for users that have Office 2007 installed. Office 2010 will be available for Windows XP, Vista and Windows 7 in both 32-bit and 64-bit, excluding Windows XP x64.
Read more at the source.
Tags: release
Nice slideshow about SharePoint 2010 architecture and infrastructure on the Sparked blog:
See the slideshow here.
Tags: Infrastructure, installation
Opening a Infopath 2007 browser based form through a link in i.e. a links webpart is done by first opening the form manually, copying the complete URL, extracting the “&Source…” part from the URL and using the URL as a hyperlink. See example below:
I have a form which opens with this complete URL:
http://intranet/eforms/_layouts/FormServer.aspx?XsnLocation=http://intranet/FormServerTemplates/DeclCashSal.xsn&SaveLocation=http%3A%2F%2Fintranet%2Feforms%2FDeclaration&Source=http%3A%2F%2Fintranet%2Feforms%2FDeclaration%2FForms%2FAllItems%2Easpx&DefaultItemOpen=1
After I extract the “&Source” part the URL looks like:
http://intranet/eforms/_layouts/FormServer.aspx?XsnLocation=http://intranet/FormServerTemplates/DeclCashSal.xsn&SaveLocation=http%3A%2F%2Fintranet%2Feforms%2FDeclaration&DefaultItemOpen=1
Use this URL as a hyperlink.
Tags: Best Practices, browser based form, Howto
