Setup & configure the User Profile Service Application (SharePoint 2010)

the way to do it: http://www.harbar.net/articles/sp2010ups.aspx

"Unable to connect to SQL Server Instance" when installing SCVMM 2007 R2

When you try to install System Center Virtual Machine Manager 2007 R2 and configure it with an existing SQL Server installation, you must have named pipes enabled on the SQL Server. If named pipes are not enabled, you will receive the following error:

setup cannot connect to the specified sql server instance

Also, when using a SQL Server 2008 installation, you must install the SQL Server 2008 Native Client and SQL Server 2008 Command Line Utilities on the SCVMM Server. Both can be installed from the SQL Server CD or downloaded from http://www.microsoft.com/downloads/details.aspx?FamilyId=C6C3E9EF-BA29-4A43-8D69-A2BED18FE73C&displaylang=en

Running remote desktop on a Windows Server Core 2008

I am currently investigating on running hyper-v server on my development machine. The main reason is the low footprint. However, as it turns out, it is not possible to ‘connect’ to the VM’s hosted on the hyper-v server from the core box itself, as the terminal services component (aka remote desktop) is missing from the Server Core.

According to Jason Hutt’s post at http://jasonhuitt.com/blog/post/Server-Core-2008-No-Built-In-MSTSC.aspx you can add the TS functionality to a Server Core box by copying the following files from a Windows Server 2008 or Vista SP1 machine

\Windows\System32\mstsc.exe

\Windows\System32\mstscax.dll

\Windows\System32\en-US\mstsc.exe.mui

\Windows\System32\en-US\mstscax.dll.mui

I have not tested this yet, but will update this post as soon as I do.

Using javascript in the NavigateUrlFormat property of the SPMenuField

When you use an SPMenuField in an SPGridView, you can use the NavigateUrlFormat property to specify an url to navigate to when the users clicks the cell. Using the TokenNameAndValueFields and the NavigateUrlFields properties you can specified tokens in the Url that should be replaced with the underlying values from the datasource for each row in the grid. This all works fine, but when you try to use a javascript function in the NavigateUrlFormat property, the javascript function is never rendered.

SPMenuField colMenu = new SPMenuField();

colMenu.HeaderText = "Company";
colMenu.TextFields = "Company";

colMenu.MenuTemplateId = "mnuCompany";
colMenu.TokenNameAndValueFields = "COMPANYID=CompanyId";
colMenu.NavigateUrlFields = "CompanyId";
colMenu.NavigateUrlFormat = "javascript:alert('you have clicked company with id {0}');";
colMenu.SortExpression = "Company";

When you start digging around in the SharePoint libraries using reflector, you’ll see that reason for this is that the code that renders the menu (Microsoft.SharePoint.WebControls.Menu.Render(HtmlTextWriter)) makes a call to ‘SPHttpUtility.HtmlUrlAttributeEncode(string url)’ passing the value of the NavigateUrlFormat (in the SPMenuField class, the value of NavigateUrlFormat is passed to the NavigateUrl property of an internally create Microsoft.SharePoint.WebControls.Menucontrol).

The method SPHttpUtitlity.HtmlUrlAttributeEncode makes a call to SPUrlUtility.IsProtocolAllowedto verify is the requested protocol (javascript: in our case) is allowed. Since the 'javascript' protocal is not in the list, the link will simply not be rendered.

The list of allowed protocols is an hardcoded string array that is initialized in the constructor of SPUrlUtility.

 

static SPUrlUtility()
{
    m_rgstrAllowedProtocols = new string[] { "http://", "https://", "file://", @"file:\\", "ftp://", 
		"mailto:", "msn:", "news:", "nntp:", "pnm://", "mms://", "outlook:" };
}

 

The list of allowed protocols is available through the public AllowedProtocolsproperty, but it is read-only and since it’s an array, it’s not possible to add additional items to it.

As a workaround, I decided to replace one of the values in the AllowedProtocols array before I render my control in the Render event and set the initial value back when the rendering is done.

The downside of this approach is that any links using the protocol that you replace in the array will not be rendered (as it is no longer an allowed protocol). Therefore I chose to ‘replace’ one of the lesser used protocols: ‘pnm://’

As you can imagine, this is not best practice and even not recommended. Although the AllowedProtocols property is public and therefore should always be available (then again, who will stop MS from changing the public interfaces of their classes if they really want to?).

protected override void Render
{
	SPUrlUtility.AllowedProtocols[9] = "javascript:";
	try
	{

		base.Render(writer);
	}
	Finally
	{
    	SPUrlUtility.AllowedProtocols[9] = "pnm://";
	}
}

protected override void CreateChildControls()
{

	SPGridView grid = new SPGridView();

	SPMenuField colMenu = new SPMenuField();

	colMenu.HeaderText = "Company";
	colMenu.TextFields = "Company";

	colMenu.MenuTemplateId = "mnuCompany";
	colMenu.TokenNameAndValueFields = "COMPANYID=CompanyId";
	colMenu.NavigateUrlFields = "CompanyId";
	colMenu.NavigateUrlFormat = "javascript:alert('you have clicked company with id {0}');";
	colMenu.SortExpression = "Company";

	grid.Columns.Add(colMenu);

	this.Controls.Add(grid);

	... (rest of code ommitted)

}

Change the language of SharePoint Site(s)

Mirjam van Olst of Macaw (http://www.macaw.nl) explains how to update the language of existing SharePoint sites by running a sql statement on the content datbase.

http://www.sharepointblogs.com/mirjam/archive/2008/04/29/changing-the-language-of-an-existing-sharepoint-site.aspx

For changing the language of all sites in the content database to Dutch the query would be:

UPDATE dbo.Webs SET Language = 1043

Changing the language of one site collection can be done with:

UPDATE dbo.Webs SET Language = 1043 WHERE SiteId = [[SiteCollectionId]]

And for changing the language of a single web or subsite you can use:

UPDATE dbo.Webs SET Language = 1043 WHERE Id = [[WebId]]