Logo 
Search:

MOSS Forum

Ask Question   UnAnswered
Home » Forum » MOSS       RSS Feeds

FBA Usability Consequences (e.g. Explorer view, mutiple document upl)

  Asked By: Kenya    Date: Feb 07    Category: MOSS    Views: 2703

This should be a fairly quick answer --

Generally, is this list still correct for MOSS 2007 if Active
Directory is NOT installed on the hosting server and only FBA is used?

When you configure a zone to use forms authentication, the Enable
Client Integration box is cleared by default. If a zone is configured
in this way, the following changes occur in functionality:

* Support for remote interfaces is turned off. That includes
WebDAV, SOAP, and Microsoft Office FrontPage remote procedure calls
(RPC). Some functionality is not available, such as Web folders or the
Web services for accessing content in that site.

* Some toolbar items no longer appear:

o New Document

o Open in Outlook

o Open In Windows Explorer

o Export to Spreadsheet

o Open with Database Program

* Explorer View option is hidden.

* Create an Access View option is hidden.

* In picture libraries, the following functionality is removed:

o Upload Multiple

o Edit Picture

o Download

o Send To

* On the Edit Control Block (ECB) menu, the drop-down menu that
appears when you click items in document libraries, the following
items are removed:

o Edit in Word

o Edit in Excel

o Edit in PowerPoint

o Discuss

o Connect To Outlook

* In slide libraries the following functionality is removed:

o Publish Slide

o Send to PowerPoint

* Also, syncing SharePoint data with Microsoft Office Outlook no
longer works.

Share: 

 

6 Answers Found

 
Answer #1    Answered By: Otis Blackwell     Answered On: Feb 07

Maybe it is not such an easy question? Anyone?

 
Answer #2    Answered By: Virendar Chaudhari     Answered On: Feb 07

The problem is that there is no quick  answer to this question. Your list  is
relatively accurate, but many of the things you've mentioned can still be used
if FBA is used for authentication in certain circumstances.

For example, if you click the Remember me checkbox on the login page and leave
Client Integration turned on (as you say, not the default) then you will still
be able to use the Client Integration Features. If you forget the checkbox it
won't work. So the problem is that there is no firm list of functionality that
is lost when only FBA is used. There are lots of other factors to be
considered.

 
Answer #3    Answered By: Mitchel Villarreal     Answered On: Feb 07

So, for sites that are external facing, yet are very collabarative in
nature (people doing a lot of uploading, downloading, etc of content)
FBA is not the best route?

Our IT people want all our external sites to be FBA in order reduce
liscensing costs and leverage server hardware - I guess.

But for these types of sites, it probably would be best to have a
dedictated server so that we could use Active Directory, thereby
enabling the ability to access Explorer View and other integrated OTB
functionality?

Would you say that is correct  (although very general)?

 
Answer #4    Answered By: Ranu Badhan     Answered On: Feb 07

So, for sites that are external facing, yet are very collabarative in
nature (people doing a lot of uploading, downloading, etc of content)
FBA is not the best route?

Reply> Not necessarily. As I pointed out using FBA you can still use Client
Integration IF you use a permanent cookie instead of a temporary one. (That's
what checking the checkbox on the login page does.) FBA doesn't effect
uploading/downloading at all. What it effects is the ability to OPEN a client
side application from SharePoint. For example, when you click on Edit in
Microsoft Word you are having SharePoint start the WORD application on your
local workstation. FBA without permanent cookies can't do that. But if you
download the file and then click OPEN it is the MIME settings in your local web
browser that is telling Word to open and load the file. No problem with that in
FBA. So FBA may change the way external users work, but won't seriously limit
their ability to collaborate.

Our IT people want all our external sites to be FBA in order reduce
liscensing costs and leverage server hardware - I guess.

Reply> I think your IT people better double check their thinking. Using FBA won't
seriously affect your licensing costs. Whether using FBA or Windows
Authentication you will need SharePoint CALs for all your own people. And if
the people are truly external users then you will need an Internet Connector
Licenses. Again, the form of authentication has no effect on this SharePoint
licensing. So the only licensing costs you could potentially save would be
Windows Server CALs because FBA users wouldn't be added to Active Directory.
But if they are employees I think you will still need to buy them Windows CALs
to access the server and a Server Internet Connection License for external
users. I'm curious why they think FBA would decrease licensing costs?

But for these types of sites, it probably would be best to have a
dedictated server so that we could use Active Directory, thereby
enabling the ability to access Explorer View and other integrated OTB
functionality?

Would you say that is correct  (although very general)?

Reply> As I tried to explain above, No I don't agree in general. FBA can be used
very effectively with external facing sites and still preserve their
collaborative nature.

 
Answer #5    Answered By: Irene Moss     Answered On: Feb 07

The FBA login form we are using does not contain a check box on the
login page for "Remember Me". I will have to look at why this has
been removed.

 
Answer #6    Answered By: John Scott     Answered On: Feb 07

If you would like additional guidance on using FBA with Client
Integration, please shoot me an email to hgravatt@.... David
Mowers and I have the FBA with Client Integration working seamlessly and
can share our many hours of expertise to help guide you down the right
path. You will want to ensure you are using Windows Server 2003 R2
Standard or Enterprise Edition and want to ensure you are using ADAM or
SQL for authentication.

If you are interested in heading down this path, please feel free to
shoot myself and David Mowers (davem@...) an email and we can
accommodate your needs.

 




Tagged: