Michel
Guest
|
 Posted:
Tue Oct 26, 2004 1:17 pm Post subject:
Problems upgrading Win2k/Exch2k cluster to Win2K3/Ech2K3 |
|
|
Hi there,
We have a Win2K/Exch2k Cluster which we want to upgrade to Win2K3/Exch2K3.
As we would like to avoid moving all the mailboxes we are using
http://support.microsoft.com/default.aspx?scid=kb;en-us;842427 to upgrade.
At the moment I'm testing this in our test domain, which is hosted on an
VMware ESX server. Here I've reconstructed the Win2K3 domain controllers,
Exchange cluster and OWA server. Everything is working well, mail is coming
in and going out, no problem.
The OWA server is already running Exch2K3 Enterprise Edition and the forest
and domain prep went without problem.
I've evicted the one node, performed a clean Win2K3 install, ran windows
update, joined the cluster, and installed Exch2K3 so far so good.
The procedure has you take the System Attendant off-line, move the Exchange
group to the new Win2K3 node and there you should upgrade the Exchange
Virtual Server.
When I attempt this I get the error message: The Network Path was not found,
Facility: Win32, ID No: C0070035, Microsoft Exchange Cluster Administrator
Extension.
I searched for this error and there seem to be 2 possible problems:
- Remote Registry Service is not running (KB 290824)
- Binding order problems with the Heartbeat config (KB 258750)
The service is running and the heartbeat works fine and the IP is configured
correctly. One set of NICs is configured as Cluster Client and the other as
Cluster Heartbeat. The only thing I don't understand is the binding order:
when I look at the properties of the cluster / Network Priority, I see only
the Cluster Heartbeat there, so I can't set an order there...
Any ideas or suggestions are more then welcome.
Greetings from Holland,
Michel
|
|
Michel
Guest
|
| Posted:
Tue Oct 26, 2004 4:01 pm Post subject:
Re: Problems upgrading Win2k/Exch2k cluster to Win2K3/Ech2K3 |
|
|
Ah.... I found it.....
You have to set the binding order in Control Panel \ Network connections \
advanced \ advanced settings....
It's alive and kicking!
Michel
"Michel" <michel_wets@unspam.hotmail.com> wrote in message
news:417e0813$0$8094$4d4ebb8e@news.nl.uu.net...
| Quote: | Hi there,
We have a Win2K/Exch2k Cluster which we want to upgrade to Win2K3/Exch2K3.
As we would like to avoid moving all the mailboxes we are using
http://support.microsoft.com/default.aspx?scid=kb;en-us;842427 to upgrade.
At the moment I'm testing this in our test domain, which is hosted on an
VMware ESX server. Here I've reconstructed the Win2K3 domain controllers,
Exchange cluster and OWA server. Everything is working well, mail is
coming
in and going out, no problem.
The OWA server is already running Exch2K3 Enterprise Edition and the
forest
and domain prep went without problem.
I've evicted the one node, performed a clean Win2K3 install, ran windows
update, joined the cluster, and installed Exch2K3 so far so good.
The procedure has you take the System Attendant off-line, move the
Exchange
group to the new Win2K3 node and there you should upgrade the Exchange
Virtual Server.
When I attempt this I get the error message: The Network Path was not
found,
Facility: Win32, ID No: C0070035, Microsoft Exchange Cluster Administrator
Extension.
I searched for this error and there seem to be 2 possible problems:
- Remote Registry Service is not running (KB 290824)
- Binding order problems with the Heartbeat config (KB 258750)
The service is running and the heartbeat works fine and the IP is
configured
correctly. One set of NICs is configured as Cluster Client and the other
as
Cluster Heartbeat. The only thing I don't understand is the binding order:
when I look at the properties of the cluster / Network Priority, I see
only
the Cluster Heartbeat there, so I can't set an order there...
Any ideas or suggestions are more then welcome.
Greetings from Holland,
Michel
|
|
|
FAQ
Memberlist
Register
Profile
Log in to check your private messages
Log in