[Webinar] Streamline your web hosting managementRegister Today

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 150
  • Last Modified:

Adding a second server to our network

We have Windows Server 2003 (5 CALs) running on our entry-level server system.  We just purchased a new mid-grade server which will become our primary server.  We're going to wipe the OS from the old system and put it on the new one.  But we want to use the old system as a backup server.  In what ways can we do this so that if the primary system goes down we can maintain the network by switching control to the secondary system?
0
psk1
Asked:
psk1
  • 4
  • 3
  • 2
  • +1
3 Solutions
 
2hypeCommented:
Windows server 2003 does not have a primary and backup Domain controllers, they just have Domain Controllers.  All are equal.  

Just install server 2003 on the new server, promote it to a DC (select the option there is already a DC in the network) and active directory will replicate between the two.

If you want to install server 2003 on the new computer and remove the old computer from the domain you will do the above.  Before you remove the domain controller you will have to transfer the FSMO Roles to the new server.

0
 
psk1Author Commented:
2hype,

So the Windows Server 2003 OS will be installed on both systems.  Re: licensing, we can do this with the single copy of Windows Server 2003 we have, right?
0
 
2hypeCommented:
You will have to purchase a copy of server 2003 for the new server.  You will not have to purchase any CAL's because you already purchased them to access the other server.
0
[Webinar] Kill tickets & tabs using PowerShell

Are you tired of cycling through the same browser tabs everyday to close the same repetitive tickets? In this webinar JumpCloud will show how you can leverage RESTful APIs to build your own PowerShell modules to kill tickets & tabs using the PowerShell command Invoke-RestMethod.

 
joedoe58Commented:
This is only possible if you have something else than SBS. If you have SBS 2003 you can not have two SBS DC's in the same domain.
0
 
psk1Author Commented:
Ok.  So I'll have 2 DC's, and AD will replicate between the two, so if one goes down I can use the other and what will that give me?  All users will still be there, what about user settings, etc?
0
 
psk1Author Commented:
It's not SBS, it's Standard.
0
 
joedoe58Commented:
User settings are replicated with AD. What you will not have is applications and files. To be able to have redundancy for those things you need something like cluster configs.
0
 
2hypeCommented:
All user acounts and settings will be replicated between the servers.  Therefore if one goes down that other will authenticate the clients.
0
 
2hypeCommented:
Any Shared folders will not be availible if they are shared from one of the servers that goes down though
0
 
mikeleebrlaCommented:
if you want redundancy make sure that BOTH servers have a copy of the global catalog, are both DNS servers, are both DHCP servers.  If only one of these DCs has a copy of the global catalog, is a DNS server, and dhcp server and it goes down you would be dead in the water.  The second sever(even though its a DC) won't do you any good.
0

Featured Post

Free Tool: ZipGrep

ZipGrep is a utility that can list and search zip (.war, .ear, .jar, etc) archives for text patterns, without the need to extract the archive's contents.

One of a set of tools we're offering as a way to say thank you for being a part of the community.

  • 4
  • 3
  • 2
  • +1
Tackle projects and never again get stuck behind a technical roadblock.
Join Now