Slight delay -o migrateuser

Well there is a slight delay on some of my documentation about converting from 2.0 to 3.0. I am still in the process of documenting the process for the company, once that is finished i will do a quick conversion and put what i have up here for all to see.

What i'd like to comment on is the domain\username to newdomain\username migration process which, in my case, needs to happen every time i convert another website from 2.0 to 3.0.

During our migration process of moving WSS 2.0 to WSS 3.0 websites, i ran into a problem with the old server not being configured correctly. More to the point the server's user lists were not connected to our Active Directory. It was all done localy (yes, each user added to the local machine, and then added to the WSS 2.0 site).

This was one of the driving factors behind why the company is converting over to MOSS servers.
However, this brought up a problem for me as i converted the websites. How do i maintain username permissions but make everyone use their Active Directory login names on the new server?

Stsadm -o migrateuser

Stsadm -o migrateuser to the rescue, this allows you to move an exsiting entry in your database from one domain to another in a totaly microsoft supported mannor. The usage is fairly straightforward you simply need 3 varables after -o migrateuser for it to work:
-oldlogin olddomain\username
-newlogin newdomain\username
-ignoresidhistory
If you do not specify the -ignoresidhistory parameter in this command line, the command queries Active Directory for the SID History attribute. This attribute is automatically populated by Microsoft Windows when you migrate a user to another domain.
Take this with a grain of salt, we did it in our solution simply because i did not want to deal with any possible problems from migrating the users over.

There is an API to allow you to program in a more direct-method of auditing the login names, but i went the easy way and just created a program that made a batch file for me automatically in c#. If you want a copy of the source just hit me up, i'm more than glad to provide it.

Usefull information:

In your SQL database you can find the login information in the "Sitename_ContentDB" in the UserInfo table. The login names are stored in the tp_Login column. A quick way to pull up the list is to simply do:
SELECT tp_Login
FROM UserInfo

Comments

Post a Comment

Popular posts from this blog

CI Build broke after nugit update

One of those moments where your heart drops : Your using CI on a remote hosting service (like AppHarbor) and your build fails. You look into the fail reason and find out it is because you updated the packages in your build. Wait, my update from nuGet broke everything?! Wtf?! The error looks something like this, putting it in here for search engine's : Build started 6/10/2013 12:30:20 AM. 1>Project "D:\temp\xly5bsff.qvp\input\.sln" on node 1 (default targets). 1>ValidateSolutionConfiguration: Building solution configuration "Release|Any CPU". 1>Project "D:\temp\xly5bsff.qvp\input\.sln" (1) is building "D:\temp\xly5bsff.qvp\input\\.csproj" (2) on node 1 (default targets). 2>D:\temp\xly5bsff.qvp\input\\.csproj(880,3): error MSB4019: The imported project "D:\temp\xly5bsff.qvp\input\packages\Microsoft.Bcl.Build.1.0.7\tools\Microsoft.Bcl.Build.targets" was not found. Confirm that the path in th
Read more

Sharepoint 2007 - Access Denied when you try to edit

I'v had this solution for a little while now but never wrote it down anywhere for people to see. Here is the situation: In a site collection, you make a new list/document library in any sub-site or the main website. You then add a new item/document to the folder, and then attempt to edit the item You then see something along the lines of "Access Denied" , even if you are on the system account. This happens with every new list you create on any site or subsite. Your problem is a corrupted field definition at the site collection level. Specifically the "Effective Permissions Mask" is missing an attribute in it's xml scheme - RenderXMLUsingPattern="TRUE" The fix comes in 3 steps: 1. Update your server to the most recent cumulative update package (Service pack 2 or greater). You can get more information about this from the Sharepoint team blog post on SP2 . Included in SP2 is a hotfix that prevents this from occurring ever again on any other site co
Read more

Project 2010 and Project Pro 2007

Just a FYI since no one knew this from what i can tell already: If you are enabling BCM (Backwards Compatibility Mode) for project 2007 to connect to Project Server 2010, there are a few things you should know first. Right off the bat, clients have to be updated to Service Pack 2 . Next, when your setting up your project server, Note this key fact I could not find anywhere, and did not get hint about in the technet forms when i posted about my problems: You CAN NOT use Claims based authentication on your web application that is hosting Project Server 2010. The 2007 Client will not connect to the server. The 2010 client will connect with no problems. Quick and dirty, hope that helps everyone!
Read more