We have a SharePoint form with a mixed set of users of two domains (Let's call A and B). Some users are being associated with one domain account and some with their B domain identity. Now we should now remove any of the domains (B) and replace all its domain domains with their own domain name.
The problem is that if I walk, then STSADM-O migrateUserB user name is a user name-the solution is that what this command does, this first time user A / username is destroyed in the user interface table. (Which means that all will be used by all sites) and then changes the B \ username with a username. This leaves us in a very bad situation, where people who add to the share page anywhere with the \ "username \" will lose access.
I got stuck on this for about a week. Do experts suggest that there is probably a resolution here?
We were in a similar situation. We were writing out a custom console application to replicate our entire SharePoint farm, and we change every example of the B \ username with a username.
This is definitely a brutal force approach, but we could not understand any other way to do it. We have restricted our scope to change the permissions for sites, groups and lists (not items in lists / libraries). At some point, people may have to re-establish some of their permissions.
Comments
Post a Comment