<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Using the people picker over a one-way trust</title>
	<atom:link href="http://blog.hompus.nl/2010/06/01/using-the-people-picker-over-a-one-way-trust/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.hompus.nl/2010/06/01/using-the-people-picker-over-a-one-way-trust/</link>
	<description>Because I like to share knowledge</description>
	<lastBuildDate>Tue, 07 Feb 2012 14:57:57 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1.3</generator>
	<item>
		<title>By: Aravind Sivanantham</title>
		<link>http://blog.hompus.nl/2010/06/01/using-the-people-picker-over-a-one-way-trust/comment-page-1/#comment-170</link>
		<dc:creator>Aravind Sivanantham</dc:creator>
		<pubDate>Mon, 31 Oct 2011 06:05:27 +0000</pubDate>
		<guid isPermaLink="false">http://blog.hompus.nl/2010/06/01/using-the-people-picker-over-a-one-way-trust/#comment-170</guid>
		<description>People import successfully for the other domain user (OWFT), When the user  try to create mysite getting SPEXCEPTION :USER NOT FOUND but the user profiles created successfully for the other domain users.
please can give suggestion</description>
		<content:encoded><![CDATA[<p>People import successfully for the other domain user (OWFT), When the user  try to create mysite getting SPEXCEPTION :USER NOT FOUND but the user profiles created successfully for the other domain users.<br />
please can give suggestion</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Configure people picker over a one-way trust using PowerShell &#124; Michaël&#039;s coding thoughts</title>
		<link>http://blog.hompus.nl/2010/06/01/using-the-people-picker-over-a-one-way-trust/comment-page-1/#comment-61</link>
		<dc:creator>Configure people picker over a one-way trust using PowerShell &#124; Michaël&#039;s coding thoughts</dc:creator>
		<pubDate>Mon, 17 Jan 2011 18:25:00 +0000</pubDate>
		<guid isPermaLink="false">http://blog.hompus.nl/2010/06/01/using-the-people-picker-over-a-one-way-trust/#comment-61</guid>
		<description>[...] a previous post I have written about Using the people picker over a one-way trust. In that post I use STSADM commands as there are no other ways to configure this. A downside of the [...]</description>
		<content:encoded><![CDATA[<p>[...] a previous post I have written about Using the people picker over a one-way trust. In that post I use STSADM commands as there are no other ways to configure this. A downside of the [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Michaël Hompus</title>
		<link>http://blog.hompus.nl/2010/06/01/using-the-people-picker-over-a-one-way-trust/comment-page-1/#comment-56</link>
		<dc:creator>Michaël Hompus</dc:creator>
		<pubDate>Sun, 24 Oct 2010 17:55:20 +0000</pubDate>
		<guid isPermaLink="false">http://blog.hompus.nl/2010/06/01/using-the-people-picker-over-a-one-way-trust/#comment-56</guid>
		<description>it should be like: 
&lt;blockquote&gt;-pw forest:a.b.com;domain:c.com,c.com\username,password&lt;/blockquote&gt;
watch where you use : ; en ,</description>
		<content:encoded><![CDATA[<p>it should be like: </p>
<blockquote><p>-pw forest:a.b.com;domain:c.com,c.com\username,password</p></blockquote>
<p>watch where you use : ; en ,</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dave</title>
		<link>http://blog.hompus.nl/2010/06/01/using-the-people-picker-over-a-one-way-trust/comment-page-1/#comment-55</link>
		<dc:creator>Dave</dc:creator>
		<pubDate>Fri, 22 Oct 2010 20:16:21 +0000</pubDate>
		<guid isPermaLink="false">http://blog.hompus.nl/2010/06/01/using-the-people-picker-over-a-one-way-trust/#comment-55</guid>
		<description>Update,  in the example above, the command is -pw forest:xx:domain:c.com\username,password.... not b.com as previously stated</description>
		<content:encoded><![CDATA[<p>Update,  in the example above, the command is -pw forest:xx:domain:c.com\username,password&#8230;. not b.com as previously stated</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dave</title>
		<link>http://blog.hompus.nl/2010/06/01/using-the-people-picker-over-a-one-way-trust/comment-page-1/#comment-54</link>
		<dc:creator>Dave</dc:creator>
		<pubDate>Fri, 22 Oct 2010 20:13:49 +0000</pubDate>
		<guid isPermaLink="false">http://blog.hompus.nl/2010/06/01/using-the-people-picker-over-a-one-way-trust/#comment-54</guid>
		<description>My SP server is on domain A,(which is a.b.com) I setup domain B (c.com) for external users.  I configured forwards in each DNS and setup a trust (domain B trusts domain a)  I created the credential key and ran stsadm -0 setproperty -url http://sqldevserver -pn peoplepicker-searchadforests -pw forest:xx:domain:b.com\username,password

every 60 seconds my front-end server registers event 6482 in the application log.  Reason:  The trust relationship between the primary domain and the trusted domain failed.  

Any suggestions?</description>
		<content:encoded><![CDATA[<p>My SP server is on domain A,(which is a.b.com) I setup domain B (c.com) for external users.  I configured forwards in each DNS and setup a trust (domain B trusts domain a)  I created the credential key and ran stsadm -0 setproperty -url <a href="http://sqldevserver" rel="nofollow">http://sqldevserver</a> -pn peoplepicker-searchadforests -pw forest:xx:domain:b.com\username,password</p>
<p>every 60 seconds my front-end server registers event 6482 in the application log.  Reason:  The trust relationship between the primary domain and the trusted domain failed.  </p>
<p>Any suggestions?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Michaël Hompus</title>
		<link>http://blog.hompus.nl/2010/06/01/using-the-people-picker-over-a-one-way-trust/comment-page-1/#comment-53</link>
		<dc:creator>Michaël Hompus</dc:creator>
		<pubDate>Thu, 30 Sep 2010 16:14:03 +0000</pubDate>
		<guid isPermaLink="false">http://blog.hompus.nl/2010/06/01/using-the-people-picker-over-a-one-way-trust/#comment-53</guid>
		<description>Authentication itself will work when a trust is in place indeed.
The configuration of the people picker is additional with a partial trust and will allow to choose accounts from (both) domains.</description>
		<content:encoded><![CDATA[<p>Authentication itself will work when a trust is in place indeed.<br />
The configuration of the people picker is additional with a partial trust and will allow to choose accounts from (both) domains.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Alex</title>
		<link>http://blog.hompus.nl/2010/06/01/using-the-people-picker-over-a-one-way-trust/comment-page-1/#comment-52</link>
		<dc:creator>Alex</dc:creator>
		<pubDate>Thu, 30 Sep 2010 14:48:52 +0000</pubDate>
		<guid isPermaLink="false">http://blog.hompus.nl/2010/06/01/using-the-people-picker-over-a-one-way-trust/#comment-52</guid>
		<description>Hi! Nice post!
Have a question: Configuring the AD trust + people picker will be enough to allow users from domain A to authenticate on the SharePoint (that is located on Domain B)?

Tks!
Alex</description>
		<content:encoded><![CDATA[<p>Hi! Nice post!<br />
Have a question: Configuring the AD trust + people picker will be enough to allow users from domain A to authenticate on the SharePoint (that is located on Domain B)?</p>
<p>Tks!<br />
Alex</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bondt</title>
		<link>http://blog.hompus.nl/2010/06/01/using-the-people-picker-over-a-one-way-trust/comment-page-1/#comment-35</link>
		<dc:creator>Bondt</dc:creator>
		<pubDate>Tue, 01 Jun 2010 14:23:30 +0000</pubDate>
		<guid isPermaLink="false">http://blog.hompus.nl/2010/06/01/using-the-people-picker-over-a-one-way-trust/#comment-35</guid>
		<description>Great timing on this article! Just needed this! Thanks!</description>
		<content:encoded><![CDATA[<p>Great timing on this article! Just needed this! Thanks!</p>
]]></content:encoded>
	</item>
</channel>
</rss>

