MCPBlog

December 2009 - Posts

TFS 2008 convert Workgroup license to Standard
Body:

If you have installed Team Foundation Server 2008 Workgroup edition than you may or may not know that you are eligible to only 5 licensed users. To unlock full potential of TFS for > 6 users you need to convert your product to Standard Edition.

Of course you need to have Standar Edition license, or if you have MSDN subscription, you can get it from there. Technet user, don't bother to look on technet since TFS is not available via technet. Microsoft Partners (Regular or Gold) will have to browse their DVD's or MSDN.

If you have key keep reading.

Go to add/remove programs, find TFS and select Change/Remove button:

Maintenance mode Options page will appear and you'll find that PID field is been prepopulated with some key. Don't be happy, because this is workgroup edition key!!! Silly, isn't it.

Problem is that setup.sdb file is been prepopulated with this key, and you need to delete PID section from this file. File can be found at:

C:\Program Files\Microsoft Visual Studio 2008 Team Foundation Server\Microsoft Visual Studio 2008 Team Foundation Server - ENU\Setup.stb

Open it with Notepad, find and delete section Product key (both rows), and save changes.

Restart maintenance mode via "change/remove" and the fields are enabled. Type new product key, and press Next.

To verify version of TFS open registry (regedit.exe) and browse to:
HKEY_LOCAL_MACHINE > SOFTWARE > Microsoft > VisualStudio > 9.0 > TeamFoundation > Registration

You'll find a value named, "Edition_CT", Here's the table of available values to determine which edition you have:

  • "Full" = Team Foundation Server ("Standard Edition")
  • "Trial" = Team Foundation Server 180-day Trial Edition
  • "Workgroup" = Team Foundation Server Workgroup Edition
Category: ASP.net
Published: 18.12.2009 13:02
Posted: Dec 18 2009, 01:02 PM by MCPblog: Posts
Filed under:
“Contains” is missing from SharePoint Advanced Search
Body:

Last night I was setting up SharePoint Advanced Search Box in Enterprise Search and I was puzzled for a couple of seconds. For all text fields that I had in metadata mappings, I had no option "Contains" and "Does not contain"!!!

But I had couple of technical documentation for "old" implementation, and had no single word about this needed to be set explicitly. "New" implementation of Search has also been slightly modified but I had no clue what happened. So I decided to investigate and luckily I've found problem/solution.

If you don't have Microsoft Office Servers Infrastructure Update in your SharePoint farm than you have this problem (Or if you have SP2).

Don't panic!!!

Simply add following piece <Option Name="AllowOpContains" Value="True"/> underneath root node.

  • Go to Advanced Search page and click Site Actions, and Edit Page.
  • On the Advanced Search Web Part, click Edit in upper right corner of web part, and then click Modify Shared Web Part.
  • In the Properties text box, click the small rectangle Builder.

  • In the Builder dialog box, under the root node create <Option Name="AllowOpContains" Value="True"/> and click OK.

Why has this been removed from SharePoint?

This option has been removed from the Advanced Search page, because setting this restriction can issue a very extensive SQL query, such as "CONTRACT". This causes a huge load on SQL server and such queries often timeout!!!

So take care with this option.

Category: Sharepoint
Published: 7.12.2009 22:29