How to choose, or mix and match, when setting up a new SP portal.
-- Joshua
------ Forwarded Message
From: Paul Stork <paul.stork@mindsharp.com>
Reply-To: "sharepointdiscussions@yahoogroups.com"
<sharepointdiscussions@yahoogroups.com>
Date: Sat, 31 Jan 2009 08:37:07 -0600
To: "sharepointdiscussions@yahoogroups.com"
<sharepointdiscussions@yahoogroups.com>
Subject: RE: [sharepointdiscussions] Publishing Portal or Collabortion
Publishing Portal
The Publishing Portal is designed to be used as an Internet Presence Site.
It is restricted to using simple Publishing sites as child sites and doesn't
have access to all the list and library types available in the Collaboration
Portal. Other child site types and the full range of list/library types can
be made available in a Publishing site by adjust configuration and turning
on Features, but they aren't there out of the box. The Collaboration Portal
is designed more for use as an Intranet site where users will be creating
their own pages of content (Publishing). It includes all the normal
Collaboration features out of the box and includes a number of custom sites
for things like a centralized Document repository, Reporting Site, and an
alternate way to find sub sites (Sites Directory).
What you have proposed would probably be best built from a Publishing Portal
after the Team Site is added back in as an available Site Definition. (You
can do this in the Site Settings page of the Top level site using the Site
Templates and Page Layouts link). You will also want to turn on the
TeamCollab Site Collection Feature to make all the Lists/Libraries
available. Otherwise your setup is a matter of setting up Anonymous access
rights on the Child sites appropriately.
Paul Papanek Stork / paul.stork@mindsharp.com<mailto:pstork@att.net> /
216-272-0573 / Know More. Do More.
SharePoint Server MVP, MCT, MCSE+I, MCSA, MCSD, MCDBA, MCITP, MCPD
MVP Profile<https://mvp.support.microsoft.com/profile/stork>
Come to the first ever SharePoint Best Practices Conference, Sept 15-17!
Register at
http://www.sharepointbestpractices.com<http://www.sharepointbestpractices.co
m/>
From: sharepointdiscussions@yahoogroups.com
[mailto:sharepointdiscussions@yahoogroups.com] On Behalf Of championeal
Sent: Friday, January 30, 2009 4:04 PM
To: sharepointdiscussions@yahoogroups.com
Subject: [sharepointdiscussions] Publishing Portal or Collabortion
Publishing Portal
We would like to have a Internet site with several team sites. The Top
Site would have the majority of Internet content for the public. When
directed to a team site within the site collection through the
Navigation Bar, we would like each of these sites to have an Internet
Welcome for the public. Then all other content for those team sites
would be only for internal personnel.
Our questions:
- the Top Site as a Publishing Portal or a Collaboration Publishing
Portal?
- the other sub-sites as Team Sites?
- what is the difference between the Publishing Portal vs a
Collaboration Portal? (In other words, what advantage does a
Publishing Portal have over the Collaboration Portal?)
[Non-text portions of this message have been removed]
------------------------------------
Yahoo! Groups Links
<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/sharepointdiscussions/
<*> Your email settings:
Individual Email Traditional
<*> To change settings online go to:
http://groups.yahoo.com/group/sharepointdiscussions/join
(Yahoo! ID required)
<*> To change settings via email:
mailto:sharepointdiscussions-digest@yahoogroups.com
mailto:sharepointdiscussions-fullfeatured@yahoogroups.com
<*> To unsubscribe from this group, send an email to:
sharepointdiscussions-unsubscribe@yahoogroups.com
<*> Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/
------ End of Forwarded Message
Monday, February 2, 2009
Publishing Portal or Collaboration Portal
Thursday, November 13, 2008
Web App, Zone, AAM: Get it right the first time
A notice about "unexpected side effects" when changing the address for the
default Zone.
------ Forwarded Message
From: Paul Stork <paul.stork@mindsharp.com>
Reply-To: "sharepointdiscussions@yahoogroups.com"
<sharepointdiscussions@yahoogroups.com>
Date: Sat, 8 Nov 2008 13:41:24 -0600
To: "sharepointdiscussions@yahoogroups.com"
<sharepointdiscussions@yahoogroups.com>
Subject: RE: [sharepointdiscussions] RE: FBA with Client Integration
That's the problem then. Extending a Web Application to Create a ZONE will
create an AAM, but they aren't the same thing. When you swapped the AAM
addresses around that didn't change the address for the Zone in the
Authentication Provider. So switching around client integration didn't
help. In general after an AAM is created by either a Web Application or a
Zone you shouldn't change the address. That's why planning the address for
the default Zone is so critical. Once its created you end up with
unexpected side effects if you try to change it.
Paul Papanek Stork /
paul.stork@mindsharp.com<mailto:paul.stork@mindsharp.com> / 216-272-0573 /
Know More. Do More.
SharePoint Server MVP, MCT, MCSE+I, MCSA, MCSD, MCDBA, MCITP, MCPD
MVP Profile<https://mvp.support.microsoft.com/profile/stork>
Come to the SharePoint Best Practices Conference in San Diego, CA: Feb. 2-4!
Register at
http://www.sharepointbestpractices.com<http://www.sharepointbestpractices.co
m/17>
From: sharepointdiscussions@yahoogroups.com
[mailto:sharepointdiscussions@yahoogroups.com] On Behalf Of Harold W.
Gravatt
Sent: Friday, November 07, 2008 7:17 PM
To: sharepointdiscussions@yahoogroups.com
Subject: RE: [sharepointdiscussions] RE: FBA with Client Integration
One thing I want to point out is that I had moved the external URL with
SSL to the Default Site to get the external URL to appear to External
Users when they have subscribed to alerts. Now when I go to
Authentication Providers the external https://mossteam.realignllc.com is
appearing in the Web Application field when I go to Authentication
Providers. I select the Extranet zone and disable client integration
and it doesn't seem to matter. My question is this. If I moved this
URL to the Default Site in Alternate Access Mappings and the internal
URL to the Intranet zone, why is this not being revealed when I go to
Authentication Providers? I would think that the Alternate Access
Mappings change should be reflected in both locations in Alternate
Access Mappings and in Authentication Providers wouldn't you?
Harold W. Gravatt, MCSE
Principal
269.978.6988 office
877.286.9120 toll free
hgravatt@realignllc.com<mailto:hgravatt%40realignllc.com>
Want to learn more about Realign? Visit our website.
<http://realign.tech.officelive.com/>
From:
sharepointdiscussions@yahoogroups.com<mailto:sharepointdiscussions%40yahoogr
oups.com>
[mailto:sharepointdiscussions@yahoogroups.com<mailto:sharepointdiscussions%4
0yahoogroups.com>] On Behalf Of Paul Stork
Sent: Friday, November 07, 2008 7:04 PM
To:
sharepointdiscussions@yahoogroups.com<mailto:sharepointdiscussions%40yahoogr
oups.com>
Subject: [sharepointdiscussions] RE: FBA with Client Integration
In SharePoint you enable the creation of a persistent cookie by click
the 'remember me' check box on the login page. You also have to enable
client integration when you setup the Authentication provider in the
Application management tab of Central Admin.
Paul Papanek Stork /
paul.stork@mindsharp.com<mailto:paul.stork%40mindsharp.com>
<mailto:paul.stork%40mindsharp.com>
<mailto:paul.stork@mindsharp.com<mailto:paul.stork%40mindsharp.com>
<mailto:paul.stork%40mindsharp.com> > / 216-272-0573 / Know More. Do
More.
SharePoint Server MVP, MCT, MCSE+I, MCSA, MCSD, MCDBA, MCITP, MCPD
MVP Profile<https://mvp.support.microsoft.com/profile/stork>
Come to the SharePoint Best Practices Conference in San Diego, CA: Feb.
2-4!
Register at http://www.sharepointbestpractices.com<
http://www.sharepointbestpractices.com/17>
From:
sharepointdiscussions@yahoogroups.com<mailto:sharepointdiscussions%40yahoogr
oups.com>
<mailto:sharepointdiscussions%40yahoogroups.com> [mailto:
sharepointdiscussions@yahoogroups.com<mailto:sharepointdiscussions%40yahoogr
oups.com>
<mailto:sharepointdiscussions%40yahoogroups.com> ] On Behalf Of Harold
W. Gravatt
Sent: Friday, November 07, 2008 6:45 PM
To:
sharepointdiscussions@yahoogroups.com<mailto:sharepointdiscussions%40yahoogr
oups.com>
<mailto:sharepointdiscussions%40yahoogroups.com>
Subject: [sharepointdiscussions] FBA with Client Integration
All,
The External Collaboration Toolkit for SharePoint allows me to install
ADAM, IIS, WSS, .Net Framework 3.0, ASP.NET onto a W2K3R2SP2 server and
allow external users to use their email address for authentication
against the ADAM store. However, one feature that does not work is
enabling FBA with Client Integration. Therefore, the context menu that
includes Edit in Microsoft Office Word or Excel is not supported and
does not function correctly. I talked to Dave Mowers at Securitay and
he suggested enabling persistent cookies. IE 7 enables persistent
cookies supposedly by adding the URL to the Trusted Sites list.
However, using this advice to enable persistent cookies using IE 7 does
not seem to do the trick.
I am all ears to another workaround or solution would be nice. I
haven't installed DotNetNuke yet, but that supposedly works with FBA and
Client Integration enabled.
Harold W. Gravatt, MCSE
Principal
269.978.6988 office
877.286.9120 toll free
hgravatt@realignllc.com<mailto:hgravatt%40realignllc.com>
------ End of Forwarded Message
Friday, October 3, 2008
Content Deployment Options Compared
It appears on the surface that SharePoint is intended to be used as a "live site" technology, where content is developed in the same place where it is published. For collaborative teamsites, this is often an appropriate model, since team members can generally be trusted with "half-baked" content. For content that is published outside the team, the built-in "publishing" feature (option) provides an extension of the develop-in-place model which hides draft content from readers until it is "approved".
However, there are many scenarios where develop-in-place is not appropriate; for example, when there is code involved as well as content, or where massive changes need to be coordinated to avoid large numbers of "did I update that link to the new page" questions. In these cases, some method of migrating content from a "development" server to a "production" server (or perhaps to some intermediate "staging" server) is needed.
Chris O'Brien, a Microsoft Most Valued Professional, does a thorough job of comparing the options in this blog post:
http://www.sharepointnutsandbolts.com/2007/10/stsadm-export-content-deployment.html
Authentication Zones and Alternate Access Mapping
http://technet.microsoft.com/en-us/library/cc261995.aspx
In the course of developing a model corporate deployment, this Technet
article does the best job yet of explaining authentication zones and
Alternate Access Mapping.
Friday, September 5, 2008
Social Networking Primer and Overview
Mike Gratta, a Principal Aalyst at the Burton Group, has contributed to Educause a 46-page primer and analysis of social networking in the enterprise:
http://net.educause.edu/ir/library/pdf/ecar_so/ers/ers0806/rs/ERS0806.pdf
[Note: a free registration (available to all WSU staff) is required.]
The key takeaway is that social networks cannot be counted on to happen via a simple "corporate Facebook" strategy; rather, an analysis of goals and methods is needed (surprise!). Anyone who wishes to plan or even discuss social networking in an enterprise context should be familiar with the terms and concepts introduced in this paper.
Thursday, July 17, 2008
MySites, Anonymous Access, and Lockdown Mode
Problem
It is sometimes desirable to have anonymous access to parts of a MySite site. The usual facilities for setting anonymous access are available, but they don't seem to work for all elements of the site. While the Default (My Home) page may not have any meaning for anonymous users, and the MyProfile not much, there are occasions when Shared Documents or another doclib might need to be accessed anonymously.
We have found that setting the site to allow anonymous access to the "Entire Web", and setting the library to inherit from its parent (or not to inherit, but to allow anonymous access), enables users to access .doc, .pdf., and other files, but not pages (.aspx). This means that (for example) web part pages, document libarary lists, and other useful sites are disabled for anonymous access, and the access can't be turned on, even by the site owner.
Tentative Diagnosis
In SharePoint, anonymous users are associated with the permission level "Limited Access". The default settings for limited access are intended for team sites. MOSS has a security provision called "lockdown mode" which is intended to improve security for publishing sites. The MS document "Plan security for an external anonymous access environment (Office SharePoint Server)" <http://technet.microsoft.com/en-us/library/cc263468.aspx> contains a description of lockdown mode:
Lockdown mode is a feature that you can use to secure published sites. When lockdown mode is turned on, fine-grain permissions for the limited access permission level are reduced.
Lockdown mode appears to be activated by default in the "Publishing Site" template, and perhaps by the "Publishing" features. The page linked above shows the following two commands for lockdown mode:
The following table lists the Stsadm commands related to using lockdown mode.
Action Command
Turn on lockdown mode for a site collection
stsadm -o activatefeature -url <site collection url> -filename ViewFormPagesLockDown\feature.xml
Turn off lockdown mode for a site collection
stsadm -o deactivatefeature -url <site collection url> -filename ViewFormPagesLockDown\feature.xml
I believe we need to check to see if the lockdown feature is enabled on MySites, and what we need to do to deactivate it across the board.
-- Joshua