Sharepoint Forum

Ask Question   UnAnswered
Home » Forum » Sharepoint       RSS Feeds

Domain migration problem

  Asked By: Colt    Date: Nov 29    Category: Sharepoint    Views: 3567

I was recently asked to migrate a bunch of users from a Windows domain
that's being retired to another domain. I pulled the user names of
everyone on the old domain by looking at our main content database and
doing the following on the UserInfo table:

SELECT tp_Login
FROM UserInfo
GROUP BY tp_Login
ORDER BY tp_Login

I then used an Excel spreadsheet to create my stsadm commands, all in
the format of:

stsadm -o migrateuser -oldlogin OLDDOMAIN\user -newlogin
NEWDOMAIN\user -ignoresidhistory

I've noticed that a very small subset of the users didn't get migrated
properly, and won't migrate no matter what I do. I issue the command
above (substituting their user names, of course) and get "Operation
completed successfully", and yet, checking the database afterwards
still shows them listed under the old domain. No matter how many
times I run this command, it won't move the users over properly.

Is there something subtle that I'm missing about the migrateuser
option, or is there a way around this?



6 Answers Found

Answer #1    Answered By: Gretchen Stokes     Answered On: Nov 29

Is there anything in the Log file in 12\Logs? The only problem  I've ever had
with that was trying to run  it without the newdomain\user being valid. As long
as it's been valid the command  has worked for me.

Answer #2    Answered By: Angarika Shroff     Answered On: Nov 29

There aren't even any log files from today (10/1) - the most recent is
9/20, which makes me think that this isn't a loggable error per se.

I did notice that a couple users  failed migration  because of an error
to the effect that the account was not unique or didn't exist (I don't
remember the precise wording). As far as I can tell, I can't easily
remove these users, since stsadm  -o deleteuser will only work if I
know what site the user  belongs to.

Answer #3    Answered By: Eliza Hutchinson     Answered On: Nov 29

Try removing the stale old users  with the techniques from here,

Answer #4    Answered By: Lesley Tate     Answered On: Nov 29

Oops - was looking in the wrong directory (I was over in the
"Microsoft Office Server" directory instead of C:\program files\Common
Files\Microsoft Shared\web server extensions\12\LOGS - my mistake).

Here's the error message I was trying to recall:

10/01/2007 10:36:34.28 STSADM.EXE (0x1E34)
0x1CDC Windows SharePoint Services General
72ju High stsadm: The user  does not exist or is not unique.
Callstack: at
pvarContentDsns, String bstrOldLogin, String bstrNewLogin, Boolean
bEnforceSidHistory, String& pbstrNewLogin, Byte[]& ppsaOldSid, Byte[]&
ppsaNewSid, Object& pvarSidHistory, Object& pvarSiteIds) at
oldLogin, String newLogin, Boolean enforceSidHistory) at
keyValues) at
globalAdmin, String strOperation, StringDictionary keyValues,
SPParamCollection pars)

The log files are incredibly cluttered, but I did manage to find one
of the users  that I know didn't migrate  properly:

10/01/2007 10:35:38.15 STSADM.EXE (0x18B8)
0x0ADC Office Server Office Server General
7hvv Medium MigrateAccount: Migrating user 'OLD\***' to 'NEW\***'
(SID lookup successful).
10/01/2007 10:35:38.22 STSADM.EXE (0x18B8)
0x0ADC Office Server Office Server General
7hvw Medium MigrateAccount: successfully  migrated 'OLD\***' to

I'll clear out the log directory and run  it again tomorrow morning and
see if there's any difference in the log messages (our log directory
is insanely cluttered, apparently...)

Answer #5    Answered By: Chris Daniel     Answered On: Nov 29

I reran some of these this morning - all I get are the same
errors/success messages as detailed in the last message. Even if it
indicates success, they're still actually in the database  under
old_domain\user. This is MOSS 2007, which I forgot to mention
earlier. I can't seem to get the trick for deleting users  to work,
primarily because I have no idea what site they actually belong to.

Answer #6    Answered By: Lynn Mann     Answered On: Nov 29

First let me reiterate that I'm not a developer and am not the person
who used the stsadm  -o migrateuser command  in our environment. However,
as the business owner I did participate the many, many support calls we
had with Microsoft afterwards. We discovered there is a bug in or
related to the use of that command that had the end result of corrupting
SIDs in the user  table (in our case, causing our search crawl to fail).
We were the first users  to report it to MSFT and work through it with
them, and there have been others since then. As I understand it now,
MSFT is working on a hotfix for it. They were able to get us a patch
that tells the crawl to ignore the corrupted SIDs, but that isn't the
best long-term solution. We've seen a few downstream funky things that
we think may be related as well.

All this to say that I'm suspicious of the stsadm -o migrate  user
command at this point, and you should probably be on the phone to
premier support about this one.

Didn't find what you were looking for? Find more on Domain migration problem Or get search suggestion and latest updates.