The first cumulative update (“June 2010 CU”) for SharePoint 2010 has been released as blogged by Stefan Goßner.

It seems that Microsoft still follows the 2007 CU model – the CU is composed of several packages. I would have also expected CUs to be distributed as official updates, but at least the June 2010 CU is still just…

As I wrote earlier, SharePoint 2010 ships with a profile synchronization engine from ForeFront Identity Manager. After performing several SharePoint 2010 environment installations, this seems also to be the most fragile part of the SharePoint 2010 architecture especially when using a least privileged accounts install model.

There are lots of content in the blogs and TechNet related to…

Here’s another handy quickie: we have a bunch of users we want to add as owners when building a SharePoint site, but the adduser STSADM command won’t accept an empty email address. We don’t have real addresses for the users, nor do we want to make something up.

The SharePoint API doesn’t require that users have email addresses, though, so…

Before the launch SharePoint 2010 was advertised to come with “AD or LDAP writeback” capabilities. SP2010 ships with the the profile synchronization engine from ForeFront Identity Manager (FIM). This is a huge step from the simple profile import functionality of MOSS.

When hearing this, every IT administrator gasps. Will SP2010 mess with my Active Directory?  Suspicions arise when SharePoint guys come to…

[edit: I forgot to save after updating the post with the relevant registry path. Apologies.]

Last weekend I was tasked with installing a cumulative update on two SharePoint servers and then joining them to two different farms. Pretty basic stuff, except for one thing: the servers were configured to be connected to two older farms, but the old farms were…

Here’s a quick update to break the silence: while browsing Twitter this morning, I came across a link that should be interesting for us PowerShell aficionados. It turns out that trying to use the 64-bit SharePoint assemblies from a 32-bit PowerShell host might not work. While the fix is trivial, the error message is certainly misleading: it looks as if…