Here's an example of what you can do
stsadm -o setsiteuseraccountdirectorypath -path "OU=Employees,DC=Company,DC=com" -url http://server/sites/teamsite Fadi ________________________________ From: [email protected] [mailto:[email protected]] On Behalf Of Daniel Brown Sent: Tuesday, 2 June 2009 12:20 PM To: [email protected] Subject: RE: [SUMMARY] Trusted Domains and user accounts Hi Mark, Thanks for the tip, People Picker is now clear of the old domains. Because the MOSS farm is already in the new domain, I did not have to supply domain\username or the password, just the domain. i.e: stsadm -o setproperty -pn peoplepicker-searchadforests -pv "domain:domain.local" -url http://intranet.domain.local Now for the next task of user profiles :-) ... then to do it in production :-) Thanks again, Daniel From: [email protected] [mailto:[email protected]] On Behalf Of Mark Rhodes Sent: Tuesday, 2 June 2009 11:40 AM To: [email protected] Subject: RE: Trusted Domains and user accounts Hey Dan, Try this : stsadm -o setproperty -pn peoplepicker-searchadforests -pv "domain:domain.com,domain\username,password" -url http://webapplication I know it does not look like it would do the trick, but I've found it seems to stop any results from appearing from the trusted domain - worth a shot? :-) Regards, Mark Rhodes Mark Rhodes | Emantra | Technology Specialist | [email protected]| 1300 728 953 | +61733337702 From: [email protected] [mailto:[email protected]] On Behalf Of Daniel Brown Sent: Tuesday, 2 June 2009 12:01 PM To: [email protected] Subject: Trusted Domains and user accounts Howdy all, I have a client which has 2 domains, DOMAIN1 and DOMAIN2. DOMAIN1 is a old domain and is knackered and DOMAIN1 will be its replacement. In the mean time, the Windows Administrators have set up a trust between both domains. Now in SharePoint which is in DOMAIN2, all DOMAIN1 user accounts are coming though. This in itself isn't an issue. However because its the same accounts, 1 account for DOMAIN1 and 1 for DOMAIN2. People are adding the wrong accounts and hitting the wall with permissions. i.e they add DOMAIN1\Daniel to the site, but Daniel is on DOMAIN2 (yes on domain1 also, but we all know about users). Has anyone done this before or have a way of removing the DOMAIN1 accounts from the user profiles and prevent their importing? Checked throughout the SSP but not much luck. Apologies if it's not explained clear. Thanks, Daniel Brown - MACS - MCP - MCTS - SharePoint MVP <https://mvp.support.microsoft.com/profile/Daniel.Brown> Blog: http://www.danielbrown.id.au <http://www.danielbrown.id.au/> Mobile: 0419-804-099 * Please consider your Environment before printing this email. ________________________________ Support procedure: https://www.codify.com/lists/support List address: [email protected] Subscribe: [email protected] Unsubscribe: [email protected] List FAQ: http://www.codify.com/lists/ozmoss <http://www.codify.com/lists/ozmoss> Other lists you might want to join: http://www.codify.com/lists <http://www.codify.com/lists> ________________________________ Support procedure: https://www.codify.com/lists/support List address: [email protected] Subscribe: [email protected] Unsubscribe: [email protected] List FAQ: http://www.codify.com/lists/ozmoss <http://www.codify.com/lists/ozmoss> Other lists you might want to join: http://www.codify.com/lists <http://www.codify.com/lists> ________________________________ Support procedure: https://www.codify.com/lists/support List address: [email protected] Subscribe: [email protected] Unsubscribe: [email protected] List FAQ: http://www.codify.com/lists/ozmoss <http://www.codify.com/lists/ozmoss> Other lists you might want to join: http://www.codify.com/lists <http://www.codify.com/lists> -------------------------------------------------------------------------------- Support procedure: http://www.codify.com/lists/support List address: [email protected] Subscribe: [email protected] Unsubscribe: [email protected] List FAQ: http://www.codify.com/lists/ozmoss Other lists you might want to join: http://www.codify.com/lists
