replacing the server that host the CA

[terry712]

i want to replace this server with a two server netware 6 cluster

netware 6 sp3 server with edir 8.7. server hosts the slpda and CA.
the DA is distributed to most sites via dhcp but there are a large amount that are statically configured (either through misconfiguration , politics or whatever).
the name of the server apears in lots of scripts and due to a citrix app - there are a number of machines that this name is incorporated into a hard mapping )this is easily
modified in a find and replace registry exercise on the citrix servers.

concerns

for all drive mappings to be ok - the physical server name would have to become a virtual name. (scared this may cause future issues as if you get any probs how to you know
if it's a link to the old ncp server or the new virtual)

if the drive mapping name is changed some pc's may have issues where word etc likes to keep unc paths

would prefer to keep the slpda ip address the same, was going to make this a clustered resource but this would mean the address of original server/replacement server would need to change

any thoughts

in changing the server with CA - is it only changing ip address that causes hassle or does the name cause same concerns

is it better to keep the CA off the cluster and bit the bullet and move it to a totally new serevr

 

[terry712]

just read lots of boring tids on this
is it ok just to do a backup and then rstore it to another server in the tree that has certificate server installed on it
verify with pkidiag
then remove orig server from tree
clean up and get rid of all refs
bring back as a virtual ncp

and exposure to this - thoughts feelings
blah bl;ah

 

[Provogeek]

Messing around with the CA as we talked about before is BAD BAD BAD BAD. But it can be done if your willing to put in the work.

This TID is pretty much the same procedure I follow when I have to do somthing like this;

http://support.novell.com/cgi-bin/search/searchtid.cgi?/10050254.htm

To answer some of your other questions;

for all drive mappings to be ok - the physical server name would have to become a virtual name.
The virtual name would need a DNS host entry so a workstation can resolve it to an IP address. It is better to just make your drive mappings go to an IP address in some cases. You do not want to involve the server name in a cluster enabled volume, or a failover will ... fail

if the drive mapping name is changed some pc's may have issues where word etc likes to keep unc paths
This is a user training issue you will have to address. I my self have not seen Word retain the UNC path to a document on the network unless the UNC path was used to access the document. You will need to train your users for the new location name and to use their drive mapping to get to their documents.

would prefer to keep the slpda ip address the same, was going to make this a clustered resource but this would mean the address of original server/replacement server would need to change
I don't think you can cluster enable the slpda, but I also have never tried it.

in changing the server with CA - is it only changing ip address that causes hassle or does the name cause same concerns
The concern is with both, changing the name and the IP address of the CA will break certificate services.

is it better to keep the CA off the cluster and bit the bullet and move it to a totally new serevr
It can be on a server that is a node in a cluster, it just can't be cluster enabled.

is it ok just to do a backup and then rstore it to another server in the tree that has certificate server installed on it
You can, but the certificate server will not work properly.



=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+
Brent Schmidt Certified nut case
Senior Network Engineer

http://www.kiscc.com

 

[terry712]

cheers
slpda does work on cluster - tried it works a treat - article on it on appnote in october
dns entry is ok for the virtual server - i want to avoid ip addresses as high probability ip numbers will change in future

well as you say it willl be a learning thing