Schuyler Kuhl
asked on
Next step after migration fails to complete due to hardware failure
Greetings,
I just received a new small business server and started the migration from my existing win 2003 small business server using the answer file.
The new server had a hardware issue and the installation didn't complete properly. For example I can see all my users in the AD Users and Computers but the main admin console shows no users and gives an error such as "this compnent is not configured properly".
Anyway there is a technicial scheduled to repair the new server today. So my question is what is my next step. I see in my original server that the new server name is shown in at least one place.
I'd like to use my original answer file and just start over again but I am sure it won't work if I don't remove the references to the new server name in the original server. Or at least I assume it won't work.
Can anyone advise me what is the best course of action assuming the hardware issues are resolved?
Thanks very much.
Sky
I just received a new small business server and started the migration from my existing win 2003 small business server using the answer file.
The new server had a hardware issue and the installation didn't complete properly. For example I can see all my users in the AD Users and Computers but the main admin console shows no users and gives an error such as "this compnent is not configured properly".
Anyway there is a technicial scheduled to repair the new server today. So my question is what is my next step. I see in my original server that the new server name is shown in at least one place.
I'd like to use my original answer file and just start over again but I am sure it won't work if I don't remove the references to the new server name in the original server. Or at least I assume it won't work.
Can anyone advise me what is the best course of action assuming the hardware issues are resolved?
Thanks very much.
Sky
ASKER
I haven't exceeded the 21 days. I was thinking that I could continue the installation but I am not sure how to do so.
The server starts into windows. So I am unsure how to continue the installation. Would I boot to the optical media again?
The hardware error was on the new server so the original server is still functioning properly, but I am worried about the 21 day issue.
Best regards and thank you.
Sky
The server starts into windows. So I am unsure how to continue the installation. Would I boot to the optical media again?
The hardware error was on the new server so the original server is still functioning properly, but I am worried about the 21 day issue.
Best regards and thank you.
Sky
ASKER
In Active Directory Users and Computers on the original server the new server is listed in "Domain Controllers". So if I try to delete it I have to decide one of three ways to delete it.
The repaired new server is in a state in which I will have to start with the Operating System cd to proceed with it.
Sky
The repaired new server is in a state in which I will have to start with the Operating System cd to proceed with it.
Sky
Still don't know enough to advise. If the NEW server went off line becuase the NIC failed and the OS on the NEW server has just been idling for a few days, it may just pick right back up where you left off. If the NEW server had a catastrophic failure rendering the OS useless, you will have to restore the source server and start again.
ASKER
Sorry.
During the migration the new server developed a hardware issue relating to a RAM error but which was eventually resolved with a new motherboard and backplane.
I did not realize this initially and I just restarted the new server and it started into windows normally but when I looked in the small business console it showed no users and gave a message such as "this component isn't configured properly".
When I looked in the original server I found that in active directory users and computers the new server name was listed in "Domain Controllers".
It took me a few days with Dell to get the hardware issue resolved and that is now done but the state of the new server is now that if you let it boot into windows it starts into "system recovery options". So I believe I will have to start again with the OS cd on that machine.
My question was originally how to proceed from here? Should I use the original answer file after removing the new server name from active directory in the old server. Now I am thinking I should create a new answer file with a new "new" server name and start from there.
Does this make it clearer?
Thanks and best regards,
Sky
During the migration the new server developed a hardware issue relating to a RAM error but which was eventually resolved with a new motherboard and backplane.
I did not realize this initially and I just restarted the new server and it started into windows normally but when I looked in the small business console it showed no users and gave a message such as "this component isn't configured properly".
When I looked in the original server I found that in active directory users and computers the new server name was listed in "Domain Controllers".
It took me a few days with Dell to get the hardware issue resolved and that is now done but the state of the new server is now that if you let it boot into windows it starts into "system recovery options". So I believe I will have to start again with the OS cd on that machine.
My question was originally how to proceed from here? Should I use the original answer file after removing the new server name from active directory in the old server. Now I am thinking I should create a new answer file with a new "new" server name and start from there.
Does this make it clearer?
Thanks and best regards,
Sky
ASKER
I decided to do the migration manually.
Thank you.
Thank you.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Is it possible that the repair will leave the server in the same condition it was just before the failure? If so, and time permits, you may be able to continue from where the new SBS went "off line", or whatever it did.