Re: Front End WSS3.0 Server
- From: AJ <andyjones99@xxxxxxxxxxxxx>
- Date: Mon, 4 Feb 2008 15:59:18 -0800 (PST)
On 26 Jan, 16:09, "callahan" <cacalla...@xxxxxxxxxxxxxxxxxxx> wrote:
That's cool AJ. I'm glad that someone got to help you in time.
AAM is a very important part of WSS, and pretty poorly documented.
In brief:
WSS only listens to addresses for web applications that are in AAM. The
default address is also used as the network load balancing address. When
you make a web application, it uses the default zone in AAM for that URL.
That default address is also the one search uses by default. Search (or
more specifically the indexer or gatherer service) cannot authenticate using
anything but Windows Authentication, and prefers NTLM.
Web applications can have five URLs associated with it, but it's default is
already it's real address when it was created, so you really only have four
to play with.
If you want a web application to be accessed, say be people outside the
office, by a different URL; make sure DNS is set up for it, then add that
URL manually as one of the public URL zones for the web application.
Another use for zones for a web application is when you extend a web app.
WSS indicates the address of an extended web app as a zone of the original
web app that was extended. Extended web apps are really only additional IIS
Web Sites that point to the same content database(s) of an existing web app.
Because it doesn't have its own content, WSS considers it an alternate way
to access the same data, and therefore considers it a zone of the original
web app, not its own, full blown, web app.
When you add a second WFE to a server farm, WSS assumes that it will be
network load balanced, and doesn't add its address to the AAM. That's why
you can't get to it directly. It assumes that you are going to set the
network load balance URL of the web apps (which ends up being the default
address) to the load balanced address, making it unnecessary to have a
specific address for the second guy. That's why people have a problem with
accessing their second WFE server directly-- the process of WFE's assumes
that second guy is backup and never to be accessed directly anyway. To get
to him, you have to add him.
In your case, you are going to add the new guy and decomission the old guy,
meaning you need to at least change the URL for the Central Administration
site to the new server (you did set it up to host CA, right?).Test it to
make sure there are no typos. Then after removing the original server from
the farm, it should use your new WFE as the default addy (although I have
had to do it manually myself before) in AAM. If not, change it yourself..
Personally, I think you are in the right newsgroup. This is about WSS
right? And this is the WSS newsgroup, natch.
But that's just my opinion. ; )
HTH,
-callahan
author: "Mastering Windows SharePoint Services 3.0"
"AJ" <andyjone...@xxxxxxxxxxxxx> wrote in message
news:bb25928f-fa88-4e72-bbba-fd1937fe62c5@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
On 26 Jan, 05:19, "callahan" <cacalla...@xxxxxxxxxxxxxxxxxxx> wrote:
AJ,
Let me see if I've got this right (and I am assuming this is the correct
newsgroup for a WSS 3.0 question), you had WSS 3.0 running fine on a
server.
You now want to replace the server hardware with another server, right?
That server is a front end server in a server farm.
I am assuming that it is the only front end server you have, correct? Is
it
still running now? If it is then what you can do is simply install the OS,
set up the prerequisites for WSS 3.0 (you probably already know that),
then
install WSS 3.0 (with SP1 preferrably) on the new server. During the
install, choose the WFE option. Then during configuration choose, add to
existing server farm (as opposed to creating a new one). It will ask you
if
you want Central Administration to be on that server, since it will be the
primary server soon, choose yes. Go through the rest of the configuration
as you should.
After that server is up and running, you can decomission the first server.
You may have to tweak Alternate Access Mapping to point to your second
server, if removing the first server does not change it on its own. Then
all should be well.
Basically you are adding a new server to the front ends for WSS, and then
removing an old one after the new one is up.
If I am wrong about your scenario, I apologize.
By the way, most of us are on here as volunteers, which means you need to
give us more than a day to respond to you, as some of us have lives and
well
as jobs. ; )
-callahan<galvin.p...@xxxxxxxxx> wrote in message
news:103d5643-01ea-4d79-996f-54ff0d25d922@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
On Jan 25, 7:15 pm, AJ <andyjone...@xxxxxxxxxxxxx> wrote:
Hello All
Second attempt at trying to get some help!!!
I want to replace my existing FE WSS3.0 server with new hardware. I
have a complete farm backup. What is the best way to go about doing
this?
Can I create a new fresh server and restore the backup directly to it.
What parts of the farm backup do I need to restore to the new FE
server? Does the new server have to have the same server name?
Pretty desperate for advice now.
Thanks
AJ
I think this is not the best group for this question. I'd post to the
admin group.
If I had to do this, I would install sharepoint onto the new machine
and during installation, tell it to join to the existing farm. Then,
decommision the older box.
But really, post this to the right group and get someone that knows
this better than me.
--Paul Galvin, Conchango
RSS @http://feeds.feedburner.com/PaulGalvinsSharepointSpace
Web site @http://paulgalvin.spaces.live.com-Hide quoted text -
- Show quoted text -
You are right Callahan, and this is what I have done. I appear to of
also picked up the wrong newsgroup which doesn't help matters!
So hopefully if I decomission the existing server all will work
becuaase at the moment it doesn't. I don't really understand AAM and I
think this is where my problem is at the moment.?
I will have a second fresh look at it this morning. Thanks for your
help it is much appreciated. I left the posting a bit late as the
planned outage was for this weekend hence needing a quick answer
Thanks
AJ- Hide quoted text -
- Show quoted text -
Thanks Callahan for your detailed posting very good stuff.
I got it all working in the end by making a change in AAM.
I actually thought I was in the right group too so I'll ignore the
comments of the other poster.
Thanks
AJ
.
- Prev by Date: Vista, Office 2007 and SharePoint 2.0
- Next by Date: Re: EditForm.aspx only shows Name field
- Previous by thread: Vista, Office 2007 and SharePoint 2.0
- Next by thread: event ID 7023
- Index(es):
Relevant Pages
|
