Re: Sharepoint Site for external users

Thanks for answering. That helps and answers my question.
Kevin

"Engelbert" wrote:

> If you run standalone WSS on its own server you won't need SPS licensing.
>
> BUT just because you have created a *WSS* site within your SPS installation
> doesn't mean that you can avoid the SPS external connector license.
>
> As far as Microsoft is concerned you have installed SPS 2003 on that server
> and you need to follow the licensing requirements for SPS 2003.
>
> (In any case WSS sites that are created within SPS have as far as I know
> functionality available to them that WSS sites created in a standalone WSS
> installation don't have.)
>
> So, tough, but you'll still need the SPS 2003 external connector license
> UNLESS you add a server; add WSS to that and provide your Internet available
> data there (at which point you'll need a [Server] Internet Connection
> license but that is at least cheaper than a SPS 2003 one).
>
> Engelbert
>
> "UA Kevin" <UAKevin@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
> news:241D0313-8593-4E18-AFB6-6CC4AFB2B384@xxxxxxxxxxxxxxxx
> > So, from within my SharePoint Portal Server 2003 at the home page, if I
> > click
> > Sites and click Create Site, I see that it created a WSS Site:
> > http://portal.myorg.org/sites/sitewss. It looks as though this site
> > provides
> > all the functionality we need.
> >
> > So, external nonemployee users can access only this site through the
> > Internet without the need for the SharePoint Portal Server 2003 external
> > connector license? I only need the Windows Server 2003 external
> > connector?
> > Will each nonemployee accessing this site through the Internet then need a
> > Windows Server 2003 CAL? Is a Windows Server 2003 CAL included with the
> > Windows XP Professional OS?
> >
> > Licensing, licensing, thanks!
> > Kevin
> >
> > "Shane Young [SPS MVP]" wrote:
> >
> >> Give domain users access to your portal. This is for all internal
> >> people.
> >>
> >> Do not put external users in the domain users group.
> >>
> >> External people should only have access to a WSS site.
> >> http://yourportal.domain.com/sites/ExternalGuysSite this is the only
> >> thing
> >> they should have access to.
> >>
> >> Make sense?
> >>
> >>
> >> --
> >> Shane Young - Now with MVP power
> >> SharePoint911 - "SharePoint Help...Now!"
> >> http://www.SharePoint911.com
> >>
> >>
> >> "Jay Taylor" <help4u@xxxxxxxxx> wrote in message
> >> news:%23QnM3Wj3FHA.3036@xxxxxxxxxxxxxxxxxxxxxxx
> >> > so then here is my stratergy to give them access.
> >> >
> >> > 1. instead of giving the authenticated users builtin group read
> >> > permissions to the entire sharepoint portal....create a nother security
> >> > group with all my company employees and give them read access to the
> >> > sharepoint portal. does this make sense.this way I can only have them
> >> > (the
> >> > employees of an external company) access to one particular wss site in
> >> > the
> >> > portal...let me know if this makes sense to you or you have another
> >> > idea ?
> >> >
> >> > thanks
> >> >
> >> > "Shane Young [SPS MVP]" <Shane @ SharePoint911 dot com> wrote in
> >> > message
> >> > news:OYXdVL92FHA.3188@xxxxxxxxxxxxxxxxxxxxxxx
> >> >>I actually recommend you do not give them access to the portal. You
> >> >>only
> >> >>create them a WSS site and point them at that. If you give them access
> >> >>to
> >> >>the portal you need to buy a portal license for them. If you give them
> >> >>access to just WSS then you can buy the external connector license for
> >> >>Windows which is very cheap compared to portal.
> >> >>
> >> >> Giving them access to portal opens up too many doors for them
> >> >> accessing
> >> >> something you do not want them to see, so that really scares me.
> >> >>
> >> >> --
> >> >> Shane Young - Now with MVP power
> >> >> SharePoint911 - "SharePoint Help...Now!"
> >> >> http://www.SharePoint911.com
> >> >>
> >> >>
> >> >> "Jay Taylor" <help4u@xxxxxxxxx> wrote in message
> >> >> news:uwnipT82FHA.2552@xxxxxxxxxxxxxxxxxxxxxxx
> >> >>> Thanks Shane -
> >> >>>
> >> >>> I have a sharepoint portal 2003 server set up and I am wondering how
> >> >>> it
> >> >>> would work with this set up...
> >> >>>
> >> >>> If I gave these guys accounts on my domain and tightened the security
> >> >>> it
> >> >>> would work , but they would get read access to the entire portal ? Is
> >> >>> this a good practise ....when outside users get involved this could
> >> >>> quickly escalate into a bigger issue even though we have nothing on
> >> >>> the
> >> >>> portal right now which wold matter to anyone...but just a thought...
> >> >>>
> >> >>> any thoughts on this would be appreciated...
> >> >>>
> >> >>> thanks
> >> >>>
> >> >>>
> >> >>> "Shane Young [SPS MVP]" <Shane @ SharePoint911 dot com> wrote in
> >> >>> message
> >> >>> news:%23tgDk1z2FHA.744@xxxxxxxxxxxxxxxxxxxxxxx
> >> >>>> The easiest answer is for you to create them local accounts on the
> >> >>>> server and them give them access that way. Then they have no access
> >> >>>> to
> >> >>>> anything else on your network. You can also add them to you AD and
> >> >>>> put
> >> >>>> them in an OU with no privileges. Or you can create a separate AD,
> >> >>>> move SharePoint to that domain, and then create a 1 way trust.
> >> >>>>
> >> >>>> All of these options work. Just depends on your security needs vs.
> >> >>>> time you want to dedicate to this project.
> >> >>>>
> >> >>>> HTH
> >> >>>>
> >> >>>>
> >> >>>> --
> >> >>>> Shane Young - Now with MVP power
> >> >>>> SharePoint911 - "SharePoint Help...Now!"
> >> >>>> http://www.SharePoint911.com
> >> >>>>
> >> >>>>
> >> >>>> "Jay Taylor" <help4u@xxxxxxxxx> wrote in message
> >> >>>> news:emE9Vvz2FHA.1700@xxxxxxxxxxxxxxxxxxxxxxx
> >> >>>>> What do you guys suggest is the easiest and best way to handle
> >> >>>>> this..some users from microsoft need to collaborate with our
> >> >>>>> internal
> >> >>>>> users and I dont know how they can be given access to my sharepoint
> >> >>>>> server without creating AD user accounts for them...
> >> >>>>>
> >> >>>>> whats the best practise ?
> >> >>>>>
> >> >>>>
> >> >>>>
> >> >>>
> >> >>>
> >> >>
> >> >>
> >> >
> >> >
> >>
> >>
> >>
>
>
>
.

Relevant Pages

  • Re: "downgrade" from SPS to WSS
    ... using the smigrate tool to first backup up the sub site on the existing SPS ... server and then restoring it on the new WSS server. ...
    (microsoft.public.sharepoint.portalserver.development)
  • Re: Sharepoint Site for external users
    ... If you run standalone WSS on its own server you won't need SPS licensing. ...
    (microsoft.public.sharepoint.portalserver)
  • Re: Reorganizing Existing Sharepoint 03 Site (Question)
    ... our SPS until another pressing thing got in the way and I'm only now getting ... With regards to using WSS as a staging area to push new content to our ... We have a 2003 server running SPS and SQL Server 2000 behind the scenes. ...
    (microsoft.public.sharepoint.portalserver)
  • Re: Searching for the Search Utility (web part)
    ... Are you using SQL Server or MSDE for your databases? ... Shane Young - SPS MVP ... WSS sites and WSS sub-sites. ... "Gary A. Bushey" wrote: ...
    (microsoft.public.sharepoint.portalserver)
  • Re: Search Service stops unexpectedly
    ... As you seem to be talking about the search service of SPS 2003, ... This newsgroup only covers common WSS functions (and specific standalone WSS ... If you are using SQL Server full-text search then ignore this message as all ...
    (microsoft.public.sharepoint.windowsservices)
Loading