Advice on KB282227 & Dismantling Cluster

All
2 x Win2k3 Active/Active Clusters act as File and Home Servers
They have a physical computer names of CLUS1 and CLUS2.

We have 2 applications that rely on the Physical computer names and IP
addresses of the Servers.

They have Network Names and IP's that users use to access these boxes by its
virtual names.

I want to destroy the clusters and turn them into stand alone servers, so
one acts as Home and the other acts as a File Server. (Member Servers
effectively).

If I follow KB282227, how can I be sure users can access their home and file
shares with the least amount of admin effort? For example do I need to create
DNS Alias for the virtual names and point them to the physical IP addresses
of the Servers?

Because we have applications that are depending on the physical IP and
Computer names changing these are not really an option.

Any advice?
Greetings

> All
> 2 x Win2k3 Active/Active Clusters act as File and Home Servers
> They have a physical computer names of CLUS1 and CLUS2.
>
> We have 2 applications that rely on the Physical computer names and IP
> addresses of the Servers.

can you not point these applications to the NetBIOS name from the clustered
Network name resource as well as the IP address of the clustered IP address
resource ?

You are giving up High Availability because of the incompatibility of 2
applications ?
what applications are these ?

rgds,
Edwin.

>
> They have Network Names and IP's that users use to access these boxes by
its
> virtual names.
>
> I want to destroy the clusters and turn them into stand alone servers, so
> one acts as Home and the other acts as a File Server. (Member Servers
> effectively).
>
> If I follow KB282227, how can I be sure users can access their home and
file
> shares with the least amount of admin effort? For example do I need to
create
> DNS Alias for the virtual names and point them to the physical IP
addresses
> of the Servers?
>
> Because we have applications that are depending on the physical IP and
> Computer names changing these are not really an option.
>
> Any advice?
> Greetings

Edwin
Political decisions to move away from clusters, after our standard member
servers showed more uptime than the clusters.

So that is why they are being dismantled.

Applications are configured using the IP Address and Names of the "Physical"
Servers. This is fine, and we are happy to keep this.

S.

"Edwin vMierlo [MVP]" wrote:

>
> > All
> > 2 x Win2k3 Active/Active Clusters act as File and Home Servers
> > They have a physical computer names of CLUS1 and CLUS2.
> >
> > We have 2 applications that rely on the Physical computer names and IP
> > addresses of the Servers.
>
> can you not point these applications to the NetBIOS name from the clustered
> Network name resource as well as the IP address of the clustered IP address
> resource ?
>
> You are giving up High Availability because of the incompatibility of 2
> applications ?
> what applications are these ?
>
> rgds,
> Edwin.
>
> >
> > They have Network Names and IP's that users use to access these boxes by
> its
> > virtual names.
> >
> > I want to destroy the clusters and turn them into stand alone servers, so
> > one acts as Home and the other acts as a File Server. (Member Servers
> > effectively).
> >
> > If I follow KB282227, how can I be sure users can access their home and
> file
> > shares with the least amount of admin effort? For example do I need to
> create
> > DNS Alias for the virtual names and point them to the physical IP
> addresses
> > of the Servers?
> >
> > Because we have applications that are depending on the physical IP and
> > Computer names changing these are not really an option.
> >
> > Any advice?
> > Greetings
>
>
>