And hope it doesn't crash like the first one did to a lot of people.
________________________________ From: [email protected] [mailto:[email protected]] On Behalf Of Paul Noone Sent: Friday, 24 April 2009 3:48 PM To: [email protected] Subject: RE: SSP out-of-synch [SEC=UNCLASSIFIED] Yeah but then you have to install it too! From: [email protected] [mailto:[email protected]] On Behalf Of Noja, Fadi Sent: Friday, 24 April 2009 3:49 PM To: [email protected] Subject: RE: SSP out-of-synch [SEC=UNCLASSIFIED] Only 4 days to go til sp2 is out. ________________________________ From: [email protected] [mailto:[email protected]] On Behalf Of Paul Noone Sent: Friday, 24 April 2009 3:45 PM To: [email protected] Subject: RE: SSP out-of-synch Finally, a solution. And who would have thought it would be a delegate control feature? I can hear Paul Turner's "duh!" from here. :-) http://solutionizing.net/2008/12/08/user-profile-mysite-redirect-via-del egate-control/ Hope this helps someone else in the same boat. For those who can wait, it seems SP2 is intending to address this. From: [email protected] [mailto:[email protected]] On Behalf Of Paul Noone Sent: Friday, 24 April 2009 2:13 PM To: [email protected] Subject: RE: SSP out-of-synch Ugh. Found it. Reflector is your friend. :-) What's supposed to happen when you click a user is that userdisp.aspx gets called and does a redirect if My Sites are enabled. If this doesn't happen for you then you're having the same problem. The userdisp.aspx page includes a delegate control which uses MySiteRedirectionUserControl to figure out where the profile page is over on the SSP and then redirect to it. For security reasons, this redirection only happens if the public profile page URL is safe. What is safe? 1. Same host name as the original URL (portal at http://mycompany:80, and my site under http://mycompany:8080). 2. The URL to be redirected is a Portal URL. That is, if we set Portal site connection (from site actions -> site settings -> Portal site connection) to be http://mysite.[hostheader], http://mysite... will then be considered as a safe URL. 3. Loop back addresses like http://localhost, http://127.0.0.1. In our case we're using a separtae webapp and subdomain for our My Sites. Option 2 works but is not agreeable. Changing the URL for the web app would be a last resort. Does anyone know another way to mark this URL as safe? From: [email protected] [mailto:[email protected]] On Behalf Of Paul Noone Sent: Friday, 24 April 2009 10:43 AM To: [email protected] Subject: SSP out-of-synch Hi all, While the list was down I was busily pestering some members (thanks guys!) about a perplexing problem we're having with user profiles and membership links in new site collections. Basically, I created a new site collection based on a blank site. All enterprise features enabled. I then performed a few basic tasks, set up groups etc., which is where I noticed the first problem. The site users are being copied locally with only a subset of the information available in the My Site Profile store. They are also fully editable and ignore all the rules applied to these profile properties in the SSP. I've run stsadm -o sync and checked that all relevant the timer jobs have run. I performed a full crawl. I've checked every setting in CA and at the site level and simply cannot work this one out. It's almost as though it's ignoring the SSP. All feedback appreciated! Paul ________________________________ 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: 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
