• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 219
  • Last Modified:

upgrading server

I am planing to upgrade my windows 2003 sever (Domain controller)
old server is IBM Infinity 5100 to HP Proliant DL 380
In my old system all the users created exchange also integrated with this

I have taken the backup of "System State"

before starting with new server what are the main points to be consider and does it effect my exchange server?

please give the the solution

Thanks

0
alfadhel
Asked:
alfadhel
  • 5
  • 4
1 Solution
 
SteveH_UKCommented:
Can you clarify the role of your existing server, please?

Is it your only domain controller, or was it your first created domain controller?

Is Exchange installed on this computer or on another computer?
0
 
alfadhelAuthor Commented:
This is only domain controller
exchange installed on other computer

0
 
SteveH_UKCommented:
In that case,

1.  Configure the new server
2.  DCPROMO it as a new domain controller
3.  Transfer all FSMO roles to the new DC
4.  Make sure new DC is a global catalog
5.  Configure time sync on the new DC (NET TIME /SETSNTP ...)
6.  Keep the old server in the domain for a few days but powered off
7.  If everything is working, turn the old DC on, then...
8.  DCPROMO demote it
9.  Change computer so it is not a domain member
10. Delete computer from Active Directory Users & Computers
11. Review AD Sites etc. to check its gone properly


Also, I recommend that you get a second DC permanently.

0
Creating Active Directory Users from a Text File

If your organization has a need to mass-create AD user accounts, watch this video to see how its done without the need for scripting or other unnecessary complexities.

 
SteveH_UKCommented:
Remember to check event logs throughout.
0
 
alfadhelAuthor Commented:
Ok Thanks
but i am going to give same computer name as old server has
and also same domain name, if I keep old server in the network it would  be conflict with new one

0
 
alfadhelAuthor Commented:
i will be back with in 15 min and i will reply u r answer

thnaks
0
 
SteveH_UKCommented:
You can't do what you suggest unless you do a disaster recovery from a complete backup, and doing this to dissimilar hardware is a particularly difficult and fraught task.

Use a different server name, please, or you are only making life really, really hard for yourself.  It is possible to rename the server later, but again I would not recommend this approach.  You can read how here:

http://technet2.microsoft.com/windowsserver/en/library/aad1169a-f0d2-47d5-b0ea-989081ce62be1033.mspx?mfr=true

As you can see, it basically means setting up your new DC, renaming your old DC, transferring roles back to the old DC, renaming the new DC, and then transferring roles back to the new DC.

You have to use the same domain name as you are transferring the role of domain controller.
0
 
alfadhelAuthor Commented:
ok i will try with different sever name

and most probably i will start this after one week  i like to continue with this same question and with you only i ll keep open this question for one week more!

Thanks
will be continue.......

0
 
SteveH_UKCommented:
No problem
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Get your problem seen by more experts

Be seen. Boost your question’s priority for more expert views and faster solutions

  • 5
  • 4
Tackle projects and never again get stuck behind a technical roadblock.
Join Now