Prev: Share point port IRM
Next: dws CreateFolder
From: David Lozzi on 10 Jan 2008 09:55
Howdy,

Here's my scenario: A admin user (not me I swear) deleted about 20 users
from our WSS3 ADAC site. In adding the users back in they all have a number
affixed to their user names. I'm guessing Sharepoint is doing that due to
unique SIDs and whatever. Anyway, we don't want the numbered names so i
created the new user directly in the SharePoint OU of AD and then used the
stsad migrateuser command to migrate the user from the numberd account to
the normal account. This new account without the number can login
successfully! However, when they go to change their password, they get the
following error:

The user does not exist or is not unique.

I'm guessing this is due to the fact that SharePoint now has two user names
cached or stored wherever it stores it but each of the same names have
different SIDs. Again, this is a huge guess. So, anyone know how I can get
around this? Is there a SQL table I can just modify the numbered user
account manually? I know that's a no-no but I need this to work.

Thanks,

--
David Lozzi
Product Development Manager
Delphi Technology Solutions
www.delphi-ts.com - www.lozzi.net

From: Mike Walsh on 10 Jan 2008 11:33
I would save template copies of any Lists you think might have been
amended in the meantime and go back to a backup before he (not you!) did
this.

Then put those lists to a spare server and do a quick comparison to add
back things that have been added in the meantime.

Safer by far than amending the database where problems even years later
will make you think they might be because of that database change.


Mike Walsh
WSS FAQ http://www.wssfaq.com
no questions by e-mail please



David Lozzi wrote:
> Howdy,
>
> Here's my scenario: A admin user (not me I swear) deleted about 20 users
> from our WSS3 ADAC site. In adding the users back in they all have a
> number affixed to their user names. I'm guessing Sharepoint is doing
> that due to unique SIDs and whatever. Anyway, we don't want the numbered
> names so i created the new user directly in the SharePoint OU of AD and
> then used the stsad migrateuser command to migrate the user from the
> numberd account to the normal account. This new account without the
> number can login successfully! However, when they go to change their
> password, they get the following error:
>
> The user does not exist or is not unique.
>
> I'm guessing this is due to the fact that SharePoint now has two user
> names cached or stored wherever it stores it but each of the same names
> have different SIDs. Again, this is a huge guess. So, anyone know how I
> can get around this? Is there a SQL table I can just modify the numbered
> user account manually? I know that's a no-no but I need this to work.
>
> Thanks,
>
From: David Lozzi on 10 Jan 2008 12:50
But the user accounts have been deleted out of AD already. When WSS is in
ADAC it deletes the account from AD as well...

--
David Lozzi
Product Development Manager
Delphi Technology Solutions
www.delphi-ts.com - www.lozzi.net
"Mike Walsh" <englantilainen(a)hotmail.com> wrote in message
news:eqewLa6UIHA.4532(a)TK2MSFTNGP02.phx.gbl...
>I would save template copies of any Lists you think might have been amended
>in the meantime and go back to a backup before he (not you!) did this.
>
> Then put those lists to a spare server and do a quick comparison to add
> back things that have been added in the meantime.
>
> Safer by far than amending the database where problems even years later
> will make you think they might be because of that database change.
>
>
> Mike Walsh
> WSS FAQ http://www.wssfaq.com
> no questions by e-mail please
>
>
>
> David Lozzi wrote:
>> Howdy,
>>
>> Here's my scenario: A admin user (not me I swear) deleted about 20 users
>> from our WSS3 ADAC site. In adding the users back in they all have a
>> number affixed to their user names. I'm guessing Sharepoint is doing that
>> due to unique SIDs and whatever. Anyway, we don't want the numbered names
>> so i created the new user directly in the SharePoint OU of AD and then
>> used the stsad migrateuser command to migrate the user from the numberd
>> account to the normal account. This new account without the number can
>> login successfully! However, when they go to change their password, they
>> get the following error:
>>
>> The user does not exist or is not unique.
>>
>> I'm guessing this is due to the fact that SharePoint now has two user
>> names cached or stored wherever it stores it but each of the same names
>> have different SIDs. Again, this is a huge guess. So, anyone know how I
>> can get around this? Is there a SQL table I can just modify the numbered
>> user account manually? I know that's a no-no but I need this to work.
>>
>> Thanks,
>>

From: Mike Walsh on 10 Jan 2008 14:15
Serves me right for posting a reply to something that mentions ADAC
which I don't use.

Sorry. Hopefully somebody else has a better suggestion.

Mike Walsh


David Lozzi wrote:
> But the user accounts have been deleted out of AD already. When WSS is
> in ADAC it deletes the account from AD as well...
>
 | 
Pages: 1
Prev: Share point port IRM
Next: dws CreateFolder