MOSS Forum

Ask Question   UnAnswered
Home » Forum » MOSS       RSS Feeds

New WFE Questions

  Asked By: Jean    Date: Jun 02    Category: MOSS    Views: 739

I am about to add 2 new WFEs to my MOSS 2007 farm and I have a few of questions
I have been unable to get clear answers on. My farm currently consists of 1
WFE, 1 Index server and clustered SQL 2005 - all are Windows 2003 x64. The WFE
also houses Central Admin and SharedServices. MOSS is patched to SP1 currently.
We have installed several custom solutions.

I want to introduce 2 new WFEs, both Windows 2008 x64, and load balance the 3
WFEs using Citrix NetScaler. When all is proven to be working OK, I want to
move Central Admin and SharedServices to one of the new WFEs and remove the
original Windows 2003 WFE from the farm.

My questions are:

1. Will there be an issue introducing Windows 2008, eventually having 2 Windows
2008 WFEs and a Windows 2003 index server?

2. Is there an easy way to move SharedServices to one of the new WFEs? I would
prefer not to have to build a replica of the existing SSP if possible.

3. Will I need to do any special modifications on the new WFEs related to the
custom solutions we have installed? I am guessing any web.config or file system
mods will have to be done manually.

4. Is there anything else I should be looking out for?



4 Answers Found

Answer #1    Answered By: Cora Bradshaw     Answered On: Jun 02

1) There will be no trouble having both Windows 2008 and Windows
2003 WFEs or a Windows 2003 Index. Though I would get them all to
Windows 2008 as soon as possible just from a support standpoint. Fewer
different OSes means less work for you.

2) SharePoint stores everything in the Databases. You can add  and
remove SharePoint servers fairly easily, since they all point to the
same databases on the back end.

3) All, and I mean ALL, custom code should be introduced to your
farm via Solutions. All of it. If you use Solutions then you don't have
to do anything when you add new servers. The Solutions are stored in the
ConfigDB and they're pushed out to new servers automatically. If your
custom code was introduced to your farm a different way, then you'll
need to reproduce that on every new server you introduce.

4) Spence Harbar has a great blog post on how to move Central
Admin. There's really nothing to do it.

What you're trying to do might sound scary, but it's not bad. You'll be

Answer #2    Answered By: Shushma Zariwala     Answered On: Jun 02

I am still a bit confused on the SharedServices, though. Does that move with
Central Admin? If I look at the properties of my SSP I see the SSP
Administration Site URL of http://oldserver:port#/ssp/admin and there is no way
I can find to change that.

Answer #3    Answered By: Bahadur Kotoky     Answered On: Jun 02

It's a web app, just like everything else. If you stand up another WFE
and add  the correct AAMs you should be able to hit it on the new WFE.
Every SharePoint server in a farm serves the same content. You can't
serve one web app on one WFE and another web app on another. As long as
the AAMs are in place you should be fine.

Answer #4    Answered By: Jeremey Avery     Answered On: Jun 02

A couple of additional comments:

1) Though mixing Windows 2003 and 2008 is fully supported, as Todd
said you will want to move to all 2008 ASAP. One of the reasons he
didn't include is for load balancing purposes - if your WFEs don't all
perform at the same level, depending on the specifics of your load
balancer you can sometimes introduce instability due to overloading one
of the lower performing WFEs.

2) In your specific SSP case you are currently not going through
your load balancer for this web app - I'd suggest you do when making the
AAM changes.

Didn't find what you were looking for? Find more on New WFE Questions Or get search suggestion and latest updates.