Die-Tech
asked on
Replacing Win2k Server domain question
Hello All,
I have a network running in mixed mode and I'm getting ready to upgrade one of our main Windows 2000 servers (member server).
The servers name is FSHIFT and it's ip address is 10.10.10.243
I have already built and configured the new server.
Can I do the following...
Remove the current server from the domain, shut it down.
Start up the new server with the same name and ip address, add it to the domain so I can test to see if the new server will work properly
If it does, I'm good.... if not I will need to remove the new server from the domain, shut it down and bring the original server back up and re-join it to the domain.
Is this going to be a problem?
Do I need to remove and re-add the servers to the domain? (I'm pretty sure I do... even if they have the same name)
TIA!
I have a network running in mixed mode and I'm getting ready to upgrade one of our main Windows 2000 servers (member server).
The servers name is FSHIFT and it's ip address is 10.10.10.243
I have already built and configured the new server.
Can I do the following...
Remove the current server from the domain, shut it down.
Start up the new server with the same name and ip address, add it to the domain so I can test to see if the new server will work properly
If it does, I'm good.... if not I will need to remove the new server from the domain, shut it down and bring the original server back up and re-join it to the domain.
Is this going to be a problem?
Do I need to remove and re-add the servers to the domain? (I'm pretty sure I do... even if they have the same name)
TIA!
i would just unplug the network cable from the older server and plug it into the newer server to check it out so incase it doesnt work you can just switch the cable over
ASKER
I've done that already... but it's not a good test for me.
I'm having a problem with the SQL instances starting.... our MRP software vendor said I need to join the new server to the domain and then give the service a domain account to logon with.
I'm afraid if I join the new server to the domain and it doesn't work, I may have problems joining the original server back into the domain.
Does that make any sense?
Thanks,
Dan
I'm having a problem with the SQL instances starting.... our MRP software vendor said I need to join the new server to the domain and then give the service a domain account to logon with.
I'm afraid if I join the new server to the domain and it doesn't work, I may have problems joining the original server back into the domain.
Does that make any sense?
Thanks,
Dan
just dont remove the old server from the domain. why would you do that before you test the other one anyway? if your worried about the name of the server the dns will still resolve it to the old ip address anyways.
ASKER
How does the new server connect to the domain? Right now it's just part of it's own workgroup.
The vendor is telling me to join the new server to the domain and then change the FSTI service to use a domain account when it starts.
The vendor is telling me to join the new server to the domain and then change the FSTI service to use a domain account when it starts.
that is correct, just unplug the old server, plug in new, add to domain, reboot. login
then go to start>settings>controllpan
then find the fsti service and go to properties> click the Logon tab
choose "this account" and add the domain account you want to use for the login
then go to start>settings>controllpan
then find the fsti service and go to properties> click the Logon tab
choose "this account" and add the domain account you want to use for the login
then restart that service
ASKER
OK.... Let's say I do all that and the FSTI service still doesn't work properly...
I shut down the new server and unplug it from the network.
Plug the original server back into the network, will it be able to connect to the domain after I've joined the new server to the domain using the original server's machine account? Or do I have to re-join the original server back into the domain?
Sorry if this sounds so confusing... if this wasn't a production evironment I'd already have tried it.... but since it is I have to have a plan "B"
I shut down the new server and unplug it from the network.
Plug the original server back into the network, will it be able to connect to the domain after I've joined the new server to the domain using the original server's machine account? Or do I have to re-join the original server back into the domain?
Sorry if this sounds so confusing... if this wasn't a production evironment I'd already have tried it.... but since it is I have to have a plan "B"
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Ok... i get what you are saying now.
I was going to put the new server in place with the same name and same ip address as the old server so I could test it completely.
The vendor's software is installed with the server's name in mind.
Their suggestion was to put the new server in using the old server's name so it would be transparent to the user.
They were also saying, if I rename the server I would need to reinstall the client software on each workstation.
I tried something like this a week ago... I left the old server (FSHIFT) online, loaded all my server software (SQL, MRP, etc.) on the new server (which was named FSHIFT at the time), renamed the server to FSHIFT2 and brought it online with a different ip address and joined it to the domain.
Many of the MRP/SQL services wouldn't start on the new server... then after shutting down the new server many of the clients (scanners) couldn't connect to the old server anymore (connection timeouts). After some research I found the WINS database had changed the ip address of FSHIFT from the old server's ip address to the new server's ip address.
I was going to put the new server in place with the same name and same ip address as the old server so I could test it completely.
The vendor's software is installed with the server's name in mind.
Their suggestion was to put the new server in using the old server's name so it would be transparent to the user.
They were also saying, if I rename the server I would need to reinstall the client software on each workstation.
I tried something like this a week ago... I left the old server (FSHIFT) online, loaded all my server software (SQL, MRP, etc.) on the new server (which was named FSHIFT at the time), renamed the server to FSHIFT2 and brought it online with a different ip address and joined it to the domain.
Many of the MRP/SQL services wouldn't start on the new server... then after shutting down the new server many of the clients (scanners) couldn't connect to the old server anymore (connection timeouts). After some research I found the WINS database had changed the ip address of FSHIFT from the old server's ip address to the new server's ip address.