http://msmvps.com/blogs/paulomorgado/archive/2010/04/08/linq-enhancing-distinct-with-the-predicateequalitycomparer.aspx

Here is a great article on creating custom administration pages in sharepoint.

http://platinumdogs.wordpress.com/2010/07/12/sharepoint-creating-custom-administration-pages/

Try this helpful little tidbit.

SPUtility.GetGenericSetupPath(@"TEMPLATE\FEATURES");

Problem: when you send a link from Communicator client to another, the link isn’t clickable, has a _ (underbar) in front of it, or both.  Results may be different on different computers. It’ll look like this

_http://www.google.com

Solution:  Two things are happening here that are not related.  The first is the OCS Server (and Edge Server) have the URL Filter enabled, which are adding the _ underbar to all links.  Also called “Intelligent IM Filter”.  You need to tone that filter down or disable all together to your liking.  If users are coming in through an Edge Server, they will follow the Filter settings of the Edge Server they are using, which seams to supersede the Front End Server (my guess is the most restrictive wins).  So be sure to set it on both servers separately.  Results were instant in new IM’s.

The other issue is the lack of a clickable hyperlink.  If you disable the URL Filters above, the underbar goes away but links are still not blue and underlined.  To fix this you need to apply a GPO or set a local registry setting to allow Communicator to make hyperlinks clickable:

HKEY_CURRENT_USER\Software\Policies\Microsoft\Communicator\
new DWORD EnableURL=1

After that exit and restart Communicator.

In both of these cases they are secure by default, which is great; but even years after this features release over several versions their use and configuration are still a mystery to most starting out.

After getting Windows 7 x64 installed, I was having a problem getting a few gadgets to work correctly (like the Pandora Gadget). It turns out this gadget uses Flash, which only comes in a 32 bit version. The Sidebar is x64, and can't access Flash. Since there is no x64 version of flash (come on Adobe -- its time to bite the bullet!!), I started digging around for a way to overcome this limitation -- as luck would have it, Microsoft ships the 32-bit version of the side bar in the x64 versions.  Now all I needed to do was get it to startup instead of the default x64 bit version.

Edit the following Registry Key:
\\HKCU\Software\Microsoft\Windows\CurrentVersion\Run\SideBar

Change the key to this: C:\Program Files (x86)\Windows Sidebar\sidebar.exe /autoRun

(The only addition is loading sidebar.exe from c:\program files (x86)\ instead of c:\program files\)

This should get you by until Adobe gets their act together!