Re: Application Pols

Tech-Archive recommends: Fix windows errors by optimizing your registry

Thansk for the advice. I misunderstod something you said. Thanks for the
clarifiaction. You didn't come across a jerk at all. I appreciate the
advice.

"Richard Dudley" wrote:

> Why not just give the new server a second name, build in your domain, and
> then rename the servers again? Since you're using domain users, you
> shouldn't have a problem. I think you may have issues because domain users
> aren't accessible in a workgroup. Workgroups isolate security from the
> domain.
>
> To make new virtual sites, use the IIS manager. Right-click on My Computer
> and choose Manage. Then drill down Services >> Internet Information
> Services, then add a new site. If you're not familiar with this, you might
> be getting in over your head with the SPS installation. I'd recommend
> holding on for a little bit and familiarizing yourself with IIS 6. I don't
> want to come across and a jerk, but a good knowledge of how IIS works is
> essential.
>
> You should use Windows Authentication.
>
> "George Schneider" <georgedschneider@xxxxxxxxxxxxxx> wrote in message
> news:95AA96EC-3377-412D-B39E-01559547A932@xxxxxxxxxxxxxxxx
> > The reason for having sharepoint in a workgroup first is because we need
> to
> > build the new sharepoint site first and then trnasfer some of the SQL
> > databases to this new server. After which we need to rename the old
> > sharepoint server and then rename the new sharpoint server to the same
> name
> > as the old server. Is building sharepoint sites in a workgroup going to
> > cause an issue?
> >
> > "Richard Dudley" wrote:
> >
> > > I would join the server to the domani before installing SPS, etc.,
> > > especially if your SQL is on a different machine. Ideally you'll have a
> > > domain user account that SPS will use to talk to SQL. If everything's
> on
> > > one machine, you might still want to use a domain user. Otherwise, if
> you
> > > move everything to a new server, or split your servers, you'll have to
> re-do
> > > the Db access.
> > >
> > > You choose which virtual site you want to extend. The default is to
> extend
> > > the default web site, but you can make other virtual sites before the SP
> > > installation and choose them instead. I have 5 portals running on the
> same
> > > box (4 divisions plus parent compant), none of which use default web
> site.
> > > If you choose to use other virtual sites, you'll need your network
> admins to
> > > add a NetBIOS/DNS pointer for that site name, and have it point to your
> SP
> > > server.
> > >
> > > Application Pools are new in Win2K3/IIS6. In IIS 5, all the installed
> sites
> > > ran as a single application. If one site bit the dust, they'd all go
> down.
> > > In IIS 6, each site can run in its own app pool. If that site bites the
> > > dust, the others keep running. It's a very nice feature. Besides
> > > stability, this helps with security. Each application pool can have its
> own
> > > identity (which needs to be a domain account, another reason to join the
> > > sever before installation), and you can assign access to network
> resources
> > > to the different app pool identities.
> > >
> > > If I remember correctly, during SP setup, you'll be asked for an admin
> app
> > > pool ID, and a default app pool ID, which should be two different domain
> > > user accounts (and not any real user--create new users, like 'SPAdmin'
> and
> > > 'SPUser' or something like that). The setup will configure your Central
> > > Admin to use the admin app pool, and place the portals into the default
> app
> > > pool. I would guess this is usually good enough for most installations
> (I
> > > haven't done many, so I say that with little conviction), especially at
> the
> > > beginning. You can change the app pool identity later, but you'll need
> to
> > > be ready to fix some permissions in different places (like in the DBs
> and on
> > > content directories if you have any). Worry about changing the app pool
> > > later--right now just get the thing running under the default and see
> how
> > > that works.
> > >
> > > I don't recommend trying to install SPS without having the Resource Kit
> > > handy (by Bill English), and at least having read and understood the
> > > chapters on installation. For my first portal, it was helpful to run
> > > through the installation once, make some mistakes, see how it worked,
> then
> > > completely format the server and do it again for real. Fortunately, I
> have
> > > a very patient boss.
> > >
> > > "George Schneider" <georgedschneider@xxxxxxxxxxxxxx> wrote in message
> > > news:60756ADA-DC8C-4FF6-9520-6C0CE1E76EA1@xxxxxxxxxxxxxxxx
> > > > I am going to Install our Sharepoitn Server which we are going to run
> on
> > > SQL
> > > > Server 2000. During the setup process it asks for an application
> pool.
> > > > What is a Application pool and do I need to define a new one for the
> admin
> > > > site as well as the regualr site? Also I'm instaling this in a
> workgroup
> > > > prior to deployment. Eventual I will join the server to the domain.
> How
> > > > will this effect the Sharepoint site. Also does sharepoint
> automatically
> > > get
> > > > installed as the default site?
> > >
> > >
> > >
>
>
>
.

Quantcast