Integrating Sharepoint into existing system, and number of servers recommended
From: Rick Kunkel (NOSPAM-kunkel_at_w-link.net)
Date: 11/22/04
- Next message: meg: "Re: Can you clone a subarea?"
- Previous message: Matthew McDermott: "Re-Allow FrontPage Editing of Site"
- Next in thread: Mike Walsh: "Re: Integrating Sharepoint into existing system, and number of servers recommended"
- Reply: Mike Walsh: "Re: Integrating Sharepoint into existing system, and number of servers recommended"
- Messages sorted by: [ date ] [ thread ]
Date: Mon, 22 Nov 2004 12:56:38 -0800
Hello all,
(First off, if I've posted this to an inappropriate newsgroup, please
let me know where it should go.)
I'm new to Sharepoint services, but have done a fair amount of reading
in the administrators guide and online. We're a medium-sized ISP that
has always offered web hosting as well, with the option for Frontpage
Extensions for customers that want them. Recently, we had a request
for a site using Sharepoint.
Everything is pretty much set up and ready to go, but there are a few
monster variables that I'd like to get a handle on. Otherwise, I'm
afraid that I'll be beating myself up 2 or 3 years from now, wondering
why in the world I chose the way I did.
I am not currently using active directory AT ALL for customer stuff.
All my production NT4/Win2k servers are standalone machines using only
Local users and groups.
My new machine that I intend to do the Sharepoint stuff on is, by
necessity I think, using active directory, and is a domain controller.
I'm running into varied problems.
1. I've heard that Sharepoint Services shouldn't be installed on a
primary domain controller. Something about not being able to use
Sharepoint to add users to the active directory.
2. I'm fine running active directory and Microsoft DNS on the new
Sharepoint Services server (assuming that's legal), but I'd like to
run Microsoft SQL 2000 on another existing server (and I hear that
separating SQL is advised anyhow). The prob is that it seems that the
preferred way to authenticate is Windows Authentication. However,
since the SQL server is not a member of the active directory or domain
or anything, I can't seem to get the windows authentication to work.
I guess the two main questions are:
1. Is it OK to have Sharepoint services, IIS, Microsoft DNS, and
Primary Domain Controller for the Active Directory all running on the
same server, or are there serious drawbacks, aside from obvious ones
like potential lack of resources?
2. If I use SQL Server Authentication instead of Windows
Authentication for the database backend, will I lose some
functionality?
And then grand momma of all questions:
Given the reseources I've got (one new fairly powerful server, several
standalone NT4 and Win2K servers, one of which runs MS SQL 2000), how
would you folks do this?
Thanks,
Rick Kunkel
post sharepoint question to pub msft nntp
? using sql auth diff than windows auth?
? no active directory accounts creation on domain controller?
- Next message: meg: "Re: Can you clone a subarea?"
- Previous message: Matthew McDermott: "Re-Allow FrontPage Editing of Site"
- Next in thread: Mike Walsh: "Re: Integrating Sharepoint into existing system, and number of servers recommended"
- Reply: Mike Walsh: "Re: Integrating Sharepoint into existing system, and number of servers recommended"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
