www.sharepointmythbuster.com

One big draw back of the way AD implements LDAP is the lack of support for querying on Organisaitonal Units. No matter what you try, you will hit a brick wall when trying something like OU=SharePoint or OU:SharePoint in a simple query. Even trying to access the value as a property of an AD object will fail as OUs are not stored as properties on objects but only form part of the hierarchy and not part of the metadata.
So the only place where you can enter an OU is when you are selecting the datasource, before applying any filters. Which means only one single OU, right?

Whoever does not know this one is going to love this gem. Ever tried editing a publishing enabled page using SharePoint Designer? Then you're familiar with that wonderful error message about not being able to edit the page using SPD and you're asked to either edit the underlying publishing layout or the content using the browser.

There are numerous articles out there about how to change the system master page on SharePoint. The master that all pages in the _layouts aka LAYOUTS folder use. In most cases they want to do this to enable a different data source for the top navigation aka global navigation. The average rookie who is in charge of creating a site in Microsoft Office SharePoint Sever using the publishing feature will stumble across this problem and start hacking away at either the original application.master, or even go and implement a custom http handler to exchange the application.master with a custom one on the fly. None of these approaches are best practice nor are they supported by Microsoft. So is it possible to fix the navigation on the SharePoint layouts master page without breaking the system? Sure thing!

This is another one those myths out there. Only because it not officially supported does not mean it is impossible.
I'll show you in a few simple steps how to export your SPD workflows and import them into a VS Workflow Project.
Okay, they might not work 100% as some SPD actions are not easily migrated, but you'll have a good starting point to make it work in VS and then reuse the WF across your solutions.

Is it tremendously hard to integrate the people picker into an infopath form? NO!
It is not obviously easy, but can be done in a few steps, especially once you realise that it is called Contact Selector in Infopath and not People Picker!