Environment:
Ad domain control
Moss Server
When a moss server was created, the system administrator at the current level was the moss administrator. Other users used users in ad, but only granted normal permissions.
Problems:
Ad reconstruction, moss reconstruction, and recovery. It is no problem to log on to the MOSS system with other domain accounts, but login with an administrator is always unsuccessful.
Solution:
The userinfo table is found in the moss content database, which has a td_systemid field. SharePoint uses the guid of the td_systemid field as the unique logon identifier. the reinstallation machine has the same username, however, The GUID is different. How is this identifier generated? It was originally generated using the suser_sid () function. Update userinfo set tp_systemid = suser_sid (tp_login) Where tp_systemid = the original guid.
The following is an example:
Select * From userinfo where tp_login = 'portal \ admin'
Go
Select suser_sid ('portal \ Administrator ')
Go
Update userinfo set tp_systemid = suser_sid ('portal \ admin') Where tp_login = 'portal \ admin' and tp_systemid = 0x01050000000000051500000054b0000d1532dfe4e9b945e46f4010000
Go