Go Premium for a chance to win a PS4. Enter to Win

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

should we create a new domain or transfer the existing domain..........?

Hi there, I would be very grateful if I could have some advice on this as we are in the middle of two scenarios and we are unsure which one to take!!

Within this school we have two old clone servers running Windows 2003 server, one a domain controller and the other a secondary (called HW and HW1). The two clone servers are about 4 years old and we have never been comfortable with the server hardware and we have had issues where the HW server has gone down apparently due to dns and hardware related.  As a result there is little confidence in the current Active directory/dns.  There are appx 120 users.

In addition to these two servers there are various other member servers plus 3 clustered terminal servers.  Terminal services is mainly used on this domain and within group policy there is a ts lockdown policy which restricts all ts users.  This is fine.  

We are going to replace the two old clone servers with fresh new HP dl380 servers but we are unsure whether to transfer the existing active directory across and making one of the two new servers a global catalogue and then demote the old servers or create a new domain from scratch.  I know if we did it from a afresh we would not inherit any issues but we would create alot more work for ourselves by then having to add all the users in again and then re-create all the policies.  

Is there a way for us to transfer what we have but to make sure that what does come across will work without any inherited dns problems..??  Could it be that it was the hardware that cuased these issues and by simply moving at all over to new equipment it will get resolved anyway..???

The main problems were dns and authenticating, any advice here would be gratefully received.

Thanks

Phil


0
philipgecko
Asked:
philipgecko
1 Solution
 
NJComputerNetworksCommented:
I would attempt to fix the domain now.  If you can fix the domain and get things working without errors, then there will be no need to recreate the domain from scratch.

1) make sure that your DNS servers are ACTIVE Directory INTEGRATED...  (go into the DNS Console...  Highlight - one a t a time- your Forward lookup zones...  Click PRoPERTIES from the drop down box.  On the General tab, make sure that the type = Active directory integrated.

2) All clients and servers should be pointed to internal DNS servers ONLY.  for example:

DNSServer1 Settings
Server NAme:  DNSServer1
IP: 10.10.10.5
Subnet: 255.255.255.0
Gateway: 10.10.10.1
DNS1: 10.10.10.5 or <127.0.0.1>     <--- Server must point to itself for DNS
DNS2: 10.10.10.6

DNSServer2 Settings
Server Name:   DNSServer2
IP:  10.10.10.6
Subnet:  255.255.255.0
Gateway:  10.10.10.1
DNS1:  10.10.10.5
DNS 2: 10.10.10.6

Clients Settings
Client Name:  Workstation1
IP:  10.10.10.25
Subnet:  255.255.255.0
Gateway:  10.10.10.1
DNS1:  10.10.10.5
DNS2:  10.10.10.6

0

Featured Post

Windows Server 2016: All you need to know

Learn about Hyper-V features that increase functionality and usability of Microsoft Windows Server 2016. Also, throughout this eBook, you’ll find some basic PowerShell examples that will help you leverage the scripts in your environments!

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