View Edwin Vriethoff's profile on LinkedIn

MigrateSPUsers: Sharepoint 2003 user account migration tool

January 30, 2008   9:10


At my current Sharepoint 2003 to 2007 migration project, we have to migrate Sharepoint 2003 users to a different domain server. On my world wide web search I bumped into an utility called “SPUserUtil” that was part of the “SharePoint Utility Suite”, but unfortunately the author decided to take the project offline and it is no longer available.

This blog post from Alexander Windel provided enough information about the process of migrating Sharepoint users. For WSS sites you can use the “stsadm -o migrateuser” command, but this is not enough for a Sharepoint 2003 Portal Server. The problem is that you’ll also need to use code to call the function PortalAccountMigrationManager.MigrateAccount() in the object model.

Last evening I created a small Sharepoint user migration utility, to make our life a bit easier. It will run both commands for you and it will allow you to migrate a larger batch of Sharepoint users at once.

(more…)

Tags: , , , , , .





How to rename the title column back to “Title”

January 28, 2008   11:53


How to rename the title column back to titleToday I’m visiting a customer who accidentally renamed the Title column in the list item content type. After they discovered that they made a mistake, they tried to rename the column back to “Title”, but SharePoint does not allow this, because you would rename the column to a reserved name.

“The Column name that you entered is already in use or reserved”

The only way to rename this column back to Title, is to talk against the SharePoint object model by writing some custom code. This blog post from Godwin Tenzing provides detailed information about the problem and also shows a quick coding example which allowed me to fix the problem within 5 minutes.

Tags: , , , , .









The content expressed in this blog are those of Edwin Vriethoff and do not represent his employer's view in anyway. The contents of this blog has been carefully put together, but Edwin Vriethoff is not responsible in any way for any direct or indirect harm caused by individuals or organizations using the content of this blog in any way.